Omarchy as an Agent Launch Surface: Designing Around 429s Without Hiding Them
说明与用途
通过包装脚本记录路由并阻止 429/504 自动重试,确保代理 CLI 启动安全,防止文件变更被无声复制。
问题
Unhandled HTTP 429 or 504 responses during agentic runs can silently corrupt local state by replaying mutating actions after rate limits are hit.
结果
The wrapper prevents silent corruption by stopping automatic retries on 429/504, providing an audit trail and deterministic behavior for file‑mutating agents.
工作流
- 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.
证据
Drop the script directly onto your PATH and route your agent CLIs through it:
The core architectural invariant is the final catch‑all branch: no automatic replay.
- 记录日期: 2026-09-16T23:45:40.625Z