Agent Autoloop Runs Claude Code and Codex Without an Open Terminal
Agent Autoloop is a self-hosted middleware that drives CLI agents like Claude Code and Codex in the background. Install with a single curl command on Mac or Linux; no cloud server or public port required.
Takeaways
- Agent Autoloop is a self-hosted middleware that drives CLI agents like Claude Code and Codex in the background.
- Install with a single curl command on Mac or Linux; no cloud server or public port required.
- Zero-dependency 1,650-line kernel with event sourcing, parameterized prompts, and a TTL-style hop-count breaker.
- Waiting agents exit the process entirely, so pending decisions cost no tokens while cards sit in Feishu, Slack, or desktop notifications.
- Benchmarks: 88 ms cold start, 2394 writes/sec, 1.82 ms p99 dispatch, 60 MB idle RSS on Apple M5 Pro.
- Repo: github.com/KKKKhazix/agent-autoloop , MIT-licensed, around 1,900 GitHub stars.
Agent Autoloop is an open-source TypeScript project for running command-line coding agents in the background. A local scheduler dispatches tasks to tools such as Claude Code and Codex, then sends an approval request through Feishu, Slack, Discord, DingTalk, WeCom, or desktop notifications when a task requires human input.
The repository currently has 4 stars. Its architecture separates a small scheduling kernel from replaceable plugins for event sources, agent adapters, notification channels, and CI/CD delivery.
Why terminal agents stall
Interactive coding agents usually depend on an open terminal and a person available to answer questions. Closing the session or leaving a prompt unanswered can interrupt the task.
Agent Autoloop turns each task into a bounded invocation called a round. The agent starts, processes the available work, records its final reply, and exits. A later event or human response can resume the original conversation through the relevant adapter.
- Local deployment: The project supports macOS and Linux without requiring a hosted control plane or public port.
- Command adapters: Any CLI tool that accepts a prompt and returns a final response can be configured through a command wrapper.
- CLI operations: There is no web dashboard. A status command reports progress.
- Existing credentials: Agents use the authentication already configured in their respective CLI tools.
From trigger to resumed session
- An event such as a cron trigger, GitHub issue, or production alert enters the scheduler in a normalized format.
Reporting is indexed from AlphaSignal. Rights remain with the original publisher and cited sources.
Read original report
