---
name: Ideaspace Protocol for developers
summary: Evaluate the open Ideaspace Protocol, inspect its repository shape, and build a conformant agent surface.
---

Ideaspace Protocol

# One standard, not one memory product.

An ideaspace is an ordinary folder of Markdown under git, plus a few files that tell any AI agent how to work in it.

The protocol is open, MIT-licensed, and provisional before 1.0. Use its repository shape directly, or make it native to a harness without inheriting somebody else's memory product.

[Browse it as an ideaspace ↗](https://ideaspaces.xyz/repos/n_64dbf7878f05362337a6cda6) [Read SPEC.md ↗](https://github.com/IdeaSpaces-xyz/ideaspace-protocol/blob/v0.4.8/SPEC.md) [How the folder shape works →](how-it-works.md)

## Published foundation

- Published release: v0.4.8
- Status: Provisional before 1.0
- License: MIT
- Package: @ideaspaces/protocol

### Inspect the same thing the integrations run.

The public repository keeps the spec, schema, reference TypeScript library, shared skills, and conformance kit together. TypeScript is the reference implementation, not the requirement.

The hosted view is the protocol repository presented as an ideaspace. Browse the shape as a user would, then inspect the same files on GitHub.

```text title="Install the reference library"
npm install @ideaspaces/protocol
```

[IdeaSpaces-xyz/ideaspace-protocol ↗](https://github.com/IdeaSpaces-xyz/ideaspace-protocol)

## The compatibility boundary

### Share the shape. Keep your harness yours.

The protocol owns portable shape and operating semantics. Your integration owns how those abilities appear to its agent and users. Claude, Pi, an MCP adapter, and a future harness can stay compatible without forcing identical tools or prompts.

**Protocol:** Repository shape, portable local awareness, shared operating skills, and conformance.

**Plugin or harness:** Prompt placement, concrete tools, permissions, session lifecycle, and the experience native to each agent.

**CLI:** Common command-line mechanics for creating, capturing, committing, publishing, and syncing spaces.

**Hosting — optional:** Remote sharing, access control, public exploration, and search across spaces. Local work does not require it.

```ts title="Portable local awareness"
import {
  assembleContentAwareness,
  renderContentAwareness,
} from "@ideaspaces/protocol";

const manifest = await assembleContentAwareness({
  position: process.cwd(),
});

if (manifest) {
  const context = renderContentAwareness(manifest);
  // Place it where your harness expects awareness.
}
```

## Shared mechanics

### Need command-line mechanics too?

The CLI implements create, capture, path-scoped commit, authentication, publish, push, and pull. Use the protocol directly for portable local reads; reach for the CLI where shared mechanics or hosting operations earn it.

```text title="Terminal"
npm install -g @ideaspaces/cli
```

[IdeaSpaces-xyz/cli ↗](https://github.com/IdeaSpaces-xyz/cli)

## Use the standard

### Make it native to the agent you already use.

[See the integrations →](integrations.md)