Skip to content
TokenShift

Core commands

Most TokenShift activity happens transparently — the agent’s tool calls flow through the hook, and there’s nothing to type. These are the commands a developer or admin might run by hand.

tokenshift doctor

Section titled “tokenshift doctor”

The single command you run to answer “is it set up correctly?”

Terminal window
tokenshift doctor             # status check, no network
tokenshift doctor --verify    # also ships one synthetic record to confirm the wire is live end-to-end

Reports, in one block: which agent hooks are wired, whether an enrollment manifest is present (and which one — per-user shadows system), what tier and config are active, and the result of the binary’s internal self-check.

Run this after tokenshift install, after pushing a new manifest via MDM, and any time something feels off. tokenshift doctor --verify is the canonical “did MDM rollout actually work?” check.

tokenshift dashboard

Section titled “tokenshift dashboard”

Interactive terminal UI that shows compression savings over time — tokens saved, cost saved, per-rule rollups, per-project / per-model / per-activity slices. Reads from local stats only; no network calls.

Terminal window
tokenshift dashboard

Useful as a quick gut-check on whether TokenShift is actually saving tokens on a developer’s machine, and which rules are pulling the most weight.

tokenshift enroll

Section titled “tokenshift enroll”

Installs a tenant-bound enrollment manifest from the PointFive customer portal. The full enrollment model — what’s in the manifest, where it lives on disk, per-user vs. system delivery — is in Enrollment.

Terminal window
tokenshift enroll ~/Downloads/enrollment.json   # the common case
tokenshift enroll -                              # read from stdin
tokenshift enroll --dry-run <path>               # validate without writing

Validates the JSON before writing. Writes with 0600 to a 0700-mode parent. Never overwrites silently — use --force for deliberate replacement.

tokenshift recover <hash>

Section titled “tokenshift recover <hash>”

Pulls back the full uncompressed output of a tool call that TokenShift previously compressed. The agent uses this automatically (the compressed response ends with tokenshift recover <hash> and the model learns to ask for it when it needs more detail), but a developer can run it too.

Terminal window
tokenshift recover a1b2c3d4

Reads from the local recovery cache only. The cache is local-only with a 1-hour TTL — past that, the original is no longer available.

tokenshift config telemetry

Section titled “tokenshift config telemetry”

Toggle or inspect what leaves the laptop. Subject to the install-time cap set by the customer admin’s manifest.

Terminal window
tokenshift config telemetry enable        # opt in (within the admin-permitted tier)
tokenshift config telemetry disable       # opt out — local stats only
tokenshift config telemetry mode <name>   # set the tier (hashes-only, hashes-plus-shapes, …)

See Tiers in the data contract for what each mode includes.

tokenshift version

Section titled “tokenshift version”
Terminal window
tokenshift version

Prints the running binary version, build date, and whether the binary is pinned (carries a compiled-in ingest URL and public key) or unpinned (built from source without ldflags — telemetry will not ship).

tokenshift uninstall

Section titled “tokenshift uninstall”

Removes the hooks from the agent’s settings. Does not by default touch the local cache or the enrollment manifest.

Terminal window
tokenshift uninstall          # remove hooks only
tokenshift uninstall --purge  # also remove ~/.tokenshift/ (cache, stats, client_id)

The system-deployed enrollment manifest at /etc/tokenshift/ (Linux/macOS) or %PROGRAMDATA%\tokenshift\ (Windows) is left alone — that’s the MDM’s responsibility to remove.