Topic starter
25/10/2026 11:11 am
TL;DR: Prompt-only routing can look efficient while missing the sessions that turn long, expensive, and operationally messy, Archestra argues from its analysis of text-only routing for coding agents. Routing based only on the opening prompt leaves later rework, cache effects, and human cleanup outside the decision that chose the model.
Editorial analysis by NHI Mgmt Group, based on content published by Archestra: “Routing coding agents is harder than it looks”.
Key questions
Q: Why can a cheaper model create higher total cost in a coding workflow?
A: A cheaper model can become more expensive when it produces long responses that expand the conversation history and raise input costs on later turns.
Q: How should teams decide when to hand work to a subagent?
A: Use a subagent only when the work is a closed stretch whose output can stand on its own and will not need heavy parent-context reasoning later.
Q: What breaks when coding-agent routing is based only on the opening prompt?
A: Prompt-only routing breaks when the task expands after the first turn, because the classifier never sees the repository, hidden dependencies, or later rework.
Practitioner guidance
- Map routing to task state, not just prompt text Require repository signals, change scope, and session history before a model tier is chosen for coding-agent work.
- Instrument session cost and context growth Track how quickly sessions expand after the first turn, and compare that to the model tier originally selected.
- Separate closed work from parent-context work Delegate only stretches that end in a self-contained result and do not need to be re-opened by the parent agent.
Bottom line: Prompt-only model routing can look efficient while still missing the sessions that become long, expensive, and operationally messy.
Glossary terms: Model Routing Layer, Context Carry, Third-party agent delegation, Routing Opacity
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
27/10/2026 7:17 pm
Text-only routing creates an identity-adjacent governance gap: when an AI coding agent is allowed to choose models from the prompt alone, the organisation is effectively delegating execution authority without seeing the full task state. That is a governance problem, not just a pricing problem, because the same session can cross from low-risk assistance into high-consequence code change, deployment, or cleanup work. The control weakness is the missing linkage between task scope, repository state, and delegated capability. Practitioners should treat routing decisions as part of the agent’s authority model, not as an isolated optimisation layer.
A few things that frame the scale:
- Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: Should organisations treat AI coding agents like privileged software identities?
A: Yes. If an AI agent can install code, access secrets, or modify repositories, it is functionally acting as a privileged non-human identity and should be governed that way. That means task-scoped access, explicit boundaries, and monitoring of its downstream actions, especially when it can touch build and release systems.
👉 Read our full editorial: Text-only routing underestimates coding agent cost and risk
This post was modified 7 days ago by NHI Mgmt Group