Getting the Metermark agent onto machines
Metermark measures AI-tool usage where it happens: on the laptop that runs Claude Code, Codex or Cursor. The hosted side never reads a machine on its own, so every account needs the agent on each machine whose sessions should count. There are two ways to get it there, and a third source that needs no agent at all.
| Path | Best for | What the person does |
|---|---|---|
| Self-install | individuals and small teams | pastes one command; signs in once in the browser |
| Fleet deployment | companies with Jamf, Kandji, Mosyle, Intune or a configuration tool | nothing; the package and its configuration arrive from the fleet tool |
| Vendor pollers | admins of Cursor Business or the Anthropic Console | pastes a vendor admin key in Settings; gives organization-level usage, not per-session labels |
Whichever path installs it, the agent does the same four things on a schedule and nothing else: import (read local session history: labels and numbers only), classify (send short prompt samples to Metermark, in memory, discarded once labeled), sync (upload label rows and usage days), and update itself when allowed. Security review is the page to hand a security team; the configuration reference lists every setting the agent honours and where it reads them from.
Design commitments
These hold for every path, so IT teams can plan against them:
- No admin rights at runtime. The agent runs as the signed-in user, because the session history it reads lives in that user's home directory. Installing a fleet package needs admin once; running it never does.
- No inbound connections, no daemons listening. Outbound HTTPS to
metermark.aionly, plusauth.metermark.aifor interactive sign-in. Proxies are honoured. - Identity is the person, not the device. Sessions are attributed to an email address: the one the fleet tool assigns, an explicit mapping, the Metermark account the person signed in with, or the AI tool's own login, in that order. See Who the sessions belong to.
- Nothing to type after setup. A launch agent (macOS), a user timer (Linux) or a scheduled task (Windows) runs the cycle every 15 minutes. A machine that was asleep catches up on wake.
- Removable in one step.
metermark uninstall, or removing the package from the fleet tool, stops the schedule and deletes the local store. Nothing lingers. - The hosted side can turn a machine off. Revoking the enrollment key in the dashboard stops every machine that used it at its next sync.