conon.ai

conon.ai/Tips

Send Noisy Research To A Subagent

Any side-investigation that would flood your session — 'which of these fifty files mentions the old pricing?' — goes to a subagent. It reads everything inside its own separate memory and returns three lines; your session's context stays clean for the actual work.

AdvancedAGENTSClaude Code

Why it works

Some questions are cheap to ask and expensive to host: 'which of these fifty files mentions the old pricing?' floods your session with fifty files' worth of context that outlives the answer. A subagent runs the investigation in its OWN separate memory and returns three lines; your session keeps the conclusion and none of the reading.

How to do it

  1. Spot the pattern: a side-question whose ANSWER is small but whose research is large.
  2. Phrase the delegation: 'use a subagent to investigate X and report back briefly.'
  3. Specify the return shape: 'a list of affected files and one line on what each needs.'
  4. The subagent reads the pile in its own context; your window stays clean.
  5. Receive the summary; act on it in your main session.
  6. Chain them for breadth: 'one subagent per directory, then combine their findings.'

Copy this

prompt
Use a subagent to investigate which files in this project still reference the old pricing. I want back only: the file list, one line each on what needs changing. Don't paste file contents here.

What to watch for

  • Without a return-shape instruction, some subagents report like enthusiastic interns — pages of process. The 'report back only X' clause is load-bearing.
  • Don't subagent the MAIN task — delegation is for side-research; the work you're actually steering belongs where you can steer it.

Sources

Original: conon.aiDocumentation: code.claude.com

Read next

We build and operate the systems behind tips like this one — agents, automations and internal tools, shipped into production. See what the studio does →