Create a room
Give every mission its own room — a launch, a research thread, an ops shift — so contexts never collide.
Your AI coding agents, memory and tools in one self-hosted workspace, on any device.
Runs in your browser with local demo data. No account, no AI provider.
Open demo in a new tabStart in Room 1. Switch rooms, type and explore the workspace.
I built it to be my main work tool. I'm a developer! And it became my main tool and work environment. I no longer need to open email, social media or any development program: absolutely nothing. I'm inside SpaceApp all day; I even watch YouTube videos and listen to music through SpaceApp.
25 years in IT, 17 of them building and running a large e-commerce platform. He builds SpaceApp with the AI coding agents that run inside it.
Pick up the same work on your phone, tablet or computer. Your workspace stays with you.
Setup starts with OpenCode; add the others with one command each when you need them. What can run depends on the accounts you sign in to.

Coming next Hermes, Oh My Pi, Qoder, Muse, Droid: declared adapters without a public installer yet.
Have a real conversation with your workspace. Open projects, direct agents and ask what’s done. Keep your hands on the idea.
Live voice runs on the maker's own SpaceApp today. In the public release it needs a Gemini key on the application core, which the launcher cannot set yet.
Start a conversation with your workspace.
Decisions, discoveries and project knowledge, connected in one canonical memory you can search and browse across sessions.
Space Memory keeps decisions and project knowledge as searchable records with a graph view. Vector search is not configurable yet.
packages/memory-graph) backed by containerized PostgreSQL with pgvector and Temporal workflows for idempotent ingestion.Project knowledge and decisions share one graph.
Each copilot is a pane with its own CLI agent, memory and activity feed. You answer its questions and reviews in the rail; how much it does alone is your choice. They run on the maker's own SpaceApp today; the public release has the copilot panes but not yet the tools their agents work with.
Works through your Gmail with gradual autonomy: it drafts and asks first, acts under rules you approve, or acts on its own when you allow it.
Coming nextWorks through your queue of job postings in the pane browser, asks you for what it cannot answer, and keeps a tracker of your applications.
Coming nextDrafts posts from your briefs and publishes them on your own accounts through the pane browser after your review.
Coming nextFinds client work on freelance platforms and writes proposals under daily limits, with each send checked first.
Coming next

Copilots are optional modules: new installs start with none of them. Turn one on with optionalModules in the launcher's config.json, then run npx --yes run-spaceapp@latest repair. Copilots that use the pane browser need the large profile.
Several models work on the same question independently, then rank each other's answers. It runs on the maker's own SpaceApp today; the public release does not yet give the Council a model to work with.

A coordinator model reads your question, asks what is missing and proposes who answers.
After your approval, each member answers on its own from the same evidence.
The positions are merged without names and every member scores them.
The coordinator writes the agreed Top 3.
Space is not another chat window. It is a system of rooms where every kind of work has its place.
Give every mission its own room — a launch, a research thread, an ops shift — so contexts never collide.
Chat with agents, attach real CLI terminals and pin browser views (large profile), all side by side.
Agents keep their context, artifacts stay within reach, and you stay in flow while the room does the heavy lifting.
Every pane in a room exists for a reason — and stays exactly where you need it.
The Room Agent watches every pane in its room and shows which ones wait for you.
Coming next Talk to it about the room, and with Auto-answer on it answers the prompts that wait for you, so the agents keep working while you are away.
Coming next: it warns when two panes change the same files, and their work joins one release train.
Codex, Claude Code, Gemini, OpenCode, Autohand Code, Qwen Code, Kimi Code, Grok Build, DeepSeek, Cursor, GitHub Copilot, Hermes, Oh My Pi, Qoder, Muse Code, and Droid share one governed operating layer: the same skills library, approved MCP server catalog and canonical memory, delivered through each runtime’s supported integration path.
Canonical memory uses a Room, Project and System taxonomy with tags, provenance, lifecycle states and audited change sets. Deterministic Greek/English TF-IDF topic vectors and cosine-similarity relationships connect related knowledge.
Inside Space, an Obsidian-style knowledge graph powered by Graphology, Sigma and ForceAtlas2 provides clustered and relationship views without leaving the app. Common History preserves operational continuity across all sixteen CLI runtimes.
Sixteen panes per room, one-click presets, and warm rooms that keep every session alive between switches.
11 installable CLI runtimes, with four focused starter panes, correct branding, shared history, and runtime-aware controls.
Live Chrome panes with tabs, device viewports, evidence capture, and one-click operator handoff (large profile).
Private clipboard history and a media dock for the files your agents produce.
Join the real build sessions, follow new features as they land, and ask questions while Space takes shape. The latest YouTube livestream appears here automatically.

Click anywhere to start video directly
These run on the maker's own SpaceApp today. They are not in the public release yet; each card says when to expect it. What shipped so far is in the release notes.
Client work on freelance platforms, proposals under a send check.
Coming nextThe Room Agent warns when two panes change the same files; work joins one release train.
Coming nextScreenshots and short videos of your own workspace in device and social sizes.
Coming nextTokens per model, provider and account, with their API value.
Coming nextOne mind for your whole space: it watches every room and brings you only the decisions that need you.
Coming nextOne gateway for your model accounts.
Coming nextSpaceApp notifications on your Android phone.
Coming nextEvery release of the public installer, run-spaceapp, is on npm and in the release notes.
SpaceApp and the run-spaceapp launcher move to the MIT License, OpenCode 2 is the first CLI, backup saves the database, files, memory and workflow history from one moment, a failed restore puts every database and file back, and dependency security updates.
Team accounts with a CLI container per user (off until the owner runs user enable), Codex sandboxing where the host allows it, install telemetry only after the owner's Yes, and session, WebSocket Origin and framing hardening.
Security hardening: other local sites cannot use your session, child processes no longer receive the session secret, and optional modules start off on new installs.
CLI panes start in their own room workspace, an update notice with a Copy button, first prompts in the setup wizard, and opt-in first-answer telemetry.
The first OpenCode task no longer stops at a scratch-directory permission prompt, and guided setup works on every screen size.
The first free OpenCode model is checked with a real tool call, with Big Pickle tried first.
The install wizard respects the telemetry answer (the default is No), and small-profile installs no longer roll back.
SpaceApp runs on your own machine. The AI providers you connect receive what you send them, under their own terms.
Open source, copyright INTRATRADE SINGLE MEMBER P.C. Use, copy, modify, distribute and sell it, including self-hosting and commercial use, as long as the copyright and licence notice stay with it. Read the LICENSE.
The install wizard lists what is sent and asks; the default is No. With Yes, a random install ID links the install, setup and first-answer events and at most one activity event a day; no files, prompts or credentials. Security & privacy guide.
Install once. Connect your AI.
Start building from wherever you are.
Small profile: 4 CPUs, 7 GiB RAM and 6.5 GiB free disk. Browser panes need the large profile: 8 CPUs, 15 GiB RAM and 11 GiB free disk. Node.js 20.11+ is required; the launcher installs Docker if it is missing. OpenCode is the first CLI in setup.
To continue from another device, connect to the same reachable host. Keep that host running. Phones and tablets access your workspace; they do not run the Docker installer.
Run directly in Command Prompt, Terminal or Bash with npx — no global installation required. First-time account registration, password resets, automatic health checks, and lifecycle management.
SpaceApp is a super agent app for building with AI. Start with a conversation, then bring your agents, tools, files, previews, plans and shared memory into the same space. Use as much of it as you need.
Yes, once your installation is reachable from them. By default SpaceApp listens only on its own host; to use it from a phone, tablet or another computer, give it a reachable address with TLS and a firewall (see Remote & mobile access in the docs). The host must stay on.
SpaceApp is free to self-host. Bring your own AI accounts or API keys; provider subscriptions and usage are separate.
SpaceApp is open source under the MIT License, copyright INTRATRADE SINGLE MEMBER P.C. You may use, copy, modify, distribute and sell it, including self-hosting and commercial use, as long as the copyright and licence notice stay with it. The LICENSE file on GitHub has the full terms. Read the LICENSE ↗
No. Start with one conversation or one agent, and add providers and accounts as your work grows. The setup starts with OpenCode; you choose what to connect next.
No. The copilot panes are optional modules, and new installs start with none of them; you turn one on with optionalModules in the launcher's config.json and npx --yes run-spaceapp@latest repair. Their agents' tools are not part of the public release yet: the copilots work on the maker's own SpaceApp today.
Everything on this page without a label is in the current public release. A card marked “Coming in” a version arrives with that release; a card marked “Coming next” runs on the maker's own SpaceApp and is not public yet.
Your workspace runs on your own installation. Connected AI and external services process the information you send to them under their own policies.
Only if you say yes. The install wizard lists what is sent and asks; the default is No. With Yes, a new install gets a random install ID that links its events: the install (OS, CPU, RAM, profile, versions), owner setup, the first CLI and the first answer, and at most one activity event a day (screen size, browser, UI language, version). No files, prompts, answers or credentials are sent, and the IP address is not stored. Nothing is sent with No.
Yes. The live demo runs in your browser with local demo data and no account; it does not contact AI providers or a real installation. When you like it, install your own workspace.
A paid pilot for software and AI teams of 3–15 developers who already use AI coding CLIs. We install SpaceApp for each developer on their own machine, using your own API keys.
CLIs in the pilot: OpenCode and Claude Code. Other CLIs are added when they pass a task on your install during setup.
MIT licensed: no licence fee. See the security boundaries.
Questions, feedback or the workspace your team needs. We’ll reply personally.
Prefer live community chat?
Join DiscordSpaceApp is a product of INTRATRADE SINGLE MEMBER P.C., Patras, Greece · GEMI 180769616000 · VAT EL802678365