ARKONE

Susan

See every agent on one board.

Your Claude Code sessions each keep a todo list. Susan reads all of them and shows you the lot.

Read the docs

01 · This is the whole product

$ susan boardDEMO
An example board. Struck through is done, ▸ is now.

02 · You already write the list

Claude Code keeps a todo list inside every session. Susan reads it off disk. Nothing to maintain.

  1. 01

    Your agent writes

    Every session keeps its own steps as it works.

  2. 02

    Susan reads

    From the transcript on disk. She never writes back to it.

  3. 03

    You see all of them

    One board. Every session, every step, live.

03 · What she shows you

One board. Everything your agents are doing, and everything they already did.

  • Every session on one board
  • Each agent’s own todo list
  • What it is working on now
  • Conflict warnings before you write
  • Search every plan you ever ran
  • History past 30 days
  • Live terminal board
  • Browser board for your phone
  • Status line that never scrolls
  • /susan inside any session
  • Hand work to another project
  • Silent when you work alone
  • @sales — an agent per domain

Get started

04 · Claude Code forgets after 30 days

Claude Code forgets after 30 days

Check it yourself. Nothing on this machine is older than four weeks. Everything before that is already gone, on every machine.

Susan copies the plans out and keeps them. She cannot recover what has gone — only stop the next month going too.

893 MBindexed in 1.5 seconds500sessions searchable
Sessions still on disk by age, counted 9 Aug 2026.
22 days5
23 days5
24 days4
25 days1
26 days17
27 days1
28 days1
29 daysgone
30 daysgone
a yeargone

Sessions run back to day 30, then stop dead. Not a fade — a cliff.

05 · Ask what you were doing

Every plan any session ever wrote, searchable by the words in it. Dated, across every project.

06 · Stop retyping the context

Name a domain, point at its folders. @sales opens already knowing the campaign files and every decision past sessions made in them.

$ susan agent create sales plans/dubai-campaign plans/fly91-outreach

@sales will point at:

plans/dubai-campaign → STATUS.md first

plans/fly91-outreach → plan.md first

✔ Type @sales in a new session to use it.

The agent file is a router, never a copy — your documents stay the only source of truth. What @sales remembers are the decisions of past sessions in those folders, each with the quote it came from.

07 · Why you cannot see it now

01

The list gets buried

Your agent writes a todo list, then 400 lines on top of it. To see it again you scroll up.

02

Four windows, one you

You cycle through terminals reading the last 20 lines of each, rebuilding what the machine already knows.

03

Six hours, wrong direction

An agent misreads the task in minute three. Nobody is watching the plan. You find out at the end.

08 · Measured, not claimed

Measured, not claimed

1.5s

to index 893 MB

0.3ms

per edit hook

~60

tokens a request

0

native deps

09 · Fair questions

Does it send my data anywhere?
No. One local file. No daemon, no port, no network.
Will it break my sessions?
Every hook exits zero. The edit hook gives up after 50ms.
Won’t Anthropic ship this?
Partly did. Not the plans on one screen, searchable past 30 days.
Does it manage worktrees?
No. She watches. She does not run your sessions.
I run one session at a time.
Then she prints nothing — until you need last month back.
I already use Crystal.
Keep it. Her history covers every transcript on the machine.

10 · Two lines and it stops happening

Two lines and it stops happening

Free and MIT. Node 22.5+, macOS and Linux, WSL on Windows.

GitHubnpm