Skip to content
1-PankajPublic

About

Desktop-first open-source workspace for architecture diagrams, local agent orchestration (Claude Code, Codex), and interactive 3D office collaboration.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

15 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Formative logo

Formative

A desktop workspace for project diagrams, tasks, and local agent conversations.

License: MIT Platform Build Release Status: Active Development Stack


Formative brings project work, architecture diagrams, and supported local agent tools into one open-source desktop app. It is released under the MIT License and has no Formative subscription plans or paid feature gates.

Note

Formative is in active development. The sections below describe what works today and what is still planned.

Download · Features · Agent connections · Privacy · Quick start · Contributing · Tech stack

Download

Check the Releases page for published Windows builds. The repository includes Electron Builder targets for a setup installer and portable executable; a release page is the source of truth for whether those artifacts have been built and published.

The GGUF model weights are not stored in this GitHub repository and are not included in default installer builds. In the desktop app, open Project Office and choose Choose model to add a compatible GGUF file; Formative copies it to local app data and runs it on this device. Releases can publish a separately licensed model asset when maintainers choose to provide one.

What works today

Area Available now
Projects Create a project, open a local folder, or start from a clearly labeled example. Choose a project before opening its work areas.
Canvas diagram Add, edit, move, and connect components. The diagram is saved with the project and stays under your control.
Project structure Browse a limited folder view and see what selected root files suggest about the project. This view does not inspect source code.
Architecture map Build a separate, read-only map from local source files. It follows resolvable imports, recognizes selected framework routes, and marks inferred links.
Tasks and issues Create and update project tasks. Link a task to Agent Chat to include its key, title, status, and description as context. Comments are not included.
Agent Chat Start or resume read-only conversations through local Codex CLI and Claude Code CLI installations.
Transcript review Open JSON or JSONL transcripts, or browse supported local transcript locations. Review is read-only and does not control the agent that created the file.
Project Office Open a project-scoped 3D office with a configurable coordinator and only the teammates you enable. Assign tasks, customize names and appearance, and see real Codex CLI or Claude Code CLI run activity reflected in the scene.

Project structure and architecture map

These are separate views. The Project structure scan samples up to 500 root entries, maps up to nine top-level folders, and samples up to 50 entries in each mapped folder. It checks selected files such as package.json, framework configuration, Python project files, and Docker configuration.

The Architecture map reads a bounded set of selected local source files. It can group files into modules, follow local imports across supported languages, recognize selected Next.js, Remix, SvelteKit, Nuxt, and Astro route patterns, and suggest links between API calls and routes or source references and schemas. Import links are observed in source; API and schema links are labeled as inferences.

Analysis runs locally. Formative does not execute project code, install dependencies, or upload source files. Dynamic imports, runtime behavior, generated code, and unsupported conventions may not appear. External package nodes currently come from package.json; other language ecosystems appear when imports resolve to scanned local files. File and graph limits are shown with the results.

JavaScript and TypeScript imports use a syntax parser, including scripts in Vue, Svelte, and Astro files. Python, Go, Rust, Java, C#, PHP, and Ruby imports use conservative pattern matching, so some relationships may be missed.

Opening a folder again refreshes its Project structure scan while preserving the editable canvas. Refreshing the Architecture map updates that map separately.

Agent connections

The current connections use the provider's installed command-line tools:

Provider Current behavior
Codex Uses its read-only sandbox and may run read-only checks.
Claude Code Starts in Plan mode with project reading and search. Shell commands, file editing, and project MCP tools are not enabled in this workflow.

These connections are early implementations. Packaged-app and provider-runtime verification is still in progress.

Formative checks whether the local command is installed, but does not check provider sign-in. Your prompt and relevant project context may be sent through the provider's service, and provider fees may apply. Formative does not currently coordinate multiple agents or measure token savings.

Codex desktop conversations, Claude Code desktop sessions, and running Antigravity IDE sessions are not connected. Antigravity IDE support is a priority. Connections for OpenCode, OpenClaw, Ollama, Kiro, API keys, and MCP are also planned, but are not available integrations today.

Transcript review

Formative can read and watch a selected transcript file for changes. It can discover supported local Claude Code, OpenCode, and Antigravity transcript locations. Antigravity IDE session folders are not discovered yet. The transcript is temporary, is cleared when you switch projects, and is not saved as an Agent Chat conversation. The picker currently supports JSON and JSONL files.

Project office and team

Each project has its own office team. The project coordinator is always present; specialist employees are not. Add, enable, disable, or remove teammates in Team setup. You can edit names, role titles, departments, preferred agent, skill labels, and procedural character appearance. A project can have up to 23 employees in addition to its coordinator.

Tasks can be assigned to enabled employees. Opening Agent Chat from a task selects that task and its enabled assignee. Starting a run in Agent Chat records the selected employee and task with the real provider run. Codex CLI and Claude Code CLI runs are the only supported run providers today. Runs remain read-only.

The coordinator can start a real read-only Codex CLI or Claude Code CLI conversation. It uses the selected task, or a bounded list of open project tasks, as context. Provider events update the office activity display; ambient scene behavior is decorative and does not represent agent work. Office chat is a separate, optional roleplay feature: choose a compatible GGUF file, then residents chat in character on this device. The local model receives the character name and role plus the messages in that chat; it does not receive project files, tasks, architecture, or agent-run activity. It is not a project assistant. Small models can still give generic or awkward roleplay replies. A persistent background monitor tracks provider runs and local model replies while you move around the project. Formative cannot attach to existing Codex desktop, Claude desktop, or Antigravity IDE sessions yet.

Employee skills are currently bounded labels included as descriptive run context. They are not executable skill packs, custom tool permissions, or project access rules.

The office is a view of project records, not a separate task database. Removing an employee clears that person’s task assignments. Disabling an employee leaves existing assignments visible as away, but they cannot be selected for new runs.

Privacy and provider costs

Project records are saved in Formative's local app data, with a browser-storage recovery copy. A model you choose is copied to Formative's local app data; office chat runs on-device and does not send its conversation to a model service. The local office model receives only the selected character's name and role and the messages in that character's conversation, not project data. The browser preview does not have Electron file access, so local folder scanning, transcript import, and local model installation require the desktop app.

Architecture analysis reads selected project files on your device and does not send them to Formative. Agent Chat uses the provider service associated with the selected CLI. The provider may receive your prompt and relevant project context; provider usage or subscription fees may apply. Transcript contents and file paths can be sensitive, so choose files deliberately.

Contributing

Formative is being built in public. Before making a substantial change, check the product plan and open an issue to discuss the problem and scope. See CONTRIBUTING.md for the development workflow, CODE_OF_CONDUCT.md for community expectations, and SECURITY.md for private vulnerability reports.

The project code is MIT licensed. Provider artwork and adapted third-party code have separate notices in THIRD_PARTY_NOTICES.md.

Dependencies and artwork

The previous office tile maps and third-party tile artwork have been removed. The integrated office uses procedural geometry and character textures generated by the application, with Three.js bundled as an application dependency. See THIRD_PARTY_NOTICES.md for provider artwork and adapted code notices.

Quick start

Prerequisites

Install

Install dependencies in the project folder:

npm ci

Run the desktop app

npm run desktop

This command checks the TypeScript, builds the interface, and launches Electron.

Browser development preview

npm run dev

The browser preview is for interface development. It cannot scan local folders or import transcripts.

Build Windows packages

npm run dist:installer   # Builds the NSIS setup installer (.exe)
npm run dist:portable    # Builds the standalone portable executable (.exe)
npm run dist             # Builds both packages into build-release/
npm run dist:dir         # Creates an unpacked review directory

These commands omit model weights by default, so source builds do not create a very large installer. To intentionally bundle a local model for a private or separately distributed build, put formativellm.gguf in LLM/ and set FORMATIVE_BUNDLE_LLM=1 before running a packaging command. Do not commit the model file to Git. For PowerShell:

$env:FORMATIVE_BUNDLE_LLM = "1"
npm run dist:installer

Canvas controls

Scroll to zoom, drag the canvas to pan, move nodes by dragging them, and connect components from one node handle to another. Canvas connections are user-authored diagram lines; Formative does not verify them against project code.

Tech stack

License

Formative's source code is distributed under the MIT License. See LICENSE for details. Third-party artwork and adapted code are listed in THIRD_PARTY_NOTICES.md.

About

Desktop-first open-source workspace for architecture diagrams, local agent orchestration (Claude Code, Codex), and interactive 3D office collaboration.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages