Subspace

What is Subspace?

Subspace is a macOS app that runs multiple agent tools in one place while keeping cross-session “memory” tied to your project workspace. It’s designed to reduce the need to re-explain context when you switch between agent sessions and tools.

The app provides a workspace-based interface where agents can operate alongside terminals, docs and files, and a browser. It also builds and surfaces structured memory so that new sessions start with recent decisions, blockers, progress, and plans.

Key Features

• Cross-session memory workspaces: Projects and worktrees get workspaces, and Subspace backfills memory from recent agent sessions for that workspace.
• Runs multiple agent CLIs side by side: Launch agent tools from the command palette (e.g., Claude Code, Codex, OpenCode, and others listed on the site) within the same app so you don’t have to juggle separate contexts.
• Token-efficient memory with structured observations: Conversations are compressed into observations tagged with information such as decisions, blockers, and progress.
• Mid-session memory search: Agents can search memory during a session by text, tag, workspace, or timeline.
• Transparent memory visibility: Everything Subspace remembers is visible in the app, and you can clear it with a command.
• Keyboard-first command palette: Cmd+K to launch agents, switch workspaces, open files, and run shell commands from one input surface.
• Browser pane with source-referenced comments: Select text on a webpage (in the app’s browser pane) to leave comments that include the source component name and file details with line numbers.

How to Use Subspace

1. Add a project folder: Point Subspace at a folder. It creates workspaces for your project and any worktrees, and backfills memory from recent agent sessions.
2. Launch agents from the command palette: Use the command palette to start an agent tool (e.g., Claude Code or Codex). Agents run in the app’s terminal panes.
3. Work with docs, files, and the browser: Open relevant documents and files in workspace panes and use the integrated browser when you need to reference what you see.
4. Leverage memory during and across sessions: Use the app’s memory so the next session starts with prior context already built and visible. Clear memory when needed.

Use Cases

• Switching between different agent tools on the same codebase: Run one agent to investigate, another to implement, and a third to validate—while sharing the same workspace memory so you don’t restate the whole situation each time.
• Project work where context changes over time: Begin a session, make decisions, track blockers, and leave actions “open” so that a later session can pick up with a synthesized status update and prior context.
• Developer workflows that require quick navigation: Use Cmd+K to open files, run shell commands, and launch agents without leaving the workspace environment.
• Reviewing and iterating on a web UI with referenced feedback: Select text in the browser pane to leave a comment; the comment carries source component/file and line references so the agent can act on the exact location.
• Collaborative-style agent feedback loops: Queue feedback from multiple spots (terminal, docs, browser) and send it as one batch so agents receive consolidated guidance.

FAQ

Does Subspace only work with one agent tool?

No. Subspace is built to run multiple agent CLIs in the same app and share memory across those tools within a workspace.

How does cross-session memory work?

Subspace builds memory in the background and associates it with the workspace. When you start a new session for that workspace, prior context (including decisions, blockers, progress, and plans) is already available.

Can I remove stored memory?

Yes. The app supports an action to clear memory (the site mentions /clear).

Is the memory visible to me?

Yes. The site states that everything Subspace remembers is visible in the app rather than being a black box.

Is there a browser inside the app?

Yes. Subspace includes a browser pane that supports highlighting and commenting on page content, with comments tied to source details such as component name and file/line information (as described on the site).

Alternatives

• Standalone agent/chat apps without workspace memory: These can help with single sessions but may require you to re-provide context when switching tools or restarting work.
• Editor-centric multi-tool workflows (terminals + AI chat): You can approximate the workflow by combining an editor, terminal, and a chat tool, but you would not necessarily get workspace-bound cross-session memory and structured, visible memory tracking.
• Local note/task systems plus manual context transfer: Keeping decisions and plans in a notes app can help across sessions, but it’s typically manual and not integrated into agent launches and memory search during a session.
• Generic project dashboards / window management tools: These centralize workspaces and reduce Alt-Tabbing, but they usually don’t provide the agent memory layer described for Subspace.