A companion for spec-driven development
SpecForge supports OpenSpec today, placing each change beside the repository-wide Git graph and the pull request it became. Local-first, free and MIT licensed.
npx @avantmedia/specforgeNode 18+ · opens http://127.0.0.1:4317
The repository remains the source of truth
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.
18 / 24modified24 / 24committed7 / 24staleOne change, end to end
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 and on the pull request.
01 / Navigate
Start from the Dashboard's overview of every registered workspace, then move across active and archived changes without walking folder trees. Progress, modified times and Git-state badges show where attention belongs.
02 / Read
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
Keep the repository-wide git log --all graph beside the change and open any commit's files and diff. When the branch reaches GitHub or BitBucket, its pull request opens in the same window, linked to its worktree, and SpecForge keeps track of the files and hunks you have viewed.
Local-first / deliberate boundaries / one Rust core
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. Its boundaries are design choices: what it will never do is as deliberate as what it shows.
OpenSpec's openspec/ tree, Markdown artifacts, task state, Git worktrees and repository history.
It never edits a spec, toggles a task checkbox, archives a change, or changes local work or git state: no checkout, merge, rebase or reset, and it never merges a pull request. Only the native desktop app can post a pull-request review — a comment, reply, approval or request for changes — and only after explicit native confirmation. The browser skin and terminal never post one.
SpecForge writes only its own app state outside your workspaces: registry, settings, favourites, presentation and activity history. GitHub and BitBucket access stays off until you configure it, and opening or publishing the browser skin grants no provider-write authority.
Desktop
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 on localhost, a headless machine, or through an SSH tunnel or Tailscale Serve connection, with durable URLs and browser navigation.
Terminal
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.
SpecForge 0.27.1 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
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
Every artefact below comes from release 0.27.1. Its notes list what changed, and the archive holds every earlier build.
Read the 0.27.1 release notesBrowse all releasesTray badge and dock indicator, one click from the menu bar.
Interactive browser, one-shot --status and a compact --line for your prompt.
The browser UI on localhost, a headless machine, or through a tunnel.
macOS Gatekeeper and Windows SmartScreen may warn on first launch. Troubleshooting gives the exact steps for each platform.
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.