|
| 1 | +# Conversation Logging |
| 2 | + |
| 3 | +Altimate Code automatically logs each conversation turn to the Altimate backend. This powers validation, audit, and quality analysis features. Logging is **enabled by default** — no configuration is required to activate it. |
| 4 | + |
| 5 | +## What Is Logged |
| 6 | + |
| 7 | +Each turn (one user prompt + all assistant responses) sends the following to the Altimate backend: |
| 8 | + |
| 9 | +| Field | Description | |
| 10 | +|-------|-------------| |
| 11 | +| `session_id` | The current session identifier | |
| 12 | +| `conversation_id` | The assistant message ID for this turn | |
| 13 | +| `user_id` | Your email or username (from your Altimate account) | |
| 14 | +| `user_prompt` | The text of your message | |
| 15 | +| `parts` | All reasoning, text, and tool call/response parts from the assistant | |
| 16 | +| `final_response` | The last text response from the assistant | |
| 17 | +| `metadata` | Model ID, token counts, and cost for the turn | |
| 18 | + |
| 19 | +Logging fires after the session becomes idle (i.e., after the assistant finishes responding). Up to 500 messages are captured per turn to ensure complete coverage of multi-step agentic sessions. |
| 20 | + |
| 21 | +## Why We Log |
| 22 | + |
| 23 | +Conversation logs are used to: |
| 24 | + |
| 25 | +- **Validate AI responses** — power the `/validate` skill that audits factual claims against source data |
| 26 | +- **Quality analysis** — identify recurring failure patterns across sessions |
| 27 | +- **Audit trails** — provide a record of what the assistant did and why |
| 28 | + |
| 29 | +## Disabling Logging |
| 30 | + |
| 31 | +Logging is on by default. To disable it, set the following environment variable before starting Altimate Code: |
| 32 | + |
| 33 | +```bash |
| 34 | +export ALTIMATE_LOGGER_DISABLED=true |
| 35 | +``` |
| 36 | + |
| 37 | +To make this permanent, add it to your shell profile (`~/.zshrc`, `~/.bashrc`, etc.): |
| 38 | + |
| 39 | +```bash |
| 40 | +echo 'export ALTIMATE_LOGGER_DISABLED=true' >> ~/.zshrc |
| 41 | +source ~/.zshrc |
| 42 | +``` |
| 43 | + |
| 44 | +To re-enable logging, unset the variable: |
| 45 | + |
| 46 | +```bash |
| 47 | +unset ALTIMATE_LOGGER_DISABLED |
| 48 | +``` |
| 49 | + |
| 50 | +Setting `ALTIMATE_LOGGER_DISABLED=false` is equivalent to not setting it — logging will be active. |
| 51 | + |
| 52 | +## Network |
| 53 | + |
| 54 | +Conversation logs are sent to: |
| 55 | + |
| 56 | +| Endpoint | Purpose | |
| 57 | +|----------|---------| |
| 58 | +| `apimi.tryaltimate.com` | Conversation log ingestion | |
| 59 | + |
| 60 | +Requests are fire-and-forget — a failed log request does not affect your session in any way. |
0 commit comments