Commands are built-in actions you can invoke from the chat input bar. Like skills, commands are triggered withDocumentation Index
Fetch the complete documentation index at: https://docs.bricks.tools/llms.txt
Use this file to discover all available pages before exploring further.
/, but instead of injecting reusable instructions they perform an action on the session directly.
Using commands
Type/ at the start of the chat input bar to open the slash popup. Built-in commands appear first with a built-in tag, followed by installed skills. Select a command to insert it into the input, or finish typing and submit it as a normal message.
Commands must be the first token of your message. Typing /compact after other text — such as “what does /compact do?” — is treated as plain text and the command is not run.
If you submit a command while the agent is still streaming, CTOR queues it and runs it at the next turn boundary instead of dropping it.
Available commands
/compact
Manually compact the current session’s conversation history. Use this when you want to free up context before hitting the automatic compaction threshold — for example, before kicking off a long sub-task.
CTOR replaces older messages with a summary while keeping the most recent turns intact. The summary message appears in place of the compacted history; subsequent messages continue against the shorter context.
Follow-up prompt. You can chain a prompt onto the same submission:
/compact entry is hidden from the popup — you can still type it manually, but nothing will happen if there’s no cut point.
Editing a previous message. Rewriting an earlier user message to /compact and submitting the edit compacts the conversation up to that message. The edit form discards any trailing text after /compact to avoid splitting the action across two operations.