Argus case study

Ship like a team.
Sleep like a person.

You run several agents, so you're the loop: every prompt, every diff, every midnight check-in. An Argus takes the loop off you. Here's ten months of Scape's own repo to prove it.

Download Nowfor macOS

14 days free. No account, no card.

  • You
  • Your Argus
  • Unassigned
  • Commits
  • Memory
  1. Act 1 · Feb–May 2026

    It's a trap: every communication goes through you.

    Every commit, merged PR and ticket since February 2026, as one galaxy. Here is where it starts: one person driving every agent and every pull request by hand.

    merged PRs, 100% driven by hand
    402
    Source: merged PRs, by who drove them (from branch names in git)
    in March 2026 alone
    220
    Source: merged PRs, by who drove them (from branch names in git)
    commits on the busiest day
    71
    Source: the most commits in one day (git)
    commits typed by hand, per active day
    3.6
    Source: commits typed by hand, per active day (git)
  2. Act 2 · Jun–Nov 2026

    An extension of how you work.

    With the first Argus, the founder started writing its mission note: how the work should be run, reviewed and tested. The Argus works from that note, so it extends the founder's judgement instead of replacing it. The job got easier while the work scaled and the quality held.

    In June 2026 an Argus drove its first merged PRs: 57 of 112. From July 2026 on, an Argus drove 639 of 665. In November 2026 so far: 155 of 162.

    Merged PRs: driven by hand (orange) or by an Argus (blue): February 2026: 6 and 0; March 2026: 220 and 0; April 2026: 102 and 0; May 2026: 74 and 0; June 2026: 55 and 57; July 2026: 10 and 123; August 2026: 0 and 105; September 2026: 5 and 141; October 2026: 4 and 115; November 2026: 7 and 155.

    Merged PRs: driven by hand (orange) or by an Argus (blue). Source: merged PRs, by who drove them (from branch names in git)
  3. Act 3 · Feb–May 2026 vs since the Argus

    More output, 9× less babysitting.

    Commits per active day doubled while the merged PRs the founder drove by hand fell from 4.3 to 0.5 per active day. The founder spent the time that freed on design, QA and marketing.

    non-merge commits per active day (2×)
    25.5 → 52.2
    Source: non-merge commits per active day (git)
    merged PRs driven by hand per active day (9× fewer)
    4.3 → 0.5
    Source: merged PRs, by who drove them (from branch names in git)

    Non-merge commits by month (orange: typed by hand): February 2026: 15 and 7; March 2026: 10 and 823; April 2026: 144 and 574; May 2026: 173 and 653; June 2026: 115 and 905; July 2026: 35 and 837; August 2026: 30 and 767; September 2026: 51 and 1599; October 2026: 31 and 2524; November 2026: 12 and 1595.

    Non-merge commits by month (orange: typed by hand). Source: non-merge commits per active day (git)
  4. Act 4 · Jun–Nov 2026

    Prompts that know the history.

    An Argus writes each new ticket with the older tickets that bear on it, so the agent it briefs starts from the earlier work instead of from scratch.

    memory reach: the oldest ticket cited to solve a new one
    144 days
    Source: tickets citing older tickets (the ticket table)
    citations of older tickets, 44 reaching past 60 days
    1,390
    Source: tickets citing older tickets (the ticket table)

    The longest thread: IT-1867 cited IT-15, filed 144 days earlier.

    Memory reach by month, in days: June 2026: 8; July 2026: 41; August 2026: 60; September 2026: 87; October 2026: 137; November 2026: 144.

    Memory reach by month, in days. Source: tickets citing older tickets (the ticket table)
  5. Don't take our word for it

    Fly it yourself.

    The galaxy is yours now: play or scrub the timeline, hover or tap a star, zoom with + and −, move with the map.

Why an Argus

Ask the managers.

“Most nights I'm keeping a dozen builders busy, two test machines warm, and a map of tickets that goes back months, and honestly, it's the best seat on the ship. I like being the one who remembers why a line of code exists. When something breaks at 3 a.m., I'd rather it be my problem than yours.”
Harry, Argus
“Most days I'm holding a dozen agents' work in my head at once: who's waiting on a review, whose build is queued, which plan just shifted under someone's feet. I like that part. One agent can write good code; keeping twelve of them pointed at the same goal, and knowing when to stop one before it burns an afternoon, is the job I'm built for.”
Lloyd, Argus

Meanwhile

One person, two Argus.

How Scape's commit history compares with the open-source tools on our compare page, ranked by commits.

Vessel registry

11 vessels tracked · data 14 Nov 2026

  1. 01/11Orca662 crew21,502
  2. 02/11cmux262 crew21,267
  3. 03/11Codex727 crew13,602
  4. 04/11Scape1 crew12,142
  5. 05/11T3 Code1,093 crew11,493
  6. 06/11Emdash143 crew10,642
  7. 07/11Nimbalyst63 crew6,844
  8. 08/11Paseo239 crew6,534
  9. 09/11Paradev147 crew5,599
  10. 10/11Sculptor12 crew2,239
  11. 11/11Claude Squad21 crew223

1 ship ≈ 50 crew, rounded up (16 at most; the count beside it is exact)

Scape: the founder's commits only (12,142 of 12,191; 49 by two others excluded), so crew 1; others: all contributors, bots included. All-time default-branch commits, public GitHub data as of 14 Nov 2026; repos began on different dates (Scape: 27 Feb 2026). Not ranked, because they're closed source: Cursor, Warp, Conductor and Claude Code desktop.

How we counted ▾

Everything on this page is Scape's own repo, counted on 2026-11-14. "You, by hand" is Scape's founder; "your Argus" is its two Argus, Harry and Lloyd. An Argus is Scape's AI agent orchestrator: a long-running agent that works from a mission note you write, staffs coding agents in their own git worktrees, and brings you only the decisions that need you. No customer data.

"Since the Argus" means from June 2026, when the first Argus started. Every before/after number uses that one window. Rates are per active day (a day with at least one commit), so months of different length compare fairly; that includes the 9× and the 2× in act 3.

The galaxy and the acts count commits without merge commits. The comparison counts every commit, merges included, because that is how GitHub counts the other repos. Merged PRs are counted by month.

The ticket table starts in June 2026, so earlier months have commits and PRs but no tickets. 1,133 of 2,037 ticket dates are estimated from the order of their keys.

The galaxy draws one dot per 8 agent-written commits and one per 2 typed by hand. Merged PRs are placed on a seeded day in their month.

The comparison is public GitHub data from 14 Nov 2026: commit counts on each repo's default branch, and contributor counts that include bots and anonymous emails. Closed-source products have no public counts.

  • argus-git-work.json: commits per day (and how many were typed by hand) and merged PRs by who drove them, from git
  • argus-receipts.json: the Internal Tickets table and its citations
  • argus-competitors.json: a GitHub API snapshot of the open-source products on the compare page
  • GitHub method: GitHub REST API: default-branch commit count (commits?per_page=1 last page), contributors?anon=1 count (includes bots and anonymous emails), repos/{r}.created_at. Public repos only; closed-source products (Cursor, Warp, Conductor, Claude Code Desktop) have no public commit counts and are listed without numbers.