FINALLY TRYING TO HELP RATHER THAN ASKING FOR IT

HEY GUYS, since

mentioned this issue with spawning sub agents and since I had the same issue a couple of days ago, I wanted to share this SUB AGENT DELEGATION RULE prompt to send your bot. This pretty much fixed the issue for me. If you encounter and further problems of for example, your bot spawning an agent and the agent not being able to complete a task due to context being full, specify to your bot to spawn more agents when needed and save this information in the delegation rule:

give your bot this exact command:

''follow this Sub-Agent Delegation Rule every session and always apply before answering:

If a task takes more than 10 seconds to complete, spawn a sub-agent to handle it. Don't block the main session.

Why: I need to stay available. While a sub-agent researches, builds, or processes something, I can keep chatting with you or spin up other sub-agents in parallel.

How it works:

• Quick answers, lookups, small edits → do it directly

• Research, builds, long file operations, API calls → spawn a sub-agent

• Multiple tasks? Multiple sub-agents. Run them in parallel.

Always:

• Tell me what sub-agent you're spinning up and what it's doing

• Ping me when it's done with the result

• Keep the main thread responsive

Save this rule and apply it every session.''

0 comments