Ways in
Coding agents
Let Claude Code, Codex or Cursor pick up a fault TrialONE found, and report the repair back.
TrialONE serves an MCP endpoint on the website. A coding agent connected to it can list your issues, read one with its full recipe, claim the repair, and ask the robot to verify it. You can simply say:
Say to your agent
Fix the newest open TrialONE issue and tell TrialONE when you are done.
Connect
Create an agent key in the app under Settings, Coding agents. The page shows the block for each agent with the key filled in. Agent keys are separate from robot keys: they read issues and report repairs, and cannot post runs.
Claude Code
$ claude mcp add --transport http trialone https://trialone.dev/api/mcp --scope user --header "Authorization: Bearer <key>"Codex
[mcp_servers.trialone]url = "https://trialone.dev/api/mcp"http_headers = { Authorization = "Bearer <key>" }
Cursor
{ "mcpServers": { "trialone": { "url": "https://trialone.dev/api/mcp", "headers": { "Authorization": "Bearer <key>" } } }}
Claude Desktop only starts local servers. The settings page shows the mcp-remote bridge for it, and the same form works for any client with that limit.
Tools
| Tool | What it gives the agent |
|---|---|
list_issues | What TrialONE found, newest first. |
get_issue | The recipe: symptom, cause, numbers, files and lines, acceptance criterion. |
claim_repair | What the agent changed; the issue goes to In repair. |
request_verification | The robot checks its newest recording. |
check_repair | Fixed and proven, looks fixed, waiting, or came back. |
What an agent cannot do
No tool marks an issue resolved. The agent claims the repair; the robot's next recording decides. A passing verification closes the issue, and the fault coming back reopens it.
An issue routed as physical needs a person at the machine: a part, a connector, the mechanics. An agent should not change code to make such a symptom quieter.
Without MCP
trialone fix hands a finished diagnosis to a coding agent on the same machine. It shows the exact command, the files the recipe names and the verdict, and asks before anything runs.
$ trialone fix <diagnosis.json>Something missing or wrong here? Tell us.