Agents & tools · Glossary term
What is Termination Condition?
An explicit rule that ends or pauses an agent run when it succeeds, fails, exhausts a budget, reaches a safe boundary, or requires escalation.
Why does Termination Condition matter?
Without a termination condition, an agent can loop, repeat side effects, waste budget, or claim completion without satisfying the goal.
Termination Condition in practice
Define success evidence, maximum steps and cost, non-retryable errors, and escalation states before starting the loop.
What is the common confusion about Termination Condition?
A stop sequence ends text generation; a termination condition decides whether the task or workflow should stop.
Learn Termination Condition in the course
No lesson links to this term yet. Search the course catalog for it.
Related terms
- Agent HarnessThe runtime around a model that assembles context, exposes tools, manages state, enforces limits, records traces, and decides when the…
- Token BudgetAn explicit allocation of token capacity across instructions, evidence, history, tool results, reasoning or working space, and output.
- Verification GateA control point that blocks progress until defined evidence satisfies a correctness or quality criterion.
- Stop SequenceAn application-specified token or text pattern that causes generation to stop when the decoding system encounters it.
Sources
More terms in Agents & tools
- Agent
- Agent Harness
- Agent Memory
- Agent State
- Agent Skill
- Approval Gate
- Checkpoint
- Compensating Action
- Delegation
- Durable Execution
- Function Calling
- Human-in-the-Loop (HITL)
- MCP (Model Context Protocol)
- Multi Round-Trip Request (MRTR)
- Orchestration
- Planning
- ReAct
- Sandbox
- Skill Bundle
- Skill Catalog
- Skill Discovery
- Skill Invocation
- Stateless MCP
- Structured Output
- Swarm
- Tool Contract
This entry comes from glossary/terms.md on GitHub. Browse all 250 glossary terms.