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

# Dashboard

The dashboard is the landing view for the terminal.

It gives users a fast read on what matters without forcing them directly into a random token page. The dashboard combines confluence, setup ideas, market context, and tracking tools.

## How To Use It

Start with the dashboard when you want a broad read.

Look for tokens that appear in confluence or setup sections, then open the token page for the detailed read. The dashboard is for triage. The token page is for judgment.

## Key Sections

**Trending Confluence** shows tokens where tracked-wallet attention passed the display policy.

**Idea Setups** shows tokens with market structures that may be worth reviewing.

**Birdeye Momentum** adds broader market discovery context.

**Tools** include watchlist and public wallet tracking surfaces.

The dashboard is meant for scanning. Token-level detail belongs on the token page.


---

# 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://dopameme.gitbook.io/docs/using-dopameme/dashboard.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.