--- title: Set Up Thegram Memory for Local Coding Agents description: Install the local MCP integration and understand its app-level Agent Access boundary before a coding agent reads or writes project memory. url: https://docs.thegram.one/ko/guides/local-agent-guide/ lang: en requested_lang: ko fallback_from: https://docs.thegram.one/guides/local-agent-guide/ tier: legacy status: component: App-mediated local MCP (Thegram for Mac Agent Access) deployment: Former local MCP socket through a running Thegram Mac app applies_to_version: Not applicable (retired) status: Retired last_verified: "2026-10-25" owner: thegram-one/thegram-mcp public_evidence: - https://thegram.one/install/agents.md - https://thegram.one/download/mac rationale: The official setup connects thegram-memory directly to Thegram Cloud and states that no Mac app, desktop socket or running desktop process is required; the Mac download route returns 410. source: https://docs.thegram.one/sources/local-agent-guide.gram date_published: "2026-10-12T13:06:16.145Z" date_modified: "2026-10-12T13:06:16.146Z" evidence: Canonical source SHA-256: 269059cef6a6a20a1072fd576b6d7de2967e07963c861e3d8c90571db62d7761 Selected revision: r1 · sha256:81be736c4487d0dce2bcce91cf018dcc7beb4196687ff7a539b2c2099dbc0afc Local renderer: configured local Thegram renderer · API thegram-web-render/1 Core source: git+https://github.com/clab-one/thegram-format.git?rev=b16489e1d0d77d38f82d2f61776524737aa31557#b16489e1d0d77d38f82d2f61776524737aa31557 --- # Set Up Thegram Memory for Local Coding Agents > Legacy archive. The official setup connects thegram-memory directly to Thegram Cloud and states that no Mac app, desktop socket or running desktop process is required; the Mac download route returns 410. Current setup: [Quickstart](/guides/quickstart/).
The local thegram-memory integration connects coding agents to project memory maintained by Thegram for Mac. It can brief an agent at session start, expose shared project files through gram\_\* tools and remind the agent to record durable outcomes. Unlike the cloud integration, it depends on a running Mac app and a person-approved local connection. Installing a plugin is not the same as granting it access to the app or authorizing any particular write. ### Requirements and explicit app permission {#h0-3} Use an Apple silicon Mac running macOS 26 or later, Node.js 22 or later on PATH, and a running Thegram app. In the app, open Thegram → Settings… → Agent Connections. The Agent Access control offers Off, Read, and Read and Write. Off disables the integration; Read permits inspection without writes; Read and Write is required for changes. The person at the computer—not the coding agent—must select the intended level, and Connection should report Running. Keep the app open while using local tools because the integration talks to the app’s local MCP connection. This is an explicit app-level boundary, not a blanket grant to read arbitrary folders, connect Google Drive or copy private material into project memory. A permission switch controls the app-mediated integration; it does not establish that a particular record is accurate or appropriate to save. Make each connector and persistence choice deliberately. The install guide tells the person to set access in the app; an agent should explain the step and wait rather than changing it silently. ### Install for your coding host {#h0-6} Start with [Quickstart](/guides/quickstart/) and [Local setup](/guides/local-setup/), then follow the official [agent installation instructions](https://thegram.one/install/agents.md) for the selected host. Host-specific commands and authorization prompts change; this guide explains the app permission and project-memory boundary rather than duplicating mutable install syntax. Before a new session, remove any manually configured MCP server named thegram to avoid duplicate registrations. From the project directory, run `node "/dist/thegram-memory.mjs" doctor`, replacing the plugin-folder placeholder with the actual installation path, or pass the project directory as the doctor argument. The doctor output should show app connection, vault and the intended project folder. If the app is unreachable, access is Off, or another app connection conflicts, resolve that before trusting a project brief. An installation log alone is not proof that the app is available. ### Repository mapping and memory behavior {#h0-9} By default, a Git repository maps to a vault folder with the same name, and worktrees share it. A local projects.json mapping can override a directory prefix; the longest matching prefix wins. For example, a monorepo subtree can map to an existing product memory instead of creating another project folder. Check the doctor output before assuming where the agent will read or write. Google Drive is separate: after the person connects Drive in Thegram, its mount can appear in gram_projects. A local folder is not visible to a cloud agent merely because a local plugin can access it. At session start, the plugin can provide a project brief; later prompts may include changes made by other writers. A reminder may ask for a durable memory update when work ends with file edits or commits but no record. It is a reminder, not a demand to write on every turn. Useful memory includes verified decisions, shipped changes, incidents, measured results, active tasks and risks. Avoid chatter, guesses, raw logs, credentials and secrets. When a write succeeds, read back the specific record and its placement; do not infer that the visible document changed simply because a record exists. ### Example: finish a small migration {#h0-12} Imagine a fictional team chooses to keep a backward-compatible import flag for one release. The agent verifies a compatibility test, updates code and finds a second provider remains unsupported. It can record the accepted decision with its test evidence, add a log event tied to the actual commit, and retain an open task or risk only if the unsupported provider is genuinely unresolved. Place these records in Decisions, Log and Plan and link them to the project. Do not claim completion because code changed; read back the decision, event and remaining work before reporting. If a checkout maps incorrectly or a writer gets a stale revision, stop before saving. Inspect the mapping and current brief, preserve another writer’s changes, and ask the user when the destination is unclear. Do not create a duplicate file to bypass a mistaken path. ### Boundaries and next steps {#h0-15} The local integration is a Node package with hooks, adapters, project mapping and a local MCP proxy; it is not the cloud package. App availability and Agent Access are necessary for local use. Check the current official install guide, package README and policy before applying version-specific advice; tools, mounts and behavior can change. The integration does not turn a local folder into remote storage, nor does a write permission prove the content is safe or true.
**Source:** thegram-memory README Public package source for local setup, doctor, repository mapping and session behavior, inspected at revision 3a1411a. Reference: [https://github.com/clab-one/thegram-mcp/blob/3a1411a/README.md](https://github.com/clab-one/thegram-mcp/blob/3a1411a/README.md)
**Source:** Local project memory policy Public guidance on durable records, safe data and read/write practices, inspected at revision 3a1411a. Reference: [https://github.com/clab-one/thegram-mcp/blob/3a1411a/policy.md](https://github.com/clab-one/thegram-mcp/blob/3a1411a/policy.md)
**Source:** Local memory skill reference Public tool usage and structured document guidance, inspected at revision 3a1411a. Reference: [https://github.com/clab-one/thegram-mcp/blob/3a1411a/skills/thegram-memory/SKILL.md](https://github.com/clab-one/thegram-mcp/blob/3a1411a/skills/thegram-memory/SKILL.md)
**Source:** Official coding-agent installation page Current public setup instructions and app-level permission steps. Reference: [https://thegram.one/install/agents.md](https://thegram.one/install/agents.md)
**Source:** Local app-mediated MCP proxy Public local app-mediated proxy source at revision 3a1411a. Reference: [https://github.com/clab-one/thegram-mcp/blob/3a1411a/src/mcp-proxy.ts](https://github.com/clab-one/thegram-mcp/blob/3a1411a/src/mcp-proxy.ts)
**Knowledge:** Keep Agent Access intentional The person configures Off, Read, or Read and Write in Thegram; installation does not silently grant permission.
**Knowledge:** The local app is a runtime dependency Local plugin tools require the running Mac app and a connection reporting Running.
**Knowledge:** Separate folder access from app permission App Agent Access does not itself approve arbitrary folder reads, Drive connections or persistence of a particular fact.