01 / Navigate
Find the work in context.
Move across registered workspaces and active or archived changes without walking folder trees. Progress, modified times and Git-state badges show where attention belongs.
A visual companion for spec-driven development
Spec-driven work, in full view.
SpecForge supports OpenSpec today, placing each change beside the repository-wide Git graph. Local, read-only, free and MIT licensed.
Or run it without downloading
npx @avantmedia/specforgeNode 18+ · opens http://127.0.0.1:4317
The repository remains the source of truth
Specs give work structure. SpecForge gives it a view.
Spec-driven development works because intent, design and tasks live beside the code. OpenSpec is the format SpecForge reads today: its files are portable, reviewable and legible to people and agents. But as repositories, changes and worktrees multiply, that state becomes hard to hold in your head.
Register a workspace once. SpecForge discovers its changes and sibling Git worktrees, groups matching copies, and updates the view when files or commits change.
No import. No migration. No second source of truth.
improve-search-ranking
1 logical changeagent/implementationupdated now
18 / 24modifiedagent/review-fixesupdated 8m ago
24 / 24committedagent/spikeupdated 2h ago
7 / 24staleOne change, end to end
Follow the thinking all the way to Git.
SpecForge keeps the artifacts, task state and repository evidence together, so a review starts with context and can move directly to what is in Git.
02 / Read
Read artifacts as documents.
Open proposals, designs, specs and tasks in a focused reader with highlighted code, Mermaid diagrams, maths and SVG. The filesystem remains underneath; the reading experience does not have to feel like one.
03 / Verify
Connect intent to evidence.
Keep the repository-wide git log --all graph beside the change. Open a commit to inspect its files and textual diff, then return to the spec context without changing tools.
Local-first / read-only / one Rust core
A companion, not another system of record.
SpecForge reads the specs and Git state on the machine where it runs. There is no hosted workspace to sync and no competing place to edit the work.
Reads locally
OpenSpec's openspec/ tree, Markdown artifacts, task state, Git worktrees and repository history.
Never changes your work
It does not edit a spec, toggle a task, archive a change, check out a branch, merge, rebase or reset anything.
Writes outside projects
SpecForge writes only its own app state outside your workspaces: registry, settings, favourites, presentation and activity history.
Desktop
Stay aware without staying in the app
Keep the change browser one click from the tray. Its badge counts distinct changes while the main window is out of the way.
Browser
Run it locally or reach it remotely
Run it on localhost, a headless machine, or through an SSH tunnel or Tailscale Serve connection, with durable URLs and browser navigation.
Terminal
Keep it inside SSH and tmux
Browse changes in a full TUI, print a one-shot status for scripts, or place a compact SpecForge line in your prompt.
Start local. Stay local.
Open your first workspace.
SpecForge 0.25.0 is free, MIT licensed and in early, active development (v0.x). Run the browser interface with one npm command, or take any binary below directly.
Fastest start / Local web app
Try the full interface in one command.
The npm package fetches only the binary for your platform, starts on loopback and needs no archive extraction, no postinstall script and no quarantine flag.
npx @avantmedia/specforgeRequires Node 18+. Open http://127.0.0.1:4317, then add the workspace's host path in Settings.
Release notes and history
Prefer to read before you install?
Every artefact below comes from release 0.25.0. Its notes list what changed, and the archive holds every earlier build.
Read the 0.25.0 release notesBrowse all releasesDesktop app
Tray badge and dock indicator, one click from the menu bar.
Terminal UI
Interactive browser, one-shot --status and a compact --line for your prompt.
Local web server
The browser UI on localhost, a headless machine, or through a tunnel.
Downloaded releases are unsigned.
macOS Gatekeeper and Windows SmartScreen may warn on first launch. Troubleshooting gives the exact steps for each platform.
Keep direct network binds private.
Keep specforge-serve on loopback, or use an SSH tunnel or Tailscale Serve. A direct --bind 0.0.0.0 is unauthenticated and belongs only on a network you trust. Read the remote-access guide.