Session summaries
A background worker distills each closed session — SSH terminal and database — into a one-paragraph summary of what the operator did, flagging notable or destructive actions. It's automatic; just use sessions normally.
- Open a session recording (a server session's playback, or a database query recording) — the AI summary card sits above the player.
- Session lists show a small marker on rows that have a summary.
- Summaries appear within ~20 seconds of a session closing.
Restarted nginx, edited 3 config files under /etc, and ran a migration that updated 1,240 rows. No destructive operations.
Subnomic AI assistant
Ask Subnomic AI plain-English questions from the dedicated Subnomic AI page, or from the Ask the audit log box on the Activity page. It searches your tenant's activity log, then replies in a sentence or two and lists the specific events it cited — it answers only from real rows, never invented ones.
- "who touched prod last week?" — matches activity against a server named
prod. - "what did alice do today?" — matches a person by name or email.
- "any deletes this week?" — filters by action and date.
When agent access is configured, Subnomic AI can also run governed, read-only queries against connected databases and inventory through the same MCP tooling — always showing exactly what it ran. See Agent access (MCP).
Permissions
Summaries surface wherever a recording does (session.read); the Subnomic AI page and the Ask
box on the Activity page need activity.read. Summary generation itself is a background job and
needs no user permission.