Commands

Every jevlin command in one table. Every flag is in jevlin help and jevlin <command> -h.

command	what it does
`setup`	Everything after the binary: previous installation, config, `connect`, profile, agents.
`uninstall`	Removes what setup wrote for one installation; `-binary` and `-purge-state` go further.
`upgrade`	Replaces a native binary with a verified release; `-rollback` swaps back. `-auto` is the daily check the hooks start, not a command a person runs.
`search`	One web search. `--stdin` for agents (JSON in, JSON out); `<query words>` for a person.
`agents install\|status\|uninstall`	Sets up, reports or removes the skills and hooks of each agent.
`agents prefer on\|off\|status`	Whether this search or the agent's own is the default.
`agents tier fast\|balanced\|max\|default\|status`	The band every search carries unless the request names one; `default` unsets it.
`flush`	One pass of the mining plane: join the open epoch, promote recorded searches, submit.
`connect`	Registers with the search platform, prints the claim link, polls until claimed.
`mining enable\|disable`	Turns mining on (asking for a payout address) or off for this installation.
`status`	What this installation has and has not completed. `-json` for one envelope.
`doctor`	Whether searches are recorded and earning, check by check. `-json` for one envelope.
`earnings`	What the chain has paid to your payout address.
`limits`	This key's spend caps and today's spend against the effective ceiling, read from the router. Reading spends nothing; setting caps is not built yet. `-json` for one envelope.
`wallet init\|address\|register\|balance\|send`	The wallet setup made, or one you make here.
`login`, `enroll`, `payout`, `join`, `provider`	The portal's older manual path.
`version`, `help`	The version, and the full usage text.

Where a command finds its config

A command that reads the config takes -config <file>; setup, upgrade and uninstall take -home <dir> instead, and wallet init and wallet address take only -dir.

Without -config, the config is the first of:

JEVLIN_CONFIG.
The installation's own, $JEVLIN_HOME/jevlin.toml, else ~/.jevlin/jevlin.toml, when that file exists.
Built-in defaults.

A jevlin.toml in the working directory is never read unless you name it, so a cloned repo cannot choose where your keys are sent. status and doctor name the file they used. connect refuses to run with no config file, and says to run jevlin setup.

search refuses a second -config, even one naming the same file: the Claude Code allow rule ends after the installed -config <file>, so a second one could otherwise send the key to another config's router without a prompt.

Where a command finds its config​

See also​

Where a command finds its config

See also