Architect mode

Refactor code you did not write

Large refactors are where an agent earns its keep, because the work is mechanical but spans too many files to hold in your head. Architect mode is built for exactly this shape of task.

How to run it

  1. 01Open the folder and let the workspace index finish.
  2. 02Switch to Analyze and ask how the module is wired today. Read the answer before you change anything.
  3. 03Switch to Plan and describe the target structure. Review the plan, not the code.
  4. 04Switch to Architect to execute it, then review the diffs file by file.
  5. 05Run your tests in the integrated terminal and let the agent fix what it broke.

Why a bigger model helps here

Refactors need the model to hold more context at once. If your GPU can take it, a 14B or larger is noticeably steadier than a 7B on multi-file work — and it is still free.

Git is your undo

Because edits land in your working tree, a bad refactor is a git checkout away. Commit before you start and you have nothing to lose.

The catch

Review every diff. A refactor that compiles is not the same as a refactor that preserves behaviour, and no agent changes that.