> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/run-operations/agent/agent-context.md).

# Agent context and tools

Understand the main sources and capabilities the Agent can use during a task.

The Agent is useful because it can work with more than the conversation itself.

Depending on the Project and your access, it can use:

* **Project instructions** — durable direction about the operational area and general behaviour;
* **Skills** — reusable ways of doing recurring work;
* **Files** — task inputs, evidence and outputs;
* **Connected systems** — authorised access to ERP, CRM, email and other systems;
* **Knowledge** — maintained reference material;
* **Tables** — maintained structured data and mappings;
* **Memory** — useful context carried across sessions;
* **Workflows** — repeatable execution for stable parts of a process.

Lleverage can also provide built-in Skills and general industry or process knowledge as a starting point.

## Available does not mean authoritative

Different sources play different roles.

A current ERP record, approved policy or maintained customer-specific mapping can be authoritative. A remembered preference, uploaded case file, general industry pattern or Agent inference can still be useful without having the same status.

When the distinction matters, tell the Agent which source should win and what to do when sources disagree.

## Scope matters

In a web Agent session, the current Project is explicit.

Slack and Microsoft Teams can also run without one fixed Project. In that case, the Agent only uses eligible capabilities from Projects the acting user is authorised to access.

Pin a channel conversation when the work should clearly stay inside one Project or when several Projects have overlapping capabilities.

## What the session shows

The session's Context and Memory views help you inspect supporting material around the work.

Treat those views as evidence, not a complete ledger of everything that influenced the result. A tool being visible does not make its data authoritative, and an empty panel is not proof that no capability contributed.

For important work, verify against the system, document or maintained source that should own the fact.

Use the pages below when you want to understand one capability in more detail. Builders who need to configure these sources should continue to [Build and improve](/build-and-improve/overview.md) or [Control](/administer-and-govern/control.md).


---

# 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.lleverage.ai/run-operations/agent/agent-context.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.