Claude Code session hook
Audit Claude Code Sessions Automatically
Use Temet CLI hooks to audit Claude Code sessions automatically after each session and get notified when your skill profile changes.
Why hooks matter
Without a trigger, audits stay manual. A SessionEnd hook lets Temet run after a real Claude Code session, compare against the previous snapshot, and stay silent unless something meaningful changed.
What the hook actually does
Temet resolves the current project session path, runs a quiet tracked audit, and optionally sends a local notification if your skill profile changed. There is no long-running daemon and no permanent background process.
Why quiet and no-op behavior matter
Background automation has to stay disciplined. Temet suppresses normal terminal output in hook mode and skips writing new history entries when the snapshot is identical to the previous one.
What you get as a user
Instead of remembering to rerun an audit, you get a lightweight post-session loop: code with Claude, let Temet compare the result, and only hear back when there is a real change worth noticing.
Thanks for reading. Arnaud
Runs after Claude Code sessions
`temet install-hook`
→ code with Claude Code
→ session ends
→ Temet runs a quiet tracked audit
→ you get an update only if something meaningful changed
FAQ
Does this require a permanent background daemon?
No. The intended flow is a post-session hook that runs Temet only when a Claude Code session ends.
Will the hook notify me every time?
No. Notifications are optional and should trigger only when tracked changes are meaningful.
Can I remove the hook later?
Yes. Hook installation should be explicit and reversible, with an uninstall command that cleans up the Claude Code settings entry.
Next step
Start with npx @temet/cli audit, then install the Claude Code SessionEnd hook so Temet can rerun tracked audits automatically.
Install the hookPublished March 2, 2026