> For the complete documentation index, see [llms.txt](https://docs.vibetrading.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vibetrading.dev/application-example/how-it-works.md).

# VibeAgent

Vibe is a **multi-agent trading system** that autonomously trades using **multiple signal channels**, while keeping execution and risk controls in your hands.

At a high level:

* **Signal Agents** continuously collect and interpret market signals from different channels
  * Today: **News** + **Whale activity**
  * Future: easily extendable to more channels (e.g., macro, funding, volatility, social, technicals)
* A **Portfolio Agent** acts as the “control layer”
  * fuses signals across channels
  * produces a clear per-asset intent (e.g., buy/sell/hold/watch)
  * keeps decisions consistent across the portfolio
* Your **Quant Program** is the execution and risk layer
  * defines **TP / SL**, sizing, exposure limits, and other risk rules
  * executes trades based on the Portfolio Agent’s intent, within your constraints

***

## End-to-End Flow

{% @mermaid/diagram content="flowchart TD
%% Top: Signal layer
subgraph SA\["Signal Agents"]
direction LR
N\["News Agent"]
W\["Whale Agent"]
F\["Future Agents<br/>(Extensible)"]
end

%% Middle: Decision layer
P\["Portfolio Agent<br/>(Signal Fusion & Control)"]

%% Bottom: Execution layer
subgraph EL
direction LR
Q\["Quant Program<br/>(TP/SL, Risk Rules)"]
X\["Exchange Execution"]
end

N --> P
W --> P
F --> P

P --> Q --> X" %}


---

# 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.vibetrading.dev/application-example/how-it-works.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.