Maestro includes an extensible slash command system with autocomplete. Type / in the input area to open the autocomplete menu, use arrow keys to navigate, and press Tab or Enter to select.
Custom AI Commands
Create your own slash commands in Settings > Custom AI Commands. Each command has a trigger (e.g., /deploy) and a prompt that gets sent to the AI agent.
Commands support template variables that are automatically substituted at runtime:
Agent Variables
| Variable | Description |
|---|
{{AGENT_NAME}} | Agent name |
{{AGENT_PATH}} | Agent home directory path (full path to project) |
{{AGENT_GROUP}} | Agent’s group name (if grouped) |
{{AGENT_SESSION_ID}} | Agent session ID (for conversation continuity) |
{{TAB_NAME}} | Custom tab name (alias: SESSION_NAME) |
{{TOOL_TYPE}} | Agent type (claude-code, codex, opencode) |
Path Variables
| Variable | Description |
|---|
{{CWD}} | Current working directory |
{{AUTORUN_FOLDER}} | Auto Run documents folder path |
Auto Run Variables
| Variable | Description |
|---|
{{DOCUMENT_NAME}} | Current Auto Run document name (without .md) |
{{DOCUMENT_PATH}} | Full path to current Auto Run document |
{{LOOP_NUMBER}} | Current loop iteration (starts at 1) |
Date/Time Variables
| Variable | Description |
|---|
{{DATE}} | Current date (YYYY-MM-DD) |
{{TIME}} | Current time (HH:MM:SS) |
{{DATETIME}} | Full datetime (YYYY-MM-DD HH:MM:SS) |
{{TIMESTAMP}} | Unix timestamp in milliseconds |
{{DATE_SHORT}} | Short date (MM/DD/YY) |
{{TIME_SHORT}} | Short time (HH:MM) |
{{YEAR}} | Current year (YYYY) |
{{MONTH}} | Current month (01-12) |
{{DAY}} | Current day (01-31) |
{{WEEKDAY}} | Day of week (Monday, Tuesday, etc.) |
Git & Context Variables
| Variable | Description |
|---|
{{GIT_BRANCH}} | Current git branch name (requires git repo) |
{{IS_GIT_REPO}} | ”true” or “false” |
{{CONTEXT_USAGE}} | Current context window usage percentage |
/standup command with prompt:
It's {{WEEKDAY}}, {{DATE}}. I'm on branch {{GIT_BRANCH}} at {{AGENT_PATH}}.
Summarize what I worked on yesterday and suggest priorities for today.
Spec-Kit Commands
Maestro bundles GitHub’s spec-kit methodology for structured feature development. Commands include /speckit.constitution, /speckit.specify, /speckit.clarify, /speckit.plan, /speckit.tasks, and /speckit.implement.
See Spec-Kit Commands for the complete workflow guide.
OpenSpec Commands
Maestro bundles OpenSpec for spec-driven change management. These commands help you propose, implement, and archive changes systematically:
| Command | Description |
|---|
/openspec.proposal | Create a change proposal with spec deltas before writing code |
/openspec.apply | Implement an approved proposal by following the tasks |
/openspec.archive | Archive completed changes after deployment |
/openspec.implement | Generate Auto Run documents from a proposal (Maestro-specific) |
/openspec.help | Get help with OpenSpec workflow and concepts |
Agent Native Commands
When using Claude Code, Maestro automatically discovers and displays the agent’s native slash commands in the autocomplete menu. These appear with a “Claude Code command” label to distinguish them from Maestro’s custom commands.
Supported in Batch Mode
Claude Code runs in batch/print mode within Maestro, which means only certain native commands work. The following commands are supported:
| Command | Description |
|---|
/compact | Compact conversation history to reduce context usage |
/context | Manage conversation context |
/cost | Show token usage and cost for the session |
/init | Initialize a CLAUDE.md file in the project |
/pr-comments | Address PR review comments |
/release-notes | Generate release notes |
/review | Request a code review |
/security-review | Perform a security review |
/commit, /pdf, /docx) are fully supported and will appear in the autocomplete menu.
Not Supported in Batch Mode
The following Claude Code commands are interactive-only and don’t work through Maestro:
| Command | Reason |
|---|
/mcp | MCP server management requires interactive TUI |
/help | Help display is interactive |
/clear | Conversation clearing is handled differently in batch mode |
/config | Configuration requires interactive prompts |
/model | Model switching mid-session requires TUI |
/permissions | Permission management is interactive |
/memory | Memory/CLAUDE.md editing requires TUI |
/rewind | Conversation rewind requires interactive selection |
/vim | Vim mode is a TUI feature |
/doctor | Diagnostics run as a separate CLI command |
/login / /logout | Authentication is interactive |
/bug | Bug reporting requires interactive input |
For commands like /mcp or /config, use the Claude Code CLI directly in a terminal: claude mcp or claude config.
