ProblemUsing the Bot as the thing that does deep production work gets weak results at high cost.
TechniqueLet the Bot notice work needs doing, gather context, stage the prompt, take your approval, fire a specialist system (a cloud coding agent, a research tool, a script it wrote earlier), then verify the result and report back.
Why it worksCoding tools are the inner loop and the outer loop is chat; the Bot is a weak production coder relative to dedicated coding agents, so this is correct allocation rather than modesty.
When to useAnything token-heavy, anything that loops, anything that builds software.
When not toTasks that genuinely require driving a GUI, which is what the Bot is uniquely for.