How Forge works
Forge keeps repository context, engineering decisions, plans, evidence, and proposed changes connected to one project thread. It is designed for continued work rather than disposable prompts.
Active Development · Software Engineering Environment
Forge
A local-first engineering environment for sustained work on real repositories and codebases.
Mission
Serious engineering work, kept in context.
Forge is a local-first software engineering environment for developers and maintainers doing sustained work on real repositories. It connects repository inspection, planning, implementation, review, and repair so that project context survives across tasks. The engineering goal is to coordinate supported models and tools without obscuring evidence, affected files, or approval boundaries. Its long-term direction is a dependable desktop workspace where complex codebase work remains continuous and reviewable.
Engineering colleagues
Dale, Iris, and Victor are selectable communication profiles applied across supported reasoning models. Dale is the default. They are not separate AI models, and changing colleagues does not change Forge's routing or engineering rules.
Review before change
Forge is designed to show plans, evidence, affected files, and proposed changes before consequential work is applied. User approval remains the trust boundary.
Development state
Forge is in active development. Product behavior, supported integrations, and release plans may change as the engineering workflow is tested and refined.
Long-term direction
Forge is intended to support continued engineering work across the life of a repository, preserving the decisions, evidence, and project context needed to understand what changed and why.
Project status
Active Development
The product is under active development. Public release timing has not been announced.
Current focus
What the studio is working through now.
Repository inspection and sustained project context
Planning, implementation, review, and repair workflows
Clear approval boundaries for consequential changes
Roadmap
Progress without invented dates.
Core engineering workflow
current
Integration and reliability validation
current
Public release
planned
Features
The work the product is organized to support.
Repository-aware project work
Model, tool, and task coordination
Selectable engineering-colleague communication profiles
Reviewable plans and proposed changes
Understand
Start with the repository itself: its files, structure, conventions, and the decisions already visible in the code.
Plan
Turn a goal into a reviewable sequence of work, with scope and affected areas made clear before consequential changes.
Work
Coordinate supported reasoning engines and tools while keeping the project thread connected to the implementation.
Review
Present evidence, affected files, and proposed diffs so the engineer can inspect the work instead of trusting a summary.
Verify
Run the available checks, investigate failures, and keep the validation result attached to the work that produced it.
Default engineering colleague
Dale
Calm, concise, and evidence-led. Dale prioritizes correctness, trust, simplicity, and maintainability.
Research engineer
Iris
Methodical and curious. Iris emphasizes architecture, patterns, tradeoffs, and understanding before change.
Performance engineer
Victor
Measured and practical. Victor looks for unnecessary work, profiles before optimizing, and keeps performance claims tied to evidence.
Engineering
Technical profile.
A Rust backend and Tauri 2 desktop shell host a Svelte 5 and SvelteKit interface. SQLite provides local persistence, while the installed Codex app-server is the currently verified engineering engine.
- Languages
- Rust · TypeScript
- Frameworks
- Tauri 2 · Svelte 5 · SvelteKit
- Database
- SQLite
- Platforms
- Windows
- Interfaces / Runtime
- Codex app-server · Git · Local process execution
- Packaging / Distribution
- Tauri desktop bundle
Gallery
Verified product media.
Product inquiry
Follow the work without pretending it is finished.
Contact Reed Creative Labs for product, development, or press inquiries.
Contact the Studio