> For the complete documentation index, see [llms.txt](https://docs.tidelight.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tidelight.app/see-the-signal-between-sessions-12.md).

# See the signal between sessions

Account, research, and data-source details in one place.

## Appearance

### Your desk, your light.

Choose a palette that feels right. Your choice is saved on this device.

**Choose a color theme**

* **Daylight** — Warm paper, clear ink
* **Night Tide** — The original deep sea ✓
* **Blue Hour** — A cooler evening desk

## Account

### Your workspace

You’re browsing as a guest. Sign in to save preferences and keep your research private across sessions.

[Sign in ↗](/see-the-signal-between-sessions-11.md)

## AI Providers

### Research synthesis

Tidelight uses Bitget’s Qwen gateway with Gemini as a fallback to draft source-bounded research. Provider responses must pass the research workflow’s evidence checks before they can inform a decision.

| Provider            | Status         |
| ------------------- | -------------- |
| Bitget Qwen gateway | **CONFIGURED** |
| Google Gemini       | **CONFIGURED** |

| Setting      | Value                     |
| ------------ | ------------------------- |
| QWEN MODEL   | **qwen3.8-max**           |
| GEMINI MODEL | **gemini-3.5-flash-lite** |

{% hint style="info" %}
Configuration does not confirm provider access, model availability, or quota. Sign in to check each provider’s current response.
{% endhint %}

## Bitget Execution Controls

### You confirm every order.

Connect a dedicated Bitget demo or live account in the trading desk. Credentials are encrypted on the server and are not returned to your browser. Tidelight checks trade read access before saving a connection; Bitget checks order permissions when you confirm an order.

| Control                   | Status                    |
| ------------------------- | ------------------------- |
| Secure connection storage | **CONFIGURED**            |
| Demo and live spot orders | **VERIFICATION REQUIRED** |

Orders are limited to verified Reality stock tokens, 250 USDT in estimated value, and 5 attempts per hour. Live orders require explicit confirmation and an authenticator check. Nightwatch automation remains paper-only.

[Manage your Bitget connection ↗](/see-the-signal-between-sessions-5.md)

[Review paper agent controls ↗](/see-the-signal-between-sessions-8.md)

## Data & Privacy

### Your research stays yours.

Saved research is attached to your Supabase account. Database row-level security prevents signed-in users from reading each other’s notes and watchlists.

[Open your private briefs ↗](/see-the-signal-between-sessions-9.md)

[Manage your watchlist ↗](/see-the-signal-between-sessions-7.md)

Market views use public Bitget prices and candle history. Briefs use the source passages you provide.


---

# 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.tidelight.app/see-the-signal-between-sessions-12.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.