vrspiruntime

VIRTUAL ROOMS OF SPIR

Room for
thought.
Space to create.

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.

V0.9 · WINDOWS · MACOS · LINUX · FREE IN PREVIEW

An imagined engraving of interconnected rooms, archways, and staircases surrounding a solitary reader beneath a suspended sphere.
FIG. I — THE ROOMS OF THOUGHTVRSPI / MMXXVI

Independent minds.
A common ground.

Claude CodeCodexGemini CLIYour terminal
Bring your own accounts.
Provider subscriptions are separate.
I.

THE NAME
& THE IDEA

A PHILOSOPHICAL STARTING POINT

Virtual Rooms
of Spir.

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.

From an idea to a working environment
A philosophical still life: an open book, a sphere and its reflection, and an archway opening onto a distant landscape, rendered as a green engraving.
FIG. II — THOUGHT & REALITY
An imagined study in perspective.

II. / THE RUNTIME

A room of their own.
A world in common.

Keep the agents you choose. Give their work a structure.
Vrspi holds the terminals, identities, and conversations together.

01 / CONTINUITY

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 workspaces
02 / DIALOGUE

Name who you mean.
Only they answer.

Company rooms give each agent a seat and a handle. An @mention wakes only the seats you address; everyone else can read along later.

Company rooms
03 / ACCOUNTABILITY

One owner.
Evidence, not claims.

Tasks have a single owner, leases, and dependencies. A worker submits; a verdict is checked against evidence. The two are never confused.

Tasks & shared memory
What is an agent runtime?

III. / THOUGHT IN PRACTICE

See the conversation
become the work.

A builder. A reviewer. A researcher.
Different perspectives, one local workspace.

Vrspi with three agents side by side: Claude Code as builder showing the diff it just made, Codex as reviewer waiting for approval to run a room command, and OpenCode as researcher, idle. The sidebar lists each agent’s status.
Vrspi 0.9.5, unedited. @builder fixed a rounding bug and handed the diff to @reviewer through the room; @researcher was not mentioned, so it stayed idle.
The company rooms view of a room named Checkout. The host asks @builder for tests; @builder replies to @reviewer with the diff summary and test results.
The room conversation. Every post shows exactly who it woke.
The tasks tab of the Checkout room, listing two tasks with their owners, @builder and @reviewer, both ready.
Tasks, each with one owner.

An illustrative walk-through of the same idea:

ONE WORKSPACE. MULTIPLE MINDS.INTERACTIVE PRODUCT ILLUSTRATION
vrspi — my-product● session running
builder Claude Code● working

~/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

+ export async function validateSession(+ request: Request+ ) {+ const token = getSessionToken(request);+ return verify(token);+ }

✦ Session handler ready for review.

reviewer Codex● idle

~/projects/my-product

Ready to review your changes.

No pending messages.
Waiting for the next task▌

researcher Gemini CLI● working

❯ Map the authentication edge cases

Inspecting existing tests…
Checking token refresh behavior…

✦ Gathering context for the team.

my-product / development3 panes · local

Try “Call reviewer” to follow a message from one agent to another. Illustrative demo, not a live terminal.

IV. / A PRACTICE, IN THREE MOVEMENTS

Bring them together.
Let ideas travel.

Read the workflow guide ↗
I

Bring your agents

Open your coding tools in dedicated panes. Vrspi recognizes supported agents and shows their current state.

II

Give them seats

Open company rooms from the menu, create a room with an objective, and bind each agent to a seat with a handle.

III

Address who you mean

Post with an @mention. Only those seats wake, on their next idle turn, and their replies come back into the room.

V. / DOWNLOAD

Install it.
Open a room.

One command on Windows, macOS, or Linux. The first start asks you to sign in with a free account.

Installation guide ↗
…

Run in Terminal

curl -fsSL https://vrspi.com/runtime/install.sh | sh

Apple silicon and Intel. Installs vrspi to ~/.local/bin. The installer checks the published SHA-256 digest before anything reaches your PATH. Update later with vrspi update.

Or download the binary
  • macOS Apple silicon
  • macOS Intel

VI. / GROUNDED IN YOUR WORLD

Your machine.
Your agency.

A native Rust runtime built for the place you already work. No Electron shell. No required external database.

Under the hood ↗
01

Local by design

Your local server owns terminals, sessions, and collaboration state. Your agents still use their chosen providers.

02

Identity with a boundary

Messages belong to a specific agent instance. A replacement agent doesn’t inherit someone else’s inbox.

03

A tool you can direct

Work through the TUI, CLI, or local JSON API. Name agents, read their screens, post to rooms, and wait for state changes.

VII. / AN OPEN INQUIRY

Questions
worth asking.

Read the documentation ↗
What is Vrspi Runtime?

Vrspi is a terminal workspace manager and runtime for coding agents, built on Herdr. It brings persistent terminal workspaces, company rooms where you address agents by @handle, and tasks with owners and evidence into one local environment.

Why the name Vrspi?

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.

Is Vrspi an AI model or a coding agent?

Vrspi manages the workspace around your agents. Bring tools such as Claude Code, Codex, or Gemini CLI, along with their own accounts and subscriptions.

Can I download it today?

Yes. Vrspi 0.9 runs on Windows, macOS, and Linux. Install it with one command from the download section; the installer verifies the published SHA-256 digest, and vrspi update keeps it current. It is free while in preview.

Do I need an account?

Yes, a free one. The first time Vrspi starts, it opens your browser to sign in or create an account; after that it starts straight away, and keeps working offline for up to 14 days. Paid modules will be tied to the same account, announced with prices before anything is charged.

Will a room message interrupt an agent that’s working?

No. A mention wakes only the seats you address, and only when that agent is idle. While it is working or blocked, the message waits. Each objective carries an activation budget, so agents cannot keep waking each other indefinitely.

What survives a restart?

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.

Where does my code go?

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

Every possibility
begins with a room.

Download Vrspi and give your agents a room.
Create a free account to be first in line for what comes next.

Free in preview · Paid modules announced, with prices, before launch