System Commands

Why commands deserve their own page

Any long-lived assistant benefits from a small, understandable operational command surface.

Commands help users:

• reset or compact sessions;
• inspect behavior;
• control operating state;
• recover when a conversation path becomes messy.

Product principle

Commands should feel like tools for keeping the workstation healthy, not like an obscure maintainer-only trick.

That principle matters for both docs and product tone:

• the assistant is powerful;
• the user remains in control;
• the operating model stays explicit.

Good documentation behavior

When describing commands:

Explain intent first

Start with what a command is for before diving into syntax.

Tie commands to actual operating problems

Examples:

• clear a session that should not keep context;
• compact a session that has grown too large;
• reset state before beginning a new workflow.

Avoid command-list bloat on the homepage

The homepage should imply operational maturity, not teach every command inline. Command details belong here in docs.