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

# Limitations

Explicit list of what Thesium does not do today. Some of these may shift over time; the current state is documented honestly.

## The extension does not

* **Execute trades.** There is no buy or sell button. Trades happen in the terminal.
* **Connect to wallets.** There is no wallet integration. The extension is read-only with respect to user funds.
* **Predict prices.** Conviction is a signal-stack confidence reading, not a price forecast.
* **Cover NFTs.** Fungible tokens only.
* **Cover pre-launch tokens.** If a token has not yet been indexed by the backend's on-chain layer (typical for the first seconds after deploy), the panel renders without on-chain data until the address propagates. Most tokens become available within seconds; some scam launches that get filtered at the indexer never appear.
* **Run outside Chromium-with-sidePanel.** Firefox / Safari support is on the roadmap.
* **Run on mobile.** Chrome on mobile does not support extensions in the same way. Mobile companion is on the roadmap.
* **Sync across devices.** A user's recently-viewed tokens on their laptop are not visible on their desktop. Future feature.
* **Customize panels.** Five tabs, fixed order. Reordering and column customization are future work.

## The data layer does not

* **Cover every chain equally.** See the chain matrix in Supported Chains.
* **Cover every wallet.** The wallet graph is the wallets we track. Wallets outside the graph do not appear in Holders or KOLs, no matter how large or notable.
* **Resolve identity for anonymous smart money.** Smart-money wallets are surfaced by behavior, but if a wallet is not publicly attributable, we show it as anonymous Smart Money tier, not as a named identity we have not earned.
* **Provide historical data depth.** The panels reflect current state and recent windows, not full historical analytics.

## The AI layer does not

* **Hallucinate price targets.** The system prompt is explicit on this; the validator rejects outputs that contain numeric price predictions.
* **Take macro context.** If BTC drops 10%, the conviction on a single memecoin does not automatically reflect that. The model evaluates the token's own footprint.
* **Adapt to your portfolio.** It does not know what else you hold. It does not optimize against your existing exposure.

## The audit layer does not

* **Cover non-EVM chains.** Solana, Tron and others do not have audit support today.
* **Guarantee safety.** A "safe" verdict means the simulation passed; a contract that is safe today can still be drained tomorrow if it was already deployed with backdoors that simply weren't triggered by the simulation.
* **Replace the rest of your diligence.** A green audit is a green light to *consider* the trade, not a recommendation to take it.

These are choices, not bugs. The product is research on a specific token, not portfolio management.


---

# 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://thesium.gitbook.io/thesium-docs/transparency/limitations.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.