Forge

Keep terminal work alive, visible and testable.

Watch the 62-second film: a long terminal job the chat forgot, and how the skill names it, checks it and closes only what it opened. The example in it is fictional.

For people and agents driving CLIs and terminal apps. Forge gives a persistent session a name, lets you inspect its screen and output, and keeps a clear test and cleanup path when the conversation moves on.

Explore the site

What you get

• Return to a running task. Use a named PTY session rather than losing the state of an interactive terminal between turns.
• Check the app itself. Read rendered screens, wait for a specific state and assert what appeared.
• Coordinate through artifacts. Use the optional relay ledger when several workers need an inspectable handoff and acceptance gate.

Start here

git clone https://github.com/michaeljabbour/amplifier-capability-forge.git
cd amplifier-capability-forge
python3 scripts/capability.py install --dest ~/.agents/skills

This installs the portable method and its packaged references into your agent skill folder. If your host uses another folder, pass that path to --dest. Start a new session or use your host’s skill refresh so it can discover the installed skill. Optional native tools are installed separately.

Try this first task:

Use Forge to plan a disposable TUI smoke test. Check daemon availability first, create one named session, wait for the ready screen, capture the observed state and close only the session created for this test. Do not change permissions or launch additional agents.

What you need

• Python 3.11 or later for the portable install helper.
• The packaged Python HTTP client and relay are stdlib-only.
• Real terminal operations need a reachable Forge daemon; the native guide covers its Node/Bun installation.
• doctor --check-only reports the installed daemon CLI's status without startup or repair. Plain doctor can start/restart the daemon and repair its helper; use it only with that authority.

For the optional native interface, use a project virtual environment:

python3 -m venv .venv
source .venv/bin/activate
python3 tools/forge.py doctor --check-only

The status-only command does not prove a terminal can start. When startup or repair is needed, obtain the operator's approval before plain doctor; its recovery can restart the shared daemon and change helper execute bits.

Status-only recognition is bounded to the first stderr header used by forge-terminal-mcp 0.9.0 (Forge daemon: running (PID <positive integer>)) with a zero exit code. Other formats fail as unverified; the helper does not guess from text such as “not currently running.” This source-format check is not live daemon acceptance.

Evidence and limits

Unit and isolated integration checks cover client and relay behavior. The portable release check deliberately does not start a daemon or prove that a particular TUI works.

The worked examples on the site are fictional. They illustrate the output and decisions; they are not user results or measured benefit. See consolidation and runtime boundaries for retained interfaces and acceptance scope.

---

Native guide

Consolidated portable package

The existing root skill, HTTP client and relay remain canonical and path-compatible. Install the bounded package with python3 scripts/capability.py install --dest ~/.agents/skills. See consolidation boundaries. Native helpers and daemon protocol are retained; packaging tests do not demonstrate daemon availability.

Give Claude Code, OpenAI Codex, OpenCode, Gemini, and Microsoft Amplifier a shared way to launch, drive, coordinate, and test terminal applications in persistent Forge PTY sessions (forgemcp.dev, npm).

This repository is both a portable Agent Skill and a zero-dependency Python toolkit. Sessions remain visible in the Forge dashboard at http://127.0.0.1:3141/, even when the calling harness does not expose Forge as an MCP server.

This is the beginning of the README. Read the rest at the original. Read the full README ↗