# Common commands

> **Generated from [`README.md`](https://github.com/Saylek-ai/TokEx/blob/main/README.md)
> by `scripts/generate-docs-cli-reference.mjs`. The `docs-parity` CI check fails closed
> if this page and the README's tables ever drift apart. Don't hand-edit the tables below;
> edit README.md and re-run the generator.**

This is the everyday subset, not the whole command tree. It is deliberately short: these
are the commands a member actually reaches for.

**The CLI is the complete reference for itself.** `saylek --help` lists every command,
`saylek <command> --help` gives full detail for one, `saylek help <topic>` covers curated
learning topics, and bare `saylek` shows the grouped everyday-first overview.

Task-shaped pages cover the commands not listed here:
[Sharing and access](/docs/sharing-and-access) for `saylek sharing`,
[Share your models](/docs/share-your-models) for `saylek host`,
[Invite flow](/docs/invite-flow) for giving someone access to a machine you share
(`saylek sharing invite`), and
[Troubleshooting](/docs/troubleshooting) for `saylek model` and the daemon verbs.

## Everyday commands

| Command | What it does |
|---|---|
| `saylek status` | Is your machine healthy? (`--watch` to live-tail) |
| `saylek models` | What this machine can serve right now (`--account` for the models your account can use) |
| `saylek claude` | Start Claude Code against the models you can reach, with a key and model already set |
| `saylek host` | Serve from this machine's GPU or an adopted engine |
| `saylek statement <YYYY-MM>` | An honest, no-money record of where each request ran |
| `saylek --help` | Everything else |

## Leaving

Leaving is meant to be honest and reachable, at whatever scope you mean, and the first
step is reversible.

| You want to… | Command | Reversible? |
|---|---|---|
| **Pause**: stop serving and asking, keep your access + standing | `saylek settings account deactivate` | Yes. `saylek settings account activate` turns it back on. |
| Stop using **someone's machines** | `saylek sharing stop-using --person <name>` | Yes, if they share with you again. |
| Leave **a group you joined** (find the id with `saylek circles list`) | `saylek circles leave <id>` | Yes. A group that needs an invitation needs a new one. |
| Leave **Saylek entirely**: delete your account + wipe this device | `saylek settings account delete` | Account: 90-day soft-delete. This device's keys: **irreversible**. |
| Remove **one machine**, keeping your account | `saylek machines remove` | No. Set it up again with `saylek host wizard` on that machine. |
| Remove only this device's local files | `saylek wipe` | Local only: the machine stays registered unless you add `--remove-machine`, which removes it *before* the local keys go. After a plain wipe there are no keys left to remove it with. |

`saylek leave` isn't a command on its own. To stop using someone's machines, run
`saylek sharing stop-using --person <name>`; to leave a group you joined, `saylek circles leave <id>`;
to leave Saylek entirely, `saylek settings account delete`.

## Next steps

- [Quickstart](/docs/quickstart): install and ask your first question.
- [Sharing and access](/docs/sharing-and-access): give access, take it back, and see who has it.
- [Share your models](/docs/share-your-models): serve from your machine, and the ways to stop.