Argus icon

Argus

Argus is Scape’s AI orchestrator for recurring coding work, coordinating agents with missions, heartbeats, isolated worktrees, tables, playbooks, and human triage.

Argus

AI orchestration for recurring coding work

Argus is Scape’s session-backed AI orchestrator for managing multiple coding agents. You give it a Mission note describing repositories, tasks, constraints, and priorities; it reads that mission on each pulse, evaluates active child sessions, starts additional sessions when needed, and reports progress.

Each child is a real coding session running in its own git worktree, so parallel tasks remain isolated. Argus can also work with Scape tables and playbooks: tables provide structured project memory, while playbooks can automate recurring checks such as reviewing customer bug reports, application logs, or documentation. The result is a recurring engineering workflow that can continue while the user is away, with explicit controls for timing and delivery mode.

Features

Configurable heartbeat

Set a heartbeat from 1 minute to 4 hours so Argus periodically reads its mission, evaluates child sessions, assigns more work when needed, and reports progress.

Mission-driven orchestration

Write instructions in a Mission note covering repositories, tasks, constraints, and priorities. Notes can reference other Scape objects, including repos, tables, and playbooks.

Parallel worktrees

Spawn multiple real coding sessions in parallel, with each child working in its own fresh git worktree to isolate changes.

Operational modes

Use Watching, Sleeping, or Disabled modes to control whether timed pulses and automated messages reach the manager. Sleeping can still respond to child reports, triggers, calendar events, and scheduled events.

Agent-readable tables

Store structured project data in per-project SQLite tables that agents and playbooks can query and update. Tables support typed columns, natural keys, and Table, Kanban, Gantt, List, and Visual views.

Playbook-based checks

Run playbooks as automation steps, such as checking customer email for bug reports, reviewing application logs, or checking whether website documentation needs updates.

Use cases

  • Parallel feature development

    Give Argus a repository-focused mission and let it break engineering work into parallel child sessions, with each session editing, testing, and potentially creating a pull request in its own worktree.

  • Proactive issue discovery

    Run a recurring pulse that checks application logs and creates tickets for problems that may not generate an explicit error or customer report, giving a human a queue to triage.

  • Customer bug intake

    Use a playbook to inspect customer email for new bug reports, query existing table records for related context, and staff follow-up work with that history available.

  • Persistent project memory

    Maintain a project table for tickets, operational notes, or other structured records so agents can query prior work instead of relying only on the current session.

  • Event-driven follow-up

    Put Argus to Sleep when work is waiting on an external event, then use scheduled events, child reports, triggers, or calendar events to wake it without a continuous heartbeat.

Pros and Cons

Pros

  • Runs multiple coding sessions in parallel while isolating each one in a separate git worktree.
  • Uses a written Mission note as a durable source of instructions and project context.
  • Offers configurable Watching, Sleeping, and Disabled modes rather than a single always-on schedule.
  • Supports structured SQLite-backed tables that agents and playbooks can read and write.
  • Can combine recurring pulses with playbooks, scheduled events, and event-driven wakeups.

Cons

  • The documented product workflow is centered on Scape and requires an active Scape subscription for Argus and tables.
  • The provided source documents macOS download availability, but does not establish support for other operating systems.
  • Automated behavior depends on configuring a Mission note, heartbeat, mode, and any supporting tables or playbooks.

FAQ

How do you set up an Argus?

Argus is created in Scape by selecting Argus from the Creation Picker, naming it, and choosing or creating a Mission note. The Mission note contains the repositories, tasks, constraints, and priorities that guide the manager.

How does Argus scheduling work?

The heartbeat is configurable from 1 minute to 4 hours. Timed pulses occur while Argus is in Watching mode; Sleeping stops timed pulses but still allows incoming events to wake it, while Disabled stops automated delivery.

What can child agents do?

Each child session runs in a fresh git worktree. Child agents can edit files, run tests, create pull requests, and report progress to Argus.

Which agent environments does Argus support?

Argus runs as a session-backed orchestrator using Claude Code, Codex, or OpenCode, whichever is configured as the default harness. The site also lists Scape support for Claude Code, Codex, Copilot, Cursor, and OpenCode.

What platform and account requirements are documented?

Argus ships with Scape and can be downloaded for macOS without an account, credit card, or license key. The documentation states that Argus requires an active Scape subscription; the site offers a seven-day trial, while the pricing page provided is not available.

Quick Facts

Category
Developer Tool
Product type
AI coding-agent orchestrator
Platform documented
macOS
Scheduling
Heartbeat configurable from 1 minute to 4 hours
Execution model
Parallel child sessions in isolated git worktrees
Agent harnesses
Claude Code, Codex, and OpenCode documented for Argus; Scape also lists Copilot and Cursor