Skip to Content
Architecture

Architecture

AgentLoop is a desktop application backed by a local background daemon. The desktop app is the user-facing surface; the daemon runs the agents, schedules work, and persists state. Each agent runs as its own process so the system can do real parallel work without one agent blocking another.

Components

Desktop App

The desktop app is an Electron-based GUI that hosts:

  • A chat surface for natural-language interaction
  • A panel workspace for visual tooling (kanban, DAG, agent workbench, etc.)
  • A sidebar for project navigation and chat threads
  • A system tray integration so the app keeps running in the background after you close the window

The app does not run agents directly — it talks to the daemon over local IPC and renders whatever the daemon reports.

Background Daemon

The daemon is the runtime. It persists tasks and history locally, schedules what to work on next, and spawns agent processes. It starts automatically when you open the app and continues running in the background even after you close the window.

Agents

Each agent runs in its own OS process and has its own behavior tree — a workflow definition that mixes deterministic logic with controlled LLM steps, so agent behavior is reproducible and inspectable.

See Agents for the full lineup.

Kanban Pipeline

All work flows through the kanban board — tasks move through Todo → In Progress → Review → Done, with a separate Blocked lane for work that can’t proceed. Each lane has agents that act on tasks landing there. Tasks move automatically as agents finish their work, but you can also drag tasks manually if you want to override.

See Kanban Board for details.

External Integrations

IntegrationPurpose
JiraBidirectional task sync, sprint management
GitHubPR creation, branch management
MCPModel Context Protocol — connect external tools to your agents

See Integrations for setup.

Last updated on
AgentLoop — Multi-agent loops you can see and control