{
  "messages": [
    {
      "role": "system",
      "content": "You are a helpful AI assistant with access to tools. Use tools when they help answer the user's question. Be concise and accurate."
    },
    {
      "role": "user",
      "content": "How does the code/docs index work?"
    },
    {
      "role": "assistant",
      "content": "<think>\nIndex tools — semantic search across indexed code and documentation. Separate from EEMS memory.\n</think>\n\nThe index system provides semantic search across code and documentation files. It chunks files, embeds them, and enables similarity search. Five tools:\n\n- **index_code** — index code files from a given path. Chunks source files and generates embeddings for semantic search. Optional project name for organizing multiple codebases.\n- **index_docs** — index documentation files (markdown, text) from a given path. Same chunking and embedding approach.\n- **index_search** — semantic search across all indexed code and documentation. Returns relevant chunks ranked by similarity.\n- **index_status** — show current index statistics: how many chunks are indexed, which projects, storage size.\n- **index_clear** — wipe all indexed content.\n\nThis is separate from EEMS memory. EEMS stores discrete knowledge records (facts, decisions, procedures). The index stores chunked source code and documentation for retrieval-augmented search.\n\nTypical use: index a project's codebase and docs once, then use `index_search` to find relevant code patterns, API usage, or documentation sections without having to grep through files manually. The current index holds 17k+ code chunks and 44k+ doc chunks across all repos."
    }
  ]
}