CLI reference
Core commands
| Command | What it does |
|---|---|
aegis | Shows the branded landing and next-step guidance. |
aegis init | Runs first-use onboarding, provider setup, requires the first clone's initial goal, and surfaces the Feishu IM handoff before wake opens. |
aegis status | Checks whether the active local install is ready. |
aegis provider | Configures or inspects the active provider, model, reasoning effort, and context window. |
aegis clone [name] | Creates a named Aegis clone, prompting for any missing name or first durable goal interactively, or taking that goal from --initial-goal. |
aegis clones | Lists known clones. |
aegis clones bye <name> | Retires one clone. |
aegis clones bye --all | Retires every clone. |
aegis wake | Opens the main conversational surface. |
aegis wake --clone-id <name> | Opens one specific clone directly. |
aegis wake --message "..." | Runs a single turn without staying in the TUI. |
aegis skills | Lists the visible skill catalog outside wake, with subcommands for active, search, view, enable, disable, and install. |
aegis gateway setup --default-clone-id demo | Opens IM setup, lets you choose an IM surface, then writes that adapter's wiring with the first clone preselected. |
aegis gateway doctor | Runs whole-surface readiness checks across configured IM providers and accounts. |
aegis gateway describe | Prints the resolved IM provider and account wiring as JSON. |
aegis gateway feishu start --transport long-connection --detach | Starts the Feishu long-connection bridge in the background and returns immediately. |
aegis gateway feishu status | Shows the Feishu runtime status, account posture, PID activity, and runtime record paths. |
aegis gateway feishu stop --force | Gracefully stops the configured Feishu runtime, with --force available when needed. |
aegis gateway feishu restart | Restarts the configured Feishu runtime in the background. |
aegis gateway feishu logs ops-feishu --follow | Tails one Feishu account log and keeps streaming new output. |
aegis gateway discord setup --account-id ops-discord --bot-token-env-var AEGIS_DISCORD_BOT_TOKEN | Adds or updates one Discord account configuration. |
aegis dashboard --dry-run | Prints the operator-dashboard launch plan against the live CLI state database. |
aegis dashboard | Launches the local operator dashboard when this install includes apps/dashboard frontend assets and dependencies. |
Installers
| Command | When to use it |
|---|---|
| `curl -fsSL https://aegis.agentic-in.ai/install.sh | bash` |
| `curl -fsSL https://aegis.agentic-in.ai/install.sh | bash -s -- --channel stable` |
bash scripts/install.sh | Repo-local install from a checkout. |
bash scripts/install.sh upgrade | Rewrites the checkout-bound launcher. |
bash scripts/install.sh health | Runs health through the checkout-bound launcher. |
In-session control surfaces
Inside wake, these slash commands stay available without leaving the
conversation:
/status/profile/activity/memory/procedure/audit/tools/skills/frozen/cron/providers/models/clear/exit
/skills now fronts discoverable skill packages inside the conversation, and
matching skill packages also register dynamic slash commands such as
/apple-notes .... Outside wake, aegis skills mirrors the same operator
inventory and install surface without opening the shell first.
/frozen inspects the initial frozen prompt envelope rather than dumping the
whole live transcript. It prints the bounded frozen_skill_ids, the current
scoped skill shelf, governed disclosure records, and the original frozen
sections so operators can verify what the prompt actually saw without exposing
full skill bodies eagerly.
Inside wake, /profile, /activity, /memory, and /audit are the main
conversation-first entry points for the same profile, activity, and evidence
truth that the API operator routes expose more explicitly over HTTP.
The built-in runtime already exposes this curated tool catalog:
terminal:tool.terminal.execprocess:tool.process.managefile:tool.file.read,tool.file.write,tool.file.patch,tool.file.searchweb:tool.web.search,tool.web.read,tool.web.extractbrowser:tool.browser.navigate,tool.browser.snapshot,tool.browser.click,tool.browser.type,tool.browser.scroll,tool.browser.back,tool.browser.press,tool.browser.images,tool.browser.vision,tool.browser.consoleclarify:tool.clarifycron:tool.cron.managecode_execution:tool.code.executememory:tool.memory.recall,tool.memory.uploadmessaging:tool.message.sendtodo:tool.todo.managecontinuity-native:tool.profile.manage,tool.activity.manage,tool.procedure.inspect,tool.procedure.manage
The wider extension surface still includes built-in skills, authored skills, and recurring cron jobs on top of the built-in tools.
Local operator dashboard
aegis dashboard is the private operator web surface. It reads the live
aegis.sqlite3 state through the API-backed dashboard projection at
/v1/operator/dashboard and launches the React app under apps/dashboard/
when the current install includes those frontend assets.
That means:
- repo checkouts can launch it directly after installing dashboard dependencies
- installs that do not include
apps/dashboardassets stay truthful by printing launch guidance instead of pretending the web surface exists
Runtime paths
By default, Aegis uses:
AEGIS_HOME=$HOME/.aegisAEGIS_STATE_DIR=$AEGIS_HOME/stateAEGIS_GATEWAY_STATE_DIR=$AEGIS_HOME/state/gatewayAEGIS_PROFILE_DIR=$AEGIS_HOME/profileAEGIS_SKILLS_DIR=$AEGIS_HOME/skillsAEGIS_INSTALLED_SKILLS_DIR=$AEGIS_SKILLS_DIR/installedAEGIS_AUTHORED_SKILLS_DIR=$AEGIS_SKILLS_DIR/authored
You can override them through environment variables when you need a custom layout.