---
title: Thegram across your AI tools
description: Shared project decisions, sources and change history across Cloud clients, coding agents and the iPhone/iPad app.
url: https://docs.thegram.one/ko/platform/platform-overview/
lang: en
requested_lang: ko
fallback_from: https://docs.thegram.one/platform/platform-overview/
tier: current
status:
  component: Thegram product overview
  deployment: Cloud clients and iOS/iPadOS; see the selected client guide
  applies_to_version: Latest
  status: GA
  last_verified: "2026-10-25"
  owner: thegram-one/thegram-blog
  public_evidence:
    - https://thegram.one/llms.txt
    - https://thegram.one/gram-file/
    - https://thegram.one/install/agents.md
  rationale: Current public product and installation sources describe Cloud agent connections and retained .gram history. Public sources establish described availability, not feature parity or a live runtime guarantee.
historical_source: https://docs.thegram.one/sources/platform-overview.gram
editorial_sources:
  - https://thegram.one/install/agents.md
  - https://github.com/thegram-one/thegram-plugin
  - https://apps.apple.com/us/app/thegram-docs-that-remember/id6821552969
---

# Thegram across your AI tools

<div class="gram-doc-anchor" id="e0-blog-platform-overview"></div>

## Keep decisions and their context together {#h0-1}

Thegram keeps document content with records such as decisions, tasks, risks, evidence and sources, plus retained change history. The useful outcome is carrying an existing project’s context into a later session or supported client, rather than treating a previous chat answer as the source of truth.

## Choose the surface for your task {#h0-4}

| Surface | Current public connection path | Start here |
| --- | --- | --- |
| ChatGPT | Published plugin and OAuth | [ChatGPT setup](/guides/cloud-setup/#h0-6) |
| Claude | Custom OAuth connector; packaged workflow documented separately | [Claude setup](/guides/cloud-setup/#h0-8) |
| Claude Code, Codex, OpenCode, OMP | Shared coding plugin with a scoped API key to Cloud MCP | [Coding setup](/guides/local-setup/) |
| Browser | Account-backed Vault at vault.thegram.one | [Open Thegram](https://vault.thegram.one/) |
| iPhone and iPad | Current App Store app with Vault editing, dashboard, history, graph and search | [iOS guide](/guides/ios-guide/) |

Current agent onboarding does not require a running Mac application, local socket or DMG. The former public viewer and desktop download paths are not current connection instructions; their captured sources and revisions remain historical evidence.

## Understand the boundaries {#h0-8}

`.gram` document meaning and history are distinct from an application’s views, search index and graph layout. A search result is not a fact or an explicit stored relationship. A revision view is not a rollback action. Cloud authorization comes from the connection, membership and policy, not a label in a document.

## Try an existing decision first {#h0-10}

Follow [Connect your AI](/guides/quickstart/), read an existing authorized project, and ask what was decided and which source supports it. Use a separate session or client to check whether that context can be retrieved again. Do not create test records in a person’s live memory to make setup look successful.

## Save deliberately {#h0-12}

A read-only task stays read-only. A save needs the person’s approved content and exact destination as well as technical write permission. Read the persisted document back and check search separately. See [permissions](/guides/permissions/) and [decision workflows](/guides/workflows/).

## Current sources {#h0-14}

The client guides cite the published installation guide, plugin repository and App Store. They do not prove a particular account is connected, a provider directory approved an entry, or every client has identical capabilities.

## Historical source records {#h0-15}

The old `.gram` publication contains source records for earlier desktop, viewer, local-agent and read-only iOS designs. Those pinned records are preserved in the historical download, not asserted here as current behavior.

<span id="e0-format-source"></span><span id="e0-desktop-source"></span><span id="e0-appstore-source"></span><span id="e0-ios-source"></span><span id="e0-web-source"></span><span id="e0-render-source"></span><span id="e0-brand-source"></span><span id="e0-vault-source"></span><span id="e0-plugin-source"></span><span id="e0-memory-source"></span><span id="e0-product-thesis"></span><span id="e0-file-as-canonical"></span><span id="e0-parity-risk"></span>
