canvas settings subcommand group manages which Chrome profile the CLI reads cookies from and lets you inspect or reset the persisted configuration. Settings are stored locally on disk and are read on every command invocation alongside the Chrome cookies.
How auth and settings interact
The CLI reads Canvas session cookies directly from Chrome. If you have multiple Chrome profiles — for example, one for a personal Google account and another for a school account — the CLI needs to know which profile to use.canvas settings is where you configure that.
When no profile is saved, the CLI attempts to auto-detect a Canvas domain across all Chrome profiles. If exactly one Canvas domain is found, it uses that profile automatically. If multiple are found, commands will fail until you pin a profile with canvas settings choose-profile.
canvas settings profiles
List all detected Chrome profiles and show their auth status.
name— Chrome profile display namepath— filesystem path to the profile directoryauth_status— whether a valid Canvas session was found (ok,error, orunknown)detected_canvas_domains— Canvas domains detected in this profile’s cookiesresolved_canvas_base_url— the resolved Canvas base URL if one was foundselected—trueif this profile is the currently saved selection
canvas settings choose-profile
Save a Chrome profile as the active selection for all subsequent CLI commands.
Profile name or domain to select. Omit for interactive selection. Required in headless (non-TTY) environments.
Interactive mode
When run in a terminal without an argument, the CLI prints a numbered list of profiles and waits for input:* marker indicates the currently saved profile.
Non-interactive mode
In scripts or CI environments where stdin is not a TTY, pass the profile name directly:canvas settings show
Print the current settings file contents alongside a live auth status check.
settings— the raw persisted settings object (selected profile name and path, if any)auth— the result of a live Canvas auth probe (equivalent tocanvas auth-status)
settings will be an empty object or omit the profile keys.
canvas settings clear
Delete the saved settings file, resetting the CLI to its default auto-detection behavior.
canvas settings choose-profile again to re-pin a profile.
What gets persisted
The settings file stores the selected Chrome profile name and filesystem path. It does not store cookies, tokens, or any Canvas credentials. Cookies are read fresh from Chrome on every request, so session and CSRF rotation are picked up automatically. The settings file location depends on the OS and follows the standard user config directory conventions used by the underlyingauth.settings module.