When your organisation runs the Context Platform in its Govern deployment, chat and agent sessions in the Editor can use organisation knowledge (indexed code, uploaded documents, issues) that you are allowed to read. Govern decides what you may read, applies data loss prevention by classification and a token budget, and records which passages each answer used. The Editor adds the passages to your prompt as data, shows the sources as citations, and never adds local files in their place. The Context section describes the platform itself.
To learn the features step by step, run Learn: Context Platform. If a feature is missing, Why Is This Context Feature Not Available? explains it, and Ask Keystone Again Which Context Features Are On checks again.
How context reaches a prompt
For each chat request (Editor chat and the Agents app; inline edits do not retrieve):
- The Editor resolves the space: your selection, then the default space setting, then the project the open repository belongs to (see Workspaces, trust and project binding), then your organisation's start space.
- It asks Govern to retrieve passages for your message, within the token budget.
- It adds only the returned passages, in rank order, inside markers with a random boundary, after a preamble that says the material is untrusted data, not instructions, and asks for citations by number.
- The block is sent with that request only. It is not shown as an attachment, not stored on the request, and not kept in chat history.
- The answer shows the sources as numbered citations with the space and lens, or why there was no context.
When the request goes to Organization models (Keystone), the call carries the retrieval's id so Govern can join the two in its evidence.
See what an answer used
Choose Context details and attribution under an answer, or run Show Context of an Answer. It shows the sources, and Govern's attribution record once it is written (the client name and version recorded, and the evidence chain position). Citations in chat history keep names, paths and line ranges, never content.
When context is not used
| You see | Meaning | What happens |
|---|---|---|
| Context withheld | Your organisation's policy (a deny rule, classification, permission) | The prompt goes without context |
| Context unavailable | Govern cannot serve it, or its address could not be verified | The prompt goes without context; the Editor tries again with backoff (5 seconds, doubling to 5 minutes) |
| Sign in to use organisation context | Signed out | The prompt goes without context |
In every failure the prompt is sent without organisation context. The Editor reads no local file in its place; the only local file it reads for context is .git/config, to find the repository address.
The status bar item shows the same state: on (space and lens), off, withheld by policy, unavailable (with the reason and when it tries again), or signed out. Click it, or run Context Status and Choices.
Choose a space, lens or snapshot
- Open Spaces (also in the Manage menu) opens the Spaces page: the state of context, how the open folder maps to a space, your spaces with search, use for the next session and make default, each space's sources with indexing status, re-index, pair sessions, and your settings (locked ones show a lock).
- Choose Context Space..., Choose Context Lens... and Use a Context Snapshot... set the selection for the session.
- Clear Context Choices clears it.
A loaded snapshot replaces retrieval: every prompt reads the snapshot again, filtered to what you may see, and nothing is retrieved. Selections are kept for the window only and not restored after a restart.
Share context
Govern decides every share; the Editor offers only what your organisation's collaboration policy allows.
- Share a Context Lens...: share a lens you own with people, groups or teams. The flow offers the allowed levels (view, use, edit) and expiries, asks for a reason when the share is above the approval line, and shows a confirmation. A share waiting for approval is shown as "waiting for approval, NOT shared".
- Manage Who a Context Lens Is Shared With..., Show Context Lenses Shared With Me..., Show Context Shares Waiting for Approval... (withdraw a pending share there).
- What Can I Share Here? shows the effective policy for the current space.
Hand off context on a pull request
- Hand Off Context for a Pull Request... turns the passages your session retrieved into a snapshot and a handoff on the pull request, after you confirm and optionally add a note. You can name up to 50 recipients, or choose everyone who may read the files.
- Load the Author's Context for a Pull Request... loads the context the author handed off, filtered to what you may read, and says how many passages were withheld.
- Show Handoffs for Me... lists your inbox.
The setting neuralInverse.context.autoHandoffOnPullRequest (ask or never) decides whether the Editor offers a handoff when a session opens a pull request, and offers to load one when you work on someone else's.
Pair sessions
Start a Context Pair Session..., Join a Context Pair Session..., Invite to the Context Pair Session..., Show Pair Session Invitations... and End the Context Pair Session. Retrieval in a pair session uses the session's space and lens. A session can be invite-only; a join link's token is shown once, and when you join you type it masked. Who is present is shown only when Govern's live feed is available.
Team memory
Open Team Memory opens a space's shared decisions, conventions, notes and glossary entries, edited together. The text of an entry reaches the AI only after a person reviews and accepts it: the page shows the document hash you review, and accepting sends exactly that hash back. Later edits stay pending until accepted again. Text your organisation's data protection withheld cannot be reviewed.
Agent instruction files
Open Agent Instructions shows the instruction files of coding agents (CLAUDE.md, AGENTS.md and the like) as your organisation layers them: organisation, department, team, project and personal layers, with the repository layer read from the indexed repository.
- At the first request of an agent session, the effective set for the bound project is placed in the session as data, read again when Govern reports a change, and at most every five minutes otherwise.
- When the set has no repository layer, or there is no set (offline, signed out, not offered), your repository's own
AGENTS.mdis added as "repository (local, not yet indexed)", up to 64 KiB. A mandatory organisation section wins over it. - The Editor never overwrites a tracked file. Where a tool needs a file, it writes only the tool's local override (
CLAUDE.local.mdfor Claude,AGENTS.override.mdfor Codex), lists it in.git/info/excludefirst, and marks it as generated. - Archiving a version, placing or clearing a legal hold, and rolling back are on a file's versions panel. Each asks for a reason and an explicit confirmation; Govern decides who may.
Settings
All are application settings (a repository cannot set them), and each can be locked by managed policy.
| Setting | Policy | Default |
|---|---|---|
neuralInverse.context.enabled | NeuralInverseContextEnabled | true |
neuralInverse.context.defaultSpaceId | NeuralInverseContextDefaultSpace | empty (the project's space) |
neuralInverse.context.tokenBudget | NeuralInverseContextTokenBudget | 4096, from 256 to 32000 |
neuralInverse.context.sourceKinds | NeuralInverseContextSourceKinds | empty (every kind). Kinds: codebase, docs, conversations, issues, workspace_live, regulatory, custom |
neuralInverse.context.autoHandoffOnPullRequest | NeuralInverseContextAutoHandoff | ask |
What is kept on the device
Passage text lives only in the request sent to the model. Ids and names of what a session retrieved, and the space and lens lists, are kept in the window's memory (lists for one minute, dropped on sign-out). Nothing is written to storage.
Maturity
The client follows Govern's published Context API. Presence and live updates need the streaming connection and Govern's live feed; without them the pages say why and show none.