Git is the source of truth
Your documentation lives as Markdown/MDX files in your own GitHub or GitLab repository. LivingContext reads from and writes to that repo — it never holds your docs hostage in a proprietary store. Every change is a commit, so you keep full history, ownership, and portability.Organizations
An organization is your team’s tenant. Each organization lives on its own subdomain, likeacme.livingcontext.ai, with its data isolated from every other organization. Members, roles, and invitations are managed on the Organization page.
Finding your way around
The left rail is the workspace’s spine, top to bottom:
API reference and Changelog sit just below, and ⌘ K opens search from anywhere. The space switcher at the very top of the rail picks your scope.
Spaces and the active repo
A space is a named scope that groups documentation repositories and Salesforce connections. Workspace-wide surfaces — Home, Inbox, and Coverage — operate on the active space. The active repo is the repository you’ve selected in the space switcher. Repo-bound surfaces — Docs, Changelog, Change requests, Commits, and API Reference — show content from that repo. See Spaces and repos.Docs
A doc is a Markdown page in your documentation repository, rendered in the Docs surface. Docs can be written by hand, generated by agents, or produced from browser captures. Docs can carry tags that link them to specific Salesforce metadata, which powers coverage and drift detection.Captures and guides
A capture is a recording made with the LivingContext browser extension: you click through a workflow, and the extension records the steps, screenshots, and context. Captures become step-by-step guides that you publish as change requests. Sensitive data is redacted at capture time, and passwords are always masked. See Capture.Change requests
A change request (CR) is a reviewable draft of documentation changes — the LivingContext equivalent of a pull request, with a rich editor and a full diff. Whether a change comes from a teammate, a capture, or an agent, it moves through a CR (or a PR in your git provider) before it’s merged into your repo.Grounded or it doesn’t ship. Agents must back their proposals with evidence from your systems, and a human always approves before anything is committed. There is no silent auto-publishing.
The Inbox
The Inbox is your review queue. Agent-proposed updates, new-doc suggestions, and generation events land here for triage: read the proposed change, see why the agent proposed it, then approve or dismiss. See Inbox.Agents
Agents are the AI workers that generate and maintain your docs. They watch your tracked repositories and Salesforce metadata, draft updates when things change, suggest missing docs (the Coverage Auditor), and assist you in the editor. Agents follow your organization’s style guide and templates, and their write actions always pass through human review. See Agents.Coverage
Coverage measures how much of your Salesforce metadata is documented. You control what counts through eligibility settings — for example, excluding managed packages or specific namespaces — so the score reflects the metadata your team actually owns. See the settings reference.Credits
Credits are the usage currency for agent work. Every plan includes a monthly credit grant, and 1 credit equals $0.01. See Billing.How it fits together
1
Connect
Link your git provider and Salesforce so agents have real systems to ground against.
2
Generate
Agents draft new docs and updates from commits, metadata changes, and your captures.
3
Review
Proposals arrive in the Inbox and as change requests. You edit, approve, or dismiss.
4
Merge
Approved changes are committed to your repository — your docs stay fresh, and git stays the source of truth.