Octop CLI: Channel, Cron, Plugin, and Admin Commands
The CLI covers channel setup, cron scheduling, plugin management, and admin tasks alongside the web UI. Use these commands to wire up IM platforms, automate recurring prompts, extend Octop with plugins, and administer users — all from the terminal.
octop channel
Create and manage IM channel connections for an agent. Most subcommands work offline; test starts an embedded server and does not need a separate octop run.
Subcommands
octop cron
Schedule recurring tasks that trigger agent prompts automatically. run-now requires a running server; all other subcommands work offline.
Trigger formats
Pass any of the following values to --trigger:
Task type flag
--prompt is required. The CLI has no --name. octop cron run-now boots an embedded server and does not need a separate octop run; newly created jobs still require a restart of a running octop run before the scheduler picks them up.
octop plugin
Install and manage third-party plugins. Plugins are dropped into ~/.octop/plugins/ and power the same plugin system used by the web UI.
Subcommands
The web UI Plugins page can also install from a local ZIP and optionally overwrite a plugin of the same name. Bundled plugins ship with Octop disabled by default; uninstalling one does not recreate it on upgrade. Per-agent plugin toggles live under Personalization (GET/PUT /api/agents/{id}/tool-settings).
Use octop plugin reload after installing or updating a plugin to apply changes to a running server without a full restart.
octop user
Manage users in the local database. Every subcommand works offline. There is no octop user login: pin a default --user with octop config set-user, or pass --user on the subcommand.
octop admin
Inspect system state, review the audit log, manage global providers, and perform administrative operations directly against the local database.
Subcommands
octop admin rotate-jwt-secret writes a new JWT secret directly to the SQLite database. This immediately invalidates all active sessions — every logged-in user, including dashboard sessions and CLI tokens, will be signed out. Use this command intentionally, not routinely.
octop backup
Export and restore the full Octop state (database, workspaces, and configuration). All subcommands work fully offline.
Automatic backups run inside octop run. Configure them in config.json → backup, with env overrides, or from Application Settings → Backup & Restore. Archives are named octop-auto-backup-*.tar.gz; retention never deletes manual octop-backup-* files. The web UI rejects concurrent backup or restore work while one operation is already running. See Backup & Restore.

