Removing and coming back
jevlin uninstall removes what setup wrote, in three levels. The first keeps your wallet, key and registration, so coming back is one jevlin setup away.
Remove
jevlin uninstall -dry-run # what would be removed; changes nothing
jevlin uninstall # skills, hooks, plugins, and the profile block
jevlin uninstall -binary # ...and this installation's binary
jevlin uninstall -purge-state # ...and the wallet, identity, key, evidence and config
npm uninstall -g @jevlinsearch/jevlin # an npm install is npm's to remove
A plain uninstall removes what setup wrote for this installation (-home, default ~/.jevlin): the skills, hooks and plugins in each agent, and the profile block. On Windows it reverts PATH and JEVLIN_CONFIG only where they still hold setup's values.
What stays. Your wallet, registration, key, unsent searches and config, and nothing is revoked. Another installation's files are left and reported, and so is a hook of yours in the same group as Jevlin's: only Jevlin's handler is taken out. uninstall lists leftover .lock files, which are safe to delete.
-binary also removes the binary, its .previous and an interrupted upgrade's leftovers, never an npm copy. On Windows it moves the running binary aside and names the file to delete later.
Purging the state
-purge-state destroys the participant state: the wallet, identity, key, recorded searches and config. At a terminal, you type the wallet's address to confirm, or the installation path when there is no wallet. -yes cannot answer it, and a run stopped at its confirmation leaves the installation exactly as it was.
It first tries, for up to eight seconds, to revoke access at the rewards service. Folders your config names outside the installation are left and listed. Close agent sessions first, or a search may recreate folders.
If you made the wallet here, keep the 24 words or move the funds before you purge. The wallet is not recoverable afterwards without them. See Earning with mining.
To take one agent out and leave the rest:
jevlin agents uninstall -client codex
Coming back
Run jevlin setup, with -home <dir> for a non-default installation. Nothing in ~/.jevlin was removed by a plain uninstall, so you get the same agent, the same wallet and no new registration.
A bare jevlin connect would register anew, because the profile block that named this installation is gone. Use setup.
A set-aside installation
Instead of purging, you can set ~/.jevlin aside as ~/.jevlin.bak-<date>. Any ~/.jevlin.<name> or ~/.jevlin-<name> counts. Setup lists what a set-aside copy holds, newest first, asks Use it?, and moves it back only when you say yes at a terminal, in pieces that belong together:
| piece | what setup does |
|---|---|
| Registration and key | Move as one. If ~/.jevlin has its own, setup stops before anything moves and names both: keep one, move the other away. A half-made key there is renamed state.unenrolled-<time>. |
| Wallet | Moves whole. A ~/.jevlin with a wallet is simply used. An unfinished wallet folder there is renamed wallet.incomplete-<time>. |
| Unsent searches, session files | Merge one file at a time, never overwriting. |
| Config | Moves only if ~/.jevlin has none. |
Symlinks and anything another account owns are not moved: a set-aside folder that is not yours is never offered. The set-aside folder is removed only once it is empty.
The profile block
The lines setup adds to your shell profile are one block between # >>> jevlin >>> and # <<< jevlin <<<. Delete the block to undo them by hand. If the block no longer has exactly one start and one end line, setup leaves the file alone and prints the lines to add by hand.