Omarchy as an Agent Launch Surface: Designing Around 429s Without Hiding Them

Description and use

Secure agent CLI launches with a wrapper that logs routes and blocks automatic retries on 429/504, preventing silent data corruption.

Problem

Unhandled HTTP 429 or 504 responses during agentic runs can silently corrupt local state by replaying mutating actions after rate limits are hit.

Outcome

The wrapper prevents silent corruption by stopping automatic retries on 429/504, providing an audit trail and deterministic behavior for file‑mutating agents.

Workflow

• 1. Create a bash wrapper script that logs agent name, route, and exit status.
• 2. Install the wrapper to ~/.local/bin/agent-run and make it executable.
• 3. Route agent CLI commands through the wrapper, e.g., agent-run aider --model "$AIDER_MODEL". 4. The wrapper exits immediately on non‑zero status, logging the event. 5. Inspect the log to verify no dirty files were committed and decide whether to retry or switch models.

Evidence

Drop the script directly onto your PATH and route your agent CLIs through it:

Source

The core architectural invariant is the final catch‑all branch: no automatic replay.

Source