See what your agents did

Claude Code and Codex have built-in OpenTelemetry exporters. Pointed at Sazabi, every session becomes searchable: prompts, tool calls and results, model requests with token counts and cost. Then "what did the agents run last night" and "which sessions cost the most" are questions for sazabi/logs.ask.

0. How the tools work

The Sazabi MCP server lists only two tools, search and execute. Browse Sazabi's operations with search and namespace: "sazabi" (an empty query without a namespace lists connected connectors, not Sazabi operations). Before calling one, repeat search with namespace: "sazabi", the hit's full name as the query, and includeInputSchema: true to load its arguments. Then run it with execute as { name, arguments }, the name copied from the hit (for example sazabi/logs.ask).

1. Decide what may leave the machine

Ask before exporting prompt text. Prompts and tool inputs can contain code, customer data and credentials. Codex always exports tool-call arguments and truncated results, whatever the prompt setting, so say that plainly when the user picks Codex. Default to prompts off unless the user opts in.

2. Get an intake URL per agent

Run sazabi/logSources.list. If there is no source for this agent yet, create one with sazabi/logSources.create in manual mode (one source per agent: Claude Code, Codex) and use the intake endpoint it returns. Keep the URL out of any committed file.

3. Configure the agent

Claude Code reads the env block of ~/.claude/settings.json (or a project's .claude/settings.local.json, which must stay untracked):

{
  "env": {
    "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
    "OTEL_LOGS_EXPORTER": "otlp",
    "OTEL_EXPORTER_OTLP_PROTOCOL": "http/protobuf",
    "OTEL_EXPORTER_OTLP_ENDPOINT": "<intake URL>",
    "OTEL_LOG_USER_PROMPTS": "0",
    "OTEL_LOG_ASSISTANT_RESPONSES": "0"
  }
}