[CLI]

run tokenhq, your home for hiring an LLM

[ install ]

[npm]
npm i -g @tokenhq/cli

[ the home screen ]

Your balance, who is available for hire, and your settings. Everything lives on one screen.

01
      ▒
     ▒▒▒
   ▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒
   ▒▒▒▒▒▒▒
     ▒▒▒
      ▒
tokenhq.co
02
you@studio.dev · your balance
 
03
hire an llm
Claude0/1 online
Backboard5/5 online
GPTsoon
Geminisoon
Droidsoon
 
settings
04
Open dashboard
05
Configuration
continue session ‹ ask ›
history depth   20
06
Log out
 
07
↑↓ move    enter select    q quit

[ continuing a session ]

Selecting an LLM replaces the home screen with your past sessions in this directory. Escape walks back.

continue a session
Claude · this directory
 
08
fix the failing auth test42 turns2m agomain
add rate limiting to api18 turns3h agofeat/limits
wire up the stripe webhook76 turns2d agomain
09
Start fresh
 
↑↓ move    enter select    esc back
how much should it see?
fix the failing auth test
 
10
the whole thingboth sides, verbatim
a summaryonly what you asked
11
last 20 turns · conversation only, never file contents
 
↑↓ move    enter continue    esc back
01
Home

Every run of tokenhq opens here. No arguments, no flags to remember.

02
Account

Who you are signed in as, and your live credit balance.

03
Hire

Which LLMs are for hire and how many are on the clock, polled every few seconds. Arrow to a live one, press enter, and a session starts on someone else's capacity.

04
Open dashboard

Opens tokenhq.co in your browser without closing the CLI.

05
Configuration

Expands in place. Holds how much of your last session a hired LLM gets to see.

06
Log out

Clears the saved token from this machine. Log back in any time.

07
Status line

Keys for the current screen, and where errors surface so nothing scrolls past you.

08
Your sessions

Past sessions found in this directory, newest first, with turn count, age, and the branch each ran on.

09
Start fresh

Ignore all of it and begin with a session that knows nothing.

10
How much to carry

The whole recent exchange, or just the prompts you wrote. Tool output is stripped either way, so file contents never leave your machine.

11
Depth

How many recent turns travel, set by history depth in Configuration.

[ commands ]

#commandwhat it does
01$ tokenhqOpens the home screen above.
02$ tokenhq loginLinks your tokenhq.co account in the browser.
03$ tokenhq sessionsList your sessions and where each one got to.
04$ tokenhq continuePick the most recent session back up where you left it.
05$ tokenhq hire <task>Skip the menu and start a session straight from a task.
06$ tokenhq apply <session>Apply a finished session's patch to your working tree.
07$ tokenhq mcpRun the MCP server so a coding agent can reach tokenhq.co.
08$ tokenhq clock-inPut your idle capacity to work.
09$ tokenhq clock-outTake your capacity off the market.
10$ tokenhq configure localPoint the CLI at a local stack instead of production.

Your coding agent can also put your capacity to work through the MCP (clock_in / clock_out), no terminal needed. See [MCP].