Look up all CLI subcommands and flags for managing the bot, routines, reminders, and Google services.
The ollim-bot CLI is the single entry point for running the bot and managing
routines, reminders, Google Tasks, Google Calendar, and Gmail from the terminal.
With no subcommand, it starts the Discord bot. With a subcommand, it runs the
corresponding operation and exits.
Run ADHD behavior evals that test whether the bot responds appropriately to
users with ADHD. Each eval plays a simulated ADHD user (Haiku-powered proxy)
against the real bot agent, then scores the transcript with an LLM judge.
eval run requires Claude authentication — run ollim-bot auth login first.
Run scenarios against the real agent. Runs all scenarios by default.
Argument / Flag
Type
Required
Default
Description
scenario_id
positional
No
all
Run a specific scenario by ID
-v, --verbose
flag
No
false
Show full transcript during execution
# Run all scenariosollim-bot eval run# Run a single scenario with transcript outputollim-bot eval run overwhelmed-by-tasks --verbose
Each scenario reports per-criterion scores (1-5 scale), an overall score,
and a PASS/FAIL status. A scenario passes when the overall score is at least
3.0 and no individual criterion scores below 2. Results are saved to a JSONL
history file for regression tracking.
Manage Claude Code authentication. ollim-bot uses the Claude CLI bundled with
the Agent SDK for OAuth — you don’t need to install Claude Code separately.At startup, the bot checks auth status automatically. If not logged in, it
extracts an OAuth URL from the bundled CLI and DMs it to you via Discord.
Click the link to sign in — the bot waits until authentication completes,
then continues startup. The auth subcommands below are for manual use
(pre-authenticating before enabling a service, checking status, or logging out).
Run diagnostic checks across every layer of your installation — environment
variables, data directory, timezone, routines, reminders, tool policy, state
files, Claude CLI, and authentication. Each check reports PASS, WARN,
or FAIL with an actionable message so you know exactly what to fix.
ollim-bot doctor
No subcommands or flags. The command loads your .env, runs all checks, prints
results grouped by section, and exits with code 0 if everything passes or
code 1 if any checks fail.Example output:
ENVIRONMENT PASS DISCORD_TOKEN: set PASS OLLIM_USER_NAME: set PASS OLLIM_BOT_NAME: setDATA DIRECTORY PASS DATA_DIR: /home/user/.ollim-bot PASS DATA_DIR writable: yes PASS DATA_DIR git: initializedTIMEZONE & SCHEDULING PASS timezone: America/Los_Angeles PASS APScheduler timezone: acceptedROUTINES PASS routine files: 3 loaded PASS morning-briefing: next fire 9:00 AM (in 2h 30m)REMINDERS PASS reminders: none pendingTOOL POLICY PASS tool policy: no background items to validateSTATE FILES PASS pending_updates.json: valid JSON PASS config.json: not present (will use defaults) PASS ping_budget.json: valid JSON PASS fork_messages.json: valid JSON PASS inquiries.json: not present (will use defaults)CLAUDE CLI PASS Claude CLI: /path/to/claudeCLAUDE AUTH PASS Claude auth: logged inSUMMARY: 19 passed, 0 warnings, 0 failures
Run ollim-bot doctor after initial setup or whenever something feels off.
It catches the most common issues — missing env vars, corrupt state files,
invalid cron expressions — before they surface as confusing runtime errors.
routine add accepts these flags when --background is set. For reminder add,
these options are always available since reminders run in the background by default.
Flag
Type
Default
Description
--model
string
—
Model override for this fork
--no-thinking
flag
false
Disable extended thinking
--isolated
flag
false
Fresh context, no session history
--update-main-session
choice
on_ping
When to report to main session
--no-ping
flag
false
Disable ping_user and discord_embed
The reminder add command also supports --allowed-tools for
restricting which tools the background fork can use, and
--skills for loading skills at fire time.
Both accept one or more space-separated values.