quell auth
quell auth manages credentials for the optional parts of the Python package: the LLM fallback and the hosted account used for cloud sync and the Claude connector. You do not need it for rule-based quell find, which works with no key and no network.
What are the subcommands?
quell auth set --provider groq --key sk-... # bring your own key
quell auth set --provider quell # use Quell-managed access (Pro)
quell auth status # provider, mode, tier, key found?
quell auth status --privacy # what leaves your machine per mode
quell auth login # browser login
quell auth logout # revoke the session and remove credentials
How do I set a provider key?
quell auth set requires --provider (groq, quell, anthropic or openai). With --key the mode is "bring your own key"; without it the mode is Quell-managed and you must also run quell auth login.
quell auth set --provider groq --key sk-...
quell auth set --provider anthropic --key sk-ant-...
Credentials are written to ~/.config/quell/auth.json (Linux and macOS, honouring XDG_CONFIG_HOME) or %APPDATA%\quell\auth.json (Windows). If the optional keyring package is installed (pip install "quelltest[keyring]"), the key goes into the operating system keyring and the file only holds a reference. Without it the key is stored in that file in plain text, with owner-only permissions on Unix.
For Groq, the GROQ_API_KEY environment variable is also read.
What does quell auth status show?
Provider, mode (byo or quell), tier and whether a key was found. With --privacy it prints what is sent in each mode:
- Rule-based mode (no auth): zero network calls; analysis is local AST scanning.
- Your own key (Groq, Anthropic, OpenAI): the provider receives the function signature, docstring and specification text for the cases the rule engine cannot handle; full source files, test code, secrets and environment variables are not sent.
- Quell-managed (Pro): the same, routed through the Quell proxy.
How do I log in?
quell auth login
Opens your browser for an OAuth login at quell.buildsbyshashank.tech. One session is active per account, so logging in on one machine revokes sessions on other devices. For CI, the command help says to set the QUELL_API_KEY environment variable instead of logging in. Logging in is needed for cloud sync and the Claude connector, not for rule-based scans.
quell auth logout revokes the token on the server and removes the local credentials.
See also LLM providers.