The cockpit is the screen half of yothere: a single page that shows the whole fleet at a glance and lets you clear what needs you. It is built around one idea, that most of the time your inbox should be empty and the fleet should just be working.
The board reads left to right and top to bottom in priority order: the things that need you, then the things in flight, then the things already done. Voice and your task list sit alongside as companions to the board, not the frame.
Opening the cockpit
The cockpit lives at /overview, served by the voice service on 127.0.0.1:8767. Start the voice service (see the Quickstart and CLI reference) and open the page in a browser on the same machine or your tailnet.
At the top is a command bar. Type a task and dispatch it, the same as yothere spawn from the CLI. For example, “scan our top 3 competitors and draft a one-pager”. A hint under the bar reminds you that yothere drafts and asks before sending, so a dispatched task never fires an outward action without your say-so.
Inbox (needs you)
The inbox is the point of the whole product. It holds only the threads that are blocked on you, each one asking a specific question or waiting for an approval. When it is empty it reads:
Inbox zero. yothere's working.The verbs on each card match the ask. A thread that asked a question gives you a reply box. A thread that drafted something outward (a message, an email) gives you a Send button. A thread that finished a result gives you a “Looks good” confirmation. You act from the card and the thread resumes on the next runner tick, no context-switch into a chat window.
Working
The working lane shows the threads currently advancing. Each card carries a live activity line (what the brain is doing right now), a short tool timeline (the last few tool calls), and elapsed time, so you can see a thread is progressing rather than stalled. Scheduled items that have not started yet also surface here. This lane is glanceable and deliberately action-free: you watch, you do not babysit.
Past sessions
Finished sessions collect here as result cards. A long result renders as a structured TL;DR card (a clamped lede with the detail folded behind it); a short result renders as a plain card. The lane is searchable, so a past piece of work is easy to find again with the “Search past work” box. This is the archive that lets the inbox and working lanes stay focused on the present.
Connect (voice)
The Connect button opens the voice loop so you can hail and reply hands-free. It runs over WebRTC on your tailnet, no phone provider needed, and connects a browser on your network straight to the local voice server.
If the media stack is not installed, the page still renders fully and the button reads “voice unavailable” rather than breaking. Install the voice extra to enable it:
pip install 'yothere[voice]'Your tasks
Alongside the board, a “From your tasks” strip shows your real open to-dos, parsed from your workspace (your prioritized task list and open queue items). It is there to fuel dispatch: glance at a to-do, hand it to the fleet from the command bar. If no task source is wired up yet, the strip prompts you to connect one.
Transcript
When a voice call is live, the transcript panel streams the running conversation line by line, so the spoken exchange has a readable record you can scan while the call is in progress.
Install as an app
The cockpit is an installable progressive web app. It ships a web manifest and a service worker, so you can add it to a phone home screen and run it standalone, and it supports web push. When a thread needs you, a push notification arrives and taps through straight to the thread: the notification deep-links to /overview?tid=<id>, opening the cockpit focused on the exact ask.
This is the pocket path: your fleet works on your machine, and a single tap from your lock screen answers the one thread that needed a decision.
Two run modes
The cockpit runs in one of two modes:
- Local single-user (the default). No login. The page and its live stream are reachable over loopback and your tailnet.
- Hosted multi-tenant. A login is required and each account sees only its own isolated fleet.
The configuration for both, including the auth and per-tenant seams, lives in Configuration.