Activity
01
First app
6/6DonePut threads and their terminals in one window.
Updated
1. First app
Steps 6 of 6
- done: Terminals in the app
- done: Tabs, sidebar and browser dock
- done: To-do ledger and PR cards
- done: A view of each thread
- done: Threads keep running when the app closes
- done: Installed on the desktop
Done when The app is installed and running on the desktop.
Updates
First build: one window with terminals, tabs and a sidebar.
Settled
- Threads outlive the appClosing the app leaves them running. Opening it picks them up again.
02
Pages
6/6DoneGive each kind of work its own page.
Updated
2. Pages
Steps 6 of 6
- done: Home, the dashboard
- done: Ledger page
- done: PR board
- done: Usage limits page
- done: Systems page
- done: Keyboard control throughout
Done when Home and the main pages are in the app.
Updates
Home, the ledger and the PR board went in, and agents got their own page.
03
Agents in the app
6/6DoneWork with the hub's agents from the same window.
Updated
3. Agents in the app
Steps 6 of 6
- done: Talk to agents
- done: Read every conversation
- done: Pick a model per conversation
- done: Scorecard for agents
- done: An inbox for what's waiting
- done: Tie a conversation to a project
Done when A conversation with an agent runs from the app.
Updates
A conversation with an agent can now be tied to a project from the message box.
Settled
- InboxIts own page with a count in the nav, not a panel on Home.
04
Daily use
7/7DoneMake it the app to work in all day.
Updated
4. Daily use
Steps 7 of 7
- done: One-click updates
- done: Viewer beside the thread
- done: Tabs beside each thread
- done: Terminal fonts and copying
- done: Weekly usage charts
- done: Star a thread to keep it on top
- done: Side browser pane
Done when Updates, the viewer and the browser pane are all in.
Updates
A side browser pane opens previews next to the thread.
Weekly usage charts, with a line for the ideal pace.
A viewer beside the thread for files and transcripts, tabs in the side column, and one-click updates.
Settled
- UpdatesA new build waits for a click. Nothing restarts on its own.
05
Less to read
5/5DoneCut the words on screen without losing the information.
Updated
5. Less to read
Steps 5 of 5
- done: Explanations move into cards
- done: Tighter thread strip
- done: Freshness shown as dots
- done: Trims across the pages
- done: A switch for legends and notes
Done when All the batches are in.
Updates
Less to read: explanations moved into cards, and a switch brings legends and notes back.
Settled
- ExplanationsLegends and method notes are off by default, behind a switch.
06
Two screens
6/6DoneFix what showed up once the app ran on a second, smaller screen.
Updated
6. Two screens
Steps 6 of 6
- done: Hide the side column
- done: Terminal size follows the screen in use
- done: Show why a thread failed to start
- done: One build with all three
- done: Fit a small screen at any zoom
- done: Thread header can sit on one line
Done when All three fixes are in a build.
Updates
The small-screen fit went in: the app fits at any zoom, and a thread's header can sit on one line.
All three two-screen fixes shipped in one build, including the one that says why a thread failed to start.
Two fixes built and reviewed: the side column can hide, and a shared terminal takes the size of the screen in use.
Settled
- Small windowsWith no room left, the side column moves under the terminal. It stacks and stays visible.
07
Backlog
0/5LaterWork that's on the list, with no date.
1 to decide
7. Backlog
To decide
- Remaining notesWhether a few intros and notes also move behind the switch.
Steps 0 of 5
- Say why a terminal closed
- Keep Home's thread list to one line
- Same freshness dots on the Systems page
- Agents use the browser pane
- Try the new visual language in the app
Done when Each item is done or dropped.
08
Reliability
8/8In progressKeep threads and the app going when something fails underneath them.
Updated
8. Reliability
The refined Roster sketch of a thread: the roster on the left, the terminal with a question docked on its edge, the thread's dossier on the right Done when The second set of fixes is live.
Steps 8 of 8
- done: Fix for a rare freeze
- done: Failure hunt in a sandbox
- done: Sixteen fixes reviewed and live
- done: The part that keeps threads alive restarts by itself
- done: Starts cleanly in more cases
- done: Next set landed
- done: Desktop app on the new build
- done: Mac app on the new build
Updates
New look for the app chosen: Roster. Threads read as a roster (state, last tool call, account, context), the Inbox as workspace lanes, a thread as its dossier beside the terminal. Its first kit parts are built and in review: frame, title and status bars, terminal frame, roster, dossier, ask and kit cards, lanes. Not in the app yet.
When a terminal's screen model has to be rebuilt, it now keeps whether the program had bracketed paste on, so an answer signed on the phone goes into that thread at once rather than waiting for typing there.
On the phone, a swipe in a terminal now moves the lines as far as the finger, and a flick carries on and slows to a stop the way a list on the phone does; a tap stops it. Before, a swipe in a full-screen program moved about a third as far and stopped dead.
20 older
A thread's screen model no longer breaks when the phone takes and gives back its size, and one that fails is rebuilt on its own, so that thread's asks don't stay stuck until a restart.
Threads started from the command line now open at the PC's pane size: the app resizes them in the background, so switching to one no longer shows a narrow screen being redrawn.
Shipped the Inbox by workspace to the PC, Mac and phone: a section per workspace with its count, chips to show one workspace, and answered asks and ran kits moved to a Handled section out of the count.
The Inbox on the PC and the phone is now split by workspace, with a chip to show just one. Answered questions and scripts that already ran move to a Handled section at the end. Built and reviewed, waiting to ship.
When an agent asks the owner a question, he can now add a note of his own to the option he picks, or send just a note when none of the options fit. It works on the PC and on the phone, and the note reaches the agent in the same typed turn as his answer.
The work built on Nov 19 went live on the workstation the same day, and the PC app took its update on Nov 20: sessions message each other by address, questions for the owner come up as cards in the Inbox and beside each thread, Codex and Antigravity sessions run as peers, and the rail shows the sessions each thread started.
Codex and Antigravity sessions as citadel bus peers is ready to merge: four review rounds closed, and live runs show both taking work from a lead thread and answering back.
On the PC, a thread's open questions for you now show in its right panel, beside the Viewer, with the same answer buttons as the Inbox; a new one comes up on its own for the thread you're looking at. The phone keeps its Inbox tab. Separately, teammates left over from before a session was resumed no longer show as running in the session tree.
Codex and Antigravity sessions can now run inside citadel as full peers on its message bus: a thread starts one, hands it work and gets the answer back, and the owner can read it and type into it from the session tree. Built and tested against real runs; not deployed yet.
Citadel's sessions can now ask the owner a question with options from inside their work. It shows up as a card in citadel's own Inbox on the PC and the phone, and his tap goes back into that session as his own typed answer. Built and tested; it goes live with the next deploy.
Threads in the rail now fold out the sessions they started: Claude subagents, Codex runs and Antigravity runs, each with its state and how long it ran. A Codex run's whole session opens in the Viewer beside its thread, as a Claude transcript does. Built and reviewed, waiting to ship.
Citadel's sessions can now message each other by address through the daemon instead of by Claude Code's peer names: news waits for one digest, real requests go straight in, and a lead can stop a session's running command. A finished Codex or agy run now wakes the session that started it. Built and tested; it goes live with the next daemon deploy.
The citadel daemon now nudges a session that has gone quiet while waiting on its own background work, so tests and workers that finish no longer leave the session silently stalled.
Starting a new thread can now pick which Claude account it runs on, the way resuming one already could: from + new thread in the app, on the phone, and from the command line. Live on the workstation and the phone; the desktop app picks it up at its next Restart to update.
Codex and Antigravity runs now show in the app beside Claude Code threads, with their own usage and limits, and both get the same standing rules from one source. One list now keeps every allowance, credit and reset across the accounts, with warnings before anything lapses.
Ready for review, not shipped yet: citadel now shows Codex and Antigravity runs under the agent thread that started them, splits usage by provider, keeps one list of every quota, credit and reset with warnings before anything lapses, and gives Codex and Antigravity the same standing rules as the Claude sessions from one source.
On a branch, not shipped yet: citadel now notices Codex runs and ties each one to the agent thread that started it, so a thread can show it's using Codex right now. Next: what Codex uses joins citadel's usage numbers, split by provider.
The bottom bar has a shell button for the workspace on screen, and a thread's status in the list now catches up after a reconnect instead of going stale. Restarting the daemon no longer interrupts the Mac app.
The second set of reliability fixes landed after a full round of tests. The workstation and the desktop app run them, and the app now starts cleanly in more cases.
Sixteen reliability fixes went live after a long round of testing. No work was lost under load, and the part that keeps threads alive now restarts by itself.
By the numbers
- Pages
- 10
- Tabs beside a thread
- 6
- Terminal fonts
- 9
- Test files
- 159
- Commits
- 565
- Last on main
- Nov 20
Counted from the code, as of
Every update
New look for the app chosen: Roster. Threads read as a roster (state, last tool call, account, context), the Inbox as workspace lanes, a thread as its dossier beside the terminal. Its first kit parts are built and in review: frame, title and status bars, terminal frame, roster, dossier, ask and kit cards, lanes. Not in the app yet.
8 ReliabilityWhen a terminal's screen model has to be rebuilt, it now keeps whether the program had bracketed paste on, so an answer signed on the phone goes into that thread at once rather than waiting for typing there.
8 ReliabilityOn the phone, a swipe in a terminal now moves the lines as far as the finger, and a flick carries on and slows to a stop the way a list on the phone does; a tap stops it. Before, a swipe in a full-screen program moved about a third as far and stopped dead.
8 ReliabilityA thread's screen model no longer breaks when the phone takes and gives back its size, and one that fails is rebuilt on its own, so that thread's asks don't stay stuck until a restart.
8 ReliabilityThreads started from the command line now open at the PC's pane size: the app resizes them in the background, so switching to one no longer shows a narrow screen being redrawn.
8 ReliabilityShipped the Inbox by workspace to the PC, Mac and phone: a section per workspace with its count, chips to show one workspace, and answered asks and ran kits moved to a Handled section out of the count.
8 ReliabilityThe Inbox on the PC and the phone is now split by workspace, with a chip to show just one. Answered questions and scripts that already ran move to a Handled section at the end. Built and reviewed, waiting to ship.
8 ReliabilityWhen an agent asks the owner a question, he can now add a note of his own to the option he picks, or send just a note when none of the options fit. It works on the PC and on the phone, and the note reaches the agent in the same typed turn as his answer.
8 ReliabilityThe work built on Nov 19 went live on the workstation the same day, and the PC app took its update on Nov 20: sessions message each other by address, questions for the owner come up as cards in the Inbox and beside each thread, Codex and Antigravity sessions run as peers, and the rail shows the sessions each thread started.
8 ReliabilityCodex and Antigravity sessions as citadel bus peers is ready to merge: four review rounds closed, and live runs show both taking work from a lead thread and answering back.
8 ReliabilityOn the PC, a thread's open questions for you now show in its right panel, beside the Viewer, with the same answer buttons as the Inbox; a new one comes up on its own for the thread you're looking at. The phone keeps its Inbox tab. Separately, teammates left over from before a session was resumed no longer show as running in the session tree.
8 ReliabilityCodex and Antigravity sessions can now run inside citadel as full peers on its message bus: a thread starts one, hands it work and gets the answer back, and the owner can read it and type into it from the session tree. Built and tested against real runs; not deployed yet.
8 ReliabilityCitadel's sessions can now ask the owner a question with options from inside their work. It shows up as a card in citadel's own Inbox on the PC and the phone, and his tap goes back into that session as his own typed answer. Built and tested; it goes live with the next deploy.
8 ReliabilityThreads in the rail now fold out the sessions they started: Claude subagents, Codex runs and Antigravity runs, each with its state and how long it ran. A Codex run's whole session opens in the Viewer beside its thread, as a Claude transcript does. Built and reviewed, waiting to ship.
8 ReliabilityCitadel's sessions can now message each other by address through the daemon instead of by Claude Code's peer names: news waits for one digest, real requests go straight in, and a lead can stop a session's running command. A finished Codex or agy run now wakes the session that started it. Built and tested; it goes live with the next daemon deploy.
8 ReliabilityThe citadel daemon now nudges a session that has gone quiet while waiting on its own background work, so tests and workers that finish no longer leave the session silently stalled.
8 ReliabilityStarting a new thread can now pick which Claude account it runs on, the way resuming one already could: from + new thread in the app, on the phone, and from the command line. Live on the workstation and the phone; the desktop app picks it up at its next Restart to update.
8 ReliabilityCodex and Antigravity runs now show in the app beside Claude Code threads, with their own usage and limits, and both get the same standing rules from one source. One list now keeps every allowance, credit and reset across the accounts, with warnings before anything lapses.
8 ReliabilityReady for review, not shipped yet: citadel now shows Codex and Antigravity runs under the agent thread that started them, splits usage by provider, keeps one list of every quota, credit and reset with warnings before anything lapses, and gives Codex and Antigravity the same standing rules as the Claude sessions from one source.
8 ReliabilityOn a branch, not shipped yet: citadel now notices Codex runs and ties each one to the agent thread that started it, so a thread can show it's using Codex right now. Next: what Codex uses joins citadel's usage numbers, split by provider.
8 ReliabilityThe bottom bar has a shell button for the workspace on screen, and a thread's status in the list now catches up after a reconnect instead of going stale. Restarting the daemon no longer interrupts the Mac app.
8 ReliabilityThe second set of reliability fixes landed after a full round of tests. The workstation and the desktop app run them, and the app now starts cleanly in more cases.
8 ReliabilitySixteen reliability fixes went live after a long round of testing. No work was lost under load, and the part that keeps threads alive now restarts by itself.
8 ReliabilityThe small-screen fit went in: the app fits at any zoom, and a thread's header can sit on one line.
6 Two screensAll three two-screen fixes shipped in one build, including the one that says why a thread failed to start.
6 Two screensTwo fixes built and reviewed: the side column can hide, and a shared terminal takes the size of the screen in use.
6 Two screensA conversation with an agent can now be tied to a project from the message box.
3 Agents in the appLess to read: explanations moved into cards, and a switch brings legends and notes back.
5 Less to readA side browser pane opens previews next to the thread.
4 Daily useWeekly usage charts, with a line for the ideal pace.
4 Daily useA viewer beside the thread for files and transcripts, tabs in the side column, and one-click updates.
4 Daily useHome, the ledger and the PR board went in, and agents got their own page.
2 PagesFirst build: one window with terminals, tabs and a sidebar.
1 First app