The first of five guides to the tool categories that get called 'AI monitoring'. This one answers whether confidential data left the company through an AI tool — and stops measuring the moment the prompt is sent.
View AI Data Loss Prevention: A Buyer's Guide to What It CoversThe second of five guides to the categories called 'AI monitoring'. This one answers which AI tools people are using without approval — an inventory question, and the one most likely to be answered wrongly with confidence.
View Shadow AI Discovery: A Buyer's Guide to Finding What Is Already in UseThe third of five guides to the categories called 'AI monitoring'. This one protects the AI systems you deploy — models, applications and agents — and has nothing to do with the AI your developers use to write code.
View AI Application Security: A Buyer's Guide for the AI You ShipThe fourth of five guides to the categories called 'AI monitoring'. This one tells you whether your own AI feature is working and what it costs — and sees exactly nothing your developers' coding tools do.
View LLM Observability: A Buyer's Guide to Watching the AI You BuiltThe last of five guides to the categories called 'AI monitoring'. This one asks what AI actually built and whether you can reconstruct why — and it is the one we sell, so read it with that in mind.
View AI Code Provenance: A Buyer's Guide to the Category We Are InEvery vendor in this space says visibility, prompts, and audit - but they solve five different problems. Here is an honest map of the categories, which tools belong to each, and how to tell which one you actually need.
View How to Monitor Employee AI Usage: A Map of the Tool CategoriesThe retention default is 30 days and the setting that controls it is absent from a normal install. Here is how to check your own machine, how to stop the deletion, and why stopping it is not the same as solving it for a team.
View Claude Code Deletes Your History After 30 DaysWhat you are actually asked to prove about AI-generated code in 2026 — which is less than the EU AI Act headlines suggest and more than most change-management narratives currently cover.
View SOC 2, Security Questionnaires and AI-Written CodeOpenCode keeps every session in one SQLite database under ~/.local/share/opencode. Here is the schema, the queries that let you read your own history, and what to do about the fact that it is one file.
View Where OpenCode Stores Your Session HistoryGemini CLI keeps sessions per project under ~/.gemini/tmp, and deletes anything older than 30 days by default. Here is the layout, the setting that controls the deletion, and how to turn it off.
View Where Gemini CLI Stores Your Chat History — and When It Deletes ItWindsurf keeps Cascade conversations in ~/.codeium as binary protobuf files — one per conversation, unreadable in a text editor, with no export. Here is the layout and what you can actually do about it.
View Where Windsurf Stores Your Cascade Chat HistoryCodex writes every session to a JSONL rollout file under ~/.codex/sessions, and recent versions index them in a SQLite database alongside. Here is the layout, what each file holds, and how to keep it.
View Where Codex CLI Stores Your Session History