Skip to main content
Almost every “it’s broken” moment in LivingContext is really a “one thing isn’t wired up yet” moment — and the app usually says so quietly. This page maps the situations you might hit to their causes and fixes.

Docs and editing

Not an error — no page is selected and there’s no remembered last doc for this space + repo. Pick a page in the sidebar, or press K and jump straight to one.
The classic cause: your active space doesn’t include the repo you expect. Surfaces show the intersection of your configured docs repos and the active space’s repos, so a repo in no space shows nothing. Open the space switcher (top of the left rail) and check which space you’re in, then Settings → Spaces — make sure the repo is ticked in the space you use. Also confirm the repo is still listed under Settings → Docs repositories.
Editing needs the Editor role or above; Readers, Commenters, and Reviewers get the read-only view by design. An Administrator can change your role under Settings → Members. See Roles and permissions.
Conflict: the branch changed under you and the changes overlap — the banner offers Keep my version or Take the branch version; both are safe, and both stay in History. Protected branch: your repo’s branch protection blocks direct commits — work through a change request and ship it as a pull request instead.
Editors can create and submit change requests but not merge them — you’ll only see Request a review, which opens a pull request. Merging in-app needs Reviewer, Creator, or Administrator. That’s the intended review path, not a bug.
Open K and run Reindex docs for search (needs edit rights) — the full-text index is built per repo and can lag a fresh import. Note the sidebar box only filters page names; full-text search lives in K.

Connections and setup

Authorizing GitHub only proves your identity — repos come from installing the GitHub App. On Connections, use Install / manage on GitHub for the account or organization that owns the repos, grant it access to them, come back, and hit refresh.
Salesforce needs your own Connected App on file first. Add its consumer key and secret on the Connections page — then Connect Sandbox / Connect Production appear.
The stored token was revoked or expired — the toast says which (for example, “Salesforce refresh token was rejected”). The fix is almost always re-connect the integration from the same card. Disconnecting first is safe: “You can connect again anytime from this page.”
Starter workspaces cap at about 100 MB. Connect your own GitHub and use Move your workspace to your own GitHub on Connections — the cap lifts and your docs move with you.

Agents, Inbox, and coverage

The Inbox fills from two sources, and both need switching on once: tracked commits (pick repo + branch pairs under Settings → Commit tracking) and doc suggestions (enable the schedule — or click Run now — under Settings → Doc suggestions). Newly tracked branches deliberately start from their current tip, so proposals begin with the next commit.
Exactly what it says: pick at least one repository + branch pair under Settings → Commit tracking. Repos must be selected under Docs repositories first.
Coverage counts synced Salesforce metadata. If nothing is ingested yet, run Fetch latest metadata on the connection’s card (Connections), give the sync a minute, then Refresh on Coverage.
Specs generate automatically after each Salesforce metadata sync, about 25 per pass — a freshly connected org fills in over a few syncs. To move faster, open Settings → API references and generate on demand. If references you had have vanished, the repo holding their specs was removed from Docs repositories — add it back and they reappear.
Charts need an analytics source — the database mirroring your Salesforce records — connected once by an admin in the Analytics section of Connections. Until then the workspace agent answers without charts.
Check three things in Agents → Channels: the workspace shows Connected, your Slack app’s Event Subscriptions and slash command point at /api/slack/events, and the bot is actually in the channel you’re mentioning it from. Failed runs show up in the Runs tab with a transcript.

Capture extension

Your key was revoked — which also happens automatically when you leave an organization. Click Reconnect in the extension (or Connect to LivingContext again). Nothing already published is affected.
The extension only records a browser tab, never your whole screen — picking the screen or a window shows “Share a browser tab” and asks again. Pick the tab you’re documenting, or choose Record without video (screenshots only).
Publishing targets your configured docs repos. In the web app, add one under Settings → Docs repositories (GitHub must be connected), then publish again.
The page changed since the guide was recorded. Guide Me shows the original screenshot so you can do the step by hand, then click “I’ve done this → Next”. If a guide falls back often, re-record it — the workflow has drifted.

Signing in and membership

It was cancelled, already used, or expired — invitations last 48 hours. Ask the Administrator to send a fresh one.
The organization’s only owner can’t leave — promote another Administrator first, then leave from your own row on Settings → Members.
By design: each account can create one organization. Join others by invitation — and switch between them from the user menu’s Workspaces list.

Still stuck?