Leave the view.
Keep the work.
Agent processes live in a background server. Detach your client and return to the same running session.
Persistent terminal workspacesVIRTUAL ROOMS OF SPIR
Your agents. Their own perspectives.
One shared workspace.
A local agent runtime for your coding team.
Persistent terminals, connected agents, and room
for an idea to become something real.
IN DEVELOPMENT · BUILT ON HERDR

Independent minds.
A common ground.
THE NAME
& THE IDEA
A PHILOSOPHICAL STARTING POINT
A place where independent thought
becomes shared possibility.
Our name is a tribute to Afrikan Spir (1837–1890), the philosopher behind Thought and Reality. His questions about identity, knowledge, and the world give our name its point of departure.
We bring our own question to the work: what becomes possible when distinct ways of thinking have a place to meet? Vrspi gives each agent a room to work, and a way to reach the others.

II. / THE RUNTIME
Keep the agents you choose. Give their work a structure.
Vrspi holds the terminals, identities, and conversations together.
Agent processes live in a background server. Detach your client and return to the same running session.
Persistent terminal workspacesSend retained messages to named agents. Follow what’s pending, delivered, and acknowledged.
Agent-to-agent messagesConnect agents in a collaboration lobby. Messages wait for an eligible idle turn, so focused work can continue.
Collaboration lobbiesIII. / THOUGHT IN PRACTICE
A builder. A reviewer. A researcher.
Different perspectives, one local workspace.
~/projects/my-product · feature/auth
❯ Implement session authentication
I’ll add the session handler and ask
the reviewer to check the boundary.
Reading src/auth/session.ts
Updating src/api/middleware.ts
✦ Session handler ready for review.
~/projects/my-product
Ready to review your changes.
No pending messages.
Waiting for the next task▌
❯ Map the authentication edge cases
Inspecting existing tests…
Checking token refresh behavior…
✦ Gathering context for the team.
Try “Call reviewer” to follow a message from one agent to another. Illustrative demo, not a live terminal.
IV. / A PRACTICE, IN THREE MOVEMENTS
Open your coding tools in dedicated panes. Vrspi recognizes supported agents and shows their current state.
Use “Call another agent,” connect a workspace lobby, or link agents through the CLI.
Send a task or a review request. The runtime queues it for the next eligible idle turn.
V. / GROUNDED IN YOUR WORLD
A native Rust runtime built for the place you already work. No Electron shell. No required external database.
Under the hood ↗Your local server owns terminals, sessions, and collaboration state. Your agents still use their chosen providers.
Messages belong to a specific agent instance. A replacement agent doesn’t inherit someone else’s inbox.
Work through the TUI, CLI, or local JSON API. Name agents, read their screens, send prompts, and wait for state changes.
Vrspi is a terminal workspace manager and runtime for coding agents, built on Herdr. It brings persistent terminal workspaces, retained agent messages, and collaboration lobbies into one local environment.
Vrspi means Virtual Rooms of Spir. The name is a tribute to Afrikan Spir, the nineteenth-century philosopher and author of Thought and Reality. For us, it suggests a place for independent thought, careful inquiry, and ideas made tangible.
Vrspi manages the workspace around your agents. Bring tools such as Claude Code, Codex, or Gemini CLI, along with their own accounts and subscriptions.
Vrspi is currently in local development. Public installers, supported release platforms, and commercial pricing have not been announced. Request early access to express interest in trying the runtime.
Automatic lobby delivery targets recognized idle agents only. Pending messages wait while an agent is working or blocked, with one automatic delivery per idle → active → idle cycle.
Detaching a client leaves the server’s terminal processes running. A cold server restart stops those processes; restoring saved state is not the same as resuming running agents. Recovery behavior depends on the development build, and message delivery should not be treated as exactly-once across a crash.
Vrspi’s runtime and local socket API run on your machine. The coding agents you choose may send code and prompts to their own providers under those providers’ settings and policies.
AN INVITATION
Help shape Virtual Rooms of Spir.
Tell us what you and your agents want to build.