Crew lens
This is about long-horizon AI coding agents: agents that carry their work across hours and many steps, not a single API call.
They run in a multi-vendor seat harness. Each agentic session gets a unique ID, can message agents from other vendors, follows a cross-LLM code review protocol, and keeps learning in context as it works. Some agents are up-skilled to sprint master or project manager, to coordinate larger pieces of work.
Scroll, or use the arrow keys.
For a crew of such agents, a full record of what it does is a must-have: work items and reviews, messages between agents, model changes, compactions, sub-agent fan-outs, security warnings.
It shows where quality slipped and where the time went, what the work cost, when a vendor's cyber classifier stepped in, and how far a sprint has come. It is the audit trail (which agent changed what, on which model, at whose request) and the first place to look when something breaks. Over weeks of work it shows how the workflow runs in practice, and which models and settings suit which jobs.
A busy crew piles up thousands of events a month, and far more log lines behind them. Reading through them is hardly a dream job. Dashboards help, and they have their place, but a dashboard is a snapshot: it shows where things stand, not how they got there.
What if observability had some flair? A theme, perhaps.
A theme
The trailer runs an evening at the camp at high speed, jumps ahead along the timeline, stops by a stalled robot, and ends with a walk through the camp to the next stone.
The numbers
The camp shows how the work unfolds. The numbers are a click away: right-click a robot and its record opens, with the robot beside it.
Token burn and what it would cost at API list prices, hours spent producing and reviewing, lines of code landed, review findings by severity (P0 to P3), the models it was served, its compactions and messages, its last health check, and any stalls, drift or cyber holds.
The crew board ranks the whole crew on one measure at a time: burn, cost, model hours, lines landed, findings, messages, compactions or stalls. It prices the burn at API list rates and sets that against what the seats cost.
A click on a row opens that agent's record.
The work board compares sprints on lines landed, review rounds, findings, burn and lead time, then drills into one sprint's work items. Its ledger splits the crew's burn into item work, sprint coordination and the rest, so the figures add up.
These views come from a real crew's record, late August to mid September 2026, with work details left out. Select a view to enlarge it.
A field guide
The outpost draws an AI coding crew as a camp in the mountains. Each agent is a small robot, and the things on its body are data, from the model it runs to how full its memory is.
It replays the build: what was worked on and by whom, the quiet hours skipped, back to the moment a cyber warning fired, or just a crew of agents organizing itself.
Scroll on to watch one robot being built, then follow it through a day at work.
1 · The agent
Each robot stands for one AI agent: a language model that runs on its own, with a job and the tools to do it. Here are two of them, a Claude agent and a Codex agent, and they start out as wireframes, the bare frame the rest hangs on.
Watch them fill in. Each part tracks something the agent is doing, and the next steps go through them one at a time. Once both stand complete, look at the tanks on their backs: the same stream of work fills the Codex tank about four times as fast.
The bubble round the head shows which model does the thinking. Its colour is the model's tier: red for the biggest models, then orange, yellow and white as they get smaller and faster.
Its size is the reasoning effort, how long the model works a problem through before it answers.
Try it: pick a model and an effort on the card next to the robot.
On its back each robot carries a tank: its context window, everything the agent can hold in mind at once, from its instructions to the code it has read.
The black liquid is context in use, flecked with the data it holds; the glowing space above it is what is still free. As the agent works the black rises, and the glow goes from green to amber to red.
A full context window takes nothing more, so the agent compacts it: it boils what it knows down to a short summary and carries on from there.
While it compacts, the robot freezes, as a real agent does: no work, and no messages in or out, until the summary is written. A little black stays at the bottom of the tank afterwards (the summary it keeps), and that floor rises as the agent gets older.
The tanks come in different sizes. Here the Claude agents run with a window of about one million tokens and the Codex agents with about 258 thousand (a token is a small piece of text, roughly three quarters of a word).
Give both the same stream of work and the smaller tank fills close to four times sooner, so it stops to compact close to four times as often. Watch the counters.
The mark at the back of the neck says who built the model: Anthropic for Claude, OpenAI for Codex. The paint follows it (warm for Claude, blue for Codex), so you can tell the two families apart across the camp.
Switch it on the card and the camera takes you to the other robot.
The chevrons are service stripes, one for every ten days the agent has been on the job, split between its two arms (the right arm takes the odd one). So the arm facing you shows about half of them, and the card gives the split. A new hire has none.
2 · On the job
Some of what an agent does is work: producing, reviewing, communicating. The rest is what happens to it along the way, and the lens flags each case: a compaction, a stall, a drift off its brief, a cyber hold.
The agent builds a work item it owns. It holds a long breaker lance against the item's rock and drives it with a hammer, and each strike throws sparks and knocks flakes off the crust.
The small copies around it are sub-agents it spun out to help, each on a thin tether back to its parent and each with a context window of its own.
Another agent's work needs a second pair of eyes. The reviewer sweeps it with a scanning laser, much as it reads a change line by line before it signs off.
Agents message each other and the operator, the human in charge. A message is a glowing arc from sender to recipient, coloured by its kind: a question, a review request, a coding request. The sender types it out on a small hologram first.
The tall tower belongs to the sprint master, the agent that keeps a sprint on track.
Mid-swing, the tank hits full. The robot freezes where it stands, the tank flushes bright cyan and the black drains back to its floor. Messages to or from it wait, and when the summary is done the hammer comes down again.
The agent holds a task but has stopped making progress. It lies down at its bench under a screen of falling green code with one word in it: Stalling. Someone should look.
The Sentinel, a watchdog that checks agents against their instructions, has flagged this one for wandering off its brief. It keeps working, but it sways and shakes its head under a screen that turns orange, or red once the Sentinel is sure.
The model's vendor runs a cyber classifier over the agent's work, and it has flagged this work as risky. The agent stops on the spot, under a blue screen, until the operator has looked. On the crew behind this lens, each hold so far has been reviewed and judged a false positive: mostly an agent running adversarial tests against freshly written code.
3 · The work
Each work item starts as a rock, with its plan and requirements, set down in front of the agent that will build it. The rock is black, and the finished work sits inside it.
As the agent works, the crust chips away from the top and the cracks glow brighter. The diamond inside shows its tip first, then its crown, then the whole stone.
You can read the progress off the rock: the lower the crust, the closer the work is to done.
4 · Done
When the producer and the reviewer agree the work is right, the review has converged: the diamond is cut free and lifted onto the sprint's pile.
Green diamonds are shipped work. A black diamond is work that was scrapped (cancelled, replaced by something better, or turned down in review), and it stays on the pile too, so the history is there to see.
5 · Sprints
Work comes in sprints, each a set of items with one goal. A sprint gets a hangar of its own, sized by how much code its work touches.
The hangar goes up just before its sprint starts. The cover stays up while the sprint runs and the pile grows as work converges; when the sprint closes, the cover comes down and the hangar stays as a record of what was built.
6 · Looking back
The lens can play the record back like a film. The bar along the bottom holds the clock, a scrubber and the play controls, and above it runs the event timeline, one row for each kind of moment worth finding again: fan-outs, stalls, drifts, cyber warnings and holds, model changes, convergences and the operator's nudges.
Click a mark and the replay jumps to five seconds before that moment, just in time to watch it happen.
Much of an agent's day is waiting, for a review, an answer or the next job. Hours pass between one message and the next and whole nights go by with nothing in flight, so a replay at one steady pace would be mostly an empty screen.
The replay squeezes the quiet instead. Once three minutes pass with nothing happening, the rest of the gap plays in fifteen seconds of replay time (about a second at the usual speed), whether it lasted ten minutes or a whole night. While things happen it runs at half the set speed, slow enough to follow. The scrubber is laid out in replay time, so a quiet night takes up a sliver of it, hatched on the timeline.
Incident mode goes further: it plays from eight minutes before each flagged moment to twenty minutes after, and jumps over the rest.
Everything on this page is drawn from the kind of record an operator would otherwise read line by line. The picture gets there sooner: who is stuck, and what is about to ship.
The stage on this page plays a scripted demo, not a live record; the dashboard views after the trailer come from a real crew's record. The context-window sizes are the ones configured for these seats, about 1M tokens for Claude and about 258k for Codex; vendor limits vary by model and plan.
The space theme
If robots are not your thing, the lens also comes with a space theme. The agents fly small craft, and their work builds a station in orbit round a ringed planet. It draws the same record, with the same timeline and replay.
The reel runs a busy evening at high speed, jumps ahead along the timeline, stops by a stalled craft under its matrix screen, and ends with a ride in one craft's cockpit.
Coming soon
The crew lens is being readied for release, with both themes and the replay. Leave an email to hear when it ships.
One email when it ships. Privacy
