Temet CLI 0.3.0
Temet CLI 0.3.0 turns audits into a real workflow
Temet CLI 0.3.0 adds a real audit command, cleaner skill output, local tracking, post-session hooks, and local notifications.
What changed in this release
Temet CLI 0.3.0 turns the project from a collection of internal scripts into a product-facing audit tool. You can now run a real local audit, track meaningful changes over time, and hook that loop into Claude Code sessions without introducing a permanent daemon.
A real audit command instead of internal scripts
The release makes temet audit the visible entry point. That matters because the product no longer depends on a developer knowing which script to run or where Claude Code stores session files. The CLI now gives Temet a real surface a user can remember and reuse.
Cleaner output, fewer fake skills
Earlier audit output could inflate the result with workflow n-grams treated as competencies. This release separates workflows from skills, cleans the naming, and makes the result much closer to something a real person could review, keep private, or eventually publish.
Tracked changes instead of one static snapshot
Temet CLI 0.3.0 adds local snapshots, meaningful diffs, and no-op guards. The point is not to save every run. The point is to tell you when a real shift happened: a stronger skill, a new stable pattern, or a change in how you repeatedly work.
From manual pull to post-session loop
This release also adds path autodetection, quiet runs, hook installation, and local notifications. That means Temet can now run after a Claude Code session, compare the result with the previous state, and stay silent unless something meaningful changed.
Why this release matters for the product
The important shift is not only technical. Temet is moving from a one-shot extraction tool toward a product that can observe work over time, surface what is getting stronger, and eventually turn repeated patterns into something more reusable than a flattering summary.
Thanks for reading. Arnaud
Run it
Audits local sessions and surfaces repeated skills.
FAQ
Is Temet CLI 0.3.0 only about nicer terminal output?
No. The terminal polish helps, but the real release adds local audits, tracking, background hooks, and notification logic that change how the product is used.
Do I need to publish anything to benefit from this release?
No. The release is valuable even if you stay completely local. The intended path is private audit first, optional publishing later.
Does this mean Temet now runs as a daemon?
No. The background loop is hook-based. Temet can run after a Claude Code session ends without requiring a permanent background process.
Next step
Start with npx @temet/cli audit, then add tracking and background hooks only after the base result already feels useful.
Install 0.3.0Published March 6, 2026