space

A space is a named subdivision of an org’s memory — one per project, service, or workstream. Spaces are how a shared workplace stays useful as it grows, instead of collapsing into one pile where every query returns everything.

Parameters

'list' | 'create' | 'info' | 'switch'

required

The operation to perform.

string

Human-readable space name. Used by create.

string

Space slug. Used by info, switch, and optionally create.

Actions

list
create
info
switch

Enumerate the spaces on this org.

{ "action": "list" }

Create a space. Pass a readable name; supply slug to control the identifier rather than having one derived.

{
  "action": "create",
  "name": "Billing service",
  "slug": "billing"
}

Inspect one space by slug.

{ "action": "info", "slug": "billing" }

Make a space the active one for this session, so subsequent calls do not need to pass space each time.

{ "action": "switch", "slug": "billing" }

Using a space

Once created, pass the slug on reads and writes:

{ "content": "Invoices generate nightly at 02:00 UTC", "space": "billing" }

{ "query": "when do invoices generate?", "space": "billing" }

Or switch once and let the session carry it.

Spaces are not a tenancy boundary

Spaces subdivide an org’s memory for relevance. They are not an isolation boundary — anyone holding the org’s API key can read any space in it.If two bodies of work must never see each other — separate clients, separate customers — they need separate orgs and separate keys, not separate spaces.

See Scope and spaces for how spaces interact with org and agent scope.

Overview

Reading

Writing

Artifacts

Managing

Parameters

Actions

Using a space

Spaces are not a tenancy boundary

​Parameters

​Actions

​Using a space

​Spaces are not a tenancy boundary

Parameters

Actions

Using a space

Spaces are not a tenancy boundary