Brainstorm with a cheaper model: ideas, risks and alternatives you may have missed. Use it when you are unsure between approaches or stuck, not on every task.

question: what you are deciding, including your current plan if you have one. context: relevant facts, constraints and what you already ruled out. lenses: up to 4 angles, each answered independently in parallel, for example ["simplest approach", "edge cases and failure modes", "performance"]. my_view: your own conclusion, written BEFORE you see Deputy's ideas. It is not sent to Deputy, so its ideas stay independent; it is echoed back so you can compare honestly. project_dir: absolute path of the project, only if Deputy picked the wrong folder.

The answers are UNVERIFIED suggestions from a weaker model. Weigh them below your own analysis, check them against the code, and adopt only what holds up.

Have independent cheap reviewers hunt for defects in a change, one per lens, in parallel. Use it for risky or large changes, not routine ones whose tests pass. By default it reviews your uncommitted changes (git diff against HEAD, plus new files).

focus: what the change is supposed to do, so reviewers can spot mismatches. diff: the change to review, if you do not want the automatic git diff. base: compare against this revision instead of HEAD (for example "main"). paths: limit the review to these files or folders. lenses: up to 4 review angles; default ["correctness and logic bugs", "edge cases, error handling and missing tests"]. thinking: leave it out for a fast review (low thinking by default); "high" or "max" think longer, for an especially risky change. project_dir: absolute path of the project, only if Deputy picked the wrong folder.

Findings are UNVERIFIED and may be false positives. Verify each against the code; fix only what you confirm, and tell the user which findings you rejected and why.

Ask Deputy a question that needs a lot of reading: where something is handled, how a flow works, what a large log says. Deputy can only list, read and search files. Returns a compact answer with file:line evidence. Treat it as leads: read the cited lines before acting. project_dir: absolute path of the project, only if Deputy picked the wrong folder.

Hand a well-specified coding task to Deputy. It reads and edits files and runs commands in the workspace on its own, then returns a short report with the files it changed. In accuracy mode, use this only when the user explicitly asks for delegation.

task: the goal, scope (files or folders), constraints and acceptance criteria. context: facts Deputy cannot discover itself (decisions made, conventions, error messages). thinking: "high" (default) or "max" for hard tasks. workdir: subfolder of the workspace to treat as the root (default: whole workspace). project_dir: absolute path of the project, only if Deputy picked the wrong folder.

Verify the result yourself before relying on it: review the changed files and run tests.

Show roughly how many tokens and how much money Deputy saved: this session, today, the last 7 days and all time. Makes no network calls.

Show Deputy's mode, model, thinking level, workspace, whether a key is set, and what this session has spent and saved. Makes no network calls to the model provider.