/**
 * Server-level instructions emitted in the MCP `initialize` response.
 *
 * MCP clients (Claude Code, Cursor, opencode, LangChain, OpenAI Agent
 * SDK, …) surface this text in the agent's system prompt automatically,
 * giving the agent a high-level playbook for the codegraph toolset
 * before it sees individual tool descriptions.
 *
 * Goals when editing this:
 *   - Tool selection by intent (which tool for which question)
 *   - Common chains (refactor planning = X then Y)
 *   - Anti-patterns (don't grep when codegraph_search is faster)
 *
 * Keep it tight. The agent reads this every session — long instructions
 * burn tokens. Reference only tools that exist on `main`; gate any
 * conditional tools behind feature checks if/when they ship.
 */
export declare const SERVER_INSTRUCTIONS = "# Codegraph \u2014 code intelligence over an indexed knowledge graph\n\nCodegraph is a SQLite knowledge graph of every symbol, edge, and file in\nthe workspace \u2014 pre-computed structure you would otherwise re-derive by\nreading files. Reads are sub-millisecond; the index lags writes by ~1s\nthrough the file watcher.\n\n## Tool selection by intent\n\n- Lower-noise first hop for an implementation task \u2192 `codegraph_context` with `mode: \"task\"`\n- Broader task-level picture \u2192 `codegraph_context`\n- Flow from X to Y \u2192 `codegraph_trace`\n- Read one surfaced symbol or one surfaced file \u2192 `codegraph_node`\n- Broad subsystem survey / unfamiliar area only after lightweight narrowing fails \u2192 `codegraph_explore`\n- Symbol location only \u2192 `codegraph_search`\n- What calls this \u2192 `codegraph_callers`\n- What this calls \u2192 `codegraph_callees`\n- What breaks if this changes \u2192 `codegraph_impact`\n\n## Retrieval protocol\n\n- Start structural, not textual: use codegraph to narrow `target`, `owner`, `chain`, or `boundary` first.\n- Treat `context(mode=\"task\")` as a locate step, not a full repo dump.\n- Use one main structural hop per unresolved question.\n- If the next unresolved question is path/relationship, switch to `trace`.\n- If the next unresolved question is \"read the surfaced thing\", switch to `node`.\n- If the next unresolved question is dependent seam / blast radius, switch to `callers`, `callees`, or `impact`.\n- After structure is narrowed, use built-in grep/read only for exact literal facts such as strings, route keys, resource IDs, or config values.\n- If one hop did not reduce the unresolved structural question, change tool or hypothesis; do not loop the same broad query.\n- Stop once the next direct code read is clear.\n\n## Common chains\n\n- Implementation first hop: `codegraph_context(mode=\"task\")` \u2192 `codegraph_trace` or `codegraph_node`\n- Refactor planning: `codegraph_callers` \u2192 `codegraph_impact` \u2192 `codegraph_node`\n- Debugging path questions: `codegraph_context(mode=\"task\")` \u2192 `codegraph_trace`\n\n## Anti-patterns\n\n- Don't grep first for structural questions.\n- Don't start with `codegraph_explore` for routine implementation tasks.\n- Don't chain many `codegraph_node` calls when one `codegraph_explore` is enough.\n- Don't use `codegraph_files` or `codegraph_status` as discovery tools in a normal coding loop.\n- Don't use grep to reopen structural exploration after codegraph has already narrowed the candidate set.\n- Trust codegraph results unless you need exact literal text.\n\n## Limitations\n\n- If a project isn't indexed, stop using codegraph for that project this session and use built-in tools instead.\n- Index lags file writes by ~1 second.\n- Cross-file resolution is best-effort name matching; ambiguous calls may return multiple candidates.\n- No live correctness validation \u2014 that's still the compiler / test suite / linter's job.\n";
/**
 * Instructions variant sent when the workspace has NO codegraph index.
 *
 * Sending the full playbook ("lean on codegraph for everything") into a
 * session where every call would fail wastes the agent's calls and — worse —
 * the failures teach it codegraph is broken. The unindexed variant is a
 * short, unambiguous "inactive this session" note; `tools/list` is gated to
 * empty in the same state, so the agent has nothing to mis-call. Indexing is
 * deliberately left to the user: the agent is told NOT to run init itself.
 */
export declare const SERVER_INSTRUCTIONS_UNINDEXED = "# Codegraph \u2014 inactive (workspace not indexed)\n\nThis workspace has no codegraph index (no `.codegraph/` directory), so no\ncodegraph tools are available this session. Work with your built-in tools as\nusual.\n\nIndexing is the user's decision \u2014 do not run it yourself. If the user asks\nabout codegraph, they can enable it by running `codegraph init` in the\nproject root and starting a new session.\n";
//# sourceMappingURL=server-instructions.d.ts.map