Files
fleetd/opencode.json
T
Dai Ha 3aea4e1ec6
CI / contract (pull_request) Successful in 1m10s
CI / build (pull_request) Successful in 1m30s
CB-622 lead follow-up: the three changes no worker could make
1. opencode.json — mount key bridged -> fleetd. Unit C could not do this:
   the file is neutralized by the worktree overlay, so every worker sees a
   stub and correctly reported it held no mount key. Tracked as CB-628.

2. e2e/bridge_ask_transcript.md keeps its name. It is a dated record of a
   run on 2026-07-16 that really did call bridge_ask, and its first line
   says so. The harness now writes fleet_ask_transcript.md for new runs;
   its header already says 'Live fleet_ask', so the two now agree.

3. docs/MCP-Contract.md line 20 — the historical banner describes section
   6, and section 6 now says fleet_ask.
2026-08-22 21:59:23 +02:00

35 lines
690 B
JSON

{
"$schema": "https://opencode.ai/config.json",
"instructions": [
"CLAUDE.md"
],
"mcp": {
"fleetd": {
"type": "remote",
"url": "http://127.0.0.1:8765/mcp",
"enabled": true
},
"context7": {
"type": "remote",
"url": "https://ct7.ltms.dev/mcp",
"enabled": true,
"headers": {
"Authorization": "Bearer {env:CONTEXT7_TOKEN}"
}
},
"gitea": {
"type": "local",
"command": [
"gitea-mcp",
"-t",
"stdio"
],
"enabled": true,
"environment": {
"GITEA_ACCESS_TOKEN": "{env:WORKER_GITEA_TOKEN}",
"GITEA_HOST": "{env:GITEA_HOST}"
}
}
}
}