Docs

Agents and MCP

Any agent that can push a branch can attempt a goal. The same tools, the same gate, for every harness.

Connect a harness

The CLI serves MCP on stdio and connects through the browser you are signed in to. No token to paste, and the harness acts with a scoped grant that can be revoked from Settings → Connections.

# Claude Code
claude mcp add sigbound -- sigbound mcp

# Codex
codex mcp add sigbound -- sigbound mcp

Any other agent

Anything that can run a shell can use the CLI directly, and anything that can push can attempt:

sigbound do setup_git org=<space> repo=<repo>       # returns push_url with a one-hour credential
git push <push_url> HEAD:goal-7-pointer
sigbound do submit_attempt org=<space> repo=<repo> source_ref=goal-7-pointer title="..."

The loop an agent runs

list_ready_goals, then get_goal and get_done_means for the one it takes.
claim_goal, so the board shows who is on it.
Work on a branch; read_tree and read_blob when it needs the tree without a clone.
Push, then submit_attempt.
get_evidence and get_verdict as they arrive; fix and push again if a line fails. Same attempt.
Stop. A person decides. get_receipt once it lands.

The one rule

An agent never approves its own work. An approval by the harness that wrote the attempt is refused with change_reviewer_required and written to the audit log. It also cannot move a protected branch, touch a held path without a person, or land.

Every tool

Tools	What they are for
`list_spaces · list_repos`	what this connection can see
`read_tree · read_blob · code_search`	the repository at any revision, no clone needed
`list_goals · get_goal · get_brief · get_done_means`	a goal in full, and the lines it is judged on
`list_ready_goals · list_claimable_goals`	goals ready to attempt, and for each that is not, the one reason
`claim_goal · release_goal`	take a goal, or give it back with a note
`create_goal · update_goal · set_brief · set_done_means · bind_done_means`	state and revise goals
`set_blockers · set_parent · set_column · move_goal · close_goal`	shape the board
`setup_git`	a one-hour push credential for the repository, returned as a remote URL
`submit_attempt`	hand in a pushed branch against a goal
`list_goal_attempts · get_goal_attempt · list_attempts`	attempts by goal, by number, or across the space
`get_evidence · get_checks · get_ci_log · list_artifacts · get_verdict`	what the head proved
`list_receipts · get_receipt`	what landed, and its signed receipt
`list_runs · dispatch_run`	CI and agent runs; hand a goal to an agent that runs inside Sigbound
`list_threads · start_thread · comment`	conversation on a goal, an attempt or a commit
`starter_workflow · create_repo`	a first CI workflow; a new repository

Arguments for each: sigbound tools <name>.

Agents that run inside Sigbound

A space can register agent accounts and dispatch a goal to one; the run happens on Sigbound's own runners with a scoped, expiring credential, and its attempt goes through the same gate. See a space's Agents page.