Home / Docs / forge

forge

A workflow analyst that automates your Thurbox for you. forge watches how you actually use Thurbox — your task backlog, the sessions you keep spawning, your existing automations and how often they fire or fail — and turns the recurring patterns into concrete, ready-to-apply proposals: mostly new thurbox-cli automation s, sometimes a pointer to another extension.

Experimental. forge is new and under active testing — its behavior spec, scripts, and manifest may change between releases.

Proposes, never imposes. A scan only ever reads state and writes a proposal file, so it is safe to run unattended on a schedule. Nothing is created until you explicitly apply it.

Overview #

A weekly forge-scan automation drives a dedicated forge session. Each scan clusters your tasks/sessions/automations by intent and, where a pattern repeats, writes a proposal to ~/.config/thurbox/extensions/forge/proposals.jsonl (rendered for humans into ~/.config/thurbox/extensions/forge/proposals.md ). Like Thurbox itself, forge is agent-agnostic : the analyst is a plain agents.toml alias ( forge ), so it can be claude, codex, antigravity, opencode, vibe, …

Install #

forge is a Thurbox extension (a declarative extension.toml manifest):

bash 
thurbox-cli extension install forge      # or ./extensions/forge from a checkout
thurbox-cli extension uninstall forge    # --purge also deletes ~/.config/thurbox/extensions/forge

Installing lays down the forge home ( ~/.config/thurbox/extensions/forge ; override with --home ), registers the forge agent (claude on sonnet by default — edit the agents.toml entry to change), and activates the forge session plus the weekly forge-scan automation — both self-healed by Thurbox.

Use #

  • forge scans on its schedule; trigger one now by sending scan to the forge session.
  • status for a one-screen list of open proposals; review the rendered backlog in ~/.config/thurbox/extensions/forge/proposals.md .
  • apply <slug> runs the proposal's stored command and marks it applied; dismiss <slug> buries one so future scans won't resurface it.
  • Anything else you type is treated as an ad-hoc question about your workflow.

How a proposal is applied safely #

proposals.jsonl is the source of truth; proposals.md is the human render. Every proposal carries an exact command, and proposals.sh apply refuses to run anything that does not start with thurbox-cli — so applying a proposal can only ever create or edit a Thurbox automation, never run arbitrary shell.

Files #

See extensions/forge for the FORGE.md behavior spec (modes, signal sources, proposal rubric), the extension.toml manifest, and the helper scripts ( forge-snapshot.sh , proposals.sh ).