Temet CLI 0.2.0
Temet CLI 0.2.0 made install and connection real
Temet CLI 0.2.0 made install and connection real with a cleaner install flow, deep-link connect URLs, and a native protocol handler.
What 0.2.0 changed
Temet CLI 0.2.0 was the point where the CLI became a believable onboarding surface instead of a rough internal utility. The release introduced a clearer install flow, deep-link connect URLs, a native protocol handler, and the first coherent BYOA entrypoint around the CLI.
Why install and connection came before audits
Before Temet could audit work or track changes over time, it needed a real first-run path. Version 0.2.0 focused on that base layer: get the CLI onto a machine, connect it cleanly, and reduce the friction between the website, the assistant, and the local environment.
The native protocol layer mattered more than it looked
Deep-link connect URLs and the native protocol handler were not just nice extras. They were the bridge between a web entrypoint and a local CLI product. Without that bridge, Temet would still feel like a disconnected tool rather than part of a usable workflow.
BYOA became easier to explain
This release also made the bring-your-own-assistant story more legible. The CLI started to feel like a real entrypoint for people who wanted to keep their existing assistant, connect it to Temet, and move into a stronger workflow without switching tools.
How 0.2.0 fits between 0.1 and 0.3
0.1 made local install possible. 0.2.0 made onboarding and connection credible. 0.3.0 then turned the CLI into a much more useful audit and tracking workflow. That makes 0.2.0 the bridge between installability and actual day-to-day product usage.
Thanks for reading. Arnaud
Run it
Audits local sessions and surfaces repeated skills.
FAQ
Was 0.2.0 already the audit-focused CLI?
No. The main focus of 0.2.0 was install, connection, deep-linking, and making the CLI a believable entrypoint. Audit and tracking became much stronger in 0.3.0.
Why keep a separate article for 0.2.0?
Because it explains an important product transition: Temet moved from installable local tooling toward a coherent onboarding and connection flow before it became an audit and tracking product.
Should I read 0.2.0 if I am installing the latest CLI?
Yes if you want the chronology. But for practical usage today, the newer install and 0.3.0 articles are more directly useful.
Next step
Read the install-first story, then see how Temet moved from local setup into connection, deep links, and a more believable CLI entrypoint.
See the next stepPublished March 4, 2026