Graphtia documentation · concept
Agent integrations
Connect Graphtia Explorer to supported coding agents through managed native adapters or the universal MCP path.
Client connections
Choose your client
Explorer provides native adapters for these external coding clients. Version ranges describe adapter configuration, not testing of every client version. For other clients that support a local stdio MCP server, follow the Universal MCP guide and verify the connection in your client.
One evidence layer, several agent surfaces
Graphtia exposes the same read-only structural analysis through each supported connection. Explorer keeps the registered workspace, approval state and current project index visible while the coding agent asks focused questions.
Native integrations
Explorer provides dedicated integration adapters for Codex, Claude Code, OpenCode, Antigravity, Visual Studio Code/Copilot, Devin Desktop and MiniMax Code. These connect external clients to Graphtia; they are not AI agents bundled with Explorer. Use the client detection, configuration scope and verification result shown in your installed app.
Universal MCP
Other clients can connect to the packaged Graphtia MCP server through local stdio when they support a standard MCP server command. The generic route requires you to supply a stable client identity and the Explorer project library path.
Permission model
Agent identity identifies the requesting client; it does not authorize a workspace.
Workspace access is read-only and must be approved in Explorer.
The adapter owns only Graphtia entries and leaves other agent configuration intact.
Graphtia has no authority to mutate code, approve changes or declare work complete.
Questions beyond symbols
APIs: locate declared or implemented endpoints, distinguish a caller from a handler, and inspect source evidence.
Database schemas: inspect supported SQL declarations, columns, keys and indexes in the indexed workspace.
Database uses: ask which supported code reads, writes or declares a table, preserving uncertain matches.
Documents: find the project’s indexed explanations before treating them as executable evidence.
Ask the agent to keep the workspace and revision fixed, follow paginated results and cite the source behind each conclusion. A query result is structural evidence, not a successful database call or live endpoint test.
Follow recorded agent activity
Open supported recorded queries from Agent activity or Agents and sessions. Select the session and event, then open its target. When compatible context is available, Recalculated identifies a graph built from the recorded target, scope and limits; it is not a replay of the agent’s original answer. If context is unavailable, Explorer can open the known target without inventing a matching query. Observed reads and local file changes do not establish that the agent edited those files. Queried tests are not executed tests. Keep the project and revision in view.
Guidance and connection are separate
A managed connection can include Graphtia guidance or a client skill where supported. These help the agent use the tools; they do not grant workspace permission, override your instructions or authorize edits. Availability depends on the installed client and version.
Workspace access is a separate choice
You can approve a client for one hour or until you revoke access. The choice is tied to the client, registered workspace and root context. A persistent approval survives normal reconnects and installation updates; it does not grant another client or a different folder access. Registration, initial indexing and agent access have separate approvals.
Read the workspace access and recovery guide
Operations, compact tools and optional local memory
Explorer exposes 26 canonical structural operations. Compatible clients can present the same operations in six groups. The number of visible tool names does not change the capabilities or permissions.
Code and index queries are observational. An explicitly enabled experimental local recovery cache can also retain client-supplied notes and continuation state. That cache is unencrypted and can be cleared; it is separate from your source, workspace permissions and validated evidence. Do not store secrets in it.
Read the MCP operations reference
Multiple coding clients can use Graphtia with separate session context and project access checks. Choose JSON for structured evidence, DIGEST for a concise text view, or bounded RECORDS/JSONL exports for reconstruction. These are representations of the requested evidence, not broader permissions.
Output modes and examples · Multiple clients and activity scope