aiedwardyi

AgentLoop — Communication skill for Claude Code

Communication community

Local agent orchestration for solo developers running long tasks without babysitting: fresh worker and critic cycles, files as memory, multi-task plans with git checkpoints, a live dashboard, and Chat.

How to install AgentLoop

This entry records only its repository, not the path inside it, so there is no exact command to give. Open aiedwardyi/AgentLoop and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What AgentLoop does

Alternatives in Communication

HolaOS — Open-source agentic workspace enterprises can make their own 10.9k ★
Claude Code Remote — Control Claude Code remotely via email 1.2k ★
Agentrove — A self-hosted web and macOS desktop app for Claude Code and Codex, powered by ACP 270 ★

README

AgentLoop

Self-improving fresh-context loops for coding work you can watch.

![AgentLoop dashboard showing a worker and critic loop](docs/dashboard.png)

[Watch the demo](https://youtu.be/4zRdMMzh3C8) | [Try the replay](https://agentloop-replay.vercel.app) - a real recorded run in the live dashboard

What it is

Plan a goal in Claude or ChatGPT, then let it rip. AgentLoop is a local orchestration daemon for coding agents: each cycle starts a fresh worker, work carries forward in project files, a fresh critic enforces your rubric, and the whole run is watchable on a local dashboard.

Codex CLI and Claude Code both run as engines. Pick one per loop from the dashboard, or per task through the bridge.

AgentLoop is for solo developers who run long agent tasks across multiple projects and cannot supervise every session.

It exists because running coding agents by hand means shuttling plans between a chat and a terminal all day, and quality slips the moment you stop watching.

Your standards live in GUIDELINES.md and the critic enforces them every cycle, so you supervise the work without babysitting it.

Why sequential fresh-context

Long-running chats collect stale assumptions and irrelevant context. That is context rot. AgentLoop starts a new engine process for every worker and critic session, so no prior chat history follows them. The durable context is the project itself plus concrete critic fixes. That keeps a loop bounded, easier to leave unattended, and less likely to spend tokens re-reading an ever-growing conversation.

A loop is intentionally sequential. Independent queued tasks can run up to `maxConcurrent`, but one loop does not create a parallel swarm that races across the same project.

Claude or ChatGPT -> MCP bridge -> daemon -> worker/critic cycles -> dashboard

How it works

Dispatch sends one one-shot task to POST /api/dispatch. Its file moves from pending to running to done, with a transcript and dashboard cancellation.