https://github.com/bowen31337/claw-forge-plugin
Claude Code plugin for the claw-forge autonomous coding-agent harness — spec-driven parallel agents billed against your Claude Pro/Max subscription pool, not the metered Agent SDK allowance.
https://github.com/bowen31337/claw-forge-plugin
agent-harness autonomous-agents claude claude-code claude-code-plugin coding-agent spec-driven-development
Last synced: 12 days ago
JSON representation
Claude Code plugin for the claw-forge autonomous coding-agent harness — spec-driven parallel agents billed against your Claude Pro/Max subscription pool, not the metered Agent SDK allowance.
- Host: GitHub
- URL: https://github.com/bowen31337/claw-forge-plugin
- Owner: bowen31337
- License: apache-2.0
- Created: 2026-05-29T01:24:02.000Z (27 days ago)
- Default Branch: main
- Last Pushed: 2026-05-29T02:45:55.000Z (27 days ago)
- Last Synced: 2026-06-12T07:35:05.457Z (12 days ago)
- Topics: agent-harness, autonomous-agents, claude, claude-code, claude-code-plugin, coding-agent, spec-driven-development
- Language: Shell
- Homepage: https://github.com/bowen31337/claw-forge-plugin
- Size: 149 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# claw-forge-plugin
A Claude Code plugin that brings the [claw-forge](https://github.com//claw-forge)
autonomous coding agent harness inside your interactive Claude Code session — so every
agent invocation bills against your Claude Pro/Max subscription pool instead of the
metered Claude Agent SDK allowance.
**Status:** Pre-implementation (v0.1.0 draft). The PRD and architecture are frozen, the
[`app_spec.txt`](./app_spec.txt) is validated (49 features across 9 categories), and the
directory layout is scaffolded — every file under `commands/`, `skills/`, `agents/`,
`hooks/`, `CI/`, and `tests/` is an empty stub waiting on its corresponding feature.
The plugin's own `claw-forge run` will fill them in.
## Why
[Anthropic's policy](https://support.claude.com/en/articles/15036540-use-the-claude-agent-sdk-with-your-claude-plan)
gives apps that use `claude-agent-sdk` or `claude -p` a limited credit allowance
**separate from your Pro/Max subscription pool**. claw-forge today uses the SDK for every
agent invocation. The plugin form moves that execution inside your CC session, where it
bills the normal way.
## Install
Install in this order:
1. Install the sidecar (Python package, provides state service, Kanban UI, spec tooling,
git helpers):
```sh
pip install -U claw-forge
```
Requires `claw-forge >= 0.6.0`. The `SessionStart` hook prints an upgrade hint if an
older version is detected.
2. Install the plugin inside Claude Code:
```
/plugin install claw-forge
```
That's it. Open any claw-forge project and the sidecar starts automatically on session
open.
## Hello world
```sh
cd my-project # a git repo with a description of what you want to build
```
1. **Author a spec.** Describe the project to Claude and generate the feature list:
```
/claw-forge spec-create
```
The host session writes `app_spec.xml` when done.
2. **Seed the plan.** Parse the spec and build the dependency graph:
```
/claw-forge plan
```
3. **Run.** Dispatch all ready features in parallel — billed against your subscription
pool, not the metered SDK allowance:
```
/claw-forge run
```
Open the Kanban UI in another tab to watch progress:
```
/claw-forge ui
```
4. **Merge.** When the run finishes, squash-merge every completed feature branch into
`main`:
```
/claw-forge merge
```
For brownfield projects start with `/claw-forge spec-import` to snapshot the existing
codebase first.
## How it works (in one paragraph)
You install two things: `pip install claw-forge` (the Python sidecar — state service,
Kanban UI, spec tooling, git helpers) and `/plugin install claw-forge` (this plugin —
slash commands, skills, subagent definitions, hooks). When you open a claw-forge project,
a SessionStart hook starts the sidecar in the background. You type `/claw-forge run`; a
skill instructs the host session to query the sidecar for ready tasks and dispatch them
in parallel via the Task tool. Each subagent does one feature inside an isolated git
worktree, reports back, and the host PATCHes the state DB and squash-merges. No SDK
calls anywhere — the host CC session is the only thing that ever talks to Claude.
## Documents
- **[PRD](docs/PRD.md)** — product requirements: motivation, users, goals, success
metrics, feature inventory, sidecar contract dependencies, constraints, open questions
- **[ARCHITECTURE](docs/ARCHITECTURE.md)** — technical architecture: repo layout,
component map, dispatch loop replacement, subagent workflow, sidecar interface,
hooks, sandboxing changes, build/test/CI strategy, migration path, sidecar slimming
needed in claw-forge v0.6.0
- **[Sidecar contract](docs/sidecar-contract.md)** — every `claw-forge` CLI subcommand
the plugin calls, its flags, and its `--json` response envelope; treat this as the
stability boundary between the plugin and the [claw-forge sidecar](https://github.com//claw-forge)
## Building this plugin
This repo is itself a greenfield claw-forge project:
1. Sidecar `claw-forge` v0.5.x is used for the bootstrap build (acknowledged one-time
metered cost — see PRD §9 "Bootstrap chicken-and-egg").
2. `/create-spec` (a sidecar slash command in claw-forge today) turns `docs/PRD.md` into
`app_spec.xml` with shape annotations.
3. `claw-forge plan` → DAG into the state DB.
4. `claw-forge run` builds the plugin features in parallel worktrees.
5. After v0.1.0 ships, future plugin development uses the plugin itself.
## License
Apache-2.0