Stop being the human router
By Soumen Sarkar · October 2026
Problem. "I'm the human router. Sessions stop to ask, and the questions wait for me."
You become the human router when every unclear point in every session waits for you. Have agents state an assumption and keep going, send each assumption to the person who knows, and keep for yourself only the calls that are yours: about ten minutes a day.
What does being the human router feel like?
You lead a team where everyone runs two or three Claude Code sessions. Each session is quick and capable, and each one meets things it can't know from the code: which plan a discount applies to, whether an old endpoint still has callers, what product meant by "archived". So it stops and asks. The question lands with whoever started the session, and very often they pass it to you.
By lunch you've answered a dozen questions, half of them about parts of the product other people know better. You've written no code, and the sessions that waited for you did nothing in the meantime. That's the router's day: every piece of context travels through one person.
Why does it happen now?
Because the agents are good at asking. A clarifying question in Claude Code is a real pause: the Agent SDK docs say a question "pauses execution until you return a response", and that the wait "can stay pending indefinitely". That is the right behaviour for one person working with one agent, for example in plan mode, while gathering requirements.
On a team it adds up differently. Ten sessions each asking a fair question means ten pauses, and the answers sit in a few heads. Nothing is wrong with the agents. What breaks is the path between the question and the person who knows.
What do teams do about it?
Three changes take the lead out of the middle:
- Assumptions instead of questions. When something is unclear, the agent writes down what it is assuming and why, and keeps working. Nothing waits. The assumption stays visible until someone confirms or corrects it. See should an AI coding agent assume or ask?
- Routing to the person who knows. A billing assumption goes to whoever made the billing calls, not to the lead by default. Assumptions where a wrong guess costs most go first (a high-stakes assumption).
- Corrections that reach the agent. An answer is only useful if the session that made the assumption hears it, and later sessions in that area hear it too.
We work this way ourselves. The instructions in this repository tell every session: "Turn unknowns into calls: when something is unclear, `stateassumption` with what you're assuming and keep going. Corrections arrive at a later turn."_
What does Campfyrr do, and what doesn't it do?
Campfyrr gives Claude Code sessions a way to state an assumption and keep going. Before it routes one, it checks whether the team's record already answers it. If not, it sends the assumption to the author of the closest matching team decision or rule. Failing that, it goes to the last other person who worked in that part of the code, and otherwise to the team. Anyone can pass one on if it isn't theirs.
Each assumption has its own page, so the person who knows can keep it, pick an answer, correct it or pass it on from a link. The answer reaches the session at its next turn.
What it doesn't do: it doesn't make the call for you, and it doesn't replace your tracker or your planning. When nobody has worked in an area yet, the assumption goes to the whole team, and someone still has to pick it up.
What are a lead's ten minutes a day?
Once questions stop arriving one by one, the lead's part fits in one sitting:
- Open the team's Activity page each morning.
- Confirm or correct the assumptions routed to you.
- Settle any clash between two decisions.
- Read what landed since yesterday.
The rest of the day is yours. For more on the morning view, see what should an engineering lead look at each day?
Where should you start?
- Read how do I stop being the human router? for the short version.
- Give your agents the instruction to state assumptions. The playbook for agents that state assumptions has the wording.
- Install Campfyrr from /connect and invite one teammate, so routing has somewhere to go.
The principle behind all of it is turn unknowns into calls.
Everything on this problem
- For you: For engineering leads running a team on Claude Code: If you lead a team on Claude Code, you are probably the router: sessions don't know about each other, questions wait for you, and pull requests arrive without their reasons. Campfyrr briefs every session, routes assumptions to the person who knows, and puts reasons on every change. A team can set it up in about an hour.
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).