Seven stories — code, research, ops, messaging, cron, kanban, and Work Mode. Each card: stuck point → what ships → privacy-safe Desktop proof → next step.
Desktop chat with Plan · Report · Design · Runs, Work inbox, approvals, and skills — the same surfaces the product pages claim.
Privacy-scrubbed Desktop captures and marketing-demo loops — not a live customer session, credential, or private project.
Filter by audience if you want — every card still shows problem, capability, Desktop proof, and a next step.
Engineers lose focus on routine and context switches — chat-only tools stop at suggestions while you still paste diffs by hand.
CapabilityDesktop chat + Plan rail + terminal/files: navigate the repo, patch, run tests, and open a PR with language/PR skills that keep the loop tight.
ProofProof: Desktop chat frame with Plan · Report · Design · Runs (privacy-safe product capture).
Analysts drown in tabs and manual summaries — citations get lost before the brief ships.
CapabilityResearch Pro + web search/extract + critique skills: gather sources, grade evidence, and draft a cited brief — pause at approval before anything leaves the machine.
ProofProof: Plan / Command Center frames on Product and Capabilities — privacy-safe Desktop captures, not a live customer session.
Teams burn mornings collecting and reconciling status — health checks and deploy notes die in a long chat scroll.
CapabilityAgent runs checks, compares signals, and explains the picture — with approval gates before outbound send or destructive ops.
ProofProof: Plan / Command Center frames on Product and Capabilities — not a live customer session.
Support and ops want the same agent in Telegram/Discord/Slack — without standing up a second product.
CapabilitySelf-host the gateway: same agent core, approvals, and session continuity on ~20 messaging platforms you configure.
ProofProof: messaging illustration + honest scope on Tour/Docs — you run the gateway; shared hosted bots are not included yet.
Leaders start the day without context — recurring digests should not need a forever-open chat window.
CapabilitySchedule with natural language or cron; deliver to a connected surface while the gateway stays awake.
ProofProof: cron + kanban demos on this page and the Tour — schedules need a running runtime, not cloud magic.
Teams lose transparency when parallel specialist work dies with a process restart.
CapabilityDurable kanban tasks for specialist profiles — reclaim, claim, complete work that outlives one Desktop session.
ProofProof: Work Mode inbox + durable board story on /work (process-local delegate_task is not restart-durable).
Closing the chat window erases the goal you still need finished.
CapabilityWork Mode keeps goal → plan → steps → approvals → deliverable past a single conversation (inbox + fleet HQ).
ProofProof: Work inbox frame and the /work pipeline (privacy-safe Desktop capture).