Memory for
AI agents

• Decisions

  What was chosen and why. When the team changes its mind, the old decision is marked superseded and the new one says what it replaces, so the reasoning is never lost.

• Events

  Shipped changes and incidents, with the time they happened and a link to the commit or pull request.

• Tasks, risks and blockers

  What is still open, with status and priority, until someone closes it. The next session starts from this list instead of from scratch.

• Metrics

  Numbers that were actually checked, with their unit and when they were observed.

• Sources

  The Slack message, email thread or document a fact came from, cited by the events and decisions that rely on it.

• Links

  Records point at each other: a change implements a decision, a blocker holds up a task, a new decision replaces an old one. A link can also point into another .gram document.

1. One memory per project

   Each Git repository uses @mounts/<vault-id>/<repository>.gram, and its worktrees share that document. Directory overrides in ~/.config/thegram-memory/projects.json name an exact Cloud document.

2. One record vocabulary

   Every memory uses the same record types and statuses. The agent records decisions, tasks, risks and events with the status that fits, and the dashboard, search and every agent count them by one rule: a mitigated risk or a proposed decision is still open, a resolved risk or an accepted decision is done, and a superseded decision is closed.

3. A brief when the session starts

   Before a coding agent answers for the first time, the plugin gives it the project's brief: its documents, the open risks and tasks, and the records that match your first prompt. Later prompts bring what other agents and people changed in the meantime. In ChatGPT, once you pick the plugin in a chat, it reads the memory before it answers.

4. Look up, then read only what is needed

   The agent searches the memory and reads the few records or sections it needs, instead of loading a whole notes file into its context.

5. Every write is a revision

   Updates compare the field values the agent read, or explicitly pin a revision. If a precondition changed, the write is refused instead of overwriting, and the agent reads again before deciding.

6. One reminder, not a nag

   If a coding agent's turn edits files or makes a commit without recording anything, the plugin reminds it once to write down what changed.

7. Ask about the past

   The agent can read the project as it was on any date, or see when and why a decision changed before it reopens the question.

1. Install the plugin

   Give your agent the canonical installation guide:

   Install Thegram by following https://thegram.one/install/agents.mdCopy

2. Connect with your private key

   In the installed plugin directory run node dist/thegram-memory.mjs connect. Paste the key at the hidden terminal prompt, not into chat, and choose your Cloud vault. Run doctor to verify the connection.

3. Start a new session

   What does Thegram remember about this project?Copy

   Revoke the key in Settings to disable it. Local-only files are not uploaded automatically.

Coding-agent connection guide

1. ChatGPT

   Install the official Thegram plugin from ChatGPT. Follow its on-screen prompts.

   Install Thegram plugin

2. Claude

   Use Claude’s MCP connectors with OAuth and its published identity. Connect Thegram in Claude.

Install Thegram in ChatGPT

• gram_projects · gram_brief

  Which folders, vaults and Google Drive accounts the agent can reach, and one call to get oriented in a folder or a document.

• gram_recall · gram_context

  Search by relevance with date filters, then read many records in one call.

• gram_read · gram_get · gram_list

  One section of a document, one record, or the records that match a type, status, tag or date.

• gram_create · gram_patch

  Create a document, or change one against the values the agent read.

• gram_changes · gram_range

  What changed since a time or revision, and when and why one thing changed.

• gram_state · gram_relations

  A document as it was at a revision or a date, and the links around one record.