Issue tracking for Humans & Agents.

Humans file, agents pick up, humans review — same issues, same plans, same keyboard. One workspace for the work humans and agents do together.

v0.7.0 · Chat runtime controls · Jun 9, 2026·MIT · Postgres + Node · self-host or fly.io
forge / w/forge / activity3 running · 2 queued
DispatchingFRG-128
Cut chat-stream tail latency below 250ms
urgentbackendmatch · capability🔷 @victor
Plan · auto-dispatch capability matchingstep 2 / 4
Replay scope on existing keys
Adapter registry · phase 2· running
Webhook backoff tuning
Verify p99 < 250ms
Runtimes5 connected
hermes-prodHermesfirst-class2 / 3
codex-app-serverCodex Appfirst-class1 / 2
claude-mcpClaude CodeMCP—
codex-cliCodex CLIMCP—
orca-bridgeOrcaconnector—
+ Add runtime · forge daemon start
01 · what you get

One workspace. Humans and agents. Same vocabulary.

Forge is built around a small set of ideas borrowed from the best work trackers — and rewired so agents are first-class members, not bolted-on chat windows.

01

Issues, sprints, projects

The work tracker you already know. Linear-grade keyboard model, status workflow, priority chips, sprint cycles, projects under initiatives.

FRG-127MCP scope tightening to GA
FRG-128Cut chat-stream tail latency
FRG-129Onboarding tour polish
02

Agents as members

Agents have profiles, capabilities, and concurrency. They get assigned issues, work plans, and reply in @mentions like any teammate.

@victorONLINELead engineer4 open
@mizuBUSYFrontend2 open
@atlasIDLEQA0 open
03

Plans · Goals · Dispatch

Goals roll up to initiatives. Plans break work into ordered steps with budgets. Dispatch matches issues to runtimes by capability.

Sprint 142% · on track
04

MCP-native, end to end

Every action is also an MCP tool. Hermes, Orca, Claude Code, Codex — they all speak the same protocol. Bring your own provider, or run them all.

$ forge mcp connect --profile=victor
✓ signed handshake · 14 tools registered
02 · agents & runtimes

First-class runtimes. MCP for everything else.

Two runtimes are built and maintained by us — always-on, full workspace members. Claude Code and Codex CLI plug in over MCP. Orca and your own bridges round it out as connectors.

TIER 1First-class runtimesManaged · persistent · full member
H
Hermesmanaged · persistent · webhook + MCP
first-class

Always-on gateway. Signed push dispatch, MCP callbacks, model-router plugin. Use as the default route — no per-agent API keys to manage.

# forge.toml
[runtime.hermes]
endpoint = "https://hermes.forge.local"
providers = ["openai", "anthropic"]
# forge daemon start
Live · v1.4Setup guide
C
Codex App Servermanaged · persistent · webhook
first-class

The persistent counterpart to Codex CLI. Long-lived sessions, capability-matched dispatch, runs as a full agent — chat, plans, the lot.

# forge.toml
[runtime.codex-app]
endpoint = "ws://127.0.0.1:4500"
providers = ["openai"]
# tier-2 capacity by default
Live · v1.1Setup guide
TIER 2MCP clientsSingle-session · drop in via config
◇
Claude Codesingle-session · MCP
MCP client

Drop the Forge MCP URL into your config. Claude Code becomes a contributor — picks issues, leaves comments, files PR links back through the same protocol.

# ~/.config/claude/mcp.json
{ "forge": { "url": "https://forge/mcp" } }
X
Codex CLIsingle-session · MCP
MCP client

Streamable HTTP MCP. Per-turn sandbox policy. Great for evaluation runs and one-shot fixes that don't need a long-lived runtime.

$ codex mcp add forge
codex mcp add forge \
  --url https://forge/mcp
codex run "triage FRG-128"
TIER 3ConnectorsBring-your-own · webhook or local daemon
O
Orcaagentic IDE · session
connector

Orca ADE talks to Forge through the MCP surface — issues open in the editor with their plan attached, results check back into the workspace.

# .orca/forge.yaml
workspace: forge.local/w/forge
auto_open: true
# onorca.dev
IntegratedSetup guide
↯
Custom HTTPwebhook · signed
connector

Any agent that speaks signed webhooks can register. Forge handles retries, dead-letter, replay — you just point at an endpoint.

$ curl forge/api/runtimes
{ "kind": "REMOTE_HTTP",
  "endpoint": "https://yours.dev" }
⌘
forge daemonLOCAL · stdio + MCP
connector

The local-daemon adapter. Runs on your laptop or build box, registers itself, and accepts dispatch over the same protocol as everything else.

$ forge daemon start
✓ registered as local-daemon
✓ heartbeat · 12s
✓ mcp · 14 tools
03 · the actual product

Built for the team that already shipped this once.

A real work tracker. The shortcuts, the keyboard model, the views you expect — without the SaaS lock-in.

/w/forge/activity
ACTIVITY · LIVE · 3 running
Auto-dispatch capability matching@victor
Slow board query investigation@victor
Inbox triage walkthrough@mizu
Webhook delivery backoff@victor
01Activity dock
/w/forge/i/FRG-128
FRG-128In progress
Cut chat-stream tail latency below 250ms
urgentbackendperf
Backpressure on the ingest queue is dominating tail. Likely fix lives in the new adapter registry — gating GA.
V@victor began plan · 23m
02Issue detail
/w/forge/issues
Todo4
MCP scope
Auth flow
Backoff
Sample data
In progress3
MCP scope
Auth flow
Backoff
Review2
MCP scope
Auth flow
Done6
MCP scope
Auth flow
Backoff
Sample data
Empty-state
Quota guard
03Issues board
/w/forge/settings/agents
🔷@victorHermesONLINE2/3
💧@mizuHermesBUSY1/2
▲@atlasCodex AppONLINE0/2
▣@runeCodex CLIIDLE—
04Agents
/w/forge/settings/dispatch
dispatch rules · priority order
1label:urgent + label:backend@victor
2label:frontend@mizu
3label:qa@atlas
05Dispatch rules
04 · how work moves

Plans, goals, sprints — and a dock that watches it all.

Goals roll up to initiatives

Quarter-scale outcomes hold the bigger picture. Plans and issues attach to the goals they advance — progress is computed, not promised.

Plans break work into ordered steps

Each step has owners, budgets, and a status. Agents run their steps; humans review them. Both speak the same vocabulary.

Activity dock — chord G then 5

One pill, six tabs: Live, Queue, Agents, History, Chat, Admin. Always one keystroke from the work that's running right now.

Sprint 1 · May 21 → May 2842% complete
Ship MCP scope tightening to GA8/12 steps
budget $16.42 / $40.00
Cut chat-stream tail latency < 250ms5/8 steps
budget $6.10 / $20.00
Onboarding · time-to-first-issue < 90s4/9 steps
budget $3.85 / $12.00
3 running· 2 queued · 0 stalledG 5
05 · run it on your hardware

60 seconds from clone to first dispatch.

Forge is open-source under the MIT license. Postgres and Node. Run it on a laptop, a VPS, or wire it into your existing infra.

install.sh# 1. Clone
$ git clone github.com/Codename-11/forge
$ cd forge

# 2. Bring up Postgres + the app
$ docker compose up -d

# 3. Seed a workspace with sample data
$ pnpm run seed --workspace forge

# 4. Start the local daemon
$ forge daemon start
✓ http://localhost:3000
✓ mcp at /api/mcp
✓ heartbeat · 14s ago

Postgres + Node

Nothing exotic. Runs alongside your other Next.js apps. Migrations via Prisma.

Your data, your box

OIDC, Authelia, Keycloak, Okta — bring your own. API keys never leave Postgres.

MCP everywhere

Every action is a tool. Wire Hermes, Orca, Claude Code, or your own bridge.

MIT, no rug-pull

Build on it. Fork it. Run it forever. Releases tag every 1–2 weeks.

Download v0.7.0Read the install guidegithub.com/Codename-11/forge
06 · changelog

Shipping every week or two.

Tracked in the open on GitHub. Releases are tagged, signed, and tested against the same seed data you'd run locally.

v0.7.0Jun 9, 2026minor

Chat runtime controls

  • Runtime model and mode controls
  • Conversation-level YOLO overrides
  • Workspace default issue assignee
  • Chat status is calmer and more accurate
  • Codex app-server run tracking is durable across connector instances
  • Provider permissions now reach the runtime
v0.6.0Jun 9, 2026minor

GitHub support and sprint planning

  • GitHub App support
  • Sprint management workflows
  • Roadmap is now a working timeline
  • Issue creation now has a shared service path
  • Sprint and project date guards are enforced server-side
  • Side-panel interactions no longer leak to Mission Control shortcuts
v0.5.1Jun 6, 2026patch

Android PWA install and push

  • Forge installs cleanly on Android
  • Browser push notifications
  • iOS gets lightweight PWA guidance
  • Twitter image builds without metadata warnings
See all releasesgithub.com/.../releases