← Plugin catalog
Productivity

Thegram

C.Lab v4.7.2

The AI knowledge base for AX

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Search and cite linked goals, decisions, requirements and sources
  • Exact counts and rankings across a vault
  • Typed records with every change kept as history

Cost & access

Thegram does not sell products or process payments.

Declared limitations

  • Unsupported bulk deletion
  • Unrelated travel booking request
  • Unauthorized cross-account access

Onboarding example

What did we decide about the launch date, and what evidence supports it?
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 7, 2026. Package observed Nov 6, 2026.

View package source →

Description

From the marketplace listing

Thegram turns scattered documents and decisions into a knowledge base of linked goals, decisions, requirements, evidence and sources, kept as typed records in .gram files with every revision. People, Thegram AI and supported assistants read the same records and answer with the documents they rest on. This plugin connects your assistant to Thegram vaults and shared GramHub datasets such as Korean law, public bids, security advisories and developer docs: it searches by meaning, record type, status and date, gives exact counts and rankings, follows links between records and shows what changed and when. When you authorize saving, it writes decisions, tasks, risks, metrics and other typed records to the vault you choose, each as a new revision with its author and time; queries, analysis and drafts stay read-only unless saving is authorized. Use Thegram Cloud vaults or Google Drive separately connected at vault.thegram.one, sign in with your own Thegram account, and grant access per vault. The cloud plugin needs no running Mac and cannot access local-only Mac files. It does not itself fetch other apps, and connected-app access alone does not authorize saving. Shared-vault viewers cannot write.

Language: English · Automatically detected from descriptions.

Matches for “developer”

Exact text from the indicated source. A mention alone does not establish support for your task.

Publisher full description

Thegram turns scattered documents and decisions into a knowledge base of linked goals, decisions, requirements, evidence and sources, kept as typed records in .gram files with every revision. People, Thegram AI and supported assistants read the same records and answer with the documents they rest on. This plugin connects your assistant to Thegram vaults and shared GramHub datasets such as Korean law, public bids, security advisories and developer docs: it searches by meaning, record type, status and date, gives exact counts and rankings, follows links between records and shows what changed and when. When you authorize saving, it writes decisions, tasks, risks, metrics and other typed records to the vault you choose, each as a new revision with its author and time; queries, analysis and drafts stay read-only unless saving is authorized. Use Thegram Cloud vaults or Google Drive separately connected at vault.thegram.one, sign in with your own Thegram account, and grant access per vault. The cloud plugin needs no running Mac and cannot access local-only Mac files. It does not itself fetch other apps, and connected-app access alone does not authorize saving. Shared-vault viewers cannot write.

What changed

· 4 observations

Capabilities & instructions

Full description changed from “Read and write Thegram memory with the vault_* tools. One method answers from the person's vaults and from every GramHub shared dataset with the right scope...” to “Load first whenever the person says record, save, note, remember, 기록, 저장 or 남겨, or names a Thegram vault or folder (the...

View comparison →
Capabilities & instructions

Full description changed from “One purpose, one structured .gram file: shared memory for people and AI, with source-grounded information, decisions, relationships and change” to “The AI knowledge base for enterprise AX: linked goals, decisions, requirements, evidence and sources that people and AI read as one...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

· 7 observations

Capabilities & instructions

Full description changed from “Build and maintain enterprise-grade, source-backed knowledge in Thegram .gram documents with vault_* tools. Research any subject, project, organization or...” to “Read and write Thegram memory with the vault_* tools. One method answers from the person's vaults and from every GramHub...

View comparison →
Capabilities & instructions

Logo url dark changed from “https://files.openai.com/content?id=file_000000001d248206874592b463008b57” to “https://files.openai.com/content?id=file_00000000bd7082099735516412210774”. Skill “thegram-cloud” description changed from “Build and maintain enterprise-grade, source-backed knowledge in Thegram .gram...

View comparison →
Capabilities & instructions

Full description changed from “gram_*” to “vault_*”. Supporting files updated; open the comparison for details. Skill instructions changed from “gram_* tools. Research any subject, project, organization or plan across the connected sources the request covers (repositories, documents, chats, mail,...” to “vault_*...

View comparison →
Capabilities & instructions

Logo url dark changed from “https://files.openai.com/content?id=file_00000000ec248206bc4dbe48e83778c5” to “https://files.openai.com/content?id=file_000000001d248206874592b463008b57”. Skill “thegram-cloud” description changed from “gram_*” to “vault_*”. Skill “thegram-cloud” short description changed from “gram_*” to...

View comparison →

Technical updates · 2

Package or technical metadata updated

View technical comparison →

Package or technical metadata updated

View technical comparison →

· 1 observation

Capabilities & instructions

Logo url dark changed from “https://files.openai.com/content?id=file_00000000ec248206bc4dbe48e83778c5” to “https://files.openai.com/content?id=file_000000001d248206874592b463008b57”. Skill “thegram-cloud” description changed from “gram_*” to “vault_*”. Skill “thegram-cloud” short description changed from “gram_*” to...

View comparison →

· 4 observations

Capabilities & instructions

Supporting files updated; open the comparison for details. Skill instructions: added “A first page that stops with `LOW_RELEVANCE` already holds the strong matches; follow `more` only when the question needs every match. - When the person asks...”.

View comparison →

Technical updates · 2

Package or technical metadata updated

View technical comparison →

Package or technical metadata updated

View technical comparison →

· 5 observations

Capabilities & instructions

Full description changed from “Use Thegram gram_* tools as purpose-based memory shared by people and AI across ChatGPT, Claude, Grok and coding agents. Retrieve source-backed context,...” to “Build and maintain enterprise-grade, source-backed knowledge in Thegram .gram documents with gram_* tools. Research any...

View comparison →
Capabilities & instructions

Logo url dark changed from “https://files.openai.com/content?id=file_00000000813c82098ef315c86a701ba7” to “https://files.openai.com/content?id=file_00000000615c82098f2cc24cf1a28c2f”. Skill “thegram-cloud” description changed from “Use Thegram gram_* tools as purpose-based memory shared by people and AI across...

View comparison →

Technical updates · 2

Package or technical metadata updated

View technical comparison →

Package or technical metadata updated

View technical comparison →

· 4 observations

Capabilities & instructions

Full description changed from “cloud gram_* MCP tools as purpose-based memory shared by people, dot, and other AI assistants. Retrieve source-backed context and change history from...” to “gram_* tools as purpose-based memory shared by people and AI across ChatGPT, Claude, Grok and coding agents. Retrieve...

View comparison →
Capabilities & instructions

Logo url dark changed from “https://files.openai.com/content?id=file_0000000057dc81f5ac4c606308a60416” to “https://files.openai.com/content?id=file_00000000813c82098ef315c86a701ba7”. Skill “thegram-cloud” description changed from “cloud gram_* MCP tools as purpose-based memory shared by people, dot, and other AI...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Keywords

Files & skills

File archives

Plugin package11 files · 32.9 KBBrowse files →
Skill instructions
thegram-cloud6.25 KB

View saved version →

---
name: thegram-cloud
description: Load first whenever the person says record, save, note, remember, 기록, 저장 or 남겨, or names a Thegram vault or folder (the vaults listed in the Thegram server instructions, e.g. "Thegram-dev docs"); those go to Thegram, never to local files. Also for any question about the person's notes, projects, decisions or tasks, any question about shared reference data in GramHub, and before any Thegram tool call (vault_ask, vault_read, vault_add, vault_change, vault_exact).
---

# Thegram: how to read and record

For the five-tool surface only: `vault_ask` (read; `op` `ask` default, `hubs`, `browse`, `changes`, `comments`, `guide`), `vault_read`, `vault_add` (`op` `create`, `comment`, `restore`, `feedback`), `vault_change` (`op` `edit`, `move`, `delete`), `vault_exact`. If the tools listed to you have other names, this skill does not apply: follow the server's instructions.

The rules below keep reads honest and records clean; when one cannot be met, do the rest and say exactly what is missing.

## Step 1. Decide the target, every time, before any call

- **Own vaults**: the person's and their organizations' notes, projects, decisions, tasks, meetings → `vault_ask {question}` with NO `scope`.
- **Hubs** (`@mounts/hub-team-*`, read-only): public or reference datasets; there can be any number of them → `vault_ask {op:"hubs", question}` returns the closest hubs. Pick the one whose `label` and `folders` fit and ask with its ref as `scope`. None fits → say Thegram holds no such dataset.
- Unsure → ask without scope first: the answer lists `scope.hub_candidates`; use one if the question is about reference data.
- NEVER search a hub without its ref in `scope`. NEVER mix own vaults and hubs. NEVER use a ref no tool returned. Hits of the wrong kind (personal notes for a reference question, or the reverse) mean the wrong target: go back to Step 1.

## Step 2. Read

1. `question` = the person's words with every exact name, number and code. For a find, add `terms` (1–4 nouns every hit must hold). `terms` and `options` work ONLY with a find: NEVER send them with `plan.operation` `count`, `list` or `changes` (`E_ARGUMENT`).
2. Filters (type, status, date, tag) go ONLY in `plan.conditions`, each with `quote` = the question's words it came from. NEVER invent a value. On `interpretation.unresolved`, use a value from `allowed` or ask the person.
3. Hubs differ from vaults: document names are opaque ids, records carry `tags` as `key:value`, and a hub folder may hold `guide.gram` (field and date meanings) and `coverage.gram` (period covered). NEVER walk a hub's folders. Narrow by copying a tag exactly from a hit into `record.tag`. Read `guide.gram` / `coverage.gram` before stating what a hub field or date means or how current it is; if they do not exist, say the meaning or freshness is unconfirmed.
4. A hit counts only if it matches EVERY entity the question names: same name, number, article or code. Another entity with the same number is not an answer.
5. Use `records` and `hits` first; `vault_read` only what they lack.
6. When an answer has `next`, call `next.tool` with `next.args` as given, even if that tool is not listed. NEVER build a cursor. If that call comes back `unresolved` or fails, apply Step 3 rule 8 before giving up.

## Step 3. Answer

7. Every claim cites `path#id`. No ref, no claim.
8. Counts, totals, averages, maxima, top N: ONLY `vault_exact {query, folder}`. Its planner understands short phrases in the source's alias words, not long questions: if a call is `unresolved`, call `vault_exact {query, folder, exact:{catalog:true}}`, rewrite the query as `<condition words> <type alias> 개수` (e.g. `미해결 할 일 레코드 개수`, `할 일 개수`) using only listed aliases, and retry once. Accept ONLY `execution.status:"complete"`; `running` → call `next` until it ends. Still not complete → say there is no exact result and why. NEVER count hits.
9. A complete exact result is exact only within its scope: if `coverage` or the source say

Preview of the first 4,000 characters. Read full instructions →

Release notes

4.7.2: The portable package no longer contains hooks, which the plugin portal refuses; Claude Code installs from the source repository keep their citation reminder. The bundled thegram-cloud skill, plugin identity, MCP configuration and skill namespace are unchanged from 4.7.1.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
Apache-2.0
Package author
Roy Kim
Keywords
See keywords
Listing translations
ko-KR
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Search and cite linked goals, decisions, requirements and sources
  • Exact counts and rankings across a vault
  • Typed records with every change kept as history
  • GramHub data next to your own knowledge

Some manifest fields differ or could not be read. The structured report retains the source references.

Package observed Nov 6, 2026.

Technical details
First seen
Oct 24, 2026 · 12:40 UTC
Last seen
Nov 7, 2026 · 06:00 UTC
Latest observed change
Nov 5, 2026 · 06:08 UTC
Collection status
Collected

plugin_asdk_app_6acc810ccabc8191acd3f457dc498d43

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.