Thegram Cloud Connection Release: Coding Plugin 3.0.0 · r11
Archived revision r11, recorded 2026-10-16T01:26:30.103Z by portal-product-quickstarts. Current page: Thegram Cloud Connection Release: Latest Coding Plugin.
Current Thegram connection release
Section titled “Current Thegram connection release”Coding plugin 3.0.0 requires Node.js 22+ and connects directly to Thegram Cloud with a scoped API key.
| Client | Authentication | Setup |
|---|---|---|
| ChatGPT chats and dots | OAuth | Install the published Thegram plugin and complete the provider account flow. |
| Claude | OAuth custom connector | Add the Cloud MCP URL in Claude Settings → Connectors. This is not an official directory listing. |
| Claude Code, Codex, OpenCode, OMP | Scoped API key | Install the shared coding plugin, issue a key in Thegram Settings, then connect privately. |
Desktop distribution is retired
Section titled “Desktop distribution is retired”The current onboarding does not use a DMG, running Mac app, Agent Access switch or local MCP socket. Older revisions of these documents preserve the previous architecture as history; they are not current installation instructions.
Use https://thegram.one/install/ for current setup. The former Mac and DMG download routes return 410.
Key authority and updates
Section titled “Key authority and updates”API-key issuance, verification and revocation use an independent authority with separate sealed records, KEK, persistent storage and backup lifecycle. Vault stores no key records or hashes. Raw keys are returned once at issuance; the CLI keeps the user-entered credential privately. Replacing or restarting the Vault image does not recreate or erase API keys. The external MCP endpoint remains on Vault, so requests may fail briefly while Vault restarts. This is credential persistence and lifecycle isolation, not zero-downtime document service. API-key backups currently use a dedicated PVC; this does not establish an off-site disaster-recovery copy.
Permissions
Section titled “Permissions”All current agent connections use Thegram Cloud. Local-only files are not uploaded or exposed automatically. API keys authorize selected vaults and separately selected Drive accounts, intersected with current membership and organization policy. A vault grant is not a document-only sandbox.
API keys authenticate MCP only; they cannot manage keys, sign in to the web UI or use general REST administration. Expiry and revocation apply to subsequent requests, including an existing MCP session.
Sources and limits
Section titled “Sources and limits”Coding package: https://github.com/clab-one/thegram-mcp. Canonical setup: https://thegram.one/install/agents.md. ChatGPT retains the published OAuth plugin. Claude has custom-connector instructions, not an official directory listing. Provider account installation was not repeated for this release. Thegram, including Core and the .gram format, is proprietary. License: Thegram Proprietary License (All rights reserved). Third-party components retain their own licenses.
Source and renderer evidence
- Canonical source SHA-256
3d3a9964968315c0107a9a3f29f0104aa336190d24f6a35b7c98776dd7bc0dcf- Selected revision
r11 · sha256:db4c0eec61faf79a0bd794d934ce26390d184525dcb6deafd273c243cbf89881- 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
Canonical source: 11.gram