Engineering Context Graph
Wikis for each repository, and one picture of the workspace
Engineering Context Graph
Engineering Context Graph is experimental. It indexes the GitHub repositories already connected for readiness, writes a wiki for each one, and shows how those repositories fit together.
A workspace admin can turn the area off. When it is on, the sidebar labels it Engineering Context Graph and shows a flask icon. Hover the icon for Experimental.
How to open it
In the app sidebar, open Engineering Context Graph, or go to /code-chat.
| Area | Path | What it does |
|---|---|---|
| Home | /code-chat |
The workspace picture, and a place to ask a question |
| Workspace | /code-chat/knowledge |
Roles, connections, and written pages for the whole workspace |
| Usage | /code-chat/usage |
Opens, downloads, and questions that cited a repository |
| Wiki | /code-chat/wiki |
Written pages for one repository |
| Conversations | /code-chat/conversations |
Questions grounded in the indexed repositories |
| Context graph | /code-chat/visualize |
A map of one repository, or of the connections between repositories |
Each wiki keeps its own repository in the address. Starting an index or a page write affects that repository only.
What you need first
- GitHub connected, with repositories available from Agentic Foundation.
- Engineering Context Graph left on by a workspace admin.
- A workspace execution key if you want the pages written in prose. The same key the workspace already uses for agent work is enough. Graph structure can still be built when a write is not running.
Repositories that already have a readiness score can be indexed unless they hit a size or scan limit. A language-coverage warning does not block the index.
Home
Home shows how the ready repositories relate. Solid lines are confirmed connections. Dashed lines are likely. A line is drawn only when there is a reason, such as a shared package both wikis name. An unnamed generated id, or the same filename in two repositories, is listed as something to check. It is not drawn as a product dependency.
Conversations
Ask from Home or open Conversations. Answers cite the wiki and the indexed code. A question about one repository stays on that repository. A workspace question can use the workspace pages.
Context graph
Open the map from a wiki or from the workspace picture. A single-repository map shows structure inside that repository. A workspace map lists every ready repository and the connections between them.
If a reading has no edges, the map says so instead of inventing a dependency. Blast radius follows the connections that are actually recorded.
Usage
Usage lists opens, exports, and questions that cited a repository. Dollar figures, when the product shows them, are estimates. For billed spend, use AI Usage & Spend.
Settings
Workspace admins manage the area from workspace settings (Engineering Context):
- Turn Engineering Context Graph on or off for the workspace (Availability).
- Code map: choose whether eligible GitHub repositories are scanned, and how often to rescan — Daily, Weekly, or Manual only (no automatic rescans until an admin uses Scan now). Scanning builds the structural map Conversations and the workspace agent file use; it does not write wiki pages.
- Pick supported Cursor and Claude models from the curated lists (including Cursor Auto with an Optimize for preference when Auto is selected).
- See each connected source, whether it can be read, and when it was last scanned. Sources that are not readable yet stay listed as not ready.
Notion and a remote tool connection are not available yet.
Next
- Wiki: write and read one repository
- Workspace: roles, shared contracts, and downloads
- Agentic Foundation: the readiness repositories that feed the index