OpenHands loop detection

Review OpenHands-style agent loops without reading the task content.

Paste structural events from an OpenHands-style run. CAUM checks whether actions, observations, retries, or status transitions are cycling across the session.

local preflight zero upload observe-only not a truth score

The problem

Open tool-using agents can alternate between action and observation for long stretches. CAUM focuses on the structural trajectory: repeated state signatures, pattern cycles, and low work conversion.

Use CAUM to separate benign long-running work from repeated structural pressure that deserves review.

Useful event fields

You do not need prompts, source code, documents, customer messages, or private payloads. Structural fields are enough for a first check.

  • action/observation event
  • tool family
  • status
  • state_id or hashed observation class
  • latency/tokens/cost if available

Example shape

[{"event":"action","tool":"shell","phase":"execute","status":"error","state_id":"same_command_error"},
 {"event":"observation","tool":"runtime","phase":"observe","status":"ok","state_id":"same_observation"},
 {"event":"action","tool":"shell","phase":"execute","status":"error","state_id":"same_command_error"}]

What the free check returns

  • events analyzed
  • exact cycle coverage
  • structural pattern cycle coverage
  • work-yield proxy
  • burn proxy
  • trace quality

Run the free local check first.

Paste a trace into CAUM Loop Check. If it shows repeated structure, run a full receipt or put the recurring workflow into CAUM Live.

CAUM observes structure only. It does not judge correctness, read private content, block agents, or promise savings.