Prompts, AI responses and code never leave the machine. A small model on the machine decides what kind of work each prompt is. nOps receives only that label. See What the agent sends and keeps.
Why install it
How it works
1
The developer works with an AI coding tool
The agent hears about sessions, prompts, tool calls and edits through the built-in hooks of Claude Code, Cursor, Codex and GitHub Copilot, and about commits through git hooks. It records only in repositories that belong to your organization’s allowed GitHub organizations, GitLab groups or Bitbucket workspaces.
2
The agent counts and labels, on the machine
It counts prompts, tool calls, file kinds and lines changed. A small model on the machine labels each prompt with a work type. The prompt text is deleted once labelled.
3
The agent sends counts and labels to nOps
Every 30 seconds, it sends the counts, labels, repository and branch names, and commit IDs. Nothing is sent while the machine is offline; it waits on disk.
4
nOps joins sessions to PRs
Commits and branches link each session to the PR it ended up in, and the session’s cost becomes that PR’s AI cost.
Supported tools and platforms
Node.js 22 or newer is required.
Get started
Install the agent
For developers: one command and a browser sign-in.
Manage the agent
For admins: allowed organizations, tools, prompt labels and machines.
What it sends and keeps
Exactly what leaves the machine, and what never does.
Commands and troubleshooting
clara status, doctor, pause, update, uninstall.Set the allowed organizations before developers install. Until at least one is set, the agent installs but records nothing. See Manage the agent.