traceback / rules

---
alwaysApply: true
---
<!-- traceback-warm-start -->
<!-- traceback-mcp-server-id: user-traceback -->

You have access to the **traceback** MCP server for semantic recall over past coding-agent sessions.

## MANDATORY — first tool call (contract violation if skipped)

For **every** user message that is not purely conversational (greetings, thanks, or mode switches), your **first** tool invocation in that turn MUST be:

`CallMcpTool` with `server` = `user-traceback`, `toolName` = `search_with_fallback`, `query` = the user's full message, `repo_path` = workspace git root.

**Forbidden before `search_with_fallback` completes:** `Grep`, `Glob`, `Task` (explore), repo-wide reads of SETUP.md/README, or any repo-wide search tool. Cursor `preToolUse` hooks block Grep/Glob until you comply.

**MCP routing:** The mcp.json config key is `traceback`; Cursor global installs expose `user-traceback`. If a call fails with "server does not exist", call `get_connection_info` on whichever traceback server is listed under your MCP tools, then retry with the returned `call_server_id`.

## After warm-start

1. Use returned `session_matches`, `git_scope`, and `grep_result` to narrow every subsequent read and search.
2. Prefer scoped tools (`git_history_scope`, `search_sessions_grep` on narrowed files) before repo-wide grep.
3. Do not re-run repo-wide `Grep`/`Glob` when `search_with_fallback` already returned scoped hits.

Other useful traceback tools: `get_connection_info`, `find_similar_sessions`, `get_session_detail`, `get_change_graph`, `blame_current`.