Overview
This is the entry point for TokenShift's technical documentation: installation, configuration, and governance policy setup, organized the way engineering and platform teams actually look things up, not by marketing feature name.
Getting started
Installation. TokenShift installs as a single lightweight Go binary. Distribute it through your existing MDM (Jamf, Kandji, Intune, or equivalent) for a fleet-wide rollout, or install manually for a pilot with a small group first.
Supported coding agents: Claude Code, Cursor, GitHub Copilot. In development: Windsurf, Codex. No IDE plugins or extensions are required for any of them.
First-run behavior. On install, TokenShift begins passive monitoring immediately. Optimization techniques can be enabled individually or all at once from the admin console; nothing is applied silently without visibility into what changed.
Configuration
Technique management. Each of the six optimization techniques (Trim, Drop, Cache, Route, Compress, Batch) can be toggled independently per team, so a team with unusual workflow requirements can disable a specific technique without losing the rest.
Model policy. Set a default model per team, with defined escalation paths for tasks that need a larger model. Policy is enforced at the endpoint, not just recommended.
Tool and MCP governance. Define which tools an agent may invoke and which MCP servers are permitted, per team. Violations are logged centrally for audit review.
Admin console reference
Core metrics tracked by default: token savings, time to first token, session duration, and governance violations. Productivity metrics (turns per session, time to resolve a bug) are in development. Each can be filtered by developer, team, or session, and exported for reporting outside the console.
Security model
Only metrics and metadata leave the machine, never prompt content. There is no model call in the request path and no access to source code or credentials at any point in this flow. This is the section most InfoSec reviews ask about directly, and it's worth linking prominently rather than burying it in a FAQ.
Updates and maintenance
Updates are distributed centrally through your MDM with zero-touch maintenance across every endpoint. No manual update process is required per developer machine.
Frequently asked questions
How do we manage Claude Code usage at the team level?
Through the admin console's model policy settings: set defaults per team, and require explicit escalation for higher-cost models, enforced at the endpoint rather than relying on developer discretion.
What governance controls exist for MCP servers and tool calls?
Admins can define which MCP tools an agent may invoke, per team, with every policy violation logged centrally for audit purposes.
Methodology
This guide reflects TokenShift's product documentation as of July 2026. For corrections, reach out at pointfive.co/contact.