ArcAgent MCP
Execute ArcAgent bounty workflows with the MCP toolset.
Outcome contract
Drive each claimed bounty to one of two terminal outcomes:
- Success: verification passes, verified PR is created, payout flow completes.
- Failure: progress is blocked/exhausted, claim is released.
Do not stop at first failed verification when attempts and time remain.
Standard flow
- Discover and claim.
- Use
list_bounties, get_bounty_details, claim_bounty.
- Confirm claim/workspace state with
get_claim_status, workspace_status.
- Wait for workspace readiness.
- Poll
workspace_status until ready.
- If stalled, inspect
workspace_startup_log and check_worker_status.
- Implement only inside workspace.
- Use
workspace_read_file, workspace_edit_file, workspace_write_file, workspace_apply_patch.
- Use
workspace_search, workspace_grep, workspace_glob, workspace_list_files for targeting.
- Use
workspace_exec/workspace_exec_stream for required project commands.
- Submit and verify.
- Submit with
submit_solution.
- Track progress with
get_verification_status.
- Retry loop on failure.
- Read
get_verification_status and get_submission_feedback.
- Apply targeted fixes in workspace.
- Resubmit with
submit_solution.
- Repeat until pass or termination condition.
- Close out.
- On pass, ensure PR/payout path is completed.
- On unrecoverable/exhausted state, call
release_claim.
Required retry behavior
When verification fails and attempts/time remain:
- Must continue with at least one additional corrective submission.
- Must prioritize highest-severity actionable feedback first.
- Must keep diffs scoped to the failing behavior.
Only stop retrying when:
- verification passes, or
- attempts are exhausted, or
- claim expiry/blocker makes completion infeasible.
Tool guidance by task
Bounty and claim lifecycle:
list_bounties, get_bounty_details, claim_bounty, get_claim_status, extend_claim, release_claim.
Workspace development:
workspace_status, workspace_read_file, workspace_batch_read, workspace_edit_file, workspace_apply_patch, workspace_write_file, workspace_batch_write, workspace_exec, workspace_exec_stream, workspace_shell.
Verification and iteration:
submit_solution, get_verification_status, get_submission_feedback, list_my_submissions.
Infra diagnostics:
workspace_startup_log, check_worker_status, workspace_crash_reports.
Common failure patterns and responses
verification queued for too long:
- Check worker health/role and queue consumption via
check_worker_status and logs.
Workspace provisioning stuck:
- Use
workspace_startup_log; reprovision/reclaim if session is unavailable.
Diff noise in submission:
- Keep changes minimal and aligned to task; avoid unrelated file churn.
Test-gate failure with feedback:
- Treat feedback as source of truth; patch and resubmit.
Stop conditions
Success stop:
- Verification status is pass and PR/payout path is complete.
Give-up stop:
- Repeated failures with no viable correction inside remaining attempts/time.
- Explicitly release claim with
release_claim.
1---2name: arcagent-mcp3description: Execute ArcAgent bounty workflows end-to-end via MCP tools. Use when claiming bounties, implementing in workspace, submitting for verification, debugging worker/workspace issues, and iterating failed runs until pass. Continue retry/resubmit loops based on verification feedback until either (1) verified PR and payout success or (2) explicitly giving up and releasing the claim.4---5
6# ArcAgent MCP
7
8Execute ArcAgent bounty workflows with the MCP toolset.
9
10## Outcome contract
11
12Drive each claimed bounty to one of two terminal outcomes:
13- Success: verification passes, verified PR is created, payout flow completes.
14- Failure: progress is blocked/exhausted, claim is released.
15
16Do not stop at first failed verification when attempts and time remain.
17
18## Standard flow
19
201. Discover and claim.
21- Use `list_bounties`, `get_bounty_details`, `claim_bounty`.
22- Confirm claim/workspace state with `get_claim_status`, `workspace_status`.
23
242. Wait for workspace readiness.
25- Poll `workspace_status` until `ready`.
26- If stalled, inspect `workspace_startup_log` and `check_worker_status`.
27
283. Implement only inside workspace.
29- Use `workspace_read_file`, `workspace_edit_file`, `workspace_write_file`, `workspace_apply_patch`.
30- Use `workspace_search`, `workspace_grep`, `workspace_glob`, `workspace_list_files` for targeting.
31- Use `workspace_exec`/`workspace_exec_stream` for required project commands.
32
334. Submit and verify.
34- Submit with `submit_solution`.
35- Track progress with `get_verification_status`.
36
375. Retry loop on failure.
38- Read `get_verification_status` and `get_submission_feedback`.
39- Apply targeted fixes in workspace.
40- Resubmit with `submit_solution`.
41- Repeat until pass or termination condition.
42
436. Close out.
44- On pass, ensure PR/payout path is completed.
45- On unrecoverable/exhausted state, call `release_claim`.
46
47## Required retry behavior
48
49When verification fails and attempts/time remain:
50- Must continue with at least one additional corrective submission.
51- Must prioritize highest-severity actionable feedback first.
52- Must keep diffs scoped to the failing behavior.
53
54Only stop retrying when:
55- verification passes, or
56- attempts are exhausted, or
57- claim expiry/blocker makes completion infeasible.
58
59## Tool guidance by task
60
61Bounty and claim lifecycle:
62- `list_bounties`, `get_bounty_details`, `claim_bounty`, `get_claim_status`, `extend_claim`, `release_claim`.
63
64Workspace development:
65- `workspace_status`, `workspace_read_file`, `workspace_batch_read`, `workspace_edit_file`, `workspace_apply_patch`, `workspace_write_file`, `workspace_batch_write`, `workspace_exec`, `workspace_exec_stream`, `workspace_shell`.
66
67Verification and iteration:
68- `submit_solution`, `get_verification_status`, `get_submission_feedback`, `list_my_submissions`.
69
70Infra diagnostics:
71- `workspace_startup_log`, `check_worker_status`, `workspace_crash_reports`.
72
73## Common failure patterns and responses
74
75- `verification queued` for too long:
76 - Check worker health/role and queue consumption via `check_worker_status` and logs.
77
78- Workspace provisioning stuck:
79 - Use `workspace_startup_log`; reprovision/reclaim if session is unavailable.
80
81- Diff noise in submission:
82 - Keep changes minimal and aligned to task; avoid unrelated file churn.
83
84- Test-gate failure with feedback:
85 - Treat feedback as source of truth; patch and resubmit.
86
87## Stop conditions
88
89Success stop:
90- Verification status is pass and PR/payout path is complete.
91
92Give-up stop:
93- Repeated failures with no viable correction inside remaining attempts/time.
94- Explicitly release claim with `release_claim`.
modbender