Slash Commands

All commands start with /. Type / and press Tab for autocomplete.

Quick Reference

Command	Description
/help	Show help information
/changelog	Show recent changes
/model	Switch AI model
/clear	Clear conversation history
/resume	Resume previous session
/init [optional msg]	Generate AGENTS.md file
/compact [guidance]	Compress conversation memory, optionally with guidance for what to keep
/stats	Show session statistics
/usage	Show plan usage, weekly limit reset time, and credit balance
/mcp	Manage MCP servers
/connector	Connect apps like Gmail, Slack, Notion and GitHub
/bashes	List background processes
/logout	Sign out and exit
/quit	Exit AdaL CLI
/theme	Change theme
/about	Show version and auth status
/bug [desc]	Report a bug
/byoak	Bring your own API keys, optionally with your own endpoint
/skills	List loaded skills
/plugin	Manage plugins/marketplaces
/cron	Schedule recurring prompts
/schedule	Run a prompt once at a chosen time, or on repeat (preview: listed in dev mode only)
/subagent	Configure subagents
/permissions	Configure approval settings

Where commands work

Slash commands are not only a terminal feature. In AdaL Desktop, type / in the chat box to get the same list, filtered as you type, and the commands that open a panel in the CLI open one there too.

A few commands are terminal-only, because the other surfaces already are what the command asks for:

Command	CLI	Desktop	Why
/ide	✅	—	It hands a terminal session to Desktop. If Desktop is not installed, it shows the install link
/resume	✅	—	Desktop opens another chat from the chat list
/theme, /quit	✅	—	Desktop keeps its own theme setting and closes like any window
/about	✅	—	Desktop shows version and account in its own menus

Everything else in the table above works on both. If you type a command a surface does not offer, the text stays in the box with a note — nothing is run or sent to the agent.

Permissions & Approvals (/permissions)

Use /permissions to configure which actions require manual confirmation before AdaL proceeds.

Common uses:

• Keep shell commands gated behind approval
• Allow auto-apply for file edits in trusted workflows
• Review and adjust safety behavior before enabling faster execution modes

Tips

• Use /help for information of all slash commands.
• Run /init to generate AGENTS.md so that AdaL can understand your codebase better.
• Use /compact after a milestone is achieved to save context and stay focused, or switch to a larger-context model via /model when needed.
• Add guidance to say what the summary must keep: /compact keep the API design details. A bare /compact behaves as before.
• Use /permissions before long tasks to match approval strictness to your risk tolerance.
• Use /cron to automate recurring tasks — training monitoring, data pipelines, literature reviews, and more.
• Use /schedule for work that should happen later without AdaL open, once or on repeat. The manager asks how often, when, what to do and what to call it — there is no time format to type.

Related: Cron: Scheduled Prompts · Scheduled Tasks · Keyboard Shortcuts · MCP · Connectors · BYOAK