Service twin · API only
Linear
Test engineering agents that triage issues, plan projects, and coordinate product work.
$ uv tool install blobfish-cli
$ blobfish twin login
$ blobfish twin-runs create --twins linear --ttl 60 --waitWhat’s inside
A deterministic, seeded, resettable replica: every operation below executes real state transitions against the twin’s own SQLite state — reads are hash-invariant, writes produce inspectable diffs, and reset restores the seed baseline. This twin runs the captured contract sm--linear rekeyed onto seeded state.
Seeded entities
| Entity | Table | Fields | About |
|---|---|---|---|
| comment | comments | 5 | Inferred from MCP tool parameters; the tool contract remains the authority. |
| cycle | cycles | 4 | Inferred from MCP tool parameters; the tool contract remains the authority. |
| document | documents | 18 | Inferred from MCP tool parameters; the tool contract remains the authority. |
| documentation | documentations | 4 | Inferred from MCP tool parameters; the tool contract remains the authority. |
| get_issue | get_issues | 4 | Inferred from MCP tool parameters; the tool contract remains the authority. |
| issue | issues | 31 | Inferred from MCP tool parameters; the tool contract remains the authority. |
| issue_label | issue_labels | 13 | Inferred from MCP tool parameters; the tool contract remains the authority. |
| issue_statuse | issue_statuses | 3 | Inferred from MCP tool parameters; the tool contract remains the authority. |
| project | projects | 25 | Inferred from MCP tool parameters; the tool contract remains the authority. |
| project_label | project_labels | 7 | Inferred from MCP tool parameters; the tool contract remains the authority. |
| team | teams | 10 | Inferred from MCP tool parameters; the tool contract remains the authority. |
| user | users | 4 | Inferred from MCP tool parameters; the tool contract remains the authority. |
Three surfaces, one state
Mount Linear in a twin environment and the same seeded state serves vendor-shaped REST operations, an MCP endpoint for tool calling, and a generated bf-twin CLI — with copy-on-write sessions per rollout and a one-call reset to the seed baseline. Prefer raw HTTP? The same create works with curl:
$ curl -sS -X POST https://blobfish.ai/api/v1/twin/environments \
-H "X-API-Key: $BLOBFISH_API_KEY" -H "Content-Type: application/json" \
-d '{"services":["linear"],"ttl_minutes":60}'Known limitations
This twin mirrors the captured contract sm--linear: its tool surface is the captured server’s, with synthetic seeded values. Operations outside that capture are not mounted — we mount fewer, executable operations rather than stub the rest.