Default engineering colleague
Dale
Calm, concise, and evidence-led. Dale prioritizes correctness, trust, simplicity, and maintainability.
Active Development · Flagship Software
Serious engineering work, kept in context.
Forge is a software-engineering environment for sustained work on real repositories. It brings project understanding, planning, implementation, review, and validation into one continuous working thread.
Product media
Forge is in active development. Approved interface captures will be added as the product approaches its public preview.
What Forge is
Forge is not positioned as a disposable prompt window or a model picker. The product is organized around one continuing project conversation where plans, evidence, files, proposed changes, approvals, and results remain connected.
Why it exists
Software work stretches across architecture decisions, defects, diffs, tests, and repeated review. Forge is being built to preserve that history, reduce repeated setup, and make consequential actions visible before they are applied.
Core workflow
Start with the repository itself: its files, structure, conventions, and the decisions already visible in the code.
Turn a goal into a reviewable sequence of work, with scope and affected areas made clear before consequential changes.
Coordinate supported reasoning engines and tools while keeping the project thread connected to the implementation.
Present evidence, affected files, and proposed diffs so the engineer can inspect the work instead of trusting a summary.
Run the available checks, investigate failures, and keep the validation result attached to the work that produced it.
Forge can discover a local project, inspect files, preserve per-project context, and present proposed changes through review and approval surfaces. The design favors cited files and visible diffs over unsupported summaries.
Forge coordinates supported reasoning engines and tools inside a consistent project workspace. Third-party models remain third-party services, and data sent to a configured cloud provider is governed by that provider. Local project state and credentials are handled on the device; consequential file changes remain subject to the user's approval and configured autonomy.
Engineering colleagues
Dale, Iris, and Victor are selectable engineering personalities applied across supported models. They shape communication and working approach; they are not separate foundational models. Dale is the default.
Default engineering colleague
Calm, concise, and evidence-led. Dale prioritizes correctness, trust, simplicity, and maintainability.
Research engineer
Methodical and curious. Iris emphasizes architecture, patterns, tradeoffs, and understanding before change.
Performance engineer
Measured and practical. Victor looks for unnecessary work, profiles before optimizing, and keeps performance claims tied to evidence.
Current development state
Project and folder discovery, a continuous working thread, streaming responses, file inspection, review and approval cards, local project state, and the engineering-colleague system are represented in the current application.
The end-to-end planning, execution, review, provider, privacy, and settings experience is being connected and hardened as one reliable workflow.
Forge is not currently released, downloadable, or purchasable. Public preview details have not been announced.
Intended audience
Development inquiry
Forge remains in active development. Contact the studio for product or press inquiries.
Contact the Studio