Rung 1 · todayThe agents you already pay for
The agents you already pay for
aegis calls no model. Each session is the vendor's own command-line agent, claude, opencode or codex, running under your account: a Claude plan, OpenCode Go or Zen, a ChatGPT plan, or any provider OpenCode or Codex reaches. aegis holds no API key, and your prompts go from the CLI to the vendor as they would from a terminal.
Sessions of every harness share one tab bar, each with its own model, effort and permission. The panel shows the quota the session spends: this one runs on OpenCode Go, so it shows Go's three windows.
aegis calls no model and holds no key: each session is the vendor's own CLI. Harness versions outside the tested range are flagged before a session starts.
Every subscription's quota, and its pace
The Fleet band reads each subscription you use: Claude's 5-hour and weekly windows, OpenCode Go's 5-hour, weekly and monthly ones. A gauge shows the share spent, a tick for how much of the window has gone, and where it lands at the reset if you keep this pace.
aegis usage turns the transcripts aegis keeps into what the work cost, by month, weekday, session or repo.
Fold the work, keep the conversation
z folds each stretch of tool calls and notes between two messages into one line that says what it holds. Press it again and only your messages and the agent's replies remain. Open a line to see that stretch alone.
Press the fold button over the message box, or a folded line.
Ten themes
Ink is the warm dark palette of the terminal app aegis used to be. Logbook is a daylight lab notebook with times in the margin. The other eight each commit to one idea: Electric lights the thread like a circuit trace, Phosphor is a green CRT, Blueprint a drafting sheet, Amphora black-figure pottery, Riso a two-ink print, Solari a departure board, Aizome indigo cloth stitched in white, and Poster a brutalist print.
Press the theme in the window's top bar.
Rung 2 · one agentAn agent that does more than chat
A plan you can see, and waits that cost nothing
In any harness, the agent keeps its plan in the panel, one step marked doing, each with its time. To wait on CI, a build or a download it arms a monitor with a done condition and a progress count, ends its turn, and is woken when the condition holds.
Monitors run on the server, so a wait spends no tokens. A stalled monitor wakes its owner.
A page instead of a paragraph
When a reply in prose would lose its structure, the agent writes a page. artifact_create gives it a working skeleton, the agent edits the HTML, and artifact_send runs the page in a hidden frame in your browser before you see it. A page that throws goes back to the agent with the error, so you only ever see one that starts.
Pick a layout in the window.
The page answers the agent
You click, drag, pick or type, and the page sends the result back. A submit wakes the agent and folds the page to one line. An event wakes it and leaves the page live. A state write waits until the agent reads it. The agent can push new state or a new version into a live page.
A page can also stay: docked beside the transcript, arranged in columns, moved to a second browser window, or shown as tabs on a phone, so the workplace grows with what its agents build.
Talk to it, and send it files
Dictate into the composer and the words appear while you talk; the agent is told the message was dictated. Drop, paste or pick files to attach them to a message.
Dictation runs in your browser. Attachments are stored with the session.
Files that preview where you are
An agent sends you a file, or a set of them, as one card: a rendered page, a PDF, an image, a diff you swipe through. Open shows it inside aegis; Alt+O opens any file on the server, and the Files view edits it.
A path in a reply opens its file with one click.
One tap to answer
An agent ends each turn by saying how it ended and may offer up to three replies, which you send with one tap. /model, /effort and /permission switch a running session, and / opens a menu that completes aegis's commands and the agent's own. Alt+M dictates into the box, transcribed in the browser.
Rung 3 · many projectsSeveral projects at once
A Fleet that says who needs you
Each tab and card carries one of six marks: working, needs you, error, review, waiting or done. The Fleet puts the sessions that block on you first, oldest wait on top, and Alt+J goes to the one that has waited longest. Each card shows the plan as a bar with an estimate of the work left.
Push notifications reach a phone with aegis closed.
A panel that stays out of the way
The session panel keeps one compact row per section: the session, the plan with each step's time, the monitors, usage and the host. Hovering a row opens its details beside the panel. Alt+B collapses it, and its edge drags to the width you want.
Hover the panel's rows, drag its edge, or press the panel button in the top bar.
Rung 4 · togetherAgents that work together
They hand work to each other
Every agent gets aegis's tools over MCP. It hands a task to a queue of workers and hears back when one finishes, starts a monitor on a CI run and ends its turn instead of polling, reads what another session is doing, and gives that session context or an instruction. It can also wait on other sessions: monitor_sessions wakes it when they have all finished, or as soon as one needs you.
Every answer lands in the transcript as a new turn, headed by whoever sent it: a monitor, a queue task or another agent.
Queues of workers
An agent hands tasks to a queue and keeps working; each result comes back as a turn in its transcript. A queue names the agent preset its workers run, and how many at once.
Point a queue at a cheaper model for tests, reviews and research.
Rung 5 · a companyA software company on demand
Workflows you approve
When the work has steps that wait on CI, on other branches or on a clock, the agent writes it as a workflow: a tree in which every node says what it does. You approve it on a card, the server runs it, and the agent hears when a step fails or a gate needs you.
Saved workflows live in the project, versioned like code. Reviewers can check implementers inside one.
Schedules, and pages that guide the decisions
A schedule fires a prompt on a clock into a new session or an existing one. One an agent creates waits, paused, until you start it from its card. Decisions arrive as pages you click, and those pages can stay docked beside the transcript.
The Schedules view lists every schedule with its next fire and its runs.
Rung 6 · beyondBeyond one machine and one person
Across machines
aegis link add vps https://dev.example makes this server a client of another aegis. The far server's sessions show in your Fleet under its own band, with its host and quota, and in your tab bar with a server tag. You prompt, interrupt and close them from here, and an agent here hands work to one there with peer_handoff(target="brisk-turing@vps").
The link goes one way. The far server can never reach the one that linked it, so a shared box cannot touch your laptop.
On a phone
Below 760 px the tabs get their own row, the panel becomes a drawer, and touch targets are 44 px. Chrome installs aegis as an app named after the server. A return to a recent tab, or a reconnect after the phone slept, sends only what changed.
A browser you share with the agent
The server holds a Chromium the agent drives and you watch, docked beside its transcript. You can take over, sign in, and hand it back.
Useful for tests against a running app and for sites that need you to log in.
A server for a team
Give each person a token and their own Linux user. Everything they start runs as that user, so the kernel checks every file their agents touch, and each one sees only their own sessions, queues and schedules. A quota policy per person keeps the shared subscriptions fair.
An admin, and root on the host, can still read everything. /multiuser has an agent walk you through the setup.