Loading article…

Loading 4weird…

DocsHeal loops

Docs · desktop · opencode

Heal until clean, or until budget.

Heal loops bugtest → fix → re-test until the suite is clean or a budget trips — iteration count, token cap, or spend cap, whichever hits first. Coin quotes follow the house rule (100 coins = $1, 75/25 split); MCP-mediated payment is a queued future where only stubs exist today.

loop: test → fix → re-test
100 🪙: = $1.00 always
75 / 25: provider / platform
MCP pay: queued future

The loop

Bugtest → fix → retest

Export writes the BUGFIX-<game>-<stamp>.md/json report; Fix hands it to OpenCode so it edits code itself and shows the diff; Heal repeats test → fix → re-test until clean or the iteration budget is spent. Swarm agents reach the same loop via the opencode.export / opencode.heal tools.

Bugtest
Run the game tools / test suite and collect failures into a BUGFIX report. A stubbed run that fails twice then passes must heal and stop.
Fix
Hand the report to OpenCode (opencode run -f file, the desktop Fix button, or the opencode.heal tool) so it edits code and shows the git diff.
Retest
Re-run the same suite. Clean → done with a verdict. Still failing → next round, until the loop terminates on clean, on max rounds, or on budget.
Always-fail stops on budget
A stubbed always-fail run must stop on the token/spend budget with a verdict — never spin forever. The loop always terminates.

Budgets

Token budgets beat iteration counts

Iteration caps alone cannot price a loop — one round can burn far more tokens than the next. The heal budget tracks input/output tokens, prices them, and stops on max tokens or max spend (USD), with per-iteration ledger lines. Integer-token accounting, fail-open clamps, never exceeds budget.

maxTokens

Hard cap on input + output tokens across all rounds. Trips before max iterations in a heavy run.

maxSpendUSD

Hard cap on priced spend. A run with maxSpendUSD set tiny stops on spend, not on round count.

Per-iteration ledger

Every round logs its token usage so the stop reason is auditable after the verdict.

Coin quotes

Every quote splits 75/25

Heal-loop cost estimates are read-only quotes in integer coins: 100 coins = $1.00, provider keeps 75% as on-site credits, platform keeps 25% for infrastructure. Quotes never write to any ledger — settlement stays a later lane.

75% provider credits

25% platform

Example: a 400-coin ($4.00) job → 300 coins provider credits, 100 coins platform. You only ever see the gross 400. All credits are on-site only (cloud compute, game credits, other on-site services); never cash-out, never withdrawable.

MCP pay

MCP-mediated payment is queued-future

Driving bugtest + fix remotely (terminal exec, heal start/status, opencode fix tools over MCP) and paying for it in coins is the queued future: where only stubs exist today, this page describes intent, not a live payment path. Nothing here debits a wallet.

Remote tools first
Terminal exec (allow-listed, token-authed), heal start/status, and opencode fix arrive as MCP tools before any money moves.
Quotes before charges
Every paid action gets a read-only coin quote first — same 100 = $1, same 75/25 split, same zero-write rule.
Settlement last, guarded
Actual ledger movement needs its own guarded lane (auth, rate limits, audit log). Until that ships, MCP pay stays described, not billed.

← Terminal

Web /terminal vs the desktop panel.

← Setup

CLI requirements and run vs serve modes.

Loading article…

DocsHeal loops

Docs · desktop · opencode

Heal until clean, or until budget.

loop: test → fix → re-test
100 🪙: = $1.00 always
75 / 25: provider / platform
MCP pay: queued future

The loop

Bugtest → fix → retest

Bugtest
Run the game tools / test suite and collect failures into a BUGFIX report. A stubbed run that fails twice then passes must heal and stop.
Fix
Hand the report to OpenCode (opencode run -f file, the desktop Fix button, or the opencode.heal tool) so it edits code and shows the git diff.
Retest
Re-run the same suite. Clean → done with a verdict. Still failing → next round, until the loop terminates on clean, on max rounds, or on budget.
Always-fail stops on budget
A stubbed always-fail run must stop on the token/spend budget with a verdict — never spin forever. The loop always terminates.

Budgets

Token budgets beat iteration counts

maxTokens

Hard cap on input + output tokens across all rounds. Trips before max iterations in a heavy run.

maxSpendUSD

Hard cap on priced spend. A run with maxSpendUSD set tiny stops on spend, not on round count.

Per-iteration ledger

Every round logs its token usage so the stop reason is auditable after the verdict.

Coin quotes

Every quote splits 75/25

75% provider credits

25% platform

MCP pay

MCP-mediated payment is queued-future

Remote tools first
Terminal exec (allow-listed, token-authed), heal start/status, and opencode fix arrive as MCP tools before any money moves.
Quotes before charges
Every paid action gets a read-only coin quote first — same 100 = $1, same 75/25 split, same zero-write rule.
Settlement last, guarded
Actual ledger movement needs its own guarded lane (auth, rate limits, audit log). Until that ships, MCP pay stays described, not billed.

← Terminal

Web /terminal vs the desktop panel.

← Setup

CLI requirements and run vs serve modes.

Heal until clean, or until budget.

Bugtest → fix → retest

Bugtest

Fix

Retest

Always-fail stops on budget

Token budgets beat iteration counts

Every quote splits 75/25

MCP-mediated payment is queued-future

Remote tools first

Quotes before charges

Settlement last, guarded

Heal until clean, or until budget.

Bugtest → fix → retest

Bugtest

Fix

Retest

Always-fail stops on budget

Token budgets beat iteration counts

Every quote splits 75/25

MCP-mediated payment is queued-future

Remote tools first

Quotes before charges

Settlement last, guarded