Guide to Forge

Start in the queue

Activity collects recent comments, reviews, commits, and state changes across every repository you track. Threaded mode groups events by pull request or issue; flat mode keeps exact order. Filter by time, event type, repository, text, or bot activity — then select a row and its detail opens beside the queue, so you never lose your place.

When you need to move faster than the mouse, the command palette is everywhere:

Explore the activity workflow →

Triage issues into work

Issues is a queue, not a list: search, filter, comment, star, close, or reopen without leaving the view. When an issue is ready for implementation, create a workspace from it directly — the branch, worktree, and context arrive together, ready for you or an agent to pick up.

Explore the issue triager workflow →

Hand the work to an agent

Create a workspace from a pull request, issue, or from scratch: each one is a Git worktree with durable, tmux-backed sessions. Choose an agent from the action menu to create the workspace and launch it in one step, then promote the session into the detail layout so it sits beside the discussion and files it is working on.

Lifecycle hooks (kenn-forge agent-hook install) surface agent activity in workspace rows — active work, approval requests, and input requests — while the sidebar is open.

Explore the workspaces workflow →

Review and merge without tab-hopping

When the agent's work comes back as a pull request, its detail view combines description, discussion, CI, branch state, review state, changed files, and provider actions. Open the file tree for line-by-line review, comment, approve, and merge when the provider allows it. Detected stacks show member order, and mid-stack merges stay blocked until earlier members land.

Conversation, files, and a workspace can share one pane layout — reorder, split, resize, or maximize panes as the task changes. A local workflow status tracks where each pull request sits in your process without touching provider labels.

Explore the code reviewer workflow →

Browse source without cloning in your head

Repos opens any tracked repository: switch among branches and tags, filter the path tree, read files with rendered Markdown previews, and follow a file's commit history in the side rail. The URL records repository, ref, path, and preview mode, so copied links restore the exact view.

Explore the repositories workflow →

Bring your other tools with you

Reviews follows Roborev jobs — filter the queue, read reviews, inspect logs and prompts. Kata tasks link to pull requests, issues, and workspaces with read-only detail inline. Docs registers local Markdown folders you can browse, search, edit, pull, and publish from the console. External systems stay the source of truth; Forge owns only the links.

Explore integrations →

Federate your workspaces across machines

When one machine stops being enough, connect full Forge daemons into a hub-and-spoke fleet over authenticated HTTPS. The hub syncs your forges once and shows workspaces across every machine; remote actions route one hop to the spoke that owns them. Each spoke keeps its own repositories, worktrees, agents, and tmux sessions — and stays usable even when the hub is unreachable.

Enrollment uses one-time tokens with separate credentials per direction, and Tailscale Serve is a first-class setup path — any mutually reachable private HTTPS ingress works. Alongside the fleet, the MCP companion gives your agents the same console over the Model Context Protocol, and activity archives keep history beyond the live sync window.

Explore federated fleets →