> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/ai-agents/run-agents-in-apps-workflows-and-tasks/how-agents-work.md).

# How Agents Work

Understand how Jetadmin Agents operate behind the scenes, breaking down the step-by-step reasoning cycle that drives their decision-making and actions.

**The Agent Process**

When an agent is triggered, it follows a structured reasoning cycle to complete its task:

**1. Task Input**\
The agent receives clear instructions in plain language—for example, *“Find all overdue invoices and email the client.”*

**2. Decision Making with LLM**\
The large language model determines the next step, which could be:

* Responding directly to the task,
* Asking for more information, or
* Activating a connected tool such as a data source, workflow, email, or even another agent.

**3. Tool Execution**\
The chosen tool performs its action, and the results are sent back to the LLM for further processing.

**4. Agentic Loop**\
This cycle of decisions and tool executions repeats until:

* The agent reaches its maximum allowed steps, or
* The LLM concludes that the task is complete.

Each complete cycle—from input to reasoning to output—is called a **run**.

{% hint style="info" %}
⚡ **Key Point:** The LLM’s role is limited to either calling tools repeatedly or providing the final response.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/ai-agents/run-agents-in-apps-workflows-and-tasks/how-agents-work.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.