Getting started
Virtia is mission control for your AI coding agents. It points at the real Claude Code sessions you already run — in your real repo, on your real machine — and lets you watch, steer, and ship them by voice from your phone.
It is not a sandboxed web IDE. There is no hosted model and no copy of your code in someone else's box. Virtia is a thin cockpit over the Claude Code you already own, so it rides your own subscription and you keep the compute and the data.
The three pieces
- The Virtia server — a tiny zero-dependency Node process that runs on the same machine as your Claude Code. It tails each session's transcript and exposes a live stream.
- The Cockpit — the web app you open in a browser (or add to your home screen). It shows every session as a feed of cards you can read and reply to.
- The bridge — the link from the Cockpit's composer back into a real terminal, so what you say or type is delivered to the actual Claude Code session.
Opening the Cockpit
- Marketing and sign-up live at virtia.com.
- The app itself lives at cockpit.virtia.com.
Open cockpit.virtia.com, authenticate, and you land in the multi-session hub. On a phone, use Add to Home Screen (see Install as an app) so it opens full-screen with no address bar — it behaves like a native app.
Your first minute
- Each project shows up as its own lane. Tap a lane to filter to just that project; you stay in it until you exit.
- New assistant replies stream in as cards, newest at the bottom.
- Tap the mic and talk, or tap the prompt line to type. Either way, your message goes straight to the live session.
- Turn on voice-out and replies are read back to you — fully hands-free.
The composer & voice
The composer is the bar pinned to the bottom of the Cockpit. It is deliberately voice-first and decluttered for one-handed phone use.
On a phone the row is just what you need and nothing else:
- ⋯ — a small menu (far left) holding the less-used actions, so they never crowd the row.
- 📷 — attach a photo or screenshot. On mobile this is a single camera button; the desktop-only screen-capture is hidden.
- 🎤 — the mic. Tap to start dictation, tap again to stop.
- Send — sits right next to the mic, so capture-then-send is one thumb movement.
Talking to Claude
Tap 🎤 and speak. Audio is captured silently and transcribed, and the text lands in the prompt line. Review it, then Send. Because real dictation is never perfect with technical jargon (session names, tool names, product names), Virtia is built to ask you what you meant when a message is ambiguous rather than act on a bad reading.
Typing when you want to
The prompt line is a review surface by default, so a stray tap never throws the keyboard in your face. When you actually want to type, tap the prompt line itself and the keyboard comes up. Only a tap on the text field does this — the mic, the buttons, and the cards never summon it.
Hands-free replies
Turn on voice-out and each new reply is read aloud with a natural voice. Combined with mic input, you can run a whole session without looking at the screen — useful while walking, driving hands-free, or away from a desk.
Attaching images
Tap 📷 to send a screenshot or photo into the session — handy for showing Claude a UI bug, an error, or a design. The image is uploaded and referenced in your message.
Threading & focus mode
A busy session is a river of messages. Virtia keeps you oriented with WhatsApp-style threading: you choose what you are replying to, and you stay there until you decide to leave.
Focus mode — the thread "jail"
Tap any card and it becomes the subject you are replying to. From that moment you are jailed into that thread — every message you send goes to it — until you explicitly exit. No more guessing which message your reply attached to. It stays consistent until you choose another card or step out.
Quote a part of a long message
Long replies often have several points. Select part of a card and it becomes a quote chip shown above the composer — your reply is clearly about that excerpt. The quote is a chip, never raw text pasted into your prompt, so your message stays clean.
Nested threads & breadcrumbs
Replying to a part of a message can open a child thread, so a side-discussion doesn't derail the main line. A breadcrumb trail shows where you are in the hierarchy, and you can walk back up it at any time. Deep conversations stay navigable instead of turning into one flat scroll.
Sticky lanes
Each project has a lane. Pick a lane (say, one project) and you stay filtered to it until you exit — tapping around won't silently drop you into another project's stream. The lane filter is sticky by design, matching the same "stay where I put you" principle as focus mode.
System notices
Not everything deserves a full card. Lightweight status lines — "ADR created", a link, a short heads-up — render as thin system notices rather than heavy message cards, so signal stays separated from chatter.
Findability, automation & agents
Search & the glossary
- Search scans the whole session so you can jump straight to a past answer instead of scrolling.
- The 📖 glossary explains the abbreviations that fly by in a technical session (ADR, PR, and the like), so nothing is opaque.
Radar — stop re-answering the same thing
The Recurring-Question Radar clusters similar questions that keep coming up. If you have effectively asked the same thing many times, Radar surfaces it so it can be answered once and settled — instead of being re-litigated every few days. Automated system pings are filtered out at the source, so Radar only ever clusters your real questions.
Rules & the playbook
Every session has a playbook — a living list of rules. When you state a preference or a correction, it gets saved so it applies again without you repeating yourself. The rules engine runs your playbook consistently, turning "how I like things done" into something the session actually follows.
The backlog
A per-session backlog captures ideas and follow-ups so they don't get lost in the scroll. Add an item by voice or text; work through it later.
The agents panel
Claude Code can dispatch background agents to do work in parallel. The 🤖 agents panel gives you live status of every agent you've launched — what it's doing and whether it's still running — right from the header, so long-running work is never a black box.
Local automation
Virtia leans on local scripts for anything that can be automated without a model: health checks, keeping the connection alive, watching for a stalled agent. The principle is simple — spend the model's effort only on judgment, and let cheap local daemons handle the routine. When something genuinely needs a decision, Virtia wakes the session; the rest runs for free in the background.
Context, reactions & installing
The context meter
A long conversation eventually fills the model's context window. Virtia pins a context meter so you can always see how full it is, and alerts you as it approaches the limit. You are never surprised by a compaction.
Compaction
When context gets full it must be compacted — summarized so work can continue without losing the thread. In Virtia the compact button is a request, not an instant action: it tells the session to compact at the next good moment, since only the session knows when it's mid-thought versus safe to summarize. Over time you'll simply be told a compaction is coming rather than having to manage it.
Reactions
React to any reply with one tap:
- 👍 Like — good: helpful, correct, yes.
- 🔥 Fire — outstanding: nailed it, do more of this. A stronger positive than a like; it marks your gold-standard moments.
- 👎 Down — off: so the session learns what to avoid.
Think of it as a dial — 👎 avoid → 👍 good → 🔥 outstanding. Reactions feed a satisfaction view so patterns you love get reinforced and patterns you dislike get dropped.
Install as an app
On a phone, use your browser's Add to Home Screen. Virtia installs like a native app: full-screen, its own icon, no address bar, no App Store review. Launch it from the home screen and it opens straight into the Cockpit.
Staying connected
The Cockpit streams live. Behind the scenes Virtia keeps its connection healthy automatically and reconnects through drops, so you can lock your phone, walk away, and pick the conversation back up where it was.
Accounts & plans
Signing up
Create an account at virtia.com and sign in from the header. Your login carries a plan, and your plan unlocks a set of modules — Virtia's features are entitlement-gated, so you turn on exactly what you pay for.
Plans
- Free / Solo — $0. Self-host the Virtia server, connect your own Claude Code, one active session, and community rule-packs. Everything you need to drive a single session from your phone.
- Pro — $19/mo. A hosted relay with a permanent URL (no tunnel fiddling), push notifications, multi-device sync, unlimited sessions, full findability and automation, and private rule-packs.
- Team — $29/seat/mo. Shared, observable sessions, org-wide rule-packs, SSO, and an audit log with roles.
Billing
Checkout runs through Stripe. Upgrading takes you to a secure Stripe-hosted page; your card details never touch Virtia. You can start on Free and upgrade when you want the hosted relay and notifications.
What "hosted relay" means
On Free you run the server yourself and reach it over your own connection. Pro's hosted relay gives your Cockpit a permanent, stable URL that stays up without you managing a tunnel — the most reliable way to reach your sessions from anywhere.
Privacy posture
Virtia never hosts your model or your repository. Your code stays on your machine, your Claude Code runs under your own subscription, and Virtia only relays the conversation between your phone and that session. You own the compute and the data — that's the whole point.