Tavronus Forge · autonomous engineering
The engineer
that never
clocks out.
Give VULCAN a task. It plans the work, waits for your approval, executes, recovers from failures, verifies every change, and hands back a reviewed diff — you stay the last gate before anything ships.
Safe browser workspace. No external repository is modified.
Approval before execution
You choose what runs.
Changes verified by tests
Every change is checked.
Safe workspace boundaries
VULCAN stays within defined limits.
Full task history
Follow the work from plan to diff.
No signup · safe browser workspace · instant to try
Don't take our word.
Cast something.
Describe an engineering task and watch VULCAN turn it into a guided plan, execution, verification, and review. Open the full workspace when you're ready to run the complete lifecycle.
Describe an engineering task below and watch VULCAN work through it.
Runs locally. No repository connection required.
What the Forge is
Not a copilot. A colleague under contract.
Six commitments define how VULCAN works. Five run live in this browser experience today. The sixth is the local and self-hosted architecture we're building toward — and it's labeled clearly, not blended in.
01 / 06
Available in browserTask ownership, not autocomplete
You hand VULCAN a complete task — migrate this, fix that — and judge the finished diff. No keystroke babysitting.
Task
Migrate billing
Acceptance
Tests green
Diff reviewed
Final gate
Awaiting approval
VULCAN · how a task moves
Heat is state. Watch it move.
Every task carries a temperature. It waits in ash, burns through planning and execution, then cools into reviewed steel. Human approval opens the Forge; human judgment closes it.
Add rate limiting to the API
Cast with a mode and explicit permissions. VULCAN reads project memory before it reads a single file.
Migrate billing to usage pricing
Plans first, then your approval. It writes and tests in isolation; a failing test triggers a visible replan, not silence.
Fix flaky auth session tests
Green suite, verification report, self-review, annotated diff — cooled and waiting on your final call.
- 01 · Queued
Add rate limiting to the API
Cast with a mode and explicit permissions. VULCAN reads project memory before it reads a single file.
Plan approval
You open the Forge
- 02 · Forging
Migrate billing to usage pricing
Plans first, then your approval. It writes and tests in isolation; a failing test triggers a visible replan, not silence.
Final review
You close it
- 03 · Tempered
Fix flaky auth session tests
Green suite, verification report, self-review, annotated diff — cooled and waiting on your final call.
Philosophy, not feature war
What the Forge is designed around
Editor agents are good and getting better — we use them. This table compares product philosophy, not present-day feature checklists.
| Category | Tavronus Forge direction | Typical editor-agent experience |
|---|---|---|
| Primary interaction | Complete task ownership | Conversation or editor assistance |
| Task lifecycle | Queued → Forging → Tempered, always visible | Tool-dependent |
| Plan approval | Explicit checkpoint before execution | Varies |
| Failure handling | Visible failure → diagnosis → replan history | Often buried in conversation |
| Memory | Inspectable, editable ledger | Often file- or rule-based |
| Review output | Verification report + self-review + diff | Usually chat plus diff |
| Execution location | Planned local / self-hosted runner options | Vendor-dependent |
| Model choice | Task-oriented modes, routed | Usually direct model picking |
"Direction" means exactly that: parts are prototype-only today. The roadmap says which.
Designed for
People who'd rather judge work than watch it.
No customers yet, so no testimonials — these are the working scenarios the product is built around.
The solo developer
clearing a refactor backlog that never survives contact with the sprint.
The startup team
preparing a migration nobody wants to own, with the plan reviewed before a line changes.
The maintainer
triaging repetitive repository work — dependency bumps, flaky tests, doc rot.
The engineering lead
reviewing agent-prepared diffs with verification evidence attached, not vibes.
The security-conscious team
waiting on the local runner so source never leaves their metal.
The student
learning from a transparent execution trace — every read, edit, and failed test visible.
Planned access tiers · nothing is for sale yet
Pay for fire — later.
There is no billing, no trial, no checkout. These are the access shapes we're planning; pricing will exist when a real service does.
Explorer
Available now- The full interactive demo
- Documentation and roadmap
- Product updates
Builder Preview
Planned- Repository-connected workflows when they land
- Early input on the permission model
- Direct line to the team
Foundry Preview
Planned- Team controls and policy management
- Local / self-hosted runners
- Audit capabilities
About this project
We got tired of watching.
Autocomplete made typing faster. Chat made searching faster. Nothing made shipping faster — because the human was still supervising every keystroke.
Tavronus Forge is our answer, built in the open as a prototype: give the agent the whole task, the whole repo, and the whole test suite — then judge the finished work at two hard gates, plan and review.
What you see here is exactly what exists: a complete, honest simulation of that workflow, a design system we love, and a roadmap toward the real thing. No customers, no funding announcements, no invented numbers.
3
Product surfaces: landing, Forge, dashboard
11
Lifecycle states in the demo engine
2
Human gates: plan approval & final review
1
Deliberate failure & replan, every run
The fire is lit
Ship while you sleep.
That's the product vision. Today you can walk the whole workflow, gate by gate, in the prototype — and tell us what the real thing must do.