Use cases

Where local state
breaks down.

These aren't edge cases. They're the normal shape of real agent workflows — and local state fails at every one of them.

Use case 01 — you come back tomorrow

You leave Friday. The agent starts from scratch Monday.

Without shared state, Monday's session has no idea what Friday's session found. Claude Code re-investigates the same bug. With Threadron, it reads the work item and continues — no re-investigation, no lost context.

      Session 1 — Claude Code
// Session 1: identifies root cause, updates structured state
PATCH /v1/tasks/t_4a2
{
  "current_state": "Race condition in pool acquire. Fix is a mutex on the acquire path.",
  "next_action": "Write concurrent request tests, then open PR",
  "confidence": "high"
}

// Attaches the branch as a first-class artifact
POST /v1/tasks/t_4a2/artifacts
{ "type": "branch", "name": "fix/connection-pool-race" }

// Session ends. Context is fully preserved.
    

      Session 2 — New Claude Code session
// New session checks in — reads structured state immediately
GET /v1/tasks/t_4a2

// Returns: current_state, next_action, full event history, branch artifact.
// Agent knows exactly what to do. Zero re-investigation.
    

"I start a new Claude Code session Monday morning. It reads the work item, sees that the race condition was already diagnosed Friday, checks out the branch, and writes the tests. It didn't need to re-read a single line of code to understand what was happening."

Use case 02 — you switch agents

Claude Code fixed it. Hermes has no idea.

Claude Code diagnoses the bug and writes the fix. Hermes is supposed to deploy it — but Hermes has never seen the work. Without shared state, every handoff is a full re-briefing. With Threadron, the handoff is structured state: current_state, artifacts, full event history.

Claude Code investigates

OBSERVER · EVENT: OBSERVATION

Reads the failing test, traces the stack, identifies root cause. Updates current_state. Adds an observation event with findings. Releases the item.

OpenClaw implements

IMPLEMENTOR · EVENT: HANDOFF

Claims the work item. Reads current_state and observation events. Implements the fix with full context of what was already tried. Opens a PR. Attaches it as an artifact.

Hermes reviews

REVIEWER · EVENT: DECISION

Reads the full event history — investigation, fix, PR. Adds a decision event: approved or changes requested. State transitions automatically on approval.

"OpenClaw didn't need to re-read the codebase to understand what was failing. It read the structured state and observation events from Claude Code's session and started implementing in under 30 seconds."

Use case 03 — you switch devices

You debug on your MacBook. Your desktop doesn't know.

You start debugging on your MacBook. You switch to your desktop to continue — but the context is gone. With Threadron, state is in the cloud. Any agent on any device picks up exactly where the last one left off. No collisions. No duplicate work.

Agent: Claude Code

Fix connection pool

Claimed. Writing concurrent request tests, opening PR

Agent: OpenClaw

Rollback test suite

In progress. Writing migration rollback coverage

Agent: Hermes

Staging OOM crashes

Blocked. Needs prod logs to continue investigation

"Each agent polls for unclaimed work from the cloud. Claim semantics mean they can't accidentally start the same item. I check the board once a day and see exactly what each agent did and what's blocked — from any device."

Cross-agent view

The full picture. From anywhere.

Every agent's execution state in one place — accessible from any device, any session. Who's doing what. What's blocked. What needs a decision.

Project: api-v2 — current state

typeitemagentstatusclaim

work Fix connection pool race condition claude-code IN PROGRESS claimed

work Write migration rollback tests openclaw PENDING —

work Investigate staging OOM crashes hermes BLOCKED needs prod logs

work Deploy v0.2 to production claude-code PENDING needs approval

Cross-device continuity · Agent handoff · Multi-agent coordination · Claim semantics · Persistent state · Artifact tracking · Event history · No collisions · Cross-device continuity · Agent handoff · Multi-agent coordination · Claim semantics · Persistent state · Artifact tracking · Event history · No collisions ·

Stop the context loss. Connect your agents.

Persistent, shared state — cloud by default. Get started in under five minutes.

Get Early Access

Where local state breaks down.