Set up Thegram Desktop and connect a storage source · r12
Archived revision r12, recorded 2026-10-12T13:08:42.173Z. Current page: Set up Thegram Desktop and connect a storage source.
Start with a file you control
Section titled “Start with a file you control”The Mac app is the direct route when you want to inspect and edit .gram documents in a native workspace. Begin by following the install instructions linked from the product site and opening a document from a location you chose. The desktop README describes a local mode that works without server requests; signing in is a separate choice. This distinction is useful: a local document workflow should not be described as requiring a Vault account, and signing in should not be treated as automatically granting access to a separate storage provider.
Before connecting anything, decide which copy is canonical. A local folder, personal Drive folder, or mounted Vault may have different ownership and synchronization behavior. Do not move a source file into a cloud account merely to make the UI appear populated. The app’s format boundary says .gram and its history are canonical; derived search, graph, and vector data can be rebuilt.
Open and read
Section titled “Open and read”Use the native file-open flow to choose a .gram file or folder. The desktop design uses a document list, central content, an inspector, and graph/history navigation. A selected historical revision is a read-only view; it is not a direct rollback. To make an intentional change based on old text, return to the current state and edit or copy the desired material into a new change. If Core reports a stale write or invalid history, preserve the original file and resolve that condition rather than replacing it with a hand-edited reconstruction.
A useful first check is whether the title, typed records, relationships and rich body appear as expected. A graph edge expresses a stored relation; visual proximity or a search result can be a derived candidate, not a fact written into the file. Likewise a status label or scope field describes data but does not change its permission model.
Connect a Thegram account or Drive
Section titled “Connect a Thegram account or Drive”Desktop documentation separates account authentication from storage mounting. Account sign-in uses the configured identity flow. Google Drive connection is separately consented to, and personal Drive and company Shared Drive flows are distinct. A logged-in user may see a company Vault mounted according to their role; a Drive connection is not simply the account login screen under a different name. Read the prompts carefully and confirm which account and folder are being connected.
After authorizing a source, inspect the displayed path and document identity before editing. Remote storage synchronization can introduce stale states or conflicts; the desktop README says agent imports should preserve stale conflict rather than silently overwrite. If two copies disagree, retain both until the application’s conflict workflow identifies the intended current file. A self-hosted connection may expose an optional advanced mTLS route, but that is not a prerequisite for ordinary local use.
Example workflow
Section titled “Example workflow”Suppose you have a local launch-review.gram and want to read team evidence. First open the local file and identify its current revision and any link to evidence. If shared material lives in a team Vault, sign in only if needed, then verify that the expected Vault appears under the correct identity and role. If a personal Drive is the actual source, use its separate consent flow and inspect that folder instead. Read the decision and its evidence together. For a new decision, create a separate decision record and link the supporting evidence; do not overwrite an old accepted fact to make a conclusion look historically true.
Tradeoffs and limits
Section titled “Tradeoffs and limits”Local work needs no account or network, but does not share files across devices. Remote storage adds identity, consent, organization roles, sync, and conflict handling. The separate sandboxed Mac App Store edition is in preparation, with App Store entitlements, a privacy manifest, and installer-signing work, but no release is evidenced. Its inherited README and acceptance retain the Source-r2 TEST/UNRESOLVED-license boundary. Use the generated platform release reference for the current release details. Core license status remains UNRESOLVED; notarization is not license review.
For exact current host steps, use Local setup and the official install instructions. Read Storage permissions before selecting a local, Vault, or Drive destination. This guide explains the decision boundary; it does not grant an account role or provider access.
Install and enable agent access
Section titled “Install and enable agent access”Start with the shared Quickstart and Local setup for current host requirements and installation steps. Use the official install page for the current release; this guide does not maintain a second copy of setup commands. Account sign-in is optional; the install guide says local files can be used without an account. For a coding agent, follow Local setup and the official agent install instructions. Choose Read or Read and Write according to the intended scope, and keep the app running; the linked instructions own current host commands and requirements. Codex asks once whether to trust plugin hooks. Grant write access only to an agent and project you intend to authorize.
Sources
Section titled “Sources”Instructions are based on Desktop README and design/architecture docs, installation materials, Vault contract, and the App Store edition’s preparation status and inherited README/acceptance boundary.
Source
Section titled “Source”Source: Desktop application README
Internal source reviewed at revision b6c769a0365166ba943d8501abb639bd09c00c6e (main: README.md; docs/ui-design.md; docs/architecture.md); not publicly available.
Source: Desktop UI design
Internal source reviewed at revision b6c769a0365166ba943d8501abb639bd09c00c6e (main: docs/ui-design.md); not publicly available.
Source: Desktop architecture
Internal source reviewed at revision b6c769a0365166ba943d8501abb639bd09c00c6e (main: docs/architecture.md); not publicly available.
Source: Sandboxed App Store edition README; not release evidence
Internal source reviewed at revision b3389ce165fa80d46873df3f4fb6951d98fbeb60 (main: README.md; inherited from the desktop line); not publicly available.
Source: App Store acceptance text; not release evidence
Internal source reviewed at revision b3389ce165fa80d46873df3f4fb6951d98fbeb60 (main: docs/acceptance.md; inherited from the desktop line); not publicly available.
Source: Vault service contract
Internal source reviewed at revision a193a190141054e07b268f0a38489467db82a335 on branch master (README.md; docs/SPEC.md); not publicly available.
Source: Product installation instructions
Reference: https://thegram.one/install/
Knowledge
Section titled “Knowledge”Knowledge: Local file workflow is independent of account login
Desktop documents local mode without server requests; authentication and storage mounting are separate choices.
Reference: → Supports: Choose identity and storage separately
Knowledge: Choose identity and storage separately
Account sign-in, Google Drive consent, company Vault role and local files represent distinct access paths.
Knowledge: The in-preparation sandboxed edition has no evidenced App Store release
The sandboxed edition is in preparation; inherited README/acceptance text from the desktop line retains Source-r2 TEST/UNRESOLVED-license status, not an App Store release report.
Source and renderer evidence
- Canonical source SHA-256
42e7762197f86ddcd8d72728149a17217efe516bbb752e7d89572d21f59338a7- Selected revision
r12 · sha256:a7e5f1275da68abae0354acab3ac159e4d606abe7497b0d2ddcb3070ff3ab1f8- 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: 12.gram