pnpm temet cli
Temet CLI 0.1 started with install and local setup
Temet CLI 0.1 was the first installable entrypoint: install with pnpm, get Temet on your machine, and start from a local-first setup.
What 0.1 represented
Temet CLI 0.1 was the first local foothold for the product. The point was not yet a mature audit workflow. The point was to make Temet installable, runnable from pnpm, and present as a real local tool instead of an internal script or ad hoc setup step.
Why install came first
Before deeper features like audits, tracking, or hooks could matter, Temet needed a credible first-run path. Version 0.1 focused on getting the CLI onto a machine and framing Temet as a local-first tool someone could actually invoke and build on.
What 0.1 did not try to solve yet
This stage was not yet about tracked audits, background hooks, or meaningful changes over time. It was a simpler step: install the CLI, make the local entrypoint believable, and create the base layer the later releases would build on.
How it connects to 0.2 and 0.3
0.1 made local install real. 0.2 made onboarding and connection more coherent with deep links and a publishable BYOA entrypoint. 0.3 then turned the CLI into something much more useful day to day with audits, tracking, hooks, and notifications.
Audits local sessions and surfaces repeated skills.
FAQ
Was 0.1 already the full Temet audit experience?
No. It was the first installable local entrypoint. The richer audit and tracking workflow came later.
Why keep a separate article for 0.1?
Because it explains the product sequence clearly: first make install and local usage real, then improve connection, then add audits and tracking.
Should I still read this if I install the latest CLI?
Yes, if you want to understand the product evolution. But for actual usage today, the newer CLI articles are more relevant.
Next step
Use the one-command entrypoint first, then install Temet globally only if you want a permanent local binary.
Open on npmPublished January 2, 2026