autourgos-agent

A self-contained general-purpose LLM agent for the Autourgos framework.

The agent alternates between Thought (reasoning about what to do next) and Action (calling a tool), looping until it has enough information to give a Final Answer.

Fully self-contained — no third-party dependencies beyond Python 3.10+ (only autourgos-core, itself a zero-dependency stdlib utility library shared across the framework). Plug in any LLM wrapper you already have.

---

Why use this?

Almost every major LLM provider today exposes an OpenAI-compatible API. autourgos-agent was designed with this in mind — it works with any LLM that has .invoke() and .ainvoke() methods. One agent, any provider:

Provider	Notes
OpenAI	gpt-4o, gpt-4o-mini, ...
Groq	Llama 3, Mixtral, Gemma
Together AI	100+ open-source models
Mistral AI	mistral-large, codestral
DeepSeek	deepseek-chat, deepseek-reasoner
Perplexity	sonar — web-connected
Ollama	local models, no internet
LM Studio	local models, GUI-based
vLLM	self-hosted, high throughput

You are not locked to a single provider.

What does it do?

The agent receives a task and a list of tools. It then iterates:

1. Think — what information do I need? which tool should I call?
2. Act — call the tool, get the result
3. Observe — add the result to the scratchpad, repeat

This continues until the agent has a final answer or hits the iteration/time limit.

---

Table of Contents

• Install
• Quick Start
• How the agent Loop Works
• Defining Tools
• Works With Any LLM
• Async Agent
• Parallel Tool Calls
• Native Tool Calling
• Verbose Mode
• Memory
• Approval Callback
• Middleware / Callbacks
  • Middleware Integration Contract
• Testing
• Context Manager
• Time and Iteration Limits
• Scratchpad Size Limits
• LLM Call Retries
• Custom System Prompt
• Constructor Reference
• Tool Dict Reference
• What the Agent Returns
• Error Tags
• v1 Backward Compatibility

---

Install

pip install autourgos-agent

No required third-party runtime dependencies (only autourgos-core, zero-dep itself). Bring your own LLM wrapper:

pip install autourgos-openaichat   # Chat Completions API
# or
pip install autourgos-responses    # OpenAI Responses API

Requires Python 3.10+.

---

Quick Start

from autourgos_agent import Agent, tool
from autourgos_openaichat  import OpenAIChatModel

# 1. Define a tool
@tool
def calculator(a: float, b: float) -> float:
    """Add two numbers together."""
    return a + b

# 2. Create the agent
agent = Agent(
    llm=OpenAIChatModel(model="gpt-4o"),
    verbose=True,
)
agent.add_tools(calculator)

# 3. Run
result = agent.invoke("What is 123 + 456?")
print(result)
# 579

(Prefer writing tools by hand instead? A plain dict — {"name", "description", "parameters", "func"} — still works exactly the same way; see Defining Tools below.)

Expected verbose output (LangChain-flavored Thought/Action/Observation trace):

> Starting Agent...

Thought: I need to add 123 and 456. I'll use the calculator tool.
Action: calculator
Action Input: {'a': 123, 'b': 456}
Observation: 579.0
Thought: I have the result from the calculator.
Final Answer: 123 + 456 = 579

> Agent finished.

(Shown here without colour; in a real terminal > Starting Agent..., > Agent finished., and Final Answer: print in bold green, Action: / Action Input: in yellow, Observation: in blue/cyan, Thought: in cyan, and Parse Error: in red.)

---

How the agent Loop Works

Each iteration the agent produces a JSON object:

{
  "thought": "I need to search for the latest Python version.",
  "actions": [
    {"action": "search", "action_input": {"query": "latest Python version 2025"}}
  ],
  "final_answer": null
}

Rules the LLM must follow (enforced by the prompt):

• If tools are needed → fill actions, set final_answer to null
• If the answer is ready → fill final_answer, set actions to []
• Never set both actions and final_answer at the same time
• Multiple tools can be called in one step if they are independent

The agent collects tool results into a scratchpad that is passed back to the LLM at each step so it always has full context of what was tried.

---

Defining Tools

There are two ways to define a tool. Both produce the same shape under the hood and can be freely mixed on the same agent.

Recommended: the @tool decorator

Decorate a type-hinted function and the name, description, and JSON-Schema parameters are inferred automatically — no dict to write by hand:

from autourgos_agent import tool

@tool
def get_weather(city: str, unit: str = "celsius") -> str:
    """Get the current weather for a city.

    Args:
        city: City name, e.g. Tokyo
        unit: celsius or fahrenheit
    """
    # Replace with real API call
    return f"The weather in {city} is 22°{unit[0].upper()} and sunny."

agent.add_tools(get_weather)

• name defaults to the function's name (override with @tool(name=...)).
• description defaults to the first line of the docstring (override with @tool(description=...)).
• parameters are inferred from type hints (str/int/float/bool/list/dict → the matching JSON-Schema type; parameters without a default are marked required). Per-parameter descriptions are parsed from a Google-style Args: section if present. Override entirely with @tool(parameters={...}) if you need something the inference can't express.
• The decorated function stays directly callable — get_weather("Tokyo") still works outside the agent, e.g. in your own tests.

# Overriding the inferred name/description:
@tool(name="calculator", description="Add two numbers together.")
def add(a: float, b: float) -> float:
    return a + b

Alternative: a plain dict

For full manual control (or if you're integrating an existing tool spec), a tool can still be a plain Python dict with these keys:

Key	Type	Required	Description
name	str	yes	Tool name (used by the LLM to call it)
description	str	yes	What the tool does — shown to the LLM
parameters	dict	recommended	JSON-Schema object describing the inputs
func	callable	yes	Python function to call

weather_tool = {
    "name": "get_weather",
    "description": "Get the current weather for a city.",
    "parameters": {
        "type": "object",
        "properties": {
            "city": {"type": "string",  "description": "City name, e.g. Tokyo"},
            "unit": {"type": "string",  "description": "celsius or fahrenheit"},
        },
        "required": ["city"],
    },
    "func": get_weather,
}

Duck-typed tool objects

A tool doesn't have to be a dict at all — any object exposing .name, .description, .parameters, and .func (or .function) as attributes instead of dict keys works the same way in both tool_calling_mode="prompt" and "native":

class WeatherTool:
    name = "get_weather"
    description = "Get the current weather for a city."
    parameters = {"type": "object", "properties": {"city": {"type": "string"}}, "required": ["city"]}
    func = staticmethod(get_weather)

agent.add_tools(WeatherTool())

Useful when wrapping an existing tool class from another library instead of reshaping it into a dict.

Adding tools

@tool-decorated functions and plain dicts both work the same way with add_tools / the constructor, and can be mixed freely:

# One at a time
agent.add_tools(get_weather)

# Multiple at once (mix @tool and dict tools freely)
agent.add_tools(get_weather, calculator_tool, search_tool)

# From a list
agent.add_tools([get_weather, calculator_tool])

# Via constructor
agent = Agent(llm=llm, tools=[get_weather, calculator_tool])

---

Works With Any LLM

Change the llm= argument to switch providers. Everything else stays the same.

OpenAI

from autourgos_openaichat import OpenAIChatModel

agent = Agent(llm=OpenAIChatModel(model="gpt-4o", api_key="sk-..."))

Groq (very fast, free tier)

from autourgos_openaichat import OpenAIChatModel

agent = Agent(
    llm=OpenAIChatModel(
        model="llama3-70b-8192",
        api_key="gsk_...",
        base_url="https://api.groq.com/openai/v1",
    )
)

Ollama (fully local, no internet, no API key)

ollama pull llama3

from autourgos_openaichat import OpenAIChatModel

agent = Agent(
    llm=OpenAIChatModel(
        model="llama3",
        api_key="ollama",
        base_url="http://localhost:11434/v1",
    )
)

Together AI

from autourgos_openaichat import OpenAIChatModel

agent = Agent(
    llm=OpenAIChatModel(
        model="meta-llama/Llama-3-70b-chat-hf",
        api_key="...",
        base_url="https://api.together.xyz/v1",
    )
)

Mistral AI

from autourgos_openaichat import OpenAIChatModel

agent = Agent(
    llm=OpenAIChatModel(
        model="mistral-large-latest",
        api_key="...",
        base_url="https://api.mistral.ai/v1",
    )
)

DeepSeek

from autourgos_openaichat import OpenAIChatModel

agent = Agent(
    llm=OpenAIChatModel(
        model="deepseek-chat",
        api_key="...",
        base_url="https://api.deepseek.com/v1",
    )
)

OpenAI Responses API (autourgos-responses)

from autourgos_responses import OpenAIResponse

agent = Agent(llm=OpenAIResponse(model="gpt-4o"))

LM Studio (local GUI)

from autourgos_openaichat import OpenAIChatModel

agent = Agent(
    llm=OpenAIChatModel(
        model="local-model",
        api_key="lm-studio",
        base_url="http://localhost:1234/v1",
    )
)

vLLM (self-hosted)

from autourgos_openaichat import OpenAIChatModel

agent = Agent(
    llm=OpenAIChatModel(
        model="meta-llama/Meta-Llama-3-8B-Instruct",
        api_key="EMPTY",
        base_url="http://your-server:8000/v1",
    )
)

---

Async Agent

All agent methods have an async counterpart.

import asyncio
from autourgos_agent import Agent
from autourgos_openaichat  import OpenAIChatModel

agent = Agent(llm=OpenAIChatModel(model="gpt-4o"))
agent.add_tools(weather_tool, calculator_tool)

async def main():
    result = await agent.ainvoke("What is the weather in Tokyo and what is 99 * 3?")
    print(result)
    # The weather in Tokyo is 22°C and sunny. 99 × 3 = 297.

asyncio.run(main())

Async tools (coroutine functions) are also supported:

import httpx

@tool
async def search(query: str) -> str:
    """Search the web."""
    async with httpx.AsyncClient() as client:
        r = await client.get(f"https://api.example.com/search?q={query}")
        return r.text
# async function — works with ainvoke(), same as a plain-dict "func" would.

---

Parallel Tool Calls

The LLM can call multiple tools in a single step when they don't depend on each other. The agent runs the approved ones concurrently (a ThreadPoolExecutor for invoke(), asyncio.gather for ainvoke()) and collects all results before the next LLM call. invoke()'s thread pool is capped at Agent.MAX_TOOL_WORKERS (default 8) regardless of how many tool calls the model requests in one step, so a step with more approved calls than that queues the rest rather than spawning one thread per call.

agent = Agent(llm=OpenAIChatModel(model="gpt-4o"))
agent.add_tools(weather_tool, calculator_tool, search_tool)

result = agent.invoke(
    "What is the weather in Paris and London, and what is 250 * 4?"
)
print(result)
# The weather in Paris is 18°C cloudy, London is 15°C rainy. 250 × 4 = 1000.

The LLM produces three tool calls in one step:

{
  "thought": "I can fetch both cities' weather and compute the multiplication in parallel.",
  "actions": [
    {"action": "get_weather", "action_input": {"city": "Paris"}},
    {"action": "get_weather", "action_input": {"city": "London"}},
    {"action": "calculator",  "action_input": {"a": 250, "b": 4}}
  ],
  "final_answer": null
}

For native structured tool-calling instead of JSON-in-text parsing, see Native Tool Calling below.

---

Native Tool Calling

tool_calling_mode="native" swaps the JSON-in-text agent loop for the LLM's own structured tool-calling — invoke_with_tools()/ainvoke_with_tools() on OpenAIChatModel/OpenAIResponse. No regex JSON parsing — tool calls come back as structured data straight from the API. Multiple tool calls in one turn run concurrently here too, the same way "prompt" mode does.

from autourgos_agent import Agent, tool
from autourgos_openaichat import OpenAIChatModel

@tool
def weather_tool(city: str) -> str:
    """Get the current weather for a city."""
    return f"{city}: 18°C, cloudy"

@tool
def calculator_tool(a: float, b: float) -> float:
    """Multiply two numbers."""
    return a * b

agent = Agent(
    llm=OpenAIChatModel(model="gpt-4o"),
    tool_calling_mode="native",
)
agent.add_tools(weather_tool, calculator_tool)

result = agent.invoke("What is the weather in Paris, and what is 250 * 4?")
print(result)

Requires the LLM to implement invoke_with_tools()/ainvoke_with_tools() — both OpenAIChatModel and OpenAIResponse do. Passing tool_calling_mode="native" with an LLM that doesn't (a plain duck-typed .invoke()-only object, or the default BaseLLM.invoke_with_tools() stub) raises a RuntimeError immediately, naming the LLM class and what's missing — it never silently falls back to prompt mode.

Trade-offs versus "prompt" mode (the default):

• More reliable: no AgentParseError from malformed JSON, since the API returns structured tool calls directly.
• No visible "Thought" per step: when the model also calls tools, the wrapper doesn't currently return accompanying reasoning text alongside the tool calls, so on_iteration/logger.thought() aren't fired on tool-call turns — only on the final answer.
• Conversation state is a real multi-turn message list, not the single rendered scratchpad string "prompt" mode uses. agent.scratchpad is still kept up to date as a human-readable trace (for middleware that reads it), but it isn't what's actually sent to the LLM in this mode.

---

Verbose Mode

Enable verbose=True to print every step to stdout.

agent = Agent(
    llm=OpenAIChatModel(model="gpt-4o"),
    verbose=True,
)
agent.add_tools(weather_tool)
result = agent.invoke("What is the weather in Sydney?")

Output (LangChain-flavored Thought/Action/Observation trace):

> Starting Agent...

Thought: I need to get the weather in Sydney using the get_weather tool.
Action: get_weather
Action Input: {'city': 'Sydney'}
Observation: The weather in Sydney is 25°C and sunny.
Thought: I have the weather information for Sydney.
Final Answer: The weather in Sydney is 25°C and sunny.

> Agent finished.

Enable full_output=True to also print the raw LLM JSON at each step — useful for debugging prompt or parse issues:

agent = Agent(llm=llm, verbose=True, full_output=True)

---

Memory

Attach a memory backend to persist conversation history across calls.

from autourgos_agent import Agent, MemoryProtocol
from typing import Dict, List

class SimpleMemory(MemoryProtocol):
    def __init__(self):
        self._history: List[Dict[str, str]] = []

    def add_user_message(self, message: str) -> None:
        self._history.append({"role": "user", "content": message})

    def add_assistant_message(self, message: str) -> None:
        self._history.append({"role": "assistant", "content": message})

    def get_history(self) -> List[Dict[str, str]]:
        return list(self._history)

memory = SimpleMemory()
agent  = Agent(llm=llm, memory=memory)
agent.add_tools(search_tool)

result1 = agent.invoke("Search for the capital of France.")
print(result1)
# The capital of France is Paris.

result2 = agent.invoke("What city did I just ask about?")
print(result2)
# You asked about Paris, the capital of France.

---

Approval Callback

Require human (or programmatic) approval before any tool is executed.

def require_approval(tool_name: str, tool_input: dict) -> bool:
    print(f"\n[Approval required] Tool: {tool_name}")
    print(f"Input: {tool_input}")
    answer = input("Allow? (y/n): ").strip().lower()
    return answer == "y"

agent = Agent(
    llm=OpenAIChatModel(model="gpt-4o"),
    approval_callback=require_approval,
)
agent.add_tools(delete_file_tool)
result = agent.invoke("Delete the temp folder.")

If the callback returns a falsy value, the tool is skipped and the agent sees:

Observation: Tool call was denied by the approval callback.

A denial still fires both on_tool_start and on_tool_end (with that same "denied by the approval callback" message as the result) — middleware that tracks tool calls by pairing start/end events sees a consistent pair either way, never a start with no matching end.

Use this to implement human-in-the-loop, audit logging, or safety checks for destructive tools.

approval_callback can also be an async def — ainvoke() awaits it if it returns an awaitable (e.g. to wait on a Slack approval), and a plain sync callback still works unchanged in both invoke() and ainvoke():

async def require_approval(tool_name: str, tool_input: dict) -> bool:
    return await ask_on_slack(tool_name, tool_input)

agent = Agent(llm=OpenAIChatModel(model="gpt-4o"), approval_callback=require_approval)
agent.add_tools(delete_file_tool)
result = await agent.ainvoke("Delete the temp folder.")

Note: invoke() (the sync entrypoint) only supports a sync approval_callback. Passing an async def callback to invoke() raises a TypeError right away (naming the problem and pointing at the fix) instead of silently approving every tool — call agent.ainvoke() instead, or use a plain sync callback.

---

Middleware / Callbacks

Register event hooks to observe the agent without modifying it. CallbackHandler exposes 11 hooks in total: on_agent_start, on_agent_end, on_agent_error, on_tool_start, on_tool_end, on_tool_error, on_iteration_start, on_before_iteration, on_iteration, on_llm_end, and on_parse_error. Every hook may receive an agent=<Agent instance> kwarg (older handlers that don't accept it still work).

from autourgos_agent import Agent, CallbackHandler

class MyLogger(CallbackHandler):

    def on_agent_start(self, query: str, **kwargs) -> None:
        print(f"Agent started with query: {query}")

    def on_agent_end(self, result: str, **kwargs) -> None:
        print(f"Agent finished: {result}")

    def on_tool_start(self, tool_name: str, tool_input: dict, **kwargs) -> None:
        print(f"Calling tool: {tool_name} with {tool_input}")

    def on_tool_end(self, tool_name: str, result: str, **kwargs) -> None:
        print(f"Tool {tool_name} returned: {result[:100]}")

    def on_iteration(self, iteration: int, thought: str, **kwargs) -> None:
        print(f"Iteration {iteration} — thought: {thought}")

    def on_parse_error(self, iteration: int, raw_response: str, **kwargs) -> None:
        print(f"Parse error at step {iteration}: {raw_response[:100]}")

    # Extra hooks (v1.1.0+) — all optional, all receive `agent=` too:
    def on_agent_error(self, error: Exception, **kwargs) -> None:
        print(f"Agent error: {error}")

    def on_tool_error(self, tool_name: str, error: Exception, **kwargs) -> None:
        print(f"Tool {tool_name} raised: {error}")

    def on_iteration_start(self, iteration: int, **kwargs) -> None:
        print(f"Starting iteration {iteration}")

    def on_llm_end(self, response, **kwargs) -> None:
        print(f"LLM responded: {str(response)[:100]}")
        # kwargs also carries raw=<untouched raw LLM response> plus, when the
        # wrapper exposes it: provider_used, input_tokens, output_tokens,
        # total_cost, latency_ms (autourgos-openaichat/-responses' dict shape)
        # or total_tokens (from a native SDK response's .usage) — useful for
        # cost/usage-tracking middleware without reaching into agent.llm.
        if "total_cost" in kwargs:
            print(f"  cost so far: ${kwargs['total_cost']}")


agent = Agent(llm=llm, middleware=[MyLogger()])
agent.add_tools(weather_tool)
result = agent.invoke("Weather in Berlin?")

You can also add middleware after construction:

agent.add_middleware(MyLogger())

Narrating middleware activity in the verbose trace

By default, verbose=True only shows the core loop (Thought/Action/Observation) -- middleware changing the agent's tools, scratchpad, or prompt behind the scenes is otherwise invisible. Middleware can narrate what it's doing into the same trace via agent.logger.middleware(source, message):

class MyLogger(CallbackHandler):
    def on_agent_start(self, query: str, agent=None, **kwargs) -> None:
        logger = getattr(agent, "logger", None)
        if logger:
            logger.middleware("MyLogger", "Doing something worth narrating.")

Printed in magenta with a [Source] prefix so it's unambiguous which middleware produced the line, e.g.:

[Toolbox] Exposed toolbox 'search_tools' to agent.
[Summarizer] Compressed scratchpad (iteration 5, was 15,320 chars).

Use getattr(agent, "logger", None) (not a direct import of AgentLogger) so your middleware doesn't crash if it's ever attached to something other than a Agent, and does nothing when verbose=False. The Autourgos middleware packages (autourgos-toolbox, autourgos-summarizer, autourgos-hcix, autourgos-preiteration) use this same pattern to narrate their own actions.

Middleware Integration Contract

These are the three pieces of surface area sibling middleware packages (autourgos-hcix, autourgos-summarizer, autourgos-preiteration, autourgos-toolbox, and anything else you write) can rely on. This is the official, stable contract — treat it as public API.

agent.scratchpad (str) A real, live instance attribute, not just a local loop variable. It is updated in place on every iteration of invoke()/ainvoke(), so a callback handler (or any other code holding a reference to the agent) can read it while the loop is still running, not only after it finishes. It's reset to "" at the start of every invoke()/ainvoke() call, so calling invoke() twice on the same agent instance never leaks the previous run's scratchpad into the new one.

class ScratchpadWatcher(CallbackHandler):
    def on_iteration_start(self, iteration, agent=None, **kwargs):
        print(f"[iter {iteration}] scratchpad so far:\n{agent.scratchpad}")

agent.current_query (str) Set once, at the start of every invoke()/ainvoke() call, to the query being worked on. Lets middleware answer "what is this agent doing right now?" without threading the query through every hook signature.

on_tool_start / on_tool_end are always paired Every on_tool_start for a given tool call is followed by exactly one on_tool_end for that same call — including when approval_callback denies it (see Approval Callback). Middleware that tracks in-flight tool calls (e.g. an "active calls" gauge, or a tracing span opened on start and closed on end) can rely on this pairing without special-casing denials.

on_before_iteration(iteration, agent=None, **kwargs) Called once per loop iteration, right before the LLM is invoked for that iteration. If a handler returns a dict, its keys are merged into the self.llm.invoke() / self.llm.ainvoke() call for that iteration only — it is not persisted to later iterations. If multiple handlers return dicts, later handlers win on key conflicts. Returning None (the default no-op, same as every other hook) changes nothing.

class TemperatureOverride(CallbackHandler):
    def on_before_iteration(self, iteration, agent=None, **kwargs):
        # only lower the temperature on the first iteration
        if iteration == 1:
            return {"temperature": 0.0}
        return None

This is how middleware can, for example, inject a trace id, override a sampling parameter, or attach per-call metadata without the agent needing to know anything about the specific middleware doing it.

Hooks may be sync or async, from either invoke() or ainvoke() Define a hook as a plain def or an async def — both work from both loops:

• From ainvoke() (the async loop), a sync hook runs on a background thread rather than the event-loop thread, so a blocking call inside it (an LLM request, a file write, time.sleep, anything) doesn't stall the loop for every other concurrent ainvoke() call sharing that thread. An async hook is awaited directly.
• From invoke() (the sync loop), a sync hook is called directly, same as always; an async hook is driven to completion with its own short-lived event loop.

class RemoteAudit(CallbackHandler):
    async def on_iteration_start(self, iteration, agent=None, **kwargs):
        await audit_client.log(agent.current_query, iteration)

You don't need to pick one style for a whole handler — different hooks on the same class can mix sync and async freely.

---

Testing

autourgos_agent.testing ships make_test_agent() — a shared test fixture that builds a real, fully-functional Agent wired to a scripted fake LLM, with zero network calls. Use it in your own tests instead of hand-rolling a fake agent (a hand-rolled fake's shape can silently drift from the real Agent and hide real bugs):

import json
from autourgos_agent.testing import make_test_agent

agent = make_test_agent(responses=[
    json.dumps({"thought": "thinking", "actions": [], "final_answer": "42"}),
])
result = agent.invoke("what is the answer?")
assert result == "42"
assert agent.llm.call_count == 1

make_test_agent() accepts responses (a list of raw JSON-text canned LLM replies in the {thought, actions, final_answer} format), and optional tools, memory, middleware, max_iterations, and any other Agent constructor kwarg. If tools is omitted, a harmless echo tool is attached automatically so agent.invoke() works out of the box.

---

Context Manager

The agent implements both sync and async context managers. They automatically close the LLM's HTTP client when the block exits.

with Agent(llm=OpenAIChatModel(model="gpt-4o")) as agent:
    agent.add_tools(calculator_tool)
    result = agent.invoke("What is 7 * 8?")
    print(result)
    # 56
# LLM client closed here

Async:

import asyncio
from autourgos_openaichat import OpenAIChatModel

async def main():
    async with Agent(llm=OpenAIChatModel(model="gpt-4o")) as agent:
        agent.add_tools(calculator_tool)
        result = await agent.ainvoke("What is 12 ** 2?")
        print(result)
        # 144

asyncio.run(main())

---

Time and Iteration Limits

Prevent runaway agents with hard limits.

agent = Agent(
    llm=OpenAIChatModel(model="gpt-4o"),
    max_iterations=10,       # stop after 10 Thought → Action → Observe cycles
    max_execution_time=30.0, # stop after 30 seconds wall-clock time
)
agent.add_tools(search_tool)

try:
    result = agent.invoke("Research the entire history of the internet.")
except AgentTimeoutError:
    ...  # 30s wall-clock elapsed without a final answer
except AgentMaxIterationsError:
    ...  # 10 iterations elapsed without a final answer

You can also override max_iterations per call:

result = agent.invoke("Quick question: capital of Japan?", max_iterations=3)

max_execution_time alone can't stop a single tool call from hanging forever — it's only checked between iterations, not while a tool call is in flight. Use tool_timeout for that:

agent = Agent(
    llm=OpenAIChatModel(model="gpt-4o"),
    tool_timeout=10.0,  # abandon any single tool call that runs past 10s
)
agent.add_tools(flaky_network_tool)

result = agent.invoke("Fetch the data and summarize it.")
# If flaky_network_tool hangs, its Observation becomes:
# "Error: tool 'flaky_network_tool' timed out after 10.0s."
# instead of blocking the agent loop forever.

A timed-out sync tool's underlying thread keeps running in the background (Python has no way to force-stop a running thread) — the agent loop itself just stops waiting on it. An async tool is actually cancelled at its next await point. tool_timeout=None (the default) disables this and matches prior behavior.

---

Scratchpad Size Limits

The scratchpad (agent.scratchpad, "prompt" mode only) is capped at Agent.MAX_SCRATCHPAD_CHARS (15,000 characters) by default — once exceeded, older steps are trimmed from the front and replaced with "[...earlier steps trimmed...]".

Character count alone is a poor proxy for what actually overflows an LLM's context window: tokens per character varies a lot by language and content (dense non-English text or code can run well under the ~4 chars/token rule of thumb, silently blowing a char-only budget's whole point long before 15,000 characters is reached). max_scratchpad_tokens adds a second, token-based cap on top of the character one:

agent = Agent(
    llm=OpenAIChatModel(model="gpt-4o"),
    max_scratchpad_tokens=4000,  # trim further if the scratchpad exceeds ~4000 tokens
)

Without a real tokenizer, token count is approximated as len(text) // 4 (the common English-prose rule of thumb). Pass token_counter= for precision — any fn(text: str) -> int, e.g.:

import tiktoken

encoding = tiktoken.encoding_for_model("gpt-4o")

agent = Agent(
    llm=OpenAIChatModel(model="gpt-4o"),
    max_scratchpad_tokens=4000,
    token_counter=lambda text: len(encoding.encode(text)),
)

max_scratchpad_tokens=None (the default) disables the token-based check — only the character cap applies, matching prior behavior.

---

LLM Call Retries

By default, any failed LLM call (rate limit, network blip, transient 5xx) raises AgentLLMError immediately and ends the run — the same call would often succeed a moment later. llm_retries retries with exponential backoff instead:

agent = Agent(
    llm=OpenAIChatModel(model="gpt-4o"),
    llm_retries=3,             # retry up to 3 times before giving up
    llm_retry_backoff=1.0,     # base delay: 1s, 2s, 4s (capped below)
    llm_retry_max_backoff=30.0,
)
agent.add_tools(search_tool)

result = agent.invoke("What's the latest news?")
# A rate-limited call now retries instead of failing the whole run outright.

By default every exception is retried except NotImplementedError (the signal that tool_calling_mode="native" isn't supported by this LLM at all — a config error, not a transient one, so retrying it would just delay the clearer error). Pass llm_retry_on to customize which errors are worth retrying:

def only_rate_limits(exc: Exception) -> bool:
    return "rate limit" in str(exc).lower()

agent = Agent(llm=llm, llm_retries=5, llm_retry_on=only_rate_limits)

llm_retries=0 (the default) disables this and matches prior behavior — a single unconditional call, raising AgentLLMError on the first failure.

---

Custom System Prompt

Add extra instructions that persist across all steps.

agent = Agent(
    llm=OpenAIChatModel(model="gpt-4o"),
    system_prompt=(
        "You are a helpful financial analyst. "
        "Always cite your sources. "
        "Never speculate without data."
    ),
)
agent.add_tools(search_tool, calculator_tool)
result = agent.invoke("What is the P/E ratio of Apple?")

---

Constructor Reference

Parameter	Type	Default	Description
llm	any	None	LLM wrapper with .invoke() / .ainvoke(). Works with OpenAIChatModel, OpenAIResponse, or any compatible object
verbose	bool	False	Print step-by-step execution to stdout
full_output	bool	False	Also print raw LLM responses (implies verbose)
memory	MemoryProtocol	None	Memory backend for conversation history
max_iterations	int	15	Max Thought → Action → Observe cycles before stopping
max_execution_time	float	None	Wall-clock time limit in seconds
tool_timeout	float	None	Per-tool-call timeout in seconds. See Time and Iteration Limits
max_scratchpad_tokens	int	None	Extra token-based scratchpad budget on top of MAX_SCRATCHPAD_CHARS. See Scratchpad Size Limits
token_counter	callable	None	fn(text) -> int used to count tokens for max_scratchpad_tokens. Defaults to a len(text) // 4 approximation
llm_retries	int	0	Retries on a failed LLM call before raising AgentLLMError. See LLM Call Retries
llm_retry_backoff	float	1.0	Base delay in seconds between retries (exponential: backoff * 2**attempt)
llm_retry_max_backoff	float	30.0	Upper bound in seconds on the exponential backoff delay
llm_retry_on	callable	None	fn(exc) -> bool deciding whether a failure is worth retrying. Defaults to retrying everything except NotImplementedError
approval_callback	callable	None	Called as fn(tool_name, tool_input) before each tool. Return truthy to allow
middleware	list[CallbackHandler]	None	Event hooks for lifecycle events
max_consecutive_parse_errors	int	3	Stop after this many back-to-back JSON parse failures
tools	list[dict]	None	Initial tool list (more can be added with add_tools())
system_prompt	str	""	Extra system-level instruction added to every prompt
tool_calling_mode	"prompt" | "native"	"prompt"	"prompt": the original JSON-in-text agent loop. "native": uses the LLM's invoke_with_tools()/ainvoke_with_tools() — structured tool calls straight from the API, no JSON parsing, and multiple tool calls in one turn run concurrently. See Native Tool Calling

---

Tool Dict Reference

Key	Type	Required	Description
name	str	yes	Identifier used by the LLM. Use snake_case
description	str	yes	Plain-English description of what the tool does and when to use it
parameters	dict	recommended	JSON-Schema object describing the function's inputs
func	callable	yes	The Python function to call. Can be sync or async

parameters format (JSON Schema):

"parameters": {
    "type": "object",
    "properties": {
        "param_name": {
            "type": "string",       # string | number | integer | boolean | array | object
            "description": "...",   # shown to the LLM — make it clear
            "enum": ["a", "b"],     # optional: restrict to specific values
        },
    },
    "required": ["param_name"],     # list required params
}

---

What the Agent Returns

• Normal completion — invoke()/ainvoke() return a str: the final answer extracted from the LLM's final_answer field
• Error / limit reached — raises one of the exceptions below instead of returning a string, so callers catch a type rather than string-sniffing the result

---

Exceptions

All of these are exported from autourgos_agent and subclass AgentError:

Exception	Meaning
AgentTimeoutError	max_execution_time was exceeded
AgentMaxIterationsError	max_iterations reached without a final answer
AgentParseError	tool_calling_mode="prompt": LLM failed to produce valid JSON max_consecutive_parse_errors times in a row
AgentEmptyResponseError	tool_calling_mode="native": LLM returned neither a final answer nor tool calls max_consecutive_parse_errors times in a row
AgentLLMError	LLM raised an exception (network, rate limit, etc.) — the original exception is on .original

from autourgos_agent import Agent, AgentError, AgentTimeoutError

try:
    result = agent.invoke("...")
except AgentTimeoutError:
    ...
except AgentError:
    ...  # catches any of the above

---

v1 Backward Compatibility

The old Create_Agent factory function still works but emits a DeprecationWarning:

from autourgos_agent import Create_Agent  # DeprecationWarning

agent = Create_Agent(llm=llm)  # same as Agent(llm=llm)

Update your code to use Agent directly.

---

License

Apache License 2.0, Copyright (c) 2026 Jitin Kumar Sengar