What Is Intent-Based Computing for Agents?
Intent-based computing is a model where a caller states the outcome it wants — "book a room under $200 near the venue" — and a system resolves the steps, rather than scripting each call itself. For agents it is foundational: an agent is handed an intent, decomposes it into capabilities to invoke, and reports back against the stated goal. The intent is the contract; the execution path is the agent’s to choose and the human’s to audit.
Why agents need it
An agent that must be told every step is a macro, not an agent. Intent-based computing is what lets a caller delegate judgement: say what success is, cap what may be spent and touched, and let the agent find a path. The value and the risk are the same property — latitude — which is why the policy plane and the record matter more here than anywhere else.
Intent is not a prompt
A prompt is free text a model interprets. An intent is a structured, bounded statement of an outcome that an agent resolves against real capabilities and a real policy, producing an auditable trail. Treating the two as the same thing is how an agent ends up acting on a sentence nobody can later reconstruct.
Questions
Is intent-based computing new?
The idea predates agents — networking used "intent-based" for declarative configuration. Agents make it general: any outcome, resolved by a reasoning system under policy.
Who is accountable for how an intent is resolved?
The human the agent acts for. The intent bounds what is allowed; the record shows the path taken, so a resolution can be reviewed after the fact.
Where this lives in the estate
FlashyOS — how intent is carried and bounded on the mesh
Keep reading
By Michael Gord · published 2026-10-04 · part of the Agentic Encyclopedia. Dates are the day of publication; events are cited at their own dates.