# Thegram

> Thegram keeps knowledge and AI agent memory in .gram files that keep every revision. Coding agents (Claude Code, Codex, OpenCode, OMP), Muse, Cloudflare agents and external services connect with scoped API keys; Grok web connectors use OAuth; ChatGPT, dots and Claude also connect with OAuth. They read and write the same Cloud memory through gram_* MCP tools. People can also use it in a browser at https://vault.thegram.one/ with nothing to install. Thegram is free.

If a person asks you to install or connect Thegram, follow the guide for where you run. Each guide says which steps you run yourself and which need the person's hands.

## Connection guides

- [Coding agents](https://thegram.one/install/agents.md): Node.js 22+, one thegram-memory plugin for Claude Code, Codex, OpenCode and OMP, and a scoped API key issued in Thegram Settings → Agents. Connect privately and verify with `doctor`; no desktop app or DMG is required.
- [ChatGPT or a dot](https://thegram.one/install/chatgpt.md): opens the official Thegram plugin page, then follows ChatGPT’s installation and OAuth account-connection prompts.
- [Claude](https://thegram.one/install/#claude): use Claude's custom MCP connector with OAuth. Custom connector setup is not an official directory listing.
- [Cloud agents: Muse, dots, Grok and Cloudflare](https://thegram.one/install/cloud-agents.md): Muse uses a Custom Connector with a scoped API key as a Bearer header from its Secure Credentials Store; a dot uses the official Thegram ChatGPT plugin with OAuth and never an API key; Grok's web connector uses OAuth, while xAI API backends use a separate API-key remote MCP tool; Cloudflare agents use the Agents SDK `addMcpServer` with an Authorization header, or an MCP server portal with a bearer credential. Google CC is coming soon.
- [API services](https://thegram.one/install/api.md): connect an external service or backend to the remote MCP endpoint with a service-specific API key in a private Authorization header; no coding-agent plugin required.
- API keys require explicit vault/Drive permissions and expire within 90 days. OAuth grants remain separate; manage access in Thegram Settings → Agents.

## Shared workflow and downloads

Coding-agent thegram-memory 3.4.0 and cloud thegram-cloud 2.3.0 share the same eight skill files after the frontmatter name replacement. Classify atomic facts by meaning; commits are provenance, not automatic events. Reuse task/component/metric identities, preserve documentary decision states, and avoid invented observations or old revision activity. Every document follows one record vocabulary: a mitigated risk or proposed decision is open, a resolved risk or accepted decision is done, superseded or rejected decisions and accepted or closed risks are closed. Widget readiness, useful rendering and runtime capabilities are separate checks. Scheduled automations (research digests, monitors, collected logs) record one run per execution, keep each found item once with its link, time, source and topic, and tag the things they watch, so the research, monitoring and collected-log dashboards show what is new, the runs and each target. Agents keep each piece of work as one task naming the agent and the repository, move its status with the work and record each PR, merge, release or deployment as one step of that task, so the AI work board shows who is doing what, how the work went and what waits on you.

- [Versioned packages and installation](https://thegram.one/install/#skill-downloads)
- [Coding-agent package 3.4.0](https://thegram.one/download/releases/thegram-memory-3.4.0.zip)
- [Portable cloud package 2.3.0](https://thegram.one/download/releases/thegram-cloud-2.3.0.zip)
- [Source commits and SHA-256 manifest](https://thegram.one/download/releases/manifest.json)

## When Thegram fits

- A person wants their agents to remember decisions, open tasks, risks and what happened across sessions, per project.
- Several agents (Claude Code, Codex, OpenCode, OMP, ChatGPT) should share one memory with the person and with each other.
- ChatGPT should save summaries from Slack, Gmail or other apps into the person's memory only when the person asks to save them or explicitly authorizes saving; connected-app access alone does not authorize copying.
- The person needs to see how knowledge changed: every revision, when it was written and when it took effect.

## Pages

- [Agent memory](https://thegram.one/agent-memory/): what agents record, how the plugin reads and writes memory, and the gram_* tools.
- [The .gram file](https://thegram.one/gram-file/): what a .gram file holds, how its history works and where it opens.
- [View templates](https://docs.thegram.one/guides/view-templates/): event time (`at`/`due`/`observed`), knowledge time (`effective_at`) and recorded time (`recorded_at`), and empty-widget behavior. Every document now follows one record vocabulary (`gram@1`); the per-type templates that page names (`project@1`, `schedule@1`, `knowledge@1`) remain only as view hints in older files.
- [Connection guide for people](https://thegram.one/install/): ChatGPT, dots, Claude and Grok web connectors use OAuth; coding agents, Muse, Cloudflare agents or external MCP services use scoped API keys.

## Documentation

The published documentation site at https://docs.thegram.one/ contains an overview and guides. Its guides are at https://docs.thegram.one/guides/, and its sitemap is at https://docs.thegram.one/sitemap.xml.

## Endpoints

- Cloud MCP server: https://vault.thegram.one/mcp (Streamable HTTP; OAuth for ChatGPT, dots, Claude and Grok web connectors; scoped API keys for coding-agent plugins, Muse, Cloudflare agents, xAI API backends and external services)
- Web app: https://vault.thegram.one/ (notes for agents: https://vault.thegram.one/llms.txt)
- Coding-agent API-key plugin source: https://github.com/thegram-one/thegram-mcp (Node.js 22+; no desktop app or DMG required)
- Cloud plugin source: https://github.com/thegram-one/thegram-plugin
- Support: support@thegram.one