00CORE
VibeSpace / Issue 00
  1. 00CoverThe workspace for the messy middle.
  2. 01One SpaceThe tabs stop multiplying.
  3. 02Many MindsChoose the mind. Keep the thread.
  4. 03Agents at WorkBrief once. Work in parallel.
  5. 04Ten TerminalsTen terminals. One approval.
  6. 05Speak to the WorkJarvis voice and Ctrl+Space dictation.
  7. 06Context Has EdgesProject scope with visible relationships.
  8. 07One Operating LoopSelect. Isolate. Trace.
  9. 08Local by DesignYour keys stay yours.
  10. 09Built OpenOpen at the core.
  11. 10One Place to WorkNot nine tools. One place to work.
Ask the VibeSpace GuideDeterministic local answers / no AI or network request
Guide / Overview

One connected workspace.

VibeSpace is the local-first desktop AI workspace. Jarvis is the built-in assistant inside it. Models, agents, terminals, context, voice, tasks, skills, actions, and memory stay connected to the work.

Open One Space
VibeSpace / Luxury AI Editorial / 00

Issue 00 / Cover

Vibe/Space

The workspace for the messy middle. Models, agents, terminals, voice, tasks, and memory in one local-first desktop workspace.

Explore the issue App coming soon

VibeSpace is the product.
Jarvis is the built-in assistant.

Local first Bring your own keys Open-source core
Issue 01 / Integration

Issue 01 / One Space

The tabs stop multiplying.

VibeSpace brings the moving parts of AI work into one desktop frame. A conversation can hold project context, hand work to agents, open terminal output, save a task, and keep the useful result nearby.

  • Chatthreads
  • Agentsroles
  • TerminalsPTY
  • VoiceJarvis
  • Tasksactions
  • Memorycontext

68% unified / one connected frame

Issue 02 / Models

Issue 02 / Many Minds

Choose the mind. Keep the thread.

A 21+ provider BYOK model hub keeps model choice inside the same conversation. Ollama adds local, keyless routing. Hive can pass one prompt through sequential refinement instead of asking one model to do everything.

BYOK contact sheetChoose the route. Keep the conversation.
Drag / arrows / focus
01 / BYOK

Reason

Route a difficult planning pass to the model you choose.

02 / BYOK

Build

Keep coding work in the same project thread.

03 / BYOK

Review

Change the model without losing the conversation around it.

04 / LOCAL

Offline

Ollama routes supported local models without an API key.

05 / FAST

Draft

Pick speed when the work needs momentum, not ceremony.

06 / LONG

Context

Attach project scope and keep the relevant material visible.

07 / HIVE

Refine

Pass a response through sequential model stages.

08 / YOU

Direct

Your keys, your routing choice, one persistent workspace.

DraftModel A maps the first useful answer.
CritiqueModel B finds gaps, risk, and missing context.
RefineModel C produces one cleaner result in the thread.

Provider labels represent routing choices, not endorsements. Adapter availability can vary by release.

Issue 03 / Collaboration

Issue 03 / Agents at Work

Brief once. Work in parallel.

Custom agents and subagents give work a visible cast. Council mode broadcasts a prompt, lets focused roles explore in parallel, and synthesizes the useful parts into one answer.

A / 01

Jarvis

Routes the brief.

Demo task: attach the release context, then send the right slice to each role.

A / 02

Researcher

Finds evidence.

Demo task: inspect the public docs and list only supported product claims.

A / 03

Builder

Maps the diff.

Demo task: propose the smallest implementation that preserves current architecture.

A / 04

Reviewer

Tests the edges.

Demo task: look for regressions, unsafe assumptions, and missing checks.

A / 05

Memory Keeper

Scopes context.

Demo task: save the final decision to this project, not every future project.

A / 06

Action Extractor

Names the next move.

Demo task: turn the synthesis into clear, reviewable tasks.

01 / BroadcastOne brief
02 / ParallelFocused work
03 / SynthesisOne result
Issue 04 / PTY

Issue 04 / Ten Terminals

Ten terminals. One approval.

A ten-pane PTY grid keeps Scout, Builder, Reviewer, OpenCode, Claude Code, Codex, and shell workflows visible. Multi-terminal orchestration remains behind a clear approval gate.

01 / Scoutready
$ inspect context --safe
project scope loaded
8 items indexed
no command executed
02 / Builderqueued
$ plan minimal-diff
architecture preserved
3 files proposed
awaiting gate
03 / Reviewerready
$ review plan
risk: low
missing: visual pass
status: hold
04 / OpenCodeidle
workspace attached
role briefing ready
shell untouched
05 / Claude Codeidle
context available
no prompt dispatched
approval required
06 / Codexidle
task lane empty
branch unchanged
waiting
07 / Testsready
viewport matrix set
keyboard path set
motion mode set
08 / Securityready
claims checked
private data: none
links staged
09 / Shellidle
manual lane
no command history
10 / Synthesishold
inputs collected
final output blocked
review the plan
Approval gate

Interface simulation only. Review a fictional plan before the panes change state. No command is executed.

Fictional plan: let Scout summarize context, Builder draft a minimal change, Reviewer inspect the result, and Synthesis report back. This demo only changes text on this page.

Issue 05 / Voice

Issue 05 / Speak to the Work

Speak to the work.
Keep your hands on the work.

Jarvis is the assistant inside VibeSpace. Local Kokoro voice supports on-device speech output. Hands-free and push-to-talk modes keep the assistant close, while Ctrl+Space dictation can write inside VibeSpace or into other desktop apps where operating-system permissions allow.

Voice
Local Kokoro output, with visible listening and paused states.
Dictation
Ctrl+Space is focus-aware inside the app and can paste into the focused desktop app when permitted.
Actions
Scheduled Jarvis Actions keep prompts and their saved output connected to the workspace.
Average typing40words / minute
Average speaking150words / minute
YOU / LIVE TRANSCRIPTReady

Your finalized speech will appear here.

Browser speech recognition is free to this page but may use your browser vendor's speech service. No paid transcription API or VibeSpace server is used.

Issue 06 / Context

Issue 06 / Memory Has a Place

Context should have edges.

Context is selected, not inhaled. Files, conversations, and decisions become a visible project boundary, so every agent can show what it read—and what stayed outside the assignment.

Project item / a scoped source
Chat or agent / an active consumer
Filament / an attached relationship
Text equivalent: Project brief connects to interface notes and release criteria. The active chat reads the brief. Researcher reads the interface notes. Reviewer reads the release criteria. The final decision is stored as project-scoped memory.
100%
Product surfaces / live optics

Open the workspace from inside the story.

Issue 07 / Operating Loop

Issue 07 / Command. Supervise. Return.

Jarvis sees the whole operation.

One real task becomes a visible route: attach context, assign terminals and agents, stop at approval, then return the evidence to the same thread.

Jarvis CAO / Node 01

State the real task.

Ask for the work you would actually do—not synthetic busywork. This website only demonstrates the route.

Visible laneHuman approvalAuditable return
State / deterministic previewExternal effect / noneOutput / visible evidence

Step 01 of 06. Request is visible.

Text equivalent: Request → Context → Route → Work → Approval → Evidence. External or destructive effects stop at the visible approval boundary.

PR31 / Draft preview

Jarvis CAO supervises the work you meant.

Schedule a scoped task, keep agent progress visible while you are away, recover after sleep or resume, and return an auditable result. Jarvis never silently approves a permission or invents busywork.

01

Schedule the actual taskExample: verify the release candidate and prepare evidence by morning.

02

Supervise bounded agentsAgent Island, sticky routing, provider identity, and current status stay visible.

03

Stop at approvalPermissions and external effects remain explicit. No automatic approval.

04

Return evidenceContext read, actions taken, blockers, and completion evidence remain inspectable.

VibeSpaceProject Atlas Interactive simulation
Jarvis sessionChoose a simulated chat to run its visible route.
Ready
ModePreview only
BoundaryApproval on
External effectsNone
EvidenceWaiting
Jarvis

Select one of the three chats. The website will simulate its route without running commands or contacting an external service.

Interactive website preview / no real commands or agents

Issue 08 / Boundaries

Issue 08 / Local by Design

Your keys stay yours.

Local-first is a boundary, not a mood. Chats, tasks, settings, schedules, and memory stay on the machine by default. Desktop API keys use the operating-system keychain. Telemetry is off by default. Cloud sync is optional.

  • 01Ollama can route supported local models offline and without a provider key.
  • 02Destructive actions and multi-terminal plans remain behind approval cards.
  • 03Declining an approval leaves the action unrun; malformed plans fail closed.
  • 04Optional cloud sync is a choice, not the default storage path.

Vault closed. Synthetic key hidden.

Issue 09 / Architecture

Issue 09 / Built Open

Open at the core.

VibeSpace uses a Tauri 2 and Rust desktop shell around a React and TypeScript interface built with Vite and Tailwind. PTY and tool layers connect the workspace to real desktop workflows. The core is available under Apache-2.0.

WindowsmacOSLinuxApache-2.0 core
View source Release status
Layer 01
Tauri 2
desktop shell Layer 02
Rust
native systems Layer 03
React / TypeScript
workspace interface Layer 04
PTY / tools
terminal workflows Layer 05
Vite / Tailwind
frontend foundation
Issue 09 → 10 / Reversible assemblyOpen systems gather into one V.
Plans / Authoritative catalog / August 2026

Choose your orbit.

Every plan starts with VibeSpace Access. Choose the feature allowance that matches the work; your own provider keys and unlimited local Kokoro remain available on every tier.

$20Access / month after trial

$20 Access includes full access to the VibeSpace app. Start with a 30-day introductory Access trial; after the trial, the required $20/month Access subscription keeps the complete desktop workspace active. Each optional feature plan is billed separately and determines hosted-service allowances.

App coming soonPayments opening later. Prices below document the current catalog for comparison; no card collects payment, creates a subscription, or opens checkout.
Plan 03 of 05 / Nova selected
VS / SPARK / 00VLocal-first foundationSpark$20monthly total$20 Access+$0 feature plan
  • Full access to the VibeSpace app
  • 1,000 shared credits
  • BYOK on every provider
  • Unlimited local Kokoro
  • Supported hosted services
  • Jarvis Call not included
  • SMS not included
  • Cloud sync not included
  • Tool publishing from Nova
  • Priority routing from Nova
Access + Spark
VS / ORBIT / 01VConnected essentialsOrbit$30monthly total$20 Access+$10 feature plan
  • Full access to the VibeSpace app
  • 5,500 shared credits
  • Jarvis Call included / Up to 55 Jarvis Call minutes
  • Up to 550 SMS texts
  • BYOK on every provider
  • Unlimited local Kokoro
  • Cloud sync included
  • Tool publishing from Nova
  • Priority routing from Nova
Access + Orbit
VS / NOVA / 02VSerious daily workNova$70monthly total$20 Access+$50 feature plan
  • Full access to the VibeSpace app
  • 27,500 shared credits
  • Jarvis Call included / Up to 275 Jarvis Call minutes
  • Up to 2,750 SMS texts
  • BYOK on every provider
  • Unlimited local Kokoro
  • Cloud sync included
  • Tool publishing included
  • Priority routing included
Access + Nova
VS / SINGULARITY / 03VHigh-throughput studioSingularity$120monthly total$20 Access+$100 feature plan
  • Full access to the VibeSpace app
  • 55,000 shared credits
  • Jarvis Call included / Up to 550 Jarvis Call minutes
  • Up to 5,500 SMS texts
  • BYOK on every provider
  • Unlimited local Kokoro
  • Cloud sync included
  • Tool publishing included
  • Priority routing included
Access + Singularity
VS / SUPERNOVA / 04VMaximum hosted allowanceSupernova$220monthly total$20 Access+$200 feature plan
  • Full access to the VibeSpace app
  • 110,000 shared credits
  • Jarvis Call included / Up to 1,100 Jarvis Call minutes
  • Up to 11,000 SMS texts
  • BYOK on every provider
  • Unlimited local Kokoro
  • Cloud sync included
  • Tool publishing included
  • Priority routing included
Access + Supernova

Usage equivalents: Maximums assume the entire monthly shared-credit pool is allocated to one service. Mixed usage reduces each maximum. Jarvis Call uses 100 credits per PSTN minute; SMS uses 10 credits per text.

N
Nova / $70 monthly total

$20 Access includes full app access; the $50 Nova feature plan adds 27,500 shared credits—up to 275 Jarvis Call minutes or 2,750 SMS texts when allocated to one service.

App coming soon / payments opening later / no checkout

Catalog authority, August 30, 2026: verified against UnifiedChungus subscription plans and billing catalog at commit adc1ee3a5b0e056ac6f5efc258afd6df5a25b4f8. The catalog is documented here for preview; the app is coming soon, payments are opening later, and checkout remains closed.

Issue 10 / One Place to Work

Not nine tools. One place to work.

One workspace. Keep moving.

AI / LOCAL / OPENVibeSpace keeps the intelligence connected to the work.

ModelsAgentsTerminalsContextVoiceSkillsActionsLocalMemory / V Core

Nine systems are visible as separate working parts.

VibeSpace keeps the model, agent, command, voice note, task, project context, and decision in one visible place—without turning local control into fine print.

App coming soon Open GitHub
DesktopWindows / macOS / Linux
CoreApache-2.0
Data postureLocal first
TelemetryOff by default

Questions / Before install

The factual part.

Is Jarvis the product?

No. VibeSpace is the desktop AI workspace. Jarvis is the built-in assistant inside it.

Can VibeSpace work with local models?

Yes. Ollama support provides local, keyless routing for supported models. Model performance and hardware requirements depend on the selected model and computer.

What does “21+ providers” mean?

VibeSpace exposes a 21+ provider BYOK model hub. Live adapter availability can vary by release; the repository and current app are the source of truth.

Where are API keys stored?

Desktop provider keys use the operating-system keychain. This website never reads a real key; the vault shows a synthetic masked token only.

Do terminal plans run without approval?

Destructive Jarvis actions and multi-terminal orchestration are approval-gated. The terminal wall on this page is fictional and never executes a command.

Is cloud sync required?

No. VibeSpace is local-first, cloud sync is optional, and telemetry is off by default.

Which platforms are supported?

VibeSpace targets Windows, macOS, and Linux. Installer and signing status can vary by current release.

What works if WebGL is unavailable?

The complete written story, CSS/SVG fallback art, interactions, official links, FAQ, and directory remain. Three.js is an enhancement, not a content dependency.

VibeSpace / Product surface

Workspace view