AI Tools
Session recording for one AI tool at a time, on by default.
console.superalign.ai/hub → AI Tools
Each card under AI Tools turns on session recording for one AI tool on every endpoint. Every AI tool in the console is on when your organization is created, so you turn off the ones you do not want rather than turning on the ones you do. Turn one off and every scanner in your organization drops it within 15 minutes.
This is the opposite of Data Sources and Cloud Agents, which run in SuperAlign’s backend and stay off until someone configures them. AI Tools decide what is collected in the first place; Data Sources decide where session data is kept.
| AI tool | Records | Needs anything else? |
|---|---|---|
| Claude Code | Claude Code sessions | No |
| Codex | OpenAI Codex sessions | No |
| Chrome browser | ChatGPT, Claude, Gemini, Perplexity, and Microsoft Copilot used in Chrome | The Surface browser extension on endpoints |
| Other coding agents | Antigravity, Microsoft Copilot, Cursor, Devin, Factory Droid, Gemini, Goose, Grok, Hermes, iFlow, Kiro, OpenCode, Pi, and Qwen sessions | No |
| Other browsers | AI websites in Brave, Chromium, Microsoft Edge, Firefox, Floorp, LibreWolf, Opera, Vivaldi, Waterfox, and Zen Browser | The Surface browser extension in that browser |
Each tool is its own card under AI Tools in Hub, with its own switch. More are added over time.
Browsers are the exception to “on by default”: their switches are on, but a browser records nothing until the browser extension is pushed to it. The Browser extension deployment guide covers Chrome today.
Before you begin
- You have the Admin role. Other roles see the switches but cannot flip them. Every change is written to the Audit Log.
How to turn one off
Open Hub
Click Hub at the bottom of the left menu. Each AI tool is a card under AI Tools.
Flip the switch
Click the tool’s card. In the panel on the right, turn Enabled off. You see a message such as “Claude Code disabled”.
Wait one scan
Every endpoint picks up the change within 15 minutes and stops recording that tool.
Sessions already recorded stay until they expire. Turn Enabled back on to record that tool once more; new sessions appear on the Sessions page.
What session recording does on the endpoint
It hooks into the tool’s own session files or events, reads each new turn of the conversation, and hands it to the scanner. The scanner adds the person and endpoint and sends it to the console. Nothing is sent to anyone else.