Agent-like systems continue across steps toward a goal and may select tools or actions. The important questions are authority, state, observation, approval, failure, and recovery—not a human-sounding identity.
Plan for this page
Understand the idea, test it actively, then explain it in your own words.
You will leave with
distinguish model, chatbot, workflow, assistant, and agent-like behavior map goals, tools, state, permissions, approvals, monitoring, and recovery judge autonomy as a set of bounded design choices rather than one yes/no label
Time
30 min
Before you begin
AI from Zero is useful preparation, but it is not a locked prerequisite. Each unit states the concepts it uses.
Do this now
Read the outcomes and useful terms before the first section.
distinguish model, chatbot, workflow, assistant, and agent-like behavior
map goals, tools, state, permissions, approvals, monitoring, and recovery
judge autonomy as a set of bounded design choices rather than one yes/no label
Terms you will use
These definitions prepare you for the reading; you do not need to memorize them.Agent-like system
A system that continues across steps toward a goal, using state and potentially selecting tools or actions within an environment and control structure.
State
Information carried across steps, such as task status, observations, plans, memory, tool results, pending approvals, or external records.
Recovery
The ability to detect, stop, reverse, compensate for, or safely continue after failure, interruption, uncertainty, or changed conditions.
01
Interface does not determine agency
A chatbot may answer one message without continuing a task. A fixed workflow may execute several predetermined steps. An assistant may use tools only when explicitly directed. An agent-like system may choose among steps or tools as it pursues a goal and updates state.
These categories overlap and product labels vary. Describe observable continuation, choice, access, and control rather than assuming that conversation, a name, or marketing proves agency.
02
Autonomy has dimensions
A system may have freedom to plan but not to execute, read data but not write, act in a sandbox but not production, spend below a limit, or continue only until an approval point. Time, scope, recipient, environment, tool, and consequence can each be bounded.
Meaningful approval is placed before the consequential boundary, shows the proposed action and evidence, and cannot be bypassed by the same untrusted process. Logs and alerts must make relevant behavior observable without pretending every internal step is interpretable.
03
Agent reliability is system reliability
Longer tasks accumulate model error, stale state, tool failure, ambiguous goals, changed external conditions, duplicated actions, and coordination problems. Successful demos may not represent repeated operation under interruption and adversarial input.
Evaluate task success, unsafe action, unnecessary action, permission violation, recovery, cost, latency, human workload, and failure visibility. Test in bounded environments before expanding authority.
Interactive model
The CONTROL review
Selected layerC · Clear goal
Define success, prohibited outcomes, stopping conditions, and who owns the decision.
Read the complete text alternative
C · Clear goalDefine success, prohibited outcomes, stopping conditions, and who owns the decision.
O · Observations and stateSpecify what the system can read, remember, infer, update, and forget across steps.
N · Narrow tools and permissionsGrant only required tools, data, recipients, environments, amounts, and duration.
T · Threshold approvalsPlace human or deterministic checks before irreversible, costly, public, or sensitive action.
R · Records and monitoringLog proposals, calls, results, approvals, errors, and outcomes at a useful level.
O · Off-switch and recoveryStop, retry safely, roll back, compensate, notify, or hand over when conditions fail.
L · Learn from incidentsReview failures and near misses before changing prompts, models, tools, permissions, or process.
Misconception to correct
“A system is an agent if it has a name, avatar, and conversational interface.”
Agent-like behavior concerns goal-directed continuation, state, tool or action choice, environment, permissions, and control. Presentation alone proves none of them.
Active checks
Decide, then compare the reasoning
No grade, score, or streak. Progress records completed learning objects, not your worth or ability.01
A system receives a travel goal, searches options, maintains a shortlist, and can book only after approval. What makes it agent-like?
02
A drafting agent works well in a sandbox. What justifies access to production publishing?
Explain back and transfer
Run an agent-control review
Choose an agent-like workflow. Map goal, state, observations, tools, permissions, approval thresholds, records, failure modes, stop conditions, recovery, and owner.
Answer both checks before completing.
Source context
What supports this unit and where it stops
Evidence status: emerging
Artificial Intelligence Risk Management Framework (AI RMF 1.0)U.S. National Institute of Standards and Technology
Lifecycle and risk-management structure applicable to agentic systems; it does not supply one final definition of agent or validate a specific product.
inAi product thesis about goals, tools, state, control and recovery; clearly an inAi perspective rather than independent evidence of market-wide outcomes.
inAi