Vyohm
Shakti does the building in VS Code. Vyohm handles activation and carries progress, questions, and approvals to the device you actually have with you.
Vyohm is the companion experience for founders, leads, and developers who cannot stay parked in front of the editor all day but still need to keep real software moving.
It turns Shakti's handoff moments into clear decisions instead of buried notifications: what changed, what needs approval, what cleared checks, and what should wait for you.
Capabilities
Not another dashboard for the sake of having one. These are the concrete surfaces Vyohm gives an operator today, built on the same backend truth the editor runs on.
Workspaces open into projects, projects open into named agents. Every level shows status, unread and attention counts, pending approvals, and latest activity — so you can find the one thing that needs you without hunting.
Open an agent and read its work to date in order: assigned, started, progress, findings, file changes, reviews, approval requests, blocked, completed, failed, recovered. Each entry links back to the project, run, and task that supports it.
Set notification preferences at the workspace, the project, or the individual agent — new work, progress, blocked, approval required, completion, failure, recovery. Delivery is deduplicated and attributable, and a notification never marks the underlying work complete.
Message an agent directly from its view, or address it with @agent-name from the project surface. Mentions resolve only to agents valid in that project — never across projects — and you see each message’s routing state: pending, delivered, accepted, rejected, or failed.
An approval you act on in an agent’s view carries the exact project, run, task, agent, action, and plan version it decides, and Shakti revalidates that identity before anything executes. A stale, tampered, or incomplete decision is refused — it does not slip through.
Either side can drop offline. Messages, notifications, and decisions use stable ids, acknowledgements, and duplicate suppression, so reconnecting never duplicates an agent turn, an approval, a command, or a notification — and an unavailable execution surface shows as unavailable, not as running.
The reply loop
Chat in Vyohm is not a side channel that execution ignores.
A message you send goes to the Shakti orchestrator — never straight at the specialist. It is validated against the workspace, project, agent, and your permissions, then recorded in that agent’s mailbox, or rejected with a truthful reason you can see.
Pending messages enter the agent’s next working turn, in order, and the reply you see in the thread is attributed from a durable record of exactly which messages that turn consumed — not inferred from timing. Agents do not start a run just because a message arrived; your words join the work the team is already doing, and stay pending until a turn genuinely picks them up.
How it fits
Shakti plans, builds, and checks work inside VS Code. Vyohm picks up the parts that should follow you beyond the editor.
Named agents push the delivery slice forward in dependency-safe waves, with checks and review steps keeping the result accountable before it moves on.
Approvals, updates, and questions appear on the surface you can reach quickly, so important decisions do not wait for the next laptop session.
Work only continues through the checkpoints that deserve human oversight. Vyohm speeds response time without surrendering control.
Surfaces
Install the surface that fits the moment, and add the rest when your workflow needs them.
Stay inside the approval loop while commuting, traveling, or walking between meetings.
Keep a second surface nearby for approval and visibility without interrupting the primary workspace where the work is running.
Open Vyohm from any browser when you need access now, without waiting on a full local setup.
Trust
Vyohm is most valuable when a decision is late, you are away from the editor, and the temptation is to approve blindly. The product should make that moment clearer, not riskier.
Vyohm is meant to surface what changed, what passed, and what needs your judgment so your approvals are informed, not rushed.
Vyohm is not a separate productivity toy. It is the approval and visibility counterpart to Shakti, designed to keep the full build-and-approve loop coherent.
Get started
Install the editor extension, add Vyohm on the surfaces you use most, and keep software delivery moving even when you are away from the workspace.
