> For the complete documentation index, see [llms.txt](https://docs.trover.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trover.tech/using-trover/chat-with-the-trover-agent.md).

# chat with the trover agent

## chat with the trover agent

the agent lives in the bottom corner of the trover web app. you can use it for product help without connecting, but onchain actions require an authenticated trover profile.

### what you can ask

* how to connect an x account or wallet
* how wallet modes and safety controls work
* how to format a stock-token trade
* how to prepare a relay bridge
* general questions about robinhood chain and trover

### sending an action

the agent recognizes supported trade and bridge commands. after parsing, it sends the structured request to the same policy and execution queues used by the x agent.

good requests are short and complete:

```
buy $AAPL with 25 USDG
bridge 20 USDC from base to robinhood chain
```

the reply tells you whether the action was understood and queued. track the resulting request from the relevant account or bridge view.

{% hint style="warning" %}
the chat reply is not a transaction receipt. wait for the intent and onchain status before treating an action as complete.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.trover.tech/using-trover/chat-with-the-trover-agent.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
