Product

Spaces

Where humans and AI work together.

A Space is a home for your team — people, agents, tools, and work. Each person has their own Space. Each team has theirs. You can share access, but boundaries are clear. Work persists across sessions. Every mission builds on the last.

Your Space

👤

You

🤖

Sarah

🤖

Maya

Files, memory, repos, MCP servers

Missions running on schedule

Colleague's Space

👤

Them

🤖

Alex

🤖

Lena

Their own files, tools, context

Shared access when needed

Separate Spaces, clear boundaries. Share access when you want to — your Space is yours, but collaboration is one click away.

What makes a Space

🧠

Memory

Agents remember context across sessions. Instructions, preferences, and learned knowledge persist in CLAUDE.md and project files — so every conversation picks up where the last one left off.

No more re-explaining. Your agents know the codebase, the brand voice, the team structure.

📂

Work Artifacts

Reports, code, images, dashboards — everything an agent produces lives in the Space as real files. Not trapped in a chat thread. Browsable, editable, version-controlled.

An SEO report isn't a chat message — it's a file you can share, edit, and build on.

🤝

Shared Access

Humans and agents see the same files. You can review what an agent wrote, edit it, and the agent picks up your changes next time. True collaboration, not a black box.

Open the file browser, read the report, fix a sentence. The agent respects your edits.

🏠

Home for Agents

Agents live in the Space — their configuration, skills, and subagents are all here. Add agents to a Space like hiring someone into a team. They inherit the full context and get to work.

The Space is where agents belong. Not floating in the cloud — grounded in a real work environment.

🔌

Connected Tools

Each Space has its own MCP servers — Google Analytics, Ahrefs, Slack, GitHub, databases. Every agent in the Space can use them. Add a tool once, every agent benefits.

MCP integrations give agents real access to your data, not summaries of it.

🔄

Continuous Work

Spaces persist. An agent can start a task on Monday, continue Wednesday, and finish Friday — all in the same context. Missions run on schedule, building on previous results.

Weekly reports get smarter over time because the agent remembers last week's data.

🛠

Version Control

Every Space has its own Git history. Connect your GitHub account to clone multiple repositories into the same Space — agents work across all of them. Change your product and update marketing in the same session.

Real git, real commits, real pull requests. Agents push to GitHub, trigger CI/CD, and review Actions results.

🌐

Public Sharing

Share any Space content publicly with a link. Documentation, reports, simple websites — anything your agents produce can be published instantly. No separate hosting needed.

Agent writes docs, you flip a switch, the world can read them. Universal publishing built into every Space.

🎯

State of Work

A Space isn't a project management tool. It's the actual state of work — the files, the context, the connected tools, the history. Everything needed to pick up and continue.

New agent joins the Space? They inherit the full context instantly.

How Spaces work

1

Create a Space

Start empty or let the concierge agent set one up based on your needs. Name it, describe the work.

2

Add agents

Hire AI employees into the Space. Each agent brings their skills, but they all share the same files and tools.

3

Connect tools

Link your data sources — analytics, databases, CRM, code repos. Agents access them directly through MCP integrations.

4

Work accumulates

Every chat, every mission output, every file created stays in the Space. Context builds over time. Agents get smarter because the Space gets richer.

Spaces in practice

A Space adapts to any function. Here are examples — but your Space will be unique to your work.

Marketing Space

SEO reports, blog drafts, analytics dashboards, and keyword research — all in one place. Your content lead and SEO analyst share context.

Agents

Sarah (SEO)Maya (Content)Echo (Social)

Tools

Google AnalyticsAhrefsSearch Console

Engineering Space

Codebase context, CI/CD logs, security audits, and dependency reports. Your engineering agents work in the same repo.

Agents

Alex (Engineer)Lena (DevOps)Casey (Docs)

Tools

GitHubSentryLinear

Sales Space

Pipeline data, prospect research, email drafts, and meeting prep. Your BDR and sales agent share the CRM context.

Agents

Riley (BDR)Blake (Sales)

Tools

HubSpotLinkedInEmail

Under the hood

A Space is a real directory on a server. When an agent starts a session, the Space becomes their working directory. Files are files — not database records, not API abstractions.

/spaces/s-abc123/          # Space root (own .git history)
  CLAUDE.md                # Agent memory & instructions
  .claude/
    agents/                # Subagent definitions
    skills/                # Installed skills
  .mcp.json                # Connected tools config
  work/
    reports/               # Generated reports
    drafts/                # Content drafts
  .missions/               # Mission run history
  app/                     # Cloned repo: github.com/org/app
    src/
    package.json
  marketing/               # Cloned repo: github.com/org/marketing
    src/
    astro.config.mjs

The Space root has its own Git history. Cloned repos live as subdirectories via GitHub App integration — agents work across all of them in one session. Same structure as Claude Code locally.

Create your first Space

Start free. Add agents, connect tools, and let work accumulate.