Capture
The Recorder
Do the work once in Chrome — it becomes a step-by-step guide.
Your Salesforce changed today. Did the wiki?
Nobody updatesthe docs. Now nobody has to.
LivingContext records your Salesforce workflows in Chrome, publishes them as a living docs site, and a crew of agents rewrites them when your org drifts — every change reviewed by you, every word stored in git.
No managed packageYour repo is canonCapture-time redaction
Reads from · writes to · renders
SalesforceGitHubGitLabConfluenceChromeClaudeCursorMCPMarkdownOpenAPIMermaidD2draw.ioExcalidrawSalesforceGitHubGitLabConfluenceChromeClaudeCursorMCPMarkdownOpenAPIMermaidD2draw.ioExcalidraw
The problem
Every doc starts dying the day it's written.
Your org changes every week — flows, fields, approval steps, permission sets. The wiki doesn't notice. So it keeps serving yesterday's truth with a straight face:
- New admins follow steps that no longer exist
- Senior people answer the same Slack question, again
- Your AI tools confidently quote the stale page
The crew
Six agents. One job:
docs that are never stale.
Each one proposes; you approve. Nothing ships to your docs without a human looking at the diff first.
Guide Me
The Guide
Walks users through Salesforce live, spotlight on the exact button.
Drift detection
The Watcher
When the org changes, the broken docs get a fix-up CR.
Coverage
The Auditor
Finds what's undocumented and files ready-to-ship drafts.
Doc copilot
The Editor
Inline suggestions in the editor — accept or reject hunk by hunk.
Changelog
The Historian
Keeps the changelog current, grouped by what actually changed.
How it works
From a screen recording to a docs site that maintains itself.
01
Record it once
Walk through the process in Chrome. The Recorder turns it into a guide with annotated screenshots and clips — you reorder, crop, redact, then publish straight to your docs repo.
02
Review the diff
Everything agents write arrives as a change request: a real diff against your docs, edit by edit. Approve, tweak or reject from the inbox — then it merges to main.
03
It stays true
The Watcher ties every doc to the metadata it describes. When the org changes, the affected docs are flagged and rewritten — so the site never quietly rots.
0
specialist agents on your docs, around the clock
0%
of agent edits reviewed by a human before merge
0 min
from screen recording to published guide
47
stale pages left for your AI tools to quote
The docs platform
A docs site your team will actually open.
Not a wiki where pages go to die. Everything the agents write lands in a fast, searchable site — and because the source of truth is a git repo you own, it's portable even if you leave.
- A real docs site — tabs, sections, and a changelog page
- Full-text search across everything (⌘K)
- API reference rendered from OpenAPI specs
- Diagrams as first-class blocks: Mermaid, D2, draw.io, Excalidraw
- Templates so every runbook starts with the same bones
- Org subdomains with role-based permissions
- Git-backed: history, blame and rollback for every word
For your AI tools
Your AI assistants stop guessing.
Point Claude, Cursor or any MCP client at the LivingContext server and they answer from docs known to be in sync with your org — stale pages are filtered out before the model ever sees them. The same grounded answers power “Ask the docs” inside the Chrome extension.
MCP serverRead + write toolsAsk-docs in Chrome
> how do opps over $250k get approved?
● livingcontext-mcp · 1 verified doc · 2 stale hidden
→ opp-approval.md — in sync with org metadata
Routes to Regional-VP, two-of-three quorum,
requires ContractTerm__c since v3.1.
Before / after
The docs you have vs. the docs you'll have.
Documentation today
- Screenshots from 2023, still in the onboarding doc
- The runbook says Sales-Director; the org says Regional-VP
- Every new admin asks the same questions in Slack
- Your AI assistant confidently quotes the stale wiki
- Nobody knows which pages are still true
With LivingContext
- Guides recorded in one take, screenshots always current
- Drift caught the moment metadata changes — CR opened
- New admins follow a spotlight inside Salesforce
- Assistants answer only from verified, in-sync docs
- Coverage and freshness, visible on one dashboard
Do I need to install anything in Salesforce?
No managed package. Capture and Guide Me run from a Chrome extension, and metadata sync uses Salesforce's standard APIs with credentials you control.
Where do my docs actually live?
In a git repository you own, on GitHub or GitLab. The docs site renders straight from it, so every page has history, diff, blame and rollback — and it's all portable if you ever leave.
What does the AI get to change on its own?
Nothing. Agents propose; humans approve. Every suggested rewrite, new doc or changelog entry arrives as a change request you can approve, edit or reject — per edit, not per document.
What about sensitive data in recordings?
Redaction happens at capture time, in the browser, before anything is stored — typed values and sensitive fields are masked by default and you can review every screenshot before publishing.
Can my AI tools read the docs?
Yes. The MCP server exposes your docs to Claude, Cursor and any MCP-compatible client, filtered to pages verified in-sync with your org — and the extension answers questions grounded in the same docs.
Closed beta · Q3 2026 · limited seats
Stop documenting.
Start approving.
Your org will change again tomorrow morning. Retire the wiki, keep the knowledge — and let six agents keep it true while you review the diffs.