Modes

The five modes

A mode is a role with its own instructions and its own set of allowed tools. The mode button sits under the task box. A new install starts in Architect, so the first task often ends with a plan instead of a changed file. Switch to Code to edit.

• Code

  What it does:Writes, changes and refactors code.
  Use it for:Most tasks: changing a resource, adding a feature, fixing a known bug.

• Architect

  What it does:Plans and designs before anything is built. Can write plan files, not code.
  Use it for:Bigger resources: let it plan, read the plan, then switch to Code.

• Ask

  What it does:Answers and explains. Does not change files.
  Use it for:"What does this resource do?", "Where is the money added?"

• Debug

  What it does:Looks for the cause of a problem step by step.
  Use it for:An error in the console you cannot place.

• Orchestrator

  What it does:Splits a large job into subtasks and hands each to the right mode.
  Use it for:Large jobs that touch many resources.

1

1. 11. Code: pick this to change files

Switching modes

• Click the mode button under the task box and pick one.
• Ctrl + . goes to the next mode, Ctrl + Shift + . to the previous one.
• Type /code, /architect, /ask or /debug at the start of the task box.

The agent can also suggest a switch itself, for example from Architect to Code once the plan is ready. It asks first, unless you allowed Mode in auto-approve.

Your own modes

Open the settings with the gear icon at the top of the panel and go to Modes. There you can create a mode with its own name, instructions and allowed tool groups, for one project or for all of them. Ideas that work well:

• A Config only mode that may only edit config.lua files.
• A Reviewer mode that reads a resource and lists problems without changing anything.

The Mode Marketplace button at the bottom of the mode list offers ready-made modes from the community. Read what a mode does before you install it.