# Docs for a product that is honest about its stage.

Documentation. Everything here is labelled. Verified means reproducible. Working now means it runs in the current internal deployment, not that public access is open. In build means the shape is decided but the product flow is not ready yet.

- Compatible: Claude, ChatGPT / Codex, Cursor and Grok Bot
- Transport: MCP, Streamable HTTP
- No self-service yet

Canonical: https://unforgetter.com/docs

## What you can do today.

| Area | Status | Notes |
| --- | --- | --- |
| Read the canonical memory | Verified | Versioned Markdown; opens in any editor. |
| Connect Claude, ChatGPT / Codex, Cursor and Grok Bot | Compatible | All connect through MCP. Client-specific setup and the current onboarding path differ. |
| OAuth login for remote MCP | In build | OAuth 2.1 with PKCE and resource binding is the alpha design. The current internal deployment uses scoped bearer tokens. |
| Revoke, export, delete | In build | Product functions with live smoke tests as their gate. |

## Five words the rest of the docs depend on.

- **Workspace · The unit of ownership**: One owner, one canonical memory, one set of scopes. Tokens are issued per workspace.
- **Project · A scope inside a workspace**: Decisions, open threads and conventions for one piece of work. A token carries a catalogue of projects it may select.
- **Working truth · The compiled current record**: What applies now: decisions with reasons, open threads, rejected proposals, methods, provenance and freshness. Not the transcript history.
- **Context bundle · What an agent receives for a task**: A bounded response: identity, relevant policies, current facts, open threads, freshness and pointers for deeper retrieval.
- **Proposal · The only way an agent writes**: A bounded change with actor, evidence and target, validated and published by a single consolidator. Never a direct write.

## How an agent connects in the current deployment.

The current internal deployment uses scoped tokens issued during guided setup. Private-alpha access is not open yet; this is the connection pattern it is being prepared to use.

1. **Receive a scoped token.** Each agent zone gets its own revocable, time-limited bearer token bound to a workspace, a trust zone and a project catalogue. Tokens are exchanged out of band during onboarding, never on this site.
2. **Point the client at the MCP endpoint.** Remote clients use Streamable HTTP against the workspace's /mcp endpoint. Local Claude Code and Codex use a small stdio proxy that reads the token from an encrypted store, so it never sits in a config file.
3. **Call list_projects, then get_context.** The agent lists the projects its token allows, selects one, and requests context for the task. Selection can never widen the token's authority.
4. **Work, then propose.** At the end of the session the agent submits a proposal with what it decided, what stayed open and the evidence. The consolidator reviews and publishes.

Representative remote client configuration. Field names follow the client; the endpoint and bearer token are supplied during onboarding. (Working now)

```json
{
  "mcpServers": {
    "unforgetter": {
      "type": "http",
      "url": "https://<your-workspace-gateway>/mcp",
      "headers": { "Authorization": "Bearer <scoped token, supplied out of band>" }
    }
  }
}
```

> In build. A hosted OAuth flow will replace bearer tokens so clients connect without handling secrets. Until then, do not paste tokens into shared configuration.

## Read next.

- [MCP reference](https://unforgetter.com/docs/mcp): Tools, inputs and outputs, scopes, errors and the proposal flow.
- [Memory is not context](https://unforgetter.com/blog/memory-is-not-context): What an agent actually needs to continue work.
- [What a context compiler does](https://unforgetter.com/blog/what-a-context-compiler-does): Include, exclude, scope and freshness, explained with a real task bundle.
- [Security and ownership](https://unforgetter.com/security): Invariants, hosting facts and what is not claimed.

## Docs are only useful with a workspace.

Apply for the private alpha and the quickstart above becomes something you can actually run.

- [Join the private alpha](https://unforgetter.com/private-alpha)

## Next

- [MCP reference](https://unforgetter.com/docs/mcp)
- [How it works](https://unforgetter.com/how-it-works)
- [Security and ownership](https://unforgetter.com/security)

---
Status: Private alpha · guided setup. Contact: hello@unforgetter.com.