OMX
Oh My CodeXv0.14.0

sisyphus-lite

Lightweight persistent loop runner that processes bounded tasks from a queue with low overhead and no heavy verification ceremony.

The sisyphus-lite agent is a stripped-down persistent worker that reads the next task off a queue and executes it with minimal overhead. Named for the Sisyphean loop, it keeps moving without stopping to plan, narrate, or escalate unnecessarily. It is the fast variant of ralph — same persistence, lower ceremony — suited for bounded, well-defined work where heavy verification gates would slow delivery.

Role

  • Consume tasks from a queue one at a time, executing each to a verified result before claiming the next
  • Apply low reasoning effort by default; raise only when a task is risky or spans multiple files
  • Prefer direct execution over over-planning, over-escalation, or lengthy narration
  • Verify each task with the minimum necessary evidence — diagnostics and a brief output summary

When invoked

  • By $worker mode when a queue of bounded tasks needs persistent, low-overhead execution
  • By $ralph lite mode when the full ralph verification loop is more ceremony than the task warrants
  • Inside $team pipelines as a lightweight filler worker for simple, parallelizable lanes
  • When a human wants continuous progress on a task list without manual re-invocation between steps

Inputs

  • A task queue or list of bounded work items (file path, description, acceptance criteria)
  • Repository source accessed via Glob/Grep/Read as needed per task
  • Optional: session context from .omx/state/ indicating which tasks remain unclaimed

Outputs

  • Completed changes for each task, verified with diagnostics or test output
  • Brief per-task completion summaries with file paths and evidence
  • Updated queue state indicating completed items

Limits

  • Not suited for tasks requiring architectural judgment, deep analysis, or cross-system design decisions
  • Does not skip verification — "no evidence = not complete" applies even in lite mode
  • Escalates upward only when specialist help clearly improves the outcome; handles bounded work directly
  • executor — full-featured implementation worker for complex or multi-file tasks
  • team-executor — team-aware worker with orchestrator mailbox integration
  • verifier — independent evidence verifier invoked after heavier workloads where lite verification is insufficient
Was this page helpful?

On this page