Start with tom

Install tom

On macOS or Linux:

curl -fsSL https://tokens-on.me/install.sh | sh

Or with Homebrew:

brew install mindsersit/tap/tokens-on-me

On Windows, in PowerShell:

irm https://tokens-on.me/install.ps1 | iex

It checks the download against the release’s checksums, then puts tom in ~/.local/bin, or in your user folder on Windows. It installs nothing else and needs no Node. On Windows it also adds that folder to your Path; on macOS and Linux it says what to add if the folder is not on yours.

Start your coding tool

Install your coding tool using its official instructions, then run tom followed by its name:

tom claude

Claude Code

tom codex

Codex

tom omp

oh-my-pi

tom gemini

Gemini CLI

The first time, tom opens your browser to log this computer in: select Allow if you just ran tom. The computer then appears in Account, where you can log it out.

On a computer without a browser, such as a server, run tom login --code: it shows an address and a code to type on another device.

Anything after the tool’s name is passed on to it:

tom claude -p "fix the failing test"

If you have several allowances

If several of your allowances fit a tool, tom asks which one to use at each start: pick one with the arrow keys or its number, then press Enter. To stop it asking, choose one with tom use. For a single run, use --allowance:

tom use workshop
tom claude --allowance=workshop

Run tom on its own to see your allowances, what is left on each and the command that starts each tool. A name can be shortened while it stays unique.

What each command does

tom

Who is logged in, your allowances, and how to start each tool.

tom list

Your allowances: who gave them, what is left, until when and on which models.

tom use <name>

Chooses the allowance used for the tools its models fit, until you choose another.

tom login

Logs this computer in through your browser. With --code, without one.

tom logout

Logs this computer out: its tokens stop working at once.

tom update

Installs the newest tom.

tom --help

Lists these commands.

What tom sends

tom only talks to Tokens On Me, to log this computer in and start your tool, and to GitHub, to update itself. It sends no telemetry and nothing about your projects, files, prompts or answers. Your coding tool sends your prompts to Tokens On Me as it would without tom; we do not store them.

This computer’s login is kept in ~/.config/tokens-on-me/, readable by you alone. A computer unused for 90 days is logged out automatically.

Update tom

tom update installs the newest version after checking its signature with the key built into the one you have:

tom update

If you installed it with Homebrew, update it with Homebrew:

brew upgrade tokens-on-me

Check a download

Each release on GitHub comes with its checksums (SHA256SUMS) and their signature (SHA256SUMS.minisig). Download those two files and your archive into one folder, then check them with minisign:

minisign -Vm SHA256SUMS -P RWQjQZP+j4ZFXuFpARpr1WbmE8rA+ih5jbmLvwT/c6apfMxOSf6sdjGo
shasum -a 256 -c SHA256SUMS --ignore-missing

The first line checks that the checksums came from us, the second that your archive matches them. On Windows, compare what Get-FileHash prints with your archive’s line in SHA256SUMS.

Remove tom

Log this computer out first: its login stops at once.

tom logout

Then delete tom and its folder: ~/.local/bin/tom and ~/.config/tokens-on-me/ on macOS and Linux, .local\bin\tom.exe and .config\tokens-on-me in your user folder on Windows. With Homebrew: brew uninstall tokens-on-me, then delete the folder. On Windows, also take .local\bin off your Path if nothing else uses it.

Or set it up by hand

Each tool’s guide also gives the lines to use with your token: Claude Code, Codex, Gemini CLI and oh-my-pi. An editor extension or a desktop app needs them: tom only starts the command-line tool.