# Atlas Documentation

This is the complete Atlas documentation (chat apps, REST API, command line, and dashboard) as one Markdown file made for AI assistants to read.

Source: https://www.mind-vest.io/atlas/setup-guide

## If you are an AI assistant and Atlas says `not_signed_in`

You are allowed to fix this, and you should offer to. You never handle the
person's password: you give them a link, they sign in or create an account
themselves, and you carry on.

Check one thing first: **can you save a token somewhere that outlives this
conversation** (a config file, a keychain, a database row, an environment
variable you control)? Your context window does not count.

- **Yes.** POST `https://atlasmcp.finmanagerai.com/oauth/device_authorization`,
  give the person the `verification_uri_complete` it returns, then poll
  `/oauth/token` until you get an `access_token`. Save it. Send it as
  `Authorization: Bearer <token>`. See "Sign in from an assistant" below.
- **No.** Do not start that flow. Tell the person to add the Atlas connector
  `https://atlasmcp.finmanagerai.com/mcp` to their chat app and sign in once.
  Their app holds the token for them.

Never ask for a password, never send one to Atlas (it is refused), and never
print a token in your reply.

---

<!-- ==== Get started ==== -->

# Atlas docs

**Atlas** is a trading and automation platform for the stock and options market,
made by [MindVest](https://www.mind-vest.io). It plugs live market data, charts,
and real trading into your AI, so your AI can not only read the market but place
and manage trades for you. And it does not stop when you close the tab: Atlas can
watch the market around the clock and act on its own with workflows,
alerts, and triggers.

These docs show everything Atlas can do and every way to use it: in a **chat
app** like ChatGPT or Claude, from **code** (the Web API), from the **command
line**, and in the **dashboard**.

## Start here

1. **Pick how you want to use it.** Add Atlas to your [chat app](#connect-overview),
   call it from [your code](#api-overview), or run it from the [command line](#cli-overview).
2. **Sign in.** Chat apps use a sign in link. Code and the command line use a key
   from your [dashboard](#authentication).
3. **Make your first request** with the [Quickstart](#quickstart).
4. **Learn the words.** [Core ideas](#concepts-overview) explains workflows,
   strategies, alerts, and triggers in plain terms.
5. **Know what you pay.** [Plans and how you get charged](#plans-and-billing)
   explains free vs paid and how automations are counted.

## What is inside

| Area | What you get |
| --- | --- |
| [Connect Atlas](#connect-overview) | Add Atlas to ChatGPT, Claude, Discord, and Cursor |
| [Core ideas](#concepts-overview) | Workflows, strategies, alerts, triggers, and how they fit |
| [Using the dashboard](#dashboard-overview) | Every page and form, step by step |
| [Chat app tools](#mcp-overview) | Use Atlas inside your assistant |
| [Command line](#cli-overview) | Run any tool from your terminal |
| [Web API](#api-overview) | Call any tool from your code |

:::tip
Every part of this page has a **Copy for LLM** button. It copies that part as
text you can paste into any AI to ask questions about it. You can also grab the
whole thing at [/atlas/setup-guide/llms](/atlas/setup-guide/llms).
:::

---

# Quickstart

## Way 1: Add it to your AI chat app (no code)

1. Open your chat app's connector settings.
2. Add a server with this link: `https://atlasmcp.finmanagerai.com/mcp`.
3. Sign in with Email, Apple, Google, or Discord when it asks.
4. Say: *"Use Atlas to get me a quote for NVDA and the SPY gamma exposure."*

Full steps: [ChatGPT](#connect-chatgpt), [Claude](#connect-claude),
[Discord](#connect-discord), [Cursor](#connect-other).

## Way 2: Call it from the terminal (Web API)

```bash
# 1. Set the address and your key (get the key from the dashboard, see Sign in)
export ATLAS_BASE_URL="https://atlasmcp.finmanagerai.com"
export ATLAS_KEY="<your key>"

# 2. Your first request: a live quote
curl -sS -X POST "$ATLAS_BASE_URL/api/v1/tools/get_stock_quote" \
  -H "Authorization: Bearer $ATLAS_KEY" \
  -H "Content-Type: application/json" \
  -d '{"symbol":"AAPL"}'
```

## Way 3: Use the command line

```bash
# Node
npm i -g mindvest-atlas
# or Python
pip install mindvest-atlas

# Sign in once, then run any tool
atlas login
atlas stock-quote --symbol AAPL
```

See the [command line docs](#cli-overview) for install, sign in, and every command.

## Way 4: Let your assistant sign the person in

If you are building an assistant, it can start the sign in itself: it asks Atlas
for a link, the person signs in or makes an account in their own browser, and
your assistant gets a key at the end of it. It never sees a password.

```bash
curl -sS -X POST "https://atlasmcp.finmanagerai.com/oauth/device_authorization" \
  -H "Content-Type: application/json" -d '{"mode":"signup"}'
```

Only do this if your assistant can **save** the key somewhere that outlives the
conversation. If it cannot, point the person at the
[Atlas connector](#connect-overview) instead and let their app hold it.

Full steps: [Sign in from an assistant](#api-agent-signin).

## What next

- See [all the tools](#mcp-tools) Atlas has.
- Learn the [core ideas](#concepts-overview) behind workflows and triggers.
- Read [how you get charged](#plans-and-billing) before you set up automations.

---

# Sign in and keys

There are two ways to sign in. Both use the **same account**, so a tool works the
same no matter which one you use.

If you are **building an assistant**, there is a third way: your assistant can
start the sign in for the person and get a key at the end of it. See
[Sign in from an assistant](#api-agent-signin).

## Sign in link (for chat apps)

When you add Atlas to a chat app, it opens a sign in page. You log in once with
**Email**, **Apple**, **Google**, or **Discord**, say yes, and you are done. There is no key
to copy.

## Key (for code and the command line)

The Web API and the command line use one secret key. You send it in the header:

```bash
curl -H "Authorization: Bearer $ATLAS_KEY" ...
```

### Where to find your key

1. Open the [dashboard](/atlas/dashboard).
2. Click your name at the bottom of the menu. That opens **Profile**.
3. Find **API / CLI / MCP Key** and copy it. **Rotate** makes a new one.

The same key works for the Web API, the command line, and any chat app that takes
a key instead of the sign in link.

:::warning
Treat your key like a password. Anyone who has it can use tools on your account,
and for trading tools that means placing real orders with your broker. Never put
it in a web page or share it. If it leaks, press **Rotate** in Profile right
away.
:::

## Check your account

```bash
atlas get-subscription-status
# shows your plan, how much you have used, and how much is left
```

---

# Plans and how you get charged

Here is the simple idea: you pay for the paid work Atlas does, not for every
click. Two limits matter.

## 1. Your monthly requests

Every account gets a set number of paid requests each month. This is the number
you watch go down in your Profile.

| Plan | Price | Requests each month | Alerts switched on at once |
| --- | --- | --- | --- |
| Free | $0 | 50 | 10 |
| Pro | $29.99 / month | 200 | 100 |
| Premium | $49.99 / month | 500 | 300 |
| Max | $99.99 / month | 1000 | 500 |

The alert number is how many alerts can be **on** at the same time. A paused or
deleted alert does not count. Your Profile always shows your own numbers.

Check yours anytime:

```bash
atlas get-subscription-status
```

### What uses one request

The simple rule: **you pay for each thing Atlas does for you, not for each time
it looks.** A run that looks at the market and decides to do nothing is always
free. You use one request each time Atlas:

- **Fetches something for you.** A quote, a chart, an options chain, a gamma
  exposure map, company numbers, a web search, a look at your broker account:
  each is one request. A few of them in the same message still count as
  **one**, not three.
- **Opens a trade or sends a note.** When a workflow acts, by placing a
  trade, sending you a buy or sell note, or sending an analysis note, that is one
  request.
- **Changes a live trade.** While a trade is running, Atlas can step back in and
  change it, like moving your take profit targets up or closing the rest early.
  Each real change is one request. If it looks and leaves the trade alone, it
  costs nothing.
- **Sends you an alert.** An alert uses one request the first time it goes off
  each day. Going off again the same day is free.
- **Takes a play nobody is paying for.** Taking a play from the community board,
  or from a public group, is one request, and only if the order reaches your
  broker. See [Signals](#concept-signals).
- **Talks with you.** Voice uses one request for each ten minutes of speaking in
  a day.

So one trade is not always one request. A trade that Atlas opens and later
adjusts twice uses **three** requests: one to open it, and one for each change.
You pay for the work, whether it is a brand new trade or an update to one you
already have.

### What is free

Working on your own setups never touches your count: making, changing, reading,
sharing and deleting workflows, strategies, folders, plays and alerts, looking at
your triggers, previewing an order before you place it, your results and your
activity, your memory, and this guide.

Anything that fetches market data is **not** free. Quotes, price history, every
chart, the options chain, company numbers, estimates and calendars each use a
request, from a chat app, the Web API and the command line alike. So does
reading your broker account, a web search, placing an order and setting up a
trigger. The tool tables mark each tool **Free** or **Premium**; a Premium tool
is one that uses a request.

## 2. Trades per day

On top of your monthly requests, each workflow has a **max trades per day** limit.
This one is about pacing your account, not cost.

- It counts **new trades opened**. A run that opens no trade does not use a slot,
  and changing a trade you already have does not either.
- When it hits the limit, the workflow **pauses** until the next trading day.
- **Running it by hand does not count.** The limit is only for automatic runs.
- Each copy has its own limit. Your copy runs on its own count, not the author's.

## Putting it together

![A summary: fetching data is one request, opening a trade is one request plus one of your daily trades, changing a live trade is one more request, and working on your own setups or a run that does nothing is always free](/atlas/docs/billing-summary.svg)

So an alert driven trading workflow that opens a trade uses **one request** and
**one of your daily trades**. If Atlas later moves the take profit on that same
trade, that is **one more request** (but not another daily trade). A run that
looks and decides to do nothing uses **neither**.

Manage your plan from the [Profile tab](#dashboard-profile).

---

<!-- ==== What's new ==== -->

# New on Nov 7, 2026

Here is what changed, in one minute. Each line opens its own page with pictures.

| What | In short |
| --- | --- |
| [Trade settings](#trade-settings) | One sheet for how a workflow's trades are placed for you: account, size (the same for all, or per trade), auto sizing, filters, exits, messages. First line of a workflow's **More**. |
| [Size and auto sizing](#sizing) | One **Contracts** row on every trade: a number ("3") or money ("up to $500"). Auto sizing puts in less after losses and more after wins. |
| [Circuit breaker](#circuit-breaker) | Pause trading for the day when the day's loss, or profit, reaches your number. Comes back by itself. |
| [Advanced filters](#advanced-filters) | 28 rules for which trades are taken for you: only SPY, nothing over $3 a contract, not on FOMC days, and more. |
| [The browser](#browser) | One browser for you, a tab for each chat or agent. It stays open until you close it. Full screen on a phone turns sideways. |
| [Agents that fix things](#agents-fix) | Your Account Manager fixes small, safe things itself, tells the Atlas team when Atlas is broken, and can open a session on your computer. |

Also new:

- **Schedules run at least 2 minutes apart.** "Every minute" is not allowed any
  more, because an agent needs time to finish a run. Pick every 2 minutes or
  more, or use an alert.
- **Lists in the chat show 10 items**, then a white **See more in Atlas
  dashboard** button that opens the full list in the dashboard.
- **A schedule is picked in rows**: Weekdays, Every day, Weekends or Once, the
  days as round chips, then **Specific times** (each time a box, **+ Add
  another time**) or **Every so often**.
- **The voice starts the moment you press it.** Start talking straight away;
  nothing you say while it connects is lost.
- **Take everything at TP N** and **Take anyway**: see
  [Trade settings](#trade-settings) and [Advanced filters](#advanced-filters).

![A held run of 14 in the chat: ten rows, and 4 more, then the white See more in Atlas dashboard button](/tutorial-files/nov7/widget-see-more-phone.jpg)

![The Schedule step on a phone: Schedule, Weekdays, the days as chips, Specific times, 9:40 AM, Add another time](/tutorial-files/nov7/schedule-phone.jpg)

![The same Schedule step on a computer](/tutorial-files/nov7/schedule-computer.jpg)

:::note
Every one of these can be done by asking the chat in your own words, for
example "put $500 into each trade" or "stop for the day if I lose $300".
:::

---

# Trade settings

**Trade settings** is one sheet for how a workflow's trades are placed for
you: which account, how big, auto sizing, filters, how you get out, and the
messages you get. It is the same sheet for a workflow you made and for a copy of
somebody's, live or paused.

## Where to find it

- **A workflow**: press **More** on its row. **Trade settings** is the first
  line.
- **A signal group you own**: the **Trade settings** button on the group (the
  sliders). It sets your own order on each play you post.
- **A signal group you follow**: its **Trade settings** button, as before.

![A workflow's More: Trade settings is the first line](/tutorial-files/nov7/ts-more-phone.jpg)

![More on a computer](/tutorial-files/nov7/ts-more-computer.jpg)

## What each part does

| Part | What it does |
| --- | --- |
| **Account** | The broker account the orders go to. |
| **Size** | **Same for all**: one size for every trade of the workflow, a number of contracts, or money with **Size this trade by an amount of money**. **Per trade**: a size for each trade card, for example 2 contracts on the call and $500 on the put. Trades that go together (OCO, OEO) are shown together. |
| **Advanced settings: Auto sizing** | Puts in less after losses and more after wins, and holds the [circuit breaker](#circuit-breaker). Only with money. See [Size and auto sizing](#sizing). |
| **Advanced settings: Advanced filters** | Which trades are taken for you. See [Advanced filters](#advanced-filters). |
| **Exits: Take everything at one target** | Switch it on and type the target's number beside **TP** (any target, 1 to 20). When that target fills, everything you still hold comes out. Later targets do nothing for you. No target moves, and nobody else's amounts change. |
| **How your exits split** | How your position comes off at the targets: the amounts on each card, the same as the author, more at the first, more at the last, or even. |
| **Notifications** | **DM me the trades** on Discord, and the message's format. |
| **Let the author's close reach me** | On a copy only: whether the author pressing **Close all** closes yours too. |

## Per trade, or the same for all

![Per trade: the SPY call at 2 contracts and the SPY put at $500, the OCO pair together](/tutorial-files/nov7/ts-per-trade-phone.jpg)

![Same for all: one Contracts box for every trade](/tutorial-files/nov7/ts-same-phone.jpg)

On a computer the sheet opens in the middle of the screen:

![Per trade on a computer](/tutorial-files/nov7/ts-per-trade-computer.jpg)

![Same for all on a computer](/tutorial-files/nov7/ts-same-computer.jpg)

## Take everything at TP N

Under **Exits**, switch on **Take everything at one target** and type the
target's number beside **TP**: 2 for TP2, 12 for TP12. "Everything left comes
out when TP2 fills." Switched off, each target takes its own amount.

![Take everything at one target: on, TP 2](/tutorial-files/nov7/ts-take-all-phone.jpg)

## One Save, and it always matches the workflow

Change what you want, then press **Save** once at the bottom. Only what you
changed is sent. On your own workflow the sheet reads and writes the trade
cards themselves, so the workflow form and Trade settings always show the same
thing. On a copy it changes only your own settings, and you keep following the
author.

## A signal group you own

The group's **Trade settings** sets **your own order** on each play you post
there. Left alone, each play trades as you post it. **What you set here wins
over what a play says**, so a play posted with the wrong account or size is
put right by itself.

- **Account**, three ways: **The account each play names** (your default when a
  play names none; the starting choice), **Always my default account**, or
  **Always this account** with the account picked under it. The last two win
  over the account a play names.
- **Size**: **Use the size each play says**, or your own count or amount of
  money. Your own size is written onto every play you post, so the play, your
  order and every follower who copies your size read one number.
- **Advanced settings**: **Auto sizing** (with your own circuit breaker) and
  **Advanced filters**. A play outside your filters still posts to your
  followers; only your own order is not placed.
- **Exits**: **Take everything at one target**, with the TP number typed.

A tripped breaker stops only your own orders; your plays still go to your
followers. Your followers have the same sections in their own Trade settings.
A group's **Delete** is in its **More** menu, last and in red.

![A signal group owner's Trade settings: the three account choices and the size](/tutorial-files/nov7/ts-signal-owner-phone.jpg)

![Advanced settings: Auto sizing and Advanced filters](/tutorial-files/nov7/ts-signal-owner-adv-phone.jpg)

![A group's More menu: Make public, Rename, Share, Delete](/tutorial-files/nov7/ts-group-more-phone.jpg)

## If you ask the chat

| You say | Atlas does |
| --- | --- |
| "Show the trade settings of my SPY workflow" | `Workflow-Trade-Settings` with only `workflow_id`: account, every trade card and its size, and the rest. |
| "$500 on every trade of that workflow" | `Workflow-Trade-Settings` `size: {"scope": "all", "mode": "budget", "budget_dollars": 500}`. |
| "3 contracts on the call, $200 on the put" | `size: {"scope": "per_card", "cards": [...]}`, each card by its label. |
| "Sell everything at TP2" | `take_all_at_tp: 2` (`0` turns it off). On a signal group: `Signal-Trade-Settings` with `group_id` and `take_all_at_tp: 2`. |
| "DM me this workflow's trades" | `notify: {"dm": true}`. |
| "Use my Schwab account for it" | `broker_account_id` from the read. |
| "Only SPY on that workflow" | `trade_filters: {"symbols": ["SPY"]}`. |
| "Size it by my account, less after losses" | `auto_size` (with a budget). |
| "Turn my own orders back on in my group" | `Signal-Trade-Settings` with `group_id` and `resume_own_orders: true`. |

---

# Size and auto sizing

Every trade form now has one **Contracts** row. It shows either a number
("4") or money ("up to $500"). You find it on:

- a workflow's trade card (Workflows, open one, **Trades** tab),
- a trigger,
- a signal you post,
- your **Trade settings** for a signal group you follow,
- the **Take** sheet when you take a play by hand,
- spreads, where the row is called **How many** (how many spreads).

## Step 1. Open the Contracts row

Tap **Contracts**. Type how many contracts you want.

![The Contracts sheet with a count of 4](/tutorial-files/nov7/size-count-phone.jpg)

## Step 2. Or size it by money

Pick **Budget** (beside **Contracts**) and type the most to put
into this trade. Atlas buys as many as fit under that amount at the price it
pays, never more.

![Budget picked, most to put in: 500](/tutorial-files/nov7/size-money-phone.jpg)

Tap **Done**. The row now reads **up to $500**.

![The trade card's Contracts row reads up to $500](/tutorial-files/nov7/size-row-phone.jpg)

For a spread the same sheet is called **How many**. The budget can be the most
you can lose or the credit you collect.

![How many iron condors, sized from a budget of $4,000: 2 at a max loss of $1,885 each](/tutorial-files/nov7/size-spread-phone.jpg)

On a computer it is the same sheet in the middle of the screen:

![The Contracts sheet on a computer](/tutorial-files/nov7/size-count-computer.jpg)

## Step 3. Auto sizing (optional)

With money switched on, an **Auto sizing** row appears under the amount. Tap it.
The same row is in a workflow's [Trade settings](#trade-settings) and in the
Trade settings of a signal group you follow or own. All of them open the same
page, with two switches: **Change my size** and **Circuit breaker**. Each opens
its own part only when it is on.

![Auto sizing as it opens: two switches, Change my size and Circuit breaker](/tutorial-files/nov8/autosize-closed-phone.jpg)

![The Auto sizing row under the amount, Off](/tutorial-files/nov7/autosize-row-phone.jpg)

Switch on **Change my size**, then choose:

![Change my size on: each trade starts from your budget, then a box for After wins and a box for After losses](/tutorial-files/nov8/autosize-size-on-phone.jpg)

| Setting | What it does |
| --- | --- |
| **Each trade starts from** | **My budget** ($500), or **Part of my account** (for example 40% of your account). It is never more than your budget. |
| **After wins** (its own box) | **In a row**: after this many wins in a row, **put in more by** a % or by $. |
| **After losses** (its own box) | **In a row**: after this many losses in a row, **put in less by** a % or by $. |

![Auto sizing: start from 40% of the account, 50% less after 1 loss, $25 more after 2 wins](/tutorial-files/nov7/autosize-account-phone.jpg)

How it works:

- It is worked out when each trade goes in, from your account then.
- It moves one step, then goes back to the start after the opposite result
  (a win after a loss, a loss after a win).
- It never goes under one contract.
- The box at the bottom says it in a sentence, so you can check it.

Tap **Done**. The row shows what you set, for example
**40% of account · −50% after 1 loss · +$25 after 2 wins · pauses at −$200 or +$500**,
and the trade's Contracts row reads **up to $500 · auto**.

![The Auto sizing row now reads 40% of account, −50% after 1 loss, +$25 after 2 wins, pauses at −$200 or +$500](/tutorial-files/nov7/autosize-card-phone.jpg)

The same page on a computer:

![Auto sizing on a computer](/tutorial-files/nov7/autosize-account-computer.jpg)

The same page also holds the [circuit breaker](#circuit-breaker), behind its own
switch. **Change my size** needs a budget: sized by contracts, it says **Set a
budget first** and only the circuit breaker can be turned on.

For a **signal group you follow**, it is the same page. The steps after losses
and wins count your own closed trades from that group, and they change only
orders your own budget sizes (never the play's size you follow).

## If you ask the chat

| You say | Atlas does |
| --- | --- |
| "Put $500 into each trade" | Sets the budget on that trade (`bracket_trade_budget: 500`, no contract count). |
| "Buy 3 contracts" | Sets the count, no budget. |
| "Start at 40% of my account, never over $1,000, and put in 25% less after 2 losses" | Workflow card: `bracket_trade_budget: 1000`, `bracket_auto_size: {"start": "account", "account_pct": 40, "down_after": 2, "down_by": 25, "down_unit": "pct"}`. |
| "Post this play with $500, sized by my account" | `Signal-Post` with `trade_budget` and `auto_size` (your own order only). |
| "My budget for this group is $250" | `Signal-Trade-Settings` `max_per_trade: 250`. |
| "On my copy of that workflow, $500 a trade" | `Workflow-Update` `execution_overrides {"budget_cents": 50000}`. |

A script workflow has no Trade settings: its script decides the size.

A trigger on its own takes only the start (`auto_size {"start": "account",
"account_pct": 40}`). The steps after losses and wins count a workflow's
trades, so they go on a workflow's trade card.

---

# Circuit breaker

The circuit breaker pauses trading for you when the day's closed trades lose,
or make, as much as you say. It has its own switch on the
[Auto sizing](#sizing) page, under **Change my size**.

## Step 1. Open Auto sizing

In a workflow's [Trade settings](#trade-settings), on its trade card, or in
**Trade settings** for a signal group you follow or own, tap **Auto sizing**.
(A workflow needs a budget for it; a signal group does not.)

## Step 2. Turn on Circuit breaker and set your numbers

Switch on **Circuit breaker**. Two boxes appear:

- **Pause at a day's loss of**: a % of your account, or $.
- **Pause at a day's profit of**: the same, for a good day.

Leave one empty to keep it off.

![Circuit breaker on: pause at a day's loss of $200, back tomorrow](/tutorial-files/nov8/breaker-on-phone.jpg)

## Step 3. Pick how long

Once a number is typed, pick under it how long the pause lasts:

| Choice | Trading comes back |
| --- | --- |
| **Back tomorrow** | At the next trading day's open, 9:30 AM ET (Friday goes to Monday; market holidays are skipped). |
| **For a week** | At the open a week later. |
| **Until I turn it on** | Only when you turn it back on yourself. |

![Circuit breaker: pause at a $200 loss, back tomorrow; pause at a $500 profit, until I turn it on; the sentence under it says back at the next trading day's open, 8:30 AM CT](/tutorial-files/nov7/breaker-how-long-phone.jpg)

![The same on a computer](/tutorial-files/nov7/breaker-how-long-computer.jpg)

## What happens when it trips

- **Your workflow** pauses. Trades already open keep their stops and targets.
- **If people follow your workflow**, it keeps running for them. Only your own
  trades are paused.
- **A signal group you follow**: automatic taking of that group's plays stops.
  You can still take a play by hand.
- **A signal group you own**: only your own order on new plays is not placed.
  Your plays still go to your followers. Turn your orders back on in the group's
  Trade settings, or ask the chat.
- You get **one** message that says why and until when, in your own time zone,
  for example "until tomorrow's open (8:30 AM CT)".
- At that time it **comes back by itself**, and you get one message that it is
  back on.

For a group you follow, it is the same Auto sizing page from your Trade
settings, the same two switches:

![Trade settings for a group you follow: the Auto sizing row reads −50% after 1 loss, pauses at −$200](/tutorial-files/nov8/autosize-follower-row-phone.jpg)

## Turn it back on early

Turn the workflow back on (its switch, or ask the chat). For a group you
follow, switch **Take every play automatically** back on in its Trade settings.

## If you ask the chat

| You say | Atlas does |
| --- | --- |
| "Stop this workflow for the day if I lose $300" | Adds `pause_loss: {"amount": 300, "unit": "usd", "resume": "tomorrow"}` to the card's `bracket_auto_size`. |
| "Pause after I make 5%, until I turn it back on" | `pause_profit: {"amount": 5, "unit": "pct", "resume": "manual"}`. |
| "Stop taking this group's plays for a week if I lose $200 in a day" | `Signal-Trade-Settings` with `group_id` and `pause_loss: {"amount": 200, "unit": "usd", "resume": "week"}`. |
| "Turn it back on now" | `Workflow-Update` `patch {"status": "active"}`, or `Signal-Trade-Settings` `accept_mode: "auto"` for a group. |
| "Remove the loss limit" | Sends `pause_loss: {}`. |

---

# Advanced filters

Advanced filters decide which trades are taken for you when you follow a
signal group or copy somebody's workflow. A filter only **skips** a trade. It
never changes one: you get the same trade as everyone else, or none.

## Step 1. Open Trade settings

On Signals, open **Trade settings** for a group you follow. Tap **Advanced
filters**. On a workflow, the same row is in its [Trade settings](#trade-settings).

![Trade settings with the Advanced filters row](/tutorial-files/nov7/filters-row-phone.jpg)

## Step 2. Fill in only what you want

Each filter has its own box, and its name says what it does (**Max** = skip
above this, **Min** = skip below this). Leave a box empty and it does not
filter. The most used come first. A **Search filters** box at the top finds one
by name. The table below says exactly what each one checks.

**Trade types** and **Days** are buttons: tap as many as you want, and the ones
you picked turn blue. None picked means every type, every day.

![The Advanced filters page: Trade types with Calls and Spreads picked in blue, Max bid/ask spread, Min rating, Min open interest](/tutorial-files/nov8/filters-top-phone.jpg)

![Searching for delta](/tutorial-files/nov7/filters-search-phone.jpg)

## Step 3. Save

Tap **Save** (it says how many are on). **Clear all** empties the page. The
row then says how many filters are on.

![Back in Trade settings: Advanced filters, 4 on](/tutorial-files/nov7/filters-saved-phone.jpg)

On a computer the page opens in the middle of the screen:

![Advanced filters on a computer](/tutorial-files/nov8/filters-computer.jpg)

## The 28 filters

In the order of the page. "All" means calls, puts, shares and spreads.

| Filter | A trade is skipped when | Works on |
| --- | --- | --- |
| **Trade types** | It is a type you did not pick (calls, puts, shares, spreads). None picked = every type. | All |
| **Max bid/ask spread** | The gap between bid and ask is wider than this % of the middle price. | All (shares: the stock's; spreads: every leg) |
| **Min rating** | Its rating (1 to 10) is lower. A trade with no rating is not skipped. | All |
| **Min open interest** | The contract's open interest is lower. | Calls, puts, spreads (every leg) |
| **Min volume today** | Today's volume is lower. | All (shares: the stock's) |
| **Max price per contract** | One contract costs more ($). A trade whose price can't be known yet is skipped too. | All (one share; a spread's net) |
| **Min price per contract** | One contract costs less ($). | All |
| **Days to expiry** | Days to expiry (0 = same day) are outside, or inside with **Skip these**. | Calls, puts, spreads |
| **Max move past entry** | The price already moved this % past the entry it was called at. | All |
| **Max play age** | The trade is older than this many minutes. | All |
| **Skip near earnings** | The company reports within this many days. | All |
| **Big news days** | Today is an FOMC, CPI or jobs report day. | All |
| **Max trades a day** | You already took this many today. | All |
| **Max open at once** | You already have this many open from this group or workflow. | All |
| **IV range** | Implied volatility is outside your range (%). | Calls, puts, spreads |
| **Delta range** | Delta (0 to 1, no sign) is outside your range. | Calls, puts, spreads (net delta) |
| **Strike range** | The strike is outside, or inside with **Skip these**. | Calls, puts, spreads (every leg) |
| **Only these symbols** | The ticker is not on your list. | All |
| **Time window** | It comes outside your hours (your own time zone). | All |
| **Days** | It comes on a day you did not pick. | All |
| **Max stock move today** | The stock already moved more than this % today. | All |
| **Max gap at open** | The stock opened more than this % from yesterday's close. | All |
| **Day direction** | **With the day**: calls only on green days, puts only on red. **Against**: the opposite. | Calls, puts, shares (bought = call side, shorted = put side), spreads (bull = call side) |
| **VIX range** | The VIX is outside your range. | All |
| **Max theta a day** | Time decay is more than this many $ a day for one contract. | Calls, puts, spreads (net) |
| **Max buying power used** | The trade would use more than this % of what is free. | All |
| **Pause after a loss** | A losing trade closed less than this many minutes ago. | All |
| **Stock price range** | The stock's price is outside your range. | All |

## Good to know

- **Market filters are checked when the trade goes in**, with the market at
  that moment (spread, open interest, volume, IV, delta, theta, slip, late
  entry, earnings, news days, open trades, stock move, gap, direction, VIX,
  buying power, pause after a loss, stock price).
- **A number Atlas can't read at that moment never skips a trade.**
- **A skipped trade sends you one notice** that names the filter that skipped it.
- **A play you take by hand is never stopped, but you are told.** When you press
  **Take now** on a play that breaks some of your filters, the sheet says which
  ones in a yellow note, for example "Bid/ask spread 14% (your widest is 10%)",
  and its button reads **Take anyway**. Press it to take the play all the same,
  or **Cancel**.

![Take now on a play outside 2 of your filters: the note names both, and the button reads Take anyway](/tutorial-files/nov7/take-anyway-phone.jpg)

![The same on a computer](/tutorial-files/nov7/take-anyway-computer.jpg)

- The person who posts the signal, or owns the workflow, is never filtered.
- The same filters are on a group you pay for (Marketplace, My subscriptions),
  on Community picks (**Settings**), and on a copy of somebody's workflow.

## If you ask the chat

| You say | Atlas does |
| --- | --- |
| "Only take SPY and QQQ from this group" | `Signal-Trade-Settings` `group_id` + `trade_filters: {"symbols": ["SPY", "QQQ"]}`. |
| "Nothing over $3 a contract, and not on FOMC days" | `trade_filters: {"max_contract_cost": 3, "skip_news_days": true}`. |
| "Skip trades within 5 days of earnings" | `trade_filters: {"earnings_days": 5}`. |
| "Only 9:45 AM to noon, Monday to Wednesday" | `trade_filters: {"window": {"from": "9:45 AM", "to": "12:00 PM"}, "days": ["mon", "tue", "wed"]}`. |
| "Same on my copy of that workflow" | `Workflow-Trade-Settings` with `trade_filters` (or `Workflow-Update` with top-level `trade_filters`). |
| "Does this play break any of my filters?" | `Signal-Filter-Check` with the play's id: each broken filter in words. Nothing is placed. |
| "Take it anyway" | Takes the play by hand (`Signal-Take`). A filter never stops a hand take. |
| "Clear my filters" | `trade_filters: {}`. |

The whole set replaces what was saved, so the chat sends every filter you
want to keep.

---

# The browser

Atlas has a real web browser the chat and your agents can use, and you watch it
live beside the chat.

## How it works

- **One browser for you.** Each chat, and each agent, gets its own tab in it.
  Sign-ins are shared, so you sign in to a site once.
- **It stays open until it is closed.** Nothing closes it for being idle. When
  you are done, press **Close browser** (or ask the chat to close it).
- **Switches, check boxes, sliders and dials** can be worked by the chat and
  your agents too, not only buttons and links.
- **A page that crashes opens again** where it was. **Reload** at the top
  loads it again yourself.
- **A link to another site opens in a new tab**, and the view follows it.

## Full screen

Press the full-screen button at the top of the browser. On a phone it turns
sideways, the same way Computer use does, so the page fills the screen.

![The browser full screen on a phone, turned sideways, with its tabs on top](/tutorial-files/nov7/browser-full-screen-phone.jpg)

![The browser full screen on a computer](/tutorial-files/nov7/browser-full-screen-computer.jpg)

## What the chat saw

When the chat takes a picture of the page to look at it, the picture shows
under that step in the chat. Tap it to see it large. Pictures are kept for one
day, then deleted ("This picture is no longer kept").

![A chat step "Read browser" with the picture the chat saw](/tutorial-files/nov7/browser-look-phone.jpg)

![The same on a computer, with the browser beside the chat](/tutorial-files/nov7/browser-look-computer.jpg)

## Signing in

When a site needs you to sign in, the chat stops and asks you to sign in in the
browser window yourself. It never sees that page and never asks for a password.

## If you ask the chat

| You say | Atlas does |
| --- | --- |
| "Open the Fed's calendar" | `Browser-Open` with this chat's id; you watch it beside the chat. |
| "Open SEC filings in another tab" | `Browser-Tab` new. |
| "What does the chart look like?" | `Browser-Read` with `look: true`; the picture shows under the step. |
| "Turn on that switch" | `Browser-Act` check on the switch's ref from the page's `controls`. |
| "I'm done" | `Browser-Close`. |

---

# Agents that fix things

Your agents now do more of the work themselves, carefully.

## The Account Manager fixes small, safe things

When something of yours breaks, the Account Manager looks into it first. If
the fix is safe and can be undone, it does it, checks it worked, and tells you
in one line what it did. These are the only things it fixes by itself:

- runs again a workflow run that failed for a passing reason (a timeout, a
  data hiccup), once, while the market is open;
- starts again a task on your computer that stopped on an error, once;
- switches back on a workflow Atlas paused by mistake (never one you paused,
  or one paused by its daily limit, loss limit or profit target);
- fills in what a workflow is plainly missing when there is only one right
  answer, such as your only broker account.

If a fix does not hold, it stops and tells you. It **never** places, closes or
changes a trade, changes a size, budget, stop or target, changes a workflow's
instructions or schedule, touches your alerts or money settings, deletes
anything, or signs in for you. For those it tells you the one thing to do and
offers to do it when you say yes.

## It tells the Atlas team when Atlas is broken

When the problem is in Atlas itself, not your setup, it files a support ticket
with the Atlas team straight away, with everything they need, and tells you in
one line that the team has it. A problem on your side (your broker, your
computer being off) is never filed; you are told what to do instead.

## A session on your computer

When a fix needs hands on your computer (a dashboard or a task in Atlas Studio
that broke), an agent can start a **session** there: a new chat in Atlas
Studio, titled with the agent's name, with everything it found. It works on it
by itself, and the agent checks on it from Atlas and tells you what changed.

- It starts one only when you said yes, or to fix something that broke on that
  computer.
- At most 2 open at a time per agent per computer.
- It never trades, changes money settings, deletes anything or signs in.
- You can watch it in Atlas Studio like any other chat.
- There is no switch to find. If you don't want agents working on your
  computers, say so to the chat in your own words, for example "don't let my
  agents work on my computers". Say "let them again" to undo it.

## Checks show their work

An agent's quiet check now writes two to four short lines of what it checked,
with the numbers, in its **Activity**, even when it had nothing to tell you.

## If you ask the chat

| You say | Atlas does |
| --- | --- |
| "Fix my SPY dashboard on my MacBook" | Asks for your yes, then `Computer-Session` start with the whole story (`confirmed_by_person: true`), and tells you where it runs. |
| "How is that session doing?" | `Computer-Session` read with its `ref`. |
| "Stop it" | `Computer-Session` stop. |
| "Don't let my agents work on my computers" | `Computer-Session` allow with `on: false`. |
| "Tell the team this is broken" | `Support-Report`, and gives you the ticket number. |

---

<!-- ==== Connect Atlas ==== -->

# Add Atlas to your AI

Atlas plugs into your AI. Any chat app that can add a tool server can use Atlas
and get the full toolset: live market data, options, charts, your broker, orders,
triggers, workflows, and strategies.

## The one link you need

```text
https://atlasmcp.finmanagerai.com/mcp
```

Point any chat app at that link, sign in once (Email, Apple, Google, or Discord), and
every Atlas tool is ready.

:::note
Add the connector on the **web** first ([chatgpt.com](https://chatgpt.com) or
[claude.ai](https://claude.ai)). Once it is added on the web, it also works in the
phone and desktop apps.
:::

## What you can do once it is on

- Ask for live quotes, company numbers, earnings, and who owns a stock.
- Make price charts, gamma heatmaps, and exposure charts.
- Link a broker, check orders, and manage triggers.
- Build **workflows** so Atlas can trade or analyze on a schedule or on an alert.
- Save and reuse **strategies** (your trading playbooks).

Pick your app below.

---

# Add Atlas to ChatGPT

![ChatGPT](/images/Chatgpt_Logo-Picsart-BackgroundRemover.jpg)

Add Atlas to ChatGPT. It takes about 2 minutes.

### Step 1. Open Plugins

On the web, open [chatgpt.com/plugins](https://chatgpt.com/plugins). You do not need to turn on Developer mode.

### Step 2. Add a server

Click the **+** button, then **Add custom MCP server**.

### Step 3. Fill in Atlas

Type these in:

- **Name**: Atlas
- **Description**: Stocks and Options
- **Server URL** (under Connection): `https://atlasmcp.finmanagerai.com/mcp`
- **Authentication**: OAuth

### Step 4. Create it

Read the warning, click **I understand and want to continue**, then click **Create as a plugin**.

### Step 5. Sign in to Atlas

ChatGPT shows the Atlas tools it found. Install it, and when ChatGPT sends you to the Atlas sign in page: Sign in with **Email**, **Apple**, **Google**, or **Discord**, click **Connect to Atlas**, agree, and click **Authorize**.

### Step 6. Use Atlas in chat

In a new chat, type **@** and pick **Atlas**.

### Step 7. Ask away

Ask Atlas anything: live quotes, company numbers, options flow, and more.

:::note
No **Add custom MCP server**? Your ChatGPT plan or your workspace does not allow your own servers yet. On a work account, your admin turns it on.
:::

---

# Add Atlas to Claude

![Claude](/images/Claude_Logo-Picsart-BackgroundRemover.jpg)

Add Atlas to Claude. It takes about 2 minutes.

### Step 1. Open Connectors

On the web at [claude.ai](https://claude.ai) or in the desktop app, go to **Customize**, then **Connectors**.

### Step 2. Add a connector

Click **+ Add**, then **Add custom connector**.

### Step 3. Fill in Atlas

Type these in and click **Continue**:

- **Name**: Atlas
- **Remote MCP server URL**: `https://atlasmcp.finmanagerai.com/mcp`

If the box shows **Advanced settings** on the same screen instead, leave them empty and click **Add**.

### Step 4. Keep the sign in settings

Claude shows how Atlas signs in. Keep what it chose and click **Add**.

### Step 5. Sign in to Atlas

Claude sends you to the Atlas sign in page (if it does not, click **Connect** beside Atlas). Sign in with **Email**, **Apple**, **Google**, or **Discord**, click **Connect to Atlas**, agree, and click **Authorize**.

### Step 6. Turn it on in chat

In a chat, click the **+** button, go to **Connectors**, and turn **Atlas** on.

### Step 7. Ask away

Ask Claude anything with Atlas on: quotes, company numbers, charts, options, and live market data.

:::note
On a **Team** or **Enterprise** plan, an owner adds Atlas once in **Organization settings**, then **Connectors**; then each person clicks **Connect** beside it in **Customize**, then **Connectors**. The free plan allows one custom connector.
:::

---

# Use Atlas in Discord

![Discord](/images/Discord_logo-Picsart-BackgroundRemover.jpg)

Add the Atlas bot to your Discord server and tag it to get quick market help.

### Step 1. Add the Atlas bot

Use the [Add Atlas Bot to your server](https://discord.com/oauth2/authorize?client_id=1434681790974398466&permissions=826781329408&integration_type=0&scope=bot) link, or [join the Atlas Discord](https://discord.gg/xcnsbPd8rz) to try it in a shared server.

### Step 2. Tag the bot

Once the Atlas bot is in your server, type **@Atlas Bot** and then your question.

![Tag the bot](/tutorial-files/Discord-Demo-1.jpg)

### Step 3. Ask for help

The Atlas bot is a market helper. Ask for quotes, company numbers, market data, options flow, and clear takes.

![Ask for help](/tutorial-files/Discord-Demo-2.jpg)

### Step 4. Get charts

Atlas can make charts, pull company numbers, look at options, and answer follow up questions right in Discord.

![Get charts](/tutorial-files/Discord-Demo-3.jpg)

---

# Cursor and other apps

Any app that can add a tool server can use Atlas. Point it at the Atlas link and
sign in.

## Cursor

Add Atlas to your `~/.cursor/mcp.json` (or the project `.cursor/mcp.json`):

```json
{
  "mcpServers": {
    "atlas": {
      "url": "https://atlasmcp.finmanagerai.com/mcp"
    }
  }
}
```

Cursor opens the sign in the first time you use Atlas. Say yes and the Atlas tools
show up.

## Any other app

Most apps take a server as a `{ "url": "..." }` entry with sign in. Use:

- **Type**: HTTP (streamable) or SSE
- **Link**: `https://atlasmcp.finmanagerai.com/mcp`
- **Sign in**: OAuth (the app opens a window for you to sign in)

## Want to use a key instead?

If your app cannot do the sign in, you can use the [Web API](#api-overview) or the
[command line](#cli-overview) with a key. See [Sign in and keys](#authentication)
for where to find your key.

## Building your own assistant?

Your assistant can start the sign in itself: it asks Atlas for a link, gives the
link to the person, and gets a key once they are done. No sign in screen for you
to build, and no password ever goes near your assistant. See
[Sign in from an assistant](#api-agent-signin).

---

<!-- ==== Core ideas ==== -->

# Core ideas

Atlas is more than a data helper. It can watch the market and act for you. Four
parts work together.

| Part | In one line |
| --- | --- |
| [Workflow](#concept-workflows) | A helper that runs again and again. It looks at the market, decides, and can trade. |
| [Strategy](#concept-strategies) | Your saved trading rules that you and your AI can reuse. |
| [Alert](#concept-alerts) | A market watcher. It can message you and start a workflow. |
| [Trigger](#concept-triggers) | One "if this, then buy or sell" order. The smallest trading piece. |

## How they fit together

![How a strategy, an alert, a workflow, a trigger, and your broker fit together](/atlas/docs/flow-concepts.svg)

- An **alert** or a **schedule** decides *when* a workflow runs.
- The **workflow** is the *brain*. It reads live data with the
  tools you picked, follows your rules (and any **strategy** you point it at), and
  makes a choice.
- If the choice is to trade, the workflow places one or more **triggers** and the
  order goes to your broker.

You can use each part on its own, like an alert that just messages you, or wire
them together into a hands off setup.

Separate from these: a [**play**](#concept-signals) is a call you make
yourself and post, either to people who follow you or to the open community
board. No AI decides any part of it.

## What a workflow can do

When you make a workflow you tick what it is for:

- **Trade it** places real orders with your broker when it decides to act.
- **Send me the order** messages you the exact order to place by hand. It never
  trades on its own.
- **Just analyse** only thinks and reports. It never trades.
- **Create alerts** sets alerts up and moves them for you.
- **Send plays** posts [plays](#concept-signals) to the community board or to one
  of your groups.

A workflow does one of the first three. **Create alerts** and **Send plays** can
be ticked on top.

---

# Workflows

A **workflow** is a helper that runs again and again. On each run, Atlas:

1. **Looks.** It calls the market tools you picked (quotes, the options chain,
   gamma, flow, charts, and more).
2. **Decides.** It reads that data, follows your written rules, and makes a choice.
3. **Acts.** If the choice is to trade, it places the order with your broker (or
   sends you the plan, in Draft mode).

## What kind of workflow

The **Basics** step asks what the workflow is for, and that decides how it acts
at the end of a run:

- **Trade it** places the trade card with your broker.
- **Send me the order** messages you the trade to place yourself.
- **Create alerts** and **Send plays** make those things.
- **Just analyse** is the one with no trade card. It reads the tools you picked,
  thinks, and writes up what it found. If you want it to *do* something with
  that conclusion, you give it **Output** tools: the tools it calls **after** it
  has decided, such as posting a play, setting an alert, messaging you, or acting
  on one of your own connected servers.

The **Output** step is for **Just analyse** workflows only. The others already
act through their trade card, their play or the alerts they make, so the step
is not offered on them and any output tools they carry are ignored.

To get the most out of an analysis workflow:

- Pick the **Input data** tools as lookups: the things it must read to decide.
- Write the reasoning so it **ends in a decision**, never "check with me first".
  Nobody is there on a scheduled run, and an analysis run is never "no action":
  the write-up is the result.
- Give it only the Output tools the reasoning actually asks for. Leave Output
  empty for a plain write-up. No broker is needed unless an Output tool places
  something.
- Your own connected servers (Connect → Connectors) count as tools too, for
  Input data and for Output. For an assistant building the workflow for you, the
  **Search-Tools** tool lists every tool in one place, Atlas's and your
  servers', with the exact name to use.

## A note on every tool

Each tool you pick, in **Input data** and in **Output**, has a box under it:
**Notes for this tool**. What you write there is what the run is told about that
tool: what to ask it for, and what to look at in its answer. For an Output tool,
when to use it and what to send.

A tool with no note is used on a guess. One or two plain sentences is enough,
for example on a gamma tool: *"SPY, today's expiration. Find the strike with the
most gamma and say whether the price is above or below it."*

An assistant building a workflow for you is told to write one for every tool.
If it leaves any empty, Atlas tells it which ones.

## What starts a run

A workflow runs from one of these:

- A **schedule**, like every weekday at 9:45 in the morning.
- An **alert** you attach. The workflow runs when the alert goes off.
- **Both** a schedule and an alert.
- **Manual**: nothing starts it but you.

You can also press **Run now** anytime in the dashboard.

## Looking before it places

Tick **Let me review each run before it places** and the workflow still runs in
full, then stops before anything reaches your broker. What it decided waits for
you on the workflow's card, behind a **Preview** button. Read it, change it, then
**Place it** or **Throw it away**.

## A journal

A workflow can keep a journal: a note after each trade, each run, or once a day
or week, written by Atlas or by you. It reads those notes back on later runs, so
what it learned last week is still there this week. An assistant can set all of
it up for you, including when it writes, with the same choices the form has.

## How it exits a trade

You set the exit: how much to risk (stop loss) and where to take profit. The
stop can be a **trailing** one, which follows the best price since you got in
and only ever tightens. Atlas also has a **scale out ladder**, where you sell in
stages at more than one target, each with its own trailing stop. See
[Exits and the scale out ladder](#workflow-exits).

## Sharing and copies

Workflows can be **shared**. When you import someone's workflow (or your own
template), you get a **linked copy**:

- The copy follows the author's setup. When the author makes it better, your copy
  updates too (if you keep auto updates on), or it shows a
  **"behind, apply updates"** note.
- Some settings are **yours** and the author never changes them: the name, the
  size, the stop loss and take profit, the broker, the alert, who can see it, the
  daily limit, and your message settings.
- **Advanced filters** on your copy are yours too: which kinds of trade, the
  widest bid/ask spread, the lowest rating, the price per contract, the expiry
  and strike, the hours and days, the most trades a day, the day's move, VIX,
  earnings and big news days, and more. A trade outside them is skipped for you
  only, you are told which filter skipped it, and the author and everybody else
  trade as usual.
- Change something deeper, like the rules, the tools, or the core exit, and your
  copy becomes your own separate workflow.

## Its life

![Make it, then on, then off if it hits the daily limit, then turn it back on, then removed](/atlas/docs/workflow-lifecycle.svg)

- **On** workflows run on their schedule or alert. **Off** ones do not.
- Hitting your **daily trade limit** pauses it until the next trading day.
- If you pause a shared workflow you made, everyone's copies pause too. Turning it
  back on brings them back.

Manage them in the [Workflows tab](#dashboard-workflows).

---

# What an alert can watch

Every alert is one of a handful of kinds. Pick the one that matches the thing
you actually want to be told about.

## Price

- **Price level cross**: the stock price crosses a level you set.
- **Price near greeks**: the price against a Greek wall. Either **gets near it**,
  so you hear about it before it happens, or **crosses it**: above the wall is
  the positive side, below it the negative side, and you can ask for one
  direction or either. A crossing follows the wall, which moves as the chain
  does. To watch a *fixed* price be crossed, use **Price level cross** instead.
- **Contract price cross**: the price of one option contract, rather than the
  stock.

## Dealer exposure

- **Greek exposure move** — everything about a Greek's dealer exposure lives in
  this one alert. Pick the Greek, then pick what counts as a move:

  - **Wall moves strike** (the default) — the strike carrying the most dealer
    exposure moves to a *different* strike. This is the wall shifting, and it is
    the one most people mean. Any move, either direction, against the last
    reading.
  - **Positive wall moves strike** / **Negative wall moves strike** — the same
    thing, but following only one side. Every exposure chart marks two walls:
    purple is the biggest positive exposure, yellow the biggest negative. These
    follow just the one you pick, where **Wall moves strike** follows whichever
    is larger and can hand over between them.
  - **Price crosses into negative exposure** (or into positive, or either way)
    — the gamma flip. Going up the strikes, a flip level is a strike whose
    exposure has the other sign to the one below it; this goes off when the
    PRICE crosses one, never when a strike changes sign under a price that has
    not moved.
  - **Moves or flips** — whichever happens first.

  A flip never goes off just because it starts on that side. It needs a real
  crossing between two checks, so an "into negative" alert set while the price
  already sits in negative exposure waits for it to reach positive and cross
  back.

## Volume and flow

- **Volume spike**: a stock's option volume jumps by the amount you set.
- **Top-volume contract rotation**: a different contract becomes the most traded
  one.
- **Options flow**: a big options trade comes through on your stock.
- **New top flow** and **Top 20 flow**: a stock breaks into, or drops out of, the
  market's most active options flow. These watch the whole market, so they need
  no stock.
- **Options ratio**: calls against puts. On open interest (checked once a day) or
  on the day's unusual flow (checked every hour). It goes off when the side in
  the lead flips, or when one side leads by the amount you set.

## Technicals

- **Technicals**: one indicator crosses another, like the price over the 200 EMA.

## Your own trades

- **My trigger acts**: one of your own triggers enters, exits, pauses or is
  deleted.

## Two settings worth knowing

**Fire once when the window opens.** Most of these watch for a *change*, which
means on a quiet morning they may not fire at all — and a workflow waiting on
one never runs. Turning this on fires the alert once at the start of its window
each day even with nothing changed, so a bound workflow gets that first look.

**A narrower window.** Alerts run through the session by default. Narrowing the
window is how you say "only in the first hour", and it also stops a busy signal
from firing all afternoon.

Set alerts up in the [Alerts tab](#dashboard-alerts).

---

# Folders

A **folder** groups your workflows so a long list stays readable. That is all it
does.

It is worth being explicit about what a folder does **not** do, because the name
suggests more than it is:

- It does not change how anything runs — no schedules, no alerts, no limits.
- It does not travel. Filing your copy of someone's workflow does not file
  theirs, and an author filing theirs does not touch yours. Everyone files their
  own.
- It does not group *other people's* things. A folder holds your own rows.

## Pausing or deleting a whole folder

The Pause and Delete buttons on a folder simply do the same thing to each
workflow in it, one by one — exactly as if you had opened each one. So pausing a
folder of shared workflows pauses their followers' copies too, for the same
reason it would have if you paused them individually. The folder adds no new
behaviour of its own.

## Sharing a folder

A folder can be made public, which puts it in Discover as a set. Only the
workflows inside it that are *themselves* public are shown — making the folder
public does not publish its contents.

Someone importing from a public folder takes a copy of each workflow one at a
time, the same as importing them individually. The folder itself is not shared
or linked; they end up with the workflows, not with your folder.

Folders live in the [Workflows tab](#dashboard-workflows). For the buttons and
what each one does, see [Using folders](#workflow-folders).

---

# Strategies

A **strategy** is your saved trading **playbook**: the plan and rules you want
Atlas to follow. You write it once and reuse it:

- Point to it in [chat](#dashboard-chat), like *"use my wheel strategy on MSFT."*
- Point a workflow at it so its choices follow your rules.
- Share it, or import someone else's.

## What is in it

- **Title**, a short name.
- **Content**, your rules in your own words, split into sections.
- **Who can see it**, just you or shared.

A **strategy** is know how, what you believe and how you like to trade. A
**workflow** is action, it runs on a schedule. A workflow can read a strategy, but
a strategy on its own never trades.

Manage strategies in the [Strategies tab](#dashboard-strategies).

---

# Alerts

An **alert** watches the market and goes off when your condition is met. On its
own it messages you on Discord. Attached to a workflow, it decides *when*
that helper runs. One alert can run several workflows and turn on several
triggers.

## What alerts can watch

- **Price**, like crossing a level or a big percent move.
- **Gamma and exposure**, like the king node — the strike with the most dealer exposure — moving to a new price.
- **Options flow**, like unusual volume and big trades.
- **Options ratio**, calls against puts.

See [What an alert can watch](#concept-alert-types) for every kind.

## When they run

- Alerts check the market during market hours (9:30 in the morning to 4:00 in
  the afternoon, Eastern time). You can make that window smaller.
- A workflow started by an alert has its own **Max runs per day**, on its
  Schedule step, so a busy alert cannot over trade your account.
- How many alerts you can have on at once depends on your
  [plan](#plans-and-billing).

## Alerts and shared workflows

If you use someone's shared workflow, your copy uses the **author's** alert by
default, so you trade on the same signal they do. You can also point your copy at
**your own** alert without leaving. Your alert then messages you on your own
window, while the copy keeps trading on the author's signal.

Manage alerts in the [Alerts tab](#dashboard-alerts).

---

# Triggers

A **trigger** is the smallest trading piece: one "if this, then buy or sell"
order. Like *"buy 1 SPY at the market if the price drops to 550."* When the
condition is met, Atlas places the order with your broker and then handles the
exit (stop loss and take profit) you set.

## What can start a trigger

- **Just the trade.** The order is set up now and waits for the entry you gave
  it, the classic "if the price hits X" order.
- **Something starts it.** A **schedule** (a set time), an **alert** (when it
  goes off), or **both**.

## More than one trade

A trigger can hold several trades, and they can be linked: **when this trade
fills, cancel that one**, or **when this trade fills, start that one**.

## Check first, then place

Trading tools always let you **check first, then place**. One tool shows you
exactly what will be set up. Another one places it. The same goes for one off
orders.

A **trigger** is a fixed rule you set up front. A **workflow** is an AI that
*decides* what to place on each run. When a workflow decides to trade, it makes
triggers. So triggers are the layer under the automation.

Manage single triggers in the [Triggers tab](#dashboard-triggers).

---

# Taking profit in stages

A trade does not have to be all-or-nothing on the way out. A **scale-out
ladder** sells part of the position at each of several targets — so you bank
something early and still leave a runner on.

## What each rung has

- **A target** — either a percentage from what you paid for the contract, or a
  dollar price on the stock. Every rung in one ladder uses the same one; you
  cannot mix them.
- **An amount** — a number of contracts, a percentage of the original position,
  or *the rest*.
- **A trailing stop** (optional) — where your stop-loss moves to once the
  *previous* rung fills. So it protects the run into the next target. Your
  general stop-loss covers the trade up to the first one.
- **A price to sell at** (optional) — the contract price that rung's sell is
  submitted at. Leave it blank and that rung sells at whatever the market is
  paying when the target hits.

## The amounts have to add up

The rungs must close exactly what you opened. End with *the rest*, or make the
fixed amounts add up to your position. Atlas refuses a ladder that would leave
part of the position with nothing to close it — "8 contracts in, 6 + 1 out" is a
mistake, not a setting.

## A price you set is a price we send

If you put a price on a rung, that is what goes to your broker. Nothing moves it
to follow the market. If the contract never reaches it, that rung simply does
not sell and keeps waiting.

That is safe by design, not by accident: **your stop-loss is always a market
order**, so the position stays protected however the take-profits are priced. A
waiting rung is also cleared by a close time if you set one, or by Atlas itself
if you have it reviewing the ladder.

## Letting Atlas manage the ladder

Turn on the review and Atlas reconsiders the remaining targets each time a rung
fills — it can move them, tighten the stop, or close the rest early if the
reason for the trade has gone. It sees what it decided last time, so its
thinking carries across the trade rather than restarting at each rung.

If you follow someone else's workflow, **their** review runs and its decision
reaches you at the same moment — you trade your own amounts on their targets.

---

# Signals: posting a play, and taking one

A **play** is a call you make yourself. You pick the contract, the entry, the
targets and the stop, and you post it. No AI decides any of it — that is the
difference between a play and a [workflow](#concept-workflows).

There are three places a play can be.

## Your own groups

A **signal group** is a place of your own to post plays to. It starts private.
Everyone following the group sees what you post there.

- **Make public** lets anyone on Atlas follow the group for free. Its plays also
  show on the community board.
- To charge for a group instead, put a price on it in the
  [Marketplace](#dashboard-marketplace).

## Groups you follow

When you follow somebody's group, **Trade settings** on that group decides what
happens with each play they post:

- **Asked first** is how every follow starts. Nothing is placed. Each play waits
  for your yes.
- **Take every play automatically** places each play in your account as it is
  posted. You choose the broker account, and either the most to spend on one
  play or how many contracts. Switching this on also places the plays that
  group already has open, and tells you how many.
- **Advanced filters** skip the plays you do not want: a kind you turned off,
  a wide bid/ask spread, a low rating, over a price, other symbols, outside your
  hours, and more. A play you take by hand is never filtered.

## Community picks

One open board that everyone shares. Anybody can post to it, whatever plan they
are on.

- **Reading** other people's plays needs a paid plan. On a free plan you still
  see the plays you posted yourself.
- **Nothing on the board ever trades for you on its own.** A group's followers
  chose to be traded for; a stranger's play has nobody's permission behind it.
  So a play sits there until you press **Take now**, which places it in your
  account at the price called.
- **Up to 20 plays a day each**, so nobody can bury the board. It resets at
  midnight New York time. Your own groups have no limit.

Take now shows up on any play you are not already in. If the play has already
entered for somebody, the button reads **Take it late**: you get in at the
market price now, which is a different trade from the one that was called, and
Atlas says so before you confirm.

## Once you are in a play

The play belongs to the person who called it. Only they can take a target early
or move the stop and the targets, and a move reaches everyone in the play.

If you followed or took the play, you have one button: **Close all**, which
closes your own position now.

When the caller closes the play, it closes for the people in it too. To stay in
until your own stop or target instead, switch off **Let the caller close my
position when they close the play** in the Signals settings.

## What uses a request, and what does not

Your plan gives you a number of **requests** a month. Plays mostly do not touch
them, because a Marketplace subscription already pays for what it covers:

| Doing this | Uses a request |
| --- | --- |
| Posting a play, to a group or the board | No |
| A play being placed for you in a group you pay for | No |
| Answering yes to a play from a group you pay for | No |
| A premium workflow you subscribe to running | No |
| **Taking a play off the community board** | **Yes, one** |
| **Taking a play from a public group** | **Yes, one** |

Those two are the exception because nobody is paying anybody for them: the plays
are free to read and free to post, so the one press that turns somebody's call
into your order is the part your plan covers.

You are only charged when an order actually reaches your broker. A play that
was skipped (no broker connected, or one contract costs more than your budget
for one trade) costs you nothing.

## Your broker set once, your size set where you use it

Open **Connect → Brokerages** and press **Make default** on the account you
want. Plays, new workflows and new triggers go to that account unless you name
another. It starts empty: an account that places real orders without asking
each time is a decision you make once, deliberately.

There is no budget for a whole account. The size is set where it is used: on a
workflow's trade card, on a trigger, on the play you take, or in the Trade
settings of a group you follow. Naming an account on a single play always beats
the default, and so do the Trade settings on a group. See [Connect](#dashboard-connect).

## From Discord

`/signal` posts a play from Discord, to a group or to the community board,
which is offered to everyone in the group list. The form has a **Trade for me
too** button for taking your own call, and a broker picker when you have more
than one account. The account never appears in the posted call: what you traded
in is yours, not the channel's.

## From the API, the CLI, or your AI

The same plays, so one posted by a person and one posted by an assistant are the
same thing with the same rules:

| Tool | What it does |
| --- | --- |
| `Signal-Groups` | Where you can post: the board plus your own groups. |
| `Signal-List` | The board's plays, or one group's, newest first. |
| `Signal-Post` | Post a play. Leave `group_id` empty for the board. |
| `Signal-Update` | Change a play that is still open, instead of posting it twice. |
| `Signal-Take` | Place somebody's play in your account. Real order. |
| `Signal-Discover` and `Signal-Follow` | Find public groups, and follow one. |
| `Signal-Pending` and `Signal-Answer` | The plays waiting for your yes, and your answer. |
| `Signal-Trade-Settings` | See or change how plays are traded for you: the account, and each group with its own budget. |
| `Signal-Group-Create` and `Signal-Group-Update` | Make a group, rename it, make it public. |

The full list is under [All tools](#mcp-tools).

:::note
**Your AI does not need to attach a broker.** When you have a default account,
Atlas uses it for every play you post or take, and there is nothing for the
assistant to decide. It should only pass an account when you name one for that
play, or when you have no default: `Signal-Trade-Settings` with nothing filled
in tells it which. And it only ever posts the play you dictated: an assistant
never invents a call or takes one you did not ask for.
:::

---

# Working on a workflow together

Most workflows are one person's. Some are not: you might build one with someone
whose read on the market you trust, or share one you wrote and keep improving it
with the people running it.

## Suggesting a change instead of saving one

Anyone you invite onto a workflow can **suggest a change**. They edit it the way
they normally would — the instruction, the tools, the days it runs, the trade —
but instead of Save they choose **Request change**. Nothing happens to their own
copy: it keeps running exactly as it was.

You see the suggestion as a plain before-and-after of what they changed, with
their note explaining why. You can take the whole thing, take one part of it, or
turn it down. **Only a person can decide that.** An AI assistant can read a
suggestion, discuss it, and write one for you — it can never take one or turn
one down on your behalf.

Whoever suggested a change can also take it back while it is still waiting.

## Everyone can talk, not everyone can suggest

Anyone **running a copy** of a workflow can comment on a suggestion. They are the
people the change will actually reach, and "I'm already in a trade on this" is
exactly what the author should hear first. Suggesting a change is limited to the
people invited onto it.

## The changelog

Every real change to a workflow lands in the same place, whether it came from a
suggestion or from the author just saving. Saving asks what changed — optional,
but it is what makes the history readable later.

The list shows three things: changes **waiting**, changes that were **taken**,
and changes that were **turned down**. A change that was taken shows exactly
which parts of it were taken, since you can accept some and not others.

What is *not* recorded: your own settings. Your contract size, broker, alert,
daily limit and notification choices are yours on your own copy, so changing one
is nobody else's history.

## Whose workflow is it?

If you took a copy of someone else's workflow, one checkbox decides this:
**taking their updates**.

- **On** — you are running their strategy. They are the author, you see everyone
  working on it, and you can suggest changes to them.
- **Off** — you have taken it in your own direction. It is your workflow now,
  you are the author, and the people working on it are yours.

You can change your mind either way. Turning it back on puts you back in their
room with everyone visible again.

Invite people from the **Collab** section of the workflow.

---

<!-- ==== Using the dashboard ==== -->

# Using the dashboard

The [dashboard](/atlas/dashboard) is where you build and manage everything by
hand. The menu on the left switches between areas. The main panel shows the one
you picked. It opens on Chat.

## Down the left

![The side panel: Setups, Local, Connect and More, then Recents, then three widgets (a workflow, an alert and an open trade), beside the Workflows tab](/atlas/docs/side-panel.png)

| Where | What it is for |
| --- | --- |
| [Chat](#dashboard-chat) | Ask Atlas anything. Pressed while you are in a chat, it starts a new one. |
| **Setups** | Everything you build. Five sub tabs, below. |
| [Connect](#dashboard-connect) | Your broker accounts, and your own connectors. |
| **More** | [Local](#dashboard-local) (your own computers running Atlas Studio), [Templates](#dashboard-templates), [Marketplace](#dashboard-marketplace), any button that did not fit in the menu, and **Arrange**. |
| **Recents** | Your last two chats. The three buttons beside the word open all of them (**See more**), start a new [chat](#dashboard-chat) and refresh the list. |
| **Widgets** | What you want to keep an eye on, live. See below. |
| **Your name** (bottom) | Opens your [Profile](#dashboard-profile). The **...** next to it has your plan's usage, your accounts, **Guide** (this guide, inside the dashboard), dark mode and sign out. |

If you use Atlas Studio (a computer is linked, or you are in Studio's Cloud
mode), **Local** comes after **Chat**, then **Connect**, and **Setups** is in
**More**, until you arrange them yourself.

On a phone the first three buttons and **More** sit along the bottom of the
screen. Recents, your widgets and your name are in the side panel behind the
button at the top left. It covers the whole screen; swipe left anywhere on it,
or press its X, to put it away.

## Widgets

Under Recents, the **+** beside **Widgets** asks what you want to see: **My
trades**, **Signals**, **Alerts** or **A workflow**, then all of them or just
one (one workflow, one signal group, one alert, one trade or one play). Each
widget is drawn live: a trade shows where it is between its stop and its next
target, an alert what it saw the last time it went off, a workflow when it runs
next and its last message.

The buttons on a widget are the dashboard's own: **Take profit** and **Close**
on your own trade, **Close all** on one you follow, **Run now** on a workflow.
Each asks before it does anything. Pressing an alert or a play opens it as a
page of its own.

You can have up to 20. Press and hold one (or right click) for **Change**,
**Arrange** and **Remove**. Arrange lists your widgets: drag one by its handle
to where you want it (or use the arrow keys), and **Back to how it came** puts
the newest on top again. The order you give them stays; a widget you add later
goes under them. Your widgets are saved to your account, so they are the same on every
device and in the phone apps.

## Make the menu yours

Press and hold (or right click) almost anything, such as a tab, a workflow, a
trigger, an alert, a folder, a signal group or a project, and choose **Add to
panel**. It becomes a button in the menu, with the icon of what it opens; the
round button before its name picks another icon (search by name or by what it
means). Hold a button for **Name and icon** to change either later.

What a button opens is a page of its own: a workflow, a signal group or one
alert, with its own buttons and a **Refresh**, and nothing of the list it
came from.

The menu shows the first three and the rest are under **More**.
**More → Arrange** lets you put the buttons in the order you want and pick the
page the dashboard opens on. The menu is saved to your account, so it is the same on
every device.

## Tabs in your order

Every row of tabs (Setups, Signals, Profile, Connect, a project's tabs, and the
rest) can be put in the order you like: drag a tab to its place, or hold it (or
right click) for **Arrange**, where **Move to More** takes a tab off the row
and **Back to how it came** undoes it all. The first tab is the one that
screen opens on. A **More** shows at the end of a row only when something is
in it. The order is saved to your account.

## Getting back

To go back to a list, press the tab you are on again. Pressing **Workflows**
while reading a workflow (or its Performance, a version, a folder or its Files)
brings back the list of workflows; the same goes for Triggers, Alerts, Signals,
Local and Marketplace. So the pages that only show something have no **Back**
button. Forms keep theirs, so nothing you typed is thrown away.

## Inside Setups

| Sub tab | What it is for |
| --- | --- |
| [Workflows](#dashboard-workflows) | Helpers that keep running. |
| [Signals](#dashboard-signals) | Plays people call by hand, yours and other people's. |
| [My Strategies](#dashboard-strategies) | Your trading playbooks. |
| [Alerts](#dashboard-alerts) | Market watchers that message you and start workflows. |
| [Triggers](#dashboard-triggers) | Single "if this, then trade" orders. |

[Performance](#dashboard-performance) is not a tab of its own. It opens from the
**Performance** button on any trading workflow.

## When it updates

- **Workflows** update on their own: every few seconds while one is running, and
  about three times a minute otherwise.
- **Signals** update on their own while the market is open and a play is live.
- **Performance, Marketplace, Strategies, Alerts and Connect** load once when
  you open them. Click **Refresh** to load them again.

---

# Workflows tab

The Workflows tab shows your helpers as cards. This is where you make and manage
them.

![The workflows list with status tags, a daily limit bar, and buttons on each card](/atlas/docs/workflows-list.png)

## Workflows, Agents, Folders

The slider at the top shows one of three at a time:

- **Workflows**: your workflow cards (the ones not in a folder).
- **Agents**: your agents.
- **Folders**: your folders. Open one to see the workflows inside.

It starts on Workflows and remembers the one you picked last on that device.

## Workflow or agent?

| | Workflow | Agent |
| --- | --- | --- |
| What it is | A trade plan | A helper with a job title |
| What it does | Runs on an alert or a schedule, then places a trade, posts a play, or holds a run for you to check | Watches, checks and tells you. It looks after things over time |
| How long it works | One run at a time, then it stops until the next alert or time | All the time, on its own, waking when something it watches happens |
| Examples | "Buy SPY calls when the gamma wall moves", "at 9:35 send a QQQ play to my group" | **Risk Manager** looks after your open trades, **Market Analyst** reads SPX each morning and checks its own calls, **Account Manager** tells you when a workflow breaks or is not doing what it is meant to |
| Talking to it | You change its form | You write to it in the box on its page, or answer its notification |

Want both? Make a workflow for the trades. Your Risk Manager already looks after
what it buys.

## Reading a card

Each workflow card shows:

- The **name** and a tag: **active** (running) or **paused** (stopped).
- What starts it: a schedule (*"Runs every weekday at 2:30 PM Eastern"*) or an alert (*"On alert: SPY king node shift"*).
- A **daily limit bar** (*"Runs today 0/3"*) when a daily trade limit is set, plus a **daily limit reached** tag once it is spent. The bar turns orange at the limit.
- A **subscribed** tag if it is a copy of someone else's workflow, **collab** if you work on it with others, and **N behind** if the author has changed it since.
- **waiting for you to place** when a run is held for your review.
- A red **Issues with this workflow** tag when something stops it from running, with the reason in plain words.

While a workflow is running, its card shows how far it has got.

## Buttons on a card

| Button | What it does |
| --- | --- |
| **Run now** | Runs it right away. Running by hand does not count against the daily limit. |
| **Preview** | Shows when a run is waiting for your review. Open it, then **Place it** or **Throw it away**. |
| **Pause / Activate** | Stops or starts automatic runs. Turning it on resets today's count. While a run is in progress this button is **Abort**, which stops that run. |
| **More → Trade settings** | The first line of **More**, on your own workflows and on copies, live or paused: the account, the size (the same for all trades, or per trade), auto sizing, filters, **Take everything at** a target, how your exits split, and the messages you get, with one **Save**. It always matches the workflow form. See [Trade settings](#trade-settings). |
| **More → Performance** | See the [profit and loss](#dashboard-performance). On trading workflows. |
| **More → History** | Every saved version. Open one to read it or go back to it. |
| **More → Files** | The files its runs keep. It opens on **Workflow Charts**, the charts its runs drew, a folder per day, newest first; beside them, anything else its runs saved, such as a CSV of what it found (it shows as a table). You can open and download them. Only its runs, and the AI assistants you use with Atlas, change them. On a copy you see the author's files and your own. |
| **More → Apply updates** | On a copy that is behind: take the author's latest edits. |
| **More → Stop following** | On a copy: keep it as it is today and stop taking the author's changes. **Follow again** undoes it. |
| **More → Reset overrides** | On a copy where you set your own size or stop: go back to the author's. |
| **More → Delete** | Removes the workflow. |

At the top of the tab: **Refresh**, **Discover & Import** (browse shared and
ready made workflows, and take a copy), **New folder** (see
[Folders](#workflow-folders)), and **New workflow** (opens the
[workflow form](#workflow-create)).

## Inside a workflow

Open a card and pick a view:

| View | What it shows |
| --- | --- |
| **Trades** | The trades it is in right now. **Close all** closes one. On your own workflow you can also **Take profit now** and move the stop and targets. |
| **Recent runs** | Each run, and why it made the choice it did. |
| **Diagram** | A picture of its flow. |
| **Form** | The [workflow form](#workflow-create), to change it. |

## Recent runs

![An opened run: what Atlas thought, what it worked out, the trade it set up, and the two charts it drew](/atlas/docs/workflow-runs.png)

Each line is one run: when, the stocks it traded, how many charts it drew, and
a tag (**Triggered**, **No action**, **Review** when it waits for you, or
**Error**). Open one to see, in this order:

- What Atlas thought, in its own words.
- What it **worked out**: any sum it did, such as how many contracts fit your
  budget, with the exact answer. **Show code** shows how it got there.
- Each trade it set up, as one line: *SPY Buy 770C 10/15/26 · 4 contracts*, then
  when it enters, the stop, the targets and when it gets out.
- The charts it drew, in the dashboard's light or dark look. Click one to see
  it full size. They are kept for 90 days.
- The tools it read, in small type. One that failed is in red.

---

# Using folders

A folder is a way to tidy your Workflows list. Nothing more: putting a workflow
in one does not change when it runs, who follows it, what it trades, or its
daily limit. It only changes where you see it. See
[Folders](#concept-folders) for the whole of what a folder does and does not do.

## Making one and filling it

**New folder** at the top of the Workflows tab makes one. Folders show as tiles
above your loose cards. Click a tile to open it, then:

| Button | What it does |
| --- | --- |
| **Add workflows** | Pick from the workflows that are not in a folder yet. |
| **New workflow** | Makes a new one, already in this folder. |
| **More → Rename folder** | Change its name. |
| **More → Make folder public** | Let other people find it. See below. |
| **More → Pause all** | Turns off every workflow in it, in one go. |
| **More → Disband folder** | Removes the folder. **The workflows are not deleted** — they go back to being loose in your list. |
| **More → Delete all workflows** | Deletes the workflows themselves, then the folder. This one cannot be undone. |

To take one workflow out, open the folder, select it, and press **Remove from
folder**. A workflow sits in **one folder at a time**, so to move it somewhere
else, take it out first.

## Folders are yours

If you follow someone else's workflow and file your copy, the author sees
nothing. If the author files theirs, your copy does not move. Each person tidies
their own list.

## Sharing a folder

**More → Make folder public** puts it in **Discover & Import** for everyone else.
They can take a copy of the workflows inside — one copy per workflow, exactly as
if they had imported each one. Only the workflows you have shared show up there;
a private one stays private even inside a public folder.

:::tip
You can ask Atlas to do this in [chat](#dashboard-chat): *"put my SPY workflows
in a folder called snipers"*. It never files or moves anything unless you ask.
:::

---

# Make or edit a workflow

Click **New workflow** (or open a card) to open the form. The steps run across
the top: **Basics, Schedule, Input data, Reasoning, Trades, Notify, Collab**.
Some steps only show when they apply: **Output** on a workflow that only
analyses, **Trades** on one that trades or sends you the order, and **Plays** on
one that sends plays. The same form is used to make and to edit. You can save
from any step.

## Basics: name, job, broker

![The Basics step of the workflow form](/atlas/docs/workflow-basics.png)

| Field | What it does |
| --- | --- |
| **Workflow name** | A short name for the card and history. |
| **What should this workflow do?** | Tick one of **Trade it** (places real orders), **Send me the order** (messages you the order to place by hand) or **Just analyse** (only thinks). **Create alerts** and **Send plays** can be ticked as well. |
| **Start paused or active?** | On workflows run on their own on their schedule or alert. |
| **Sharing** | **Private** (only you), **Unlisted** (anyone with the link) or **Atlas-public** (listed in Discover for people signed in). A shared workflow has a link you can copy. |
| **Which broker should it trade in?** | The linked account orders go to. It starts on your default account. See [Connect](#dashboard-connect). |
| **Let me review each run before it places** | The workflow runs in full, then waits for you before anything is placed. See [Workflows](#concept-workflows). |
| **Keep this one personal** | For a workflow about your own account. Anyone who copies it gets a copy of their own that does not follow yours, so your runs never trade in their account. |
| **Auto-apply the author's updates** | On a copy: take the author's changes as they make them. |

On a shared workflow you can also let the people who copy it have their trades
closed when you close yours. On a copy, the same box reads **Let the author close
this trade for me**.

## Schedule: when it runs

![The Schedule step: Schedule, Weekdays, the days as chips, Specific times, Add another time](/tutorial-files/nov7/schedule-computer.jpg)

Pick how it starts: a **Schedule** (a set time), an **Alert** (when a market alert
goes off), **Both schedule and alert**, or **Manual**. A schedule is picked in
rows: **Weekdays**, **Every day**, **Weekends** or **Once**, the days as round
chips, then **Specific times** (each time a box, **+ Add another time**) or
**Every so often** (at least 2 minutes apart). Then the timezone and a **Max runs
per day**. Hitting the limit **pauses** it until the
next trading day. Running it by hand is always allowed.

**Manual** means nothing starts it but you. No schedule, no alert: it sits there
until you press **Run now**. If you switch back to a schedule later, the times you
had are still there.

:::note
On a copy, the timing comes from the author. You can still add **your own** alert.
It messages you on your own window without changing the copy.
:::

## Asking you some questions first

A **Manual** workflow can ask you a few things before it runs. Tick **Ask me some
questions before it runs** and write them. Press **Run now** and you get the form;
what you fill in goes to Atlas as part of the instruction for that one run.

Each question has an answer type:

| Type | The person gets |
| --- | --- |
| **Free form** | A box to type in, short or long. |
| **Date** | A date picker. |
| **Time** | A time picker. |
| **Pick one** | Your choices, one selectable. |
| **Pick several** | Your choices, any number selectable. |

**Pick one** and **Pick several** need at least one choice. Tick **Must be
answered** on anything the run cannot do without, and the form will not submit
until it is filled in.

Submitting **always** stops for review, whether or not you use *Let me review each
run*. You typed the inputs, so you see what they produced before anything is
placed. Accept it or throw it away.

The questions travel with the workflow. Anyone who imports it is asked the same
things when they run their own copy — their trades still come from your runs, as
they always did.

:::note
Only on **Manual**. A scheduled or alert-driven workflow starts on its own, with
nobody there to answer, so there is nothing to ask.
:::

## Input data: what Atlas looks at

![The Input data step: the tools Atlas can use, each with a box for your notes](/atlas/docs/workflow-tools.png)

Pick the tools Atlas can use on each run: quotes, the options chain, gamma, flow,
charts, company numbers, and more, plus the tools of any
[connector](#dashboard-connect) you added. The workflow only **looks** with
these. It does not trade from this list (you set trading in the Trades step).

Under each tool is a box, **Notes for this tool**. Write a sentence or two on
what Atlas should ask it for and what to pay attention to in the answer. A tool
with a note is used the way you meant. One without is used on a guess.

## Output: what it does at the end

Only on a workflow set to **Just analyse**. These are the tools it uses **after**
it has decided: post a play, set an alert, message you, or act on one of your
connectors. Each has the same **Notes for this tool** box: say when to use it
and what to send. Leave the step empty for a plain write-up.

![The Output step: pick what Atlas does once it has decided, with notes for the tool](/atlas/docs/workflow-output.png)

## Reasoning: your rules

![The Reasoning step: your rules and a strategy](/atlas/docs/workflow-reasoning.png)

Choose **Write my own** and write the plan in your own words, the rules Atlas
follows every run. Or choose **Use one of my strategies** to point it at a
[strategy](#dashboard-strategies).

**Keep a journal** is on this step too: **Atlas writes it**, **I write it**, or
**No journal**. When Atlas writes it, you say what to write down and when: after
every trade, after an alert goes off, after every run, or once a day, every 3
days, every week or every month. **Let the journal update your instructions**
lets what it learns change the plan.

## Trades: what it trades

![The Trades step: the trade card, contract details, entry and exit](/atlas/docs/workflow-trades.png)

First choose who names the trades: **I'll name the trades** (one card per stock
you want traded) or **Atlas picks the tickers** (one card, used for every stock
Atlas chooses on a run).

On a card, lock in what you want fixed and let Atlas pick the rest (each field is
set to **AI** by default. Tap to set a fixed value):

| Group | Fields |
| --- | --- |
| **What to trade** | Stock symbol, **Options** or **Stock**. |
| **Contract** | Call or put, strike, expiry, number of contracts. Each can be AI or fixed. |
| **Size by money** | **Most to put into this trade**, in dollars. Atlas then works out how many contracts fit, and the contract count reads **From your budget**. |
| **Entry** | One buy or several, order type, price to enter. |
| **Exit** | How to exit, a stop loss (a fixed one, or **Trailing %**, which follows the best price since entry and only tightens), and a single take profit or a [scale out ladder](#workflow-exits). |

## Plays: what it posts

Only on a workflow with **Send plays** ticked. It works like the Trades step, but
what it makes is a [play](#concept-signals) posted to the community board or to
one of your groups.

:::tip
On a **copy**, the size and the stop loss and take profit are **yours**. You can
change them and stay linked. Change the rules, the tools, or the core exit and the
copy becomes your own.
:::

## Notify: how it tells you

![The Notify step: where the message goes (Discord, phone, its widget) and how it reads](/atlas/docs/workflow-notify.png)

Under **Send the message to**, pick where each run's message goes: **Discord
DM**, **Phone notification**, and **Its widget in the side panel**. Each is its
own switch. Then, if you want, paste how it should read. Order messages show
the entry and exit prices, why it exited (stopped out, take profit, AI exit, or
time), and the profit or loss.

## Collab: who works on it with you

Invite people onto the workflow and give each a part: change it, decide on
suggested changes, manage its trades, or run and pause it. See
[Working on a workflow together](#concept-collab).

---

# Exits and the scale out ladder

In the **Trades** step, set **Exit type** to **Scale out (multiple targets)** to
sell in stages instead of all at once.

![The scale out ladder with three take profit levels, trailing stops, and the loop switch](/atlas/docs/workflow-exits.png)

## How a ladder works

Each level has a **target**, an **amount to sell**, and an optional **trailing
stop** that turns on after the level before it fills.

| Setting | Choices | Notes |
| --- | --- | --- |
| **Target as** | **Percent** or **Price** | Set it on the first level. Every later level uses the same one. |
| **Target** | a number, or **AI** | AI lets Atlas pick the level while it runs (loop workflows). |
| **Amount to sell** | a number, a percent, or **remaining** | The last level should sell **remaining**, so nothing is left over. |
| **Move stop to** | a level, breakeven, or **keep** | The trailing stop that guards the run into the next target. |
| **Loop** | on or off | With loop on, Atlas checks again after each fill and can move later targets or exit early. You get a message when it changes something. |

## Rules the form checks for you

- **One target type.** Every level is all percent or all price. You cannot mix.
- **Cover it all.** The amounts must add up to the whole entry. A **remaining**
  amount always covers the rest. Fixed amounts must add up to the size, and
  percents must add up to 100.
- **Fast moves.** If the price jumps past a few targets at once, they all fill
  together, so you do not miss one.

:::tip
Each time the loop **actually changes** your trade (moves a target or closes the
rest early), it uses **one request**, the same as opening a trade. A check that
leaves the trade alone is free. See [Plans and how you get charged](#plans-and-billing).
:::

---

# Signals tab

A **signal**, or a **play**, is a call a person makes: buy this contract, here,
take profit there, get out at this stop. No AI decides any of it — someone fills
in the form and posts it. That is the whole difference between a play and a
[workflow](#dashboard-workflows). See
[Signals](#concept-signals) for how one works end to end.

Nothing on this screen trades on its own. A play sits there until you press
**Take now**.

## The four tabs

| Tab | What is in it |
| --- | --- |
| **Personal** | Your own signal groups, and the groups you follow. |
| **Community picks** | The open board. Anyone can post, anyone can read. |
| **Public plays** | Groups other people have made public. **Follow** one to add it to your Personal tab. |
| **Plays taken** | Every play you have money on: waiting to fill, and running. |

## The community board

![The community board: one row per play, with entry, targets, stop, who called it, and what happened to your order](/atlas/docs/signals-community.png)

One row per play. Reading it left to right:

| Column | What it means |
| --- | --- |
| **Play** | Buy or sell, the stock, the strike, call or put, and the expiry. |
| **Entry** | Where the caller wants in. `premium` means the option's own price. `stock` means it waits for the stock to reach that price. |
| **Targets** | Where to take profit. `40%, 90%` means the first slice sells up 40 percent and the rest up 90 percent. |
| **Stop** | Where to get out if it goes the wrong way. |
| **By** | Who called it. |
| **Score** | How strongly they rate it, 1 to 10. Their opinion. It never sizes or filters anything. |
| **Status** | What happened to **your** order on it. What anyone else did is theirs. |

**Today / 7d / 30d / All** narrows how far back you are looking. It opens on
Today, because a board of same day plays is something you check this morning.

## Taking a play

**Take now** asks you a few things, then places a real order in your account:

- **How much.** Either **How many contracts?**, or switch on **Size by budget**
  and give **Most to put in**, in dollars. Atlas then works out how many fit.
  Yours, not the caller's: their size sizes them.
- **How it comes off**, on a play with more than one target: how many contracts
  to sell at each target. The last target takes the rest.
- **Broker account.** It starts on your default account.

If the play has already entered for somebody, the button reads **Take it late**.
You get in at the market price now, not at the price that was called.

Once you hold it, the button becomes **My order**, which opens the same sheet so
you can change the size, or **Cancel mine** while nothing has filled yet.

When the play is running, you have **Close all**, which closes your own position
now. Taking a target early and moving the stop or targets are for the person who
called it. See [Signals](#concept-signals).

:::warning
Taking a play places a **real order** in your broker account. Nothing on the
board does that on its own, and nobody else can do it for you.
:::

## Your own groups

![The Personal tab: your signal groups, with the plays inside each one](/atlas/docs/signals.png)

A **signal group** is a folder of plays with your name on it. Make one with
**New group** in the header, then **Post a play** into it. Everyone following
the group sees what you post.

- **Post a play** opens the same form the board uses: stock, contract, entry,
  targets, stop, and why.
- Still open? **Edit** it rather than posting a second one, so the same trade is
  not sitting on the board twice. Once somebody has filled you can still move
  the stop and each target; the contract, the entry and the size stay.
- **My order** is on your own plays too: your size (which is the play's size),
  your account, and how many of yours come off at each target.
- **Close** sells it for everyone riding it, unless they chose to stay in (see
  Settings below). **Delete** pulls it off the board and cancels the waiting
  orders, and only works before anyone has filled.
- **Performance** shows the group's closed trades, as the caller's record or as
  your own trades.
- **Trade settings** (the sliders) sets **your own order** on each play you
  post: your account, your size when a play says none, auto sizing with your own
  circuit breaker, and **Take everything at** a target. A tripped breaker stops
  only your orders; the plays still go to your followers. See
  [Trade settings](#trade-settings).
- **More → Make public** lets anyone on Atlas follow the group for free. Its
  plays then show on Community picks too. **Make private** undoes it.
- To charge for a group, put a price on it in
  [Marketplace](#dashboard-marketplace).

## A group you follow: Trade settings

Each group you follow has a **Trade settings** button:

![Trade settings for a group you follow: take plays automatically, which broker, how much per play, auto sizing, filters, take everything at](/tutorial-files/nov7/filters-row-phone.jpg)

| Setting | What it does |
| --- | --- |
| **Take every play automatically** | Off, each play waits for your yes. On, each play is placed for you as it is posted. |
| **Use my default broker** | Or pick another **Broker account** for this group. |
| **How each play is sized for you** | **Contracts** (a count for each play) or **Budget** (**Most to put into one trade**). |
| **Auto sizing** | **Change my size** (with a budget: less after losses, more after wins) and the [circuit breaker](#circuit-breaker), each its own switch. |
| **Take everything at** | **Off**, or a target (**TP1**, **TP2**, ...): when it fills, everything you still hold comes out; later targets do nothing for you. |

Saving with automatic on places the plays that group already has open, and tells
you how many.

### Advanced filters

**Advanced filters** in the same box opens a page of its own: which of the
group's plays are taken for you. Leave a field empty and it does not filter. A
search box at the top finds one by name. **Save** keeps them, **Clear all**
empties the page. The most used come first:

| Filter | A play is skipped when |
| --- | --- |
| **Trade types** | It is a kind you did not pick: calls, puts, shares or spreads. |
| **Max bid/ask spread** | The spread is wider than this, as a % of the middle price, at the moment it would go in. Shares use the stock's; a spread checks every leg. |
| **Min rating** | Its rating is lower. A trade with no rating is not skipped by this one. |
| **Min open interest** / **Min volume today** | Lower than this. Open interest is for options; volume is the stock's for shares. |
| **Max / Min price per contract** | One contract (one share, a spread's net) costs more, or less. |
| **Days to expiry** | Days to expiry, 0 for the same day: **Only these** or **Skip these**. Options only. |
| **Max move past entry** | The price already moved this far past the entry it was called at. |
| **Max play age** | The trade is older than this many minutes. |
| **Skip near earnings** | The company reports within this many days. |
| **Big news days** | Today is an FOMC, CPI or jobs report day. |
| **Max trades a day** / **Max open at once** | You already took this many today, or have this many open from the group. |
| **IV range** / **Delta range** / **Max theta a day** | Options only: outside your IV or delta, or more time decay a day than this. |
| **Strike range** | Options only, every leg: **Only these** or **Skip these**. |
| **Only these symbols** / **Time window** / **Days** | Not on your list, outside your hours (your own time zone), or another day. |
| **Max stock move today** / **Max gap at open** | The stock already moved, or opened, more than this % from yesterday's close. |
| **Day direction** | **With the day**: calls only on green days, puts only on red. **Against**: the opposite. Bought shares count as calls. |
| **VIX range** / **Stock price range** | The VIX, or the stock, is outside it. |
| **Max buying power used** | The trade would use more than this % of what is available. |
| **Pause after a loss** | A losing trade from the group closed less than this many minutes ago. |

A skipped play is not placed or offered to you, and you are told which filter
skipped it. A number Atlas cannot read at the moment of entry never skips a
play. A play you take by hand with **Take now** is never stopped by them: if it
breaks any, the sheet says which in a yellow note and its button reads **Take
anyway**. The same
filters are on a group you pay for (Marketplace → My subscriptions) and on
Community picks (**Settings**), where they decide which picks you are told about.
Every filter, with what it works on (calls, puts, shares, spreads), is on
[Advanced filters](#advanced-filters). A loss or profit limit for the day is the
[circuit breaker](#circuit-breaker).

## Settings

**Settings** in the header holds:

- **Message me on Discord when a community pick is posted.**
- **Let the caller close my position when they close the play.** Switch it off to
  stay in until your own stop or target.
- **How your exits split**: follow the caller's split, leave more on for the last
  target, the same at each target, or ask me every time.
- **Advanced filters** for Community picks: only hear about the picks that
  match.

The account your plays go to, and the most one trade may spend, are set once in
[Connect → Brokerages](#dashboard-connect).

---

# Marketplace

The Marketplace is where you subscribe to somebody else's work, and where you
charge for yours. Two things are for sale: a **premium workflow** that trades in
your own account, and a **signal group** whose calls you copy.

## Browse

![The Marketplace browse tab, with premium workflows and signal groups](/atlas/docs/marketplace.png)

Each row is one thing for sale, with the record behind it: total profit, the
percentage, the win rate, and a line of how it got there. Those are the same
numbers the workflow's own [Performance](#dashboard-performance) page shows, so
you can check them.

| Button | What it does |
| --- | --- |
| **All trades** | Every trade it has made, so you can look before you pay. |
| **Subscribe** | Takes you to checkout. Once you are paying, a copy lands in your Workflows tab. |
| **Subscribed** | You already pay for this one. |
| **Yours** | You are the one selling it. |

Prices are monthly: $10, $20, $50, $100, or $200. **The seller receives 70% of
what you pay**, at every price.

## Selling

![The Selling tab: monthly revenue, subscribers, and your listings](/atlas/docs/marketplace-selling.png)

Put a price on anything you own and it goes on sale. The top shows what you are
earning a month, what that is a year at the same rate, and how many people are
paying, with how many joined and how many are leaving this month. Someone who
cancels still counts until their paid month actually ends.

- **Pick a price**, then **List it**. Nothing is on sale until you do both.
- **View subscribers** shows who is paying.
- **Stop taking new subscribers** closes it to new people without dropping
  anyone already paying.
- **Payouts**, in the header, is where the money goes. You set that up once.

## My subscriptions

![The My subscriptions tab, with what you pay for each month](/atlas/docs/marketplace-subscriptions.png)

What you pay for, what it costs, and when it renews. **Manage subscription**
opens the billing page, where you can cancel. You keep it until the month you
have paid for runs out.

This is also where you set how a subscription that trades for you behaves:
**Trade it for me** or **Ask me first**, and a **Budget**, the most any one
trade of theirs may spend in your account.

---

# Strategies tab

A **strategy** is your saved trading playbook. The Strategies tab lists yours and
lets you make, edit, import, and share them. Opening one shows its title, who
can see it, and the names of its sections; open a section to read it, or press
**Edit** to change it.

![A saved strategy: its title, who can see it, and its sections, with Edit and Upload file](/atlas/docs/strategy.png)

## What is in it

| Field | What it does |
| --- | --- |
| **Title** | A short name for the playbook. |
| **Who can see it** | **Private** (only you), **Invite-only**, **Unlisted** (anyone with the link) or **Atlas Public** (anyone signed in). |
| **Content** | Your rules in your own words, split into sections. |
| **Tools** | The Atlas tools this playbook uses. |
| **Import files** | Add files to it. |

Point to a strategy in [Chat](#dashboard-chat) (*"use my wheel strategy on MSFT"*)
or point a workflow's [Reasoning](#workflow-create) at it so its choices follow
your rules. **Discover** shows shared strategies you can import.

---

# Alerts tab

An **alert** watches the market and goes off when your condition is met. On its
own it messages you. Attached to workflows or triggers, it decides *when* they
run.

![The alerts list: each alert with what it last saw and when, and its buttons](/atlas/docs/alerts-list.png)

Each alert in the list says what it saw the last time it went off, short, and
when: *GAMMA wall moved: 768.0 → 770.0 · Today 2:20 PM ET*. One that has never
gone off says so. Press an alert to open its page.

## An alert's page

![One alert's page: the values it saw last time, what it fires on, what it watches, when, and the workflow it runs](/atlas/docs/alert-page.png)

- At the top: its name, the stock, **Watching** (or paused), and **Last went
  off**, with each value it saw then in a box of its own.
- One sentence on what this alert fires on, from its own settings.
- **What it watches**: the kind, the stock and what sets it off.
- **When**: the days and hours it watches, and whether it fires once when the
  window opens.
- **When it goes off**: each workflow it runs (with **Open**), the triggers it
  turns on, and anything else it does.
- **Recent fires**: the charts sent with each time it went off, when there are
  any.

## Making an alert

Click **New alert** to open the builder. It walks you through: **what kind of
alert**, **which stock**, **what to match**, **filters**, an optional **time
window**, and **what happens when it goes off**.

![The alert builder: kind, stock, what to match, filters, and window](/atlas/docs/alert.png)

## Kinds of alert

| Kind | Watches for |
| --- | --- |
| **Price level cross** | The stock crossing a price you set. |
| **Contract price cross** | One option's price crossing a level. |
| **Greek exposure move** | The "wall" (the strike with the most dealer exposure) moving to a new strike, or the price crossing a flip level, a strike where that Greek's exposure changes sign. You choose which. This is the only alert that measures exposure. |
| **Price near greeks** | The stock PRICE getting close to a Greek wall, or crossing to the other side of it. Never about the exposure's sign. |
| **Options flow** | Unusual trades on a stock (you set the size). |
| **Top 20 flow** / **New top flow (no ticker)** | Unusual trades across the whole market. |
| **Volume spike** / **Top-volume contract rotation** | A jump in volume, or the most active contract changing. |
| **Options ratio** | Calls against puts, on open interest (checked once a day) or on the day's unusual flow (checked every hour). Goes off when the side in the lead flips, or leads by the amount you set. |
| **Technicals** | One indicator crossing another, like the price over the 200 EMA. |
| **My trigger acts** | Goes off when one of your triggers enters, exits, pauses or is deleted. |

### What counts as a move

**Greek exposure move** and **Price near greeks** each ask what should set them
off, because the same wall can be watched in more than one way.

On **Greek exposure move**: *Wall moves to a new strike* (the default) is the wall
shifting to a new price. *Positive wall* and *Negative wall* follow only one
side: every exposure chart marks two, purple for the biggest positive exposure
and yellow for the biggest negative. *Price crosses into negative exposure*
(or into positive, or a flip level either way) is the gamma flip: going up the
strikes, a flip level is a strike whose exposure has the other sign to the one
below it, and the alert goes off when the PRICE crosses one, from a strike with
positive exposure to one with negative. A strike changing sign while the price
stands still does not set it off. *Any move or flip* takes whichever comes
first.

**The two alerts use one vocabulary, and the subject is always named.** A wall
is one STRIKE. A flip level is where the exposure changes sign along the
strikes. Price is PRICE. Only **Greek exposure move** measures exposure: if you
want the price to move into positive gamma, that is *Price crosses into
positive exposure*, and no setting on any other alert does it.

On **Price near greeks**: *Price gets near it* is the original proximity band.
*Price crosses up through it* / *down through it* go off when the price moves to
the other side of the wall. That is the stock price crossing a level, not the
Greek's sign changing. To watch a fixed price be crossed instead, use **Price
level cross**.

Neither one goes off just because it starts on that side. It needs a real
crossing between two checks, so *Price crosses down through it* set while the
price is already below the wall waits for it to go above and come back down.

### Does an overnight move count?

Every one of these alerts has this tick box, and it is **off** by default —
meaning a move that happened while the market was shut still counts, and you
hear about it on the first check after the open. Turn it on to count only moves
during one session; the first check of each day then simply gets it ready
again.

Two things worth knowing either way. If you do not pin an expiry, the alert
follows the nearest one, which becomes a new contract each day — that changeover
is never reported as a move. And **Top 20 flow** and **New top flow** compare
against yesterday's board, so with this off they report the whole leaderboard as
new every morning.

## Common fields

- **Stock**, the symbol to watch (not needed for whole market flow alerts).
- **When it goes off, also**: **Send a DM when it fires**, **Run workflows** (pick
  one or several) and **Turn on trading triggers** (pick one or several).
- **Active from / Active until**, in Eastern time, makes the watch window smaller.
- **Cooldown between fires**, the least time between two messages.
- **Delete after**, a time when the alert is deleted, whether it is on or paused.
  Blank keeps it until you delete it.

The list shows **Active** alerts first (on, even outside their hours), then
**Paused** ones, and each says **Deletes on** when it has a time.

To limit how many times an alert can drive a trade in a day, set **Max runs per
day** on the workflow's [Schedule step](#workflow-create).

---

# Triggers tab

A **trigger** is one "if this, then trade" order. The Triggers tab lists your set
up triggers, with filters along the top: **All, Active, Trade open, Paused,
Preview, Fired**. **New trigger** opens the builder, in two steps: **Setup** and
**Trade**.

![The Setup step of the trigger builder: the account, and what starts it](/atlas/docs/trigger.png)

| Step | Fields |
| --- | --- |
| **Setup** | The linked account the order goes to, and what starts it: **Just the trade** (it waits for its entry), or **Something starts it**: a **Schedule** (a time), an **Alert**, or **Both**. |
| **Trade** | Stock symbol, **Options** or **Stock**, the **Contract** (call or put, strike, expiry, contracts), the **Entry** (order type, price), and the **Exit** (stop loss, which can be a **Trailing %**, take profit, order type). |

**+ Add another stock** puts a second trade in the same trigger. Two trades can
be linked: **Cancels when it fills** or **Starts when it fills**, with the
other trade picked.

Trading always lets you **check first, then place**: the **Preview** tab on each
trade shows exactly what will be set up, and **Create trigger** places it.

---

# Templates

Templates are **Atlas's own ready made setups**. Pick one and it is added to
your account, ready to change. Open them from **More → Templates** in the
dashboard, or from the **Templates** link in this guide's sidebar.

Templates are not the same thing as **Discover & Import**. Discover & Import
(on the Workflows tab) is where you browse workflows **other people** have made
public. Templates are written and kept up to date by Atlas.

![The templates shelf with cards you can filter and import](/atlas/docs/templates.png)

## What is on the shelf

Filter by **Stocks**, **Options**, or **Both**. Each card is marked by kind.

| Template | Kind | What it does |
| --- | --- | --- |
| GLD 0DTE Agent | Workflow | Gold same day calls and puts from levels it sets itself. |
| SPY 0DTE Agent | Workflow | SPY same day calls and puts on EMA 9/20, VWAP, CVD and gamma. |
| QQQ 0DTE Agent | Workflow | The SPY agent's rules, on QQQ. |
| SPY GEX Sniper Ladder | Workflow | SPY same day options off its own alert levels, selling in two steps. |
| QQQ GEX Sniper Loop | Workflow | QQQ same day options at the nearest decision level, selling in three steps. |
| P2P Gamma Flip | Workflow | Buys a 3 to 5 day call when a stock crosses up through its gamma flip. |
| Options Day and Swing | Workflow | Type a ticker, pick Day or Swing and when to buy (at Atlas's entry, now, or at your price for the option): a call and a put setup. |
| Stock Day and Swing | Workflow | Type a stock or ETF, pick Day or Swing and when to buy (at Atlas's entry, now, or at your price): buys shares with a trailing stop. |
| Portfolio Risk Manager | Workflow | Every morning, sets the budget for one trade to 40% of each account's buying power, on your workflows and the signal groups you follow. Changes budgets only. |
| Morning Market Brief | Workflow | A daily brief on the market and your watchlist. |
| Trade Desk | Trigger | Stages an order for you to place in a tap. |
| GEX Flip Alert | Alert | Messages you when a stock's net gamma turns from negative to positive. |
| GEX Alert | Alert | Messages you when the biggest gamma level moves. |
| Technicals Setup Alert | Alert | Messages you on indicator crossovers. |
| Top 20 Flow Alert | Alert | Messages you when the top 20 flow list changes. |
| Fundamentals | Strategy | A deep look at a company's financials. |
| Smart-Money Tracker | Strategy | Tracks insiders, institutions and Congress. |
| Options Strategist | Strategy | Reads the chain, the greeks and the expected move. |

## Tested results

Six of the workflows are Atlas's own, run on Atlas's own account. Their
cards show when they were tested and how they did: the dates, the result in
dollars and how many trades won. **See performance** opens the workflow's
public performance page: who tested it and every trade, live. **Past results do not
guarantee future performance.** Options can lose everything put into them, and
a workflow can behave differently in a different market. Start small, and
read every trade it holds for review before you place it.

## One step

Choose the card that fits what you trade. That is all.

Nothing has to be connected first. The template is added to your account,
switched off, and opens in its editor, filled in. A short **Before you
save** popup opens over it first: what still needs doing (a broker to connect,
with **Connect**), the size of a trade, and where notifications go. It ticks a
line off once you connect, and **Got it** closes it. Discord is optional: a
template's notifications go to your phone, and you can turn them off in the
editor. Change anything before you
turn it on. If a setup needs a broker or Discord (a workflow that trades needs
a **broker**; an alert messages you on **Discord**), you are told when you
switch it on.

## What you get

- A **workflow** template adds the workflow, as it was set up, to your
  Workflows tab. Set your size and your broker, then turn it on.
- Some workflows run on something else, and that is added too, switched off:
  the four agents and sniper workflows come with the workflow that sets their
  alerts each morning, and **P2P Gamma Flip** comes with a **GEX Flip Alert**
  on AAPL (add the same alert on any stock you want it to watch). Turning the
  workflow on turns these on as well.
- An **alert** template opens the alert form, filled in.
- A **strategy** template adds a reusable strategy to My Strategies.
- The **Trade Desk** template sets up a trigger that stages an order.

Everything a template adds is yours to change afterwards. See
[Workflows](#concept-workflows) for how copies and forks work.

---

# Performance

Open **More → Performance** on any trading workflow to see how it has done.
Signal groups and Community picks have a **Performance** button too.

![The performance view: total profit, a line chart, and a table of trades](/atlas/docs/performance.png)

- **Top numbers**: total profit or loss, the percent return, the win rate, and
  wins against losses.
- **Positions** or **Calendar View**: one row per close with the contract, when
  it closed, the amount, entry, exit, and profit or loss.
- **Refresh** loads it again and matches the rows to your broker in one go.

Each workflow shows **its own** money at **your** size, so a copy shows its own
results, not the author's. Every close makes a row. If a number is not ready yet
(a gap in prices or a manual close), it shows a dash instead of a blank.

---

# Atlas Chat

The Chat tab is a full chat. Ask Atlas anything and it uses your tools, shows its
thinking, and draws live charts and order previews right in the chat.

![The Chat tab with the box to type in](/atlas/docs/chat.png)

- **Type box**, ask a question and Atlas picks the tools it needs.
- **Tool folds**, each tool it uses shows as a fold you can open to see what went in and out.
- **Charts**, charts and trading views draw right in the chat, and their buttons work.
- **Ask first**, in ask mode Atlas waits for your OK before each tool. Switch to skip in [Profile](#dashboard-profile) to let it run tools without asking.
- **Recents**, your latest chats are listed in the menu. Open one to carry on, or delete it from its **...**.
- **Something to ask**, a new chat offers three questions to start with, taken from your chats and what Atlas remembers about you. Press one to use it.
- **While Atlas works**, you can keep typing. What you send waits in a list above the box (up to five): change one, remove it, or **Send now** to stop the answer and send it at once. **Stop** stops the answer, and the list carries on.

## Talk to Atlas

Press the **microphone** next to Send and speak. Atlas answers out loud, and what
is said is written into the chat.

- While you talk, a moving wave shows with **Stop voice**. After about a minute
  of quiet it goes to sleep, and the button becomes **Resume voice**.
- Atlas can move around the dashboard for you, point at things and press
  buttons. Before it presses something that matters, it asks: **Decline** or
  **Allow**. Change that in Profile → **Voice**.
- You can still type. What you type is said to the voice.
- The microphone on a chat under Recents starts talking in that chat.
- One conversation can run for an hour of speaking, and you get two hours a day.
  Quiet time does not count. See [what uses a request](#plans-and-billing).

The first time you open the dashboard, Atlas starts talking on its own and gives
you a short tour. If your browser does not allow the microphone, it simply skips
it. You can ask for the tour again in any chat.

## Who answers

The picker in the chat box chooses who answers:

- **Atlas cloud** is the normal chat, answered on our side.
- **One of your computers**, then a project on it. The chat is then answered by
  the model on that computer, running Atlas Studio, and it can work on that
  project. See [Local](#dashboard-local).

Your chats and the ask or skip setting live in the [Profile](#dashboard-profile) tab.

---

# Connect: brokers and connectors

The Connect tab has two parts: **Brokerages** and **Connectors**.

To add Atlas to ChatGPT, Claude or Discord instead, see
[Connect Atlas](#connect-overview).

## Brokerages

**Connect a Brokerage** links a broker account so Atlas can trade in it. You sign
in on your broker's own page. Atlas never sees your broker password.

When you have signed in, press **Done** on that page. Its window closes (in the
phone apps, the broker's sheet closes) and you are back on Connect, where
**Connected** shows every account you just added, under its broker. **Connect
another** links one more.

![Connect, Brokerages: your default account](/atlas/docs/connect-brokerages.png)

Each connected account shows whether it can trade or only be read. On an account
that can trade:

| Control | What it does |
| --- | --- |
| **Make default** | Beside **Remove**. New workflows, triggers and plays go to this account unless you choose another. Press it again (**Default ×**) to have no default. A broker with several accounts has one on each account. There is no budget for a whole account: set the size on the workflow, trigger, play or group. |
| **Remove** | Disconnects the broker. If it still has open trades Atlas warns you first, then removes the trades, workflows and defaults that used it. Positions at your broker are not closed. |

## Connectors

A connector links Atlas to another service's own tools. Press **+ Add a
connector**, give it a name and its address, and choose how it signs in: by
signing in on that service's page, or with a key.

Press a connector to see everything Atlas can do with it. The round buttons on
its row say what they do when you rest the pointer on them:

| Button | What it does |
| --- | --- |
| **Refresh tools** | Check again for what it can do. |
| **Sign out** | Disconnect it for now. |
| **Delete** | Remove it completely. |

Once connected, its tools can be used in [chat](#dashboard-chat) and picked in a
workflow's **Input data** and **Output** steps.

---

# Local: your own computers

**Local** shows the computers where you run
[Atlas Studio](/studio-setup-guide), the Atlas desktop app, and the projects on
them. A computer shows here once Atlas Studio is open on it, you are signed in
with the same account, and **Local Mode** is switched on there (in Studio: This
Computer, then **Run tasks on this computer from the web**).

Pick a computer, then a project. Each project has five tabs:

| Tab | What it is |
| --- | --- |
| **Dashboard** | The project's own dashboard, if it has one. |
| **Files** | The project's files. A CSV opens as a table. |
| **Checks** | The project's checks: its latest ten, each passed or not, with its report, pictures and formulas. Where a check rests on numbers you can change (its **Assumptions**), change them and run it again with yours. |
| **Computer Use** | Watch that computer's screen while Atlas works on it. |
| **Chats** | Chat about this project. The model on that computer answers. |

In a project's chat, a file the chat names is shown as blue words: tap them to
open the file beside the chat, at the rows or lines it means. The dropdown in
the chat box opens **Checks**, **Dashboard**, **Computer use** or the chat's
own charts beside the chat in the same way.

You can also share a project with someone from here.

Everything about the desktop app is in the
[Atlas Studio guide](/studio-setup-guide).

---

# Memory

Atlas remembers things about you between chats, like how you size a trade or
what you never hold through earnings, so you do not have to say them again.

Open **Profile**, then the **Memory** tab.

![Profile, Memory: what Atlas remembers about you, how important each one is, and Forget](/atlas/docs/memory.png)

| Tab | What is in it |
| --- | --- |
| **Short term** | Kept for hours. |
| **Long term** | Kept for weeks. |
| **Permanent** | Kept until you remove it. |
| **Forgotten** | The trash. A forgotten memory waits here for 30 days and can be brought back. |

What you can do:

- **Search** what is remembered, or look at it as a **Map** or a **List**.
- **New memory** writes one yourself.
- **Select**, then forget the ones that are wrong or out of date.
- Choose how often Atlas learns from your chats: **Learn daily**, **weekly**,
  **monthly**, or **Never learn**. **Learn now** does it straight away.

## Who stored it

Each memory says who wrote it. One you typed here has no label. One Atlas picked
up from your chats, or wrote in the web chat, says **by Atlas**. One an assistant
wrote through the Memory tools carries that assistant's own name, such as **by
claude** or **by gpt**. Open a memory to see it beside the date it was stored.

The same goes for forgetting: the **Forgotten** tab shows who forgot each one,
and why.

## Share with my computers

Atlas Studio keeps a memory of its own on each computer you run it on, and your
past chats stay there too. One button lets Atlas use both.

Press **Share with my computers** to switch sharing on. The button then reads
**Stop sharing with my computers**. While it is on:

- Asking Atlas what it remembers looks in one go at this profile's memory, the
  memory of every computer that is on, and past chats there. From a chat it
  brings back the message that matched and the 3 either side: only your words
  and the AI's, never what a tool read, and never your files.
- Atlas in the web chat also brings in the memory of your computers that are on.
  A computer that is off or slow is skipped, and the chat does not wait for it.
- Atlas and assistants you connected can add to or change the memory on a
  computer. Past chats can only be read.
- Nothing a computer answers is stored on Atlas. It is passed along and that is
  all.

Press the button again to switch it off. Atlas then reads this profile's memory
only. A computer has to be on, with Atlas Studio open and Local Mode on, to
answer.

Assistants reach all of this through the Memory tools. See
[All tools](#mcp-tools).

---

# Profile

Click your name at the bottom of the menu to open Profile. It has three tabs
along the top: **Profile**, **Chat Sessions** and [**Memory**](#dashboard-memory).

![The Profile tab: look, voice, notifications, plan, Discord, your key and your invite link](/atlas/docs/profile.png)

## The Profile tab

| Section | What is there |
| --- | --- |
| **Appearance** | Dark mode. |
| **Voice** | Which voice Atlas speaks with, the language, and **When Atlas needs to press something**: **Ask for permission** or **Fully auto**. |
| **Notifications** | **Phone notifications**. **Manage** chooses which ones you get: workflows, triggers and trades, alerts, collaborators, Studio. |
| **Subscription** | Your plan, how much you have used, and **Manage Subscription**. See [Plans and how you get charged](#plans-and-billing). |
| **Linked Accounts** | Link Discord to get workflow and trade messages. |
| **API / CLI / MCP Key** | Show, copy or **Rotate** the key for the [Web API](#authentication) and [command line](#cli-overview). |
| **Invite** | Your invite link, to share. |
| **Danger Zone** | **Sign Out** and **Delete Account**. |

Your broker is not here. It is in [Connect → Brokerages](#dashboard-connect).

## Chat Sessions

Your saved [chats](#dashboard-chat), to open or delete, and **Tool permissions**:
whether Atlas asks before it changes anything (an order, a trade, a workflow, an
alert, a message). Looking things up never asks.

## More than one account

The **...** next to your name lists the accounts signed in on this device. **Add
account** signs in another, and clicking one switches to it. Dark mode and
**Sign out** are there too.

## Deleting your account

**Delete Account** tells you exactly what will be removed before you confirm.
It cannot be undone. Positions at your broker are not closed for you, so close
those first.

:::warning
Your key can place real orders with a linked broker. Keep it secret, and press
**Rotate** here if it ever leaks.
:::

---

<!-- ==== MCP (chat apps) ==== -->

# Atlas in your chat app (MCP)

Atlas plugs into chat apps like ChatGPT, Claude, and Cursor. You do not install
anything. You add one link, sign in once, and your assistant can use every Atlas
tool.

## The link

```text
https://atlasmcp.finmanagerai.com/mcp
```

You sign in with Email, Apple, Google, or Discord.

## Three ways to use the same tools

There is one set of tools behind three doors. Pick whichever fits you.

| Way | How you call a tool | Sign in with |
| --- | --- | --- |
| Chat app (MCP) | The assistant uses the tool by name, like `Stock-Quote` | Sign in link |
| Web API | `POST /api/v1/tools/get_stock_quote` | Your key |
| CLI | `atlas stock-quote --symbol AAPL` | Your key |

The name the assistant uses and the name in the API and CLI point to the same
thing. So anything you learn in the [Web API](#api-overview) works here too.

## Set it up

See [Connect Atlas](#connect-overview) for step by step help with
[ChatGPT](#connect-chatgpt), [Claude](#connect-claude),
[Discord](#connect-discord), and [Cursor and others](#connect-other).

---

# All tools in your chat app

Once Atlas is connected, ask your assistant to use any of these. The name on the
left is what the assistant calls the tool.

## Stocks

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Multi-Timeframe-Price-Overview` | Premium | Daily / weekly / monthly snapshot in one image. |
| `Price-Data-OHLCV` | Premium | Historical OHLCV bars. |
| `Price-Chart` | Premium | Candlestick price chart with overlays. |
| `Stock-Quote` | Premium | Latest quote for a symbol. |

## Options

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Option-Expiration-Dates` | Premium | Available expirations for a symbol. |
| `Options-Chain` | Premium | Full options chain for an expiration. |
| `Single-Option-Quote` | Premium | Bid/ask/IV/greeks for one contract. |
| `Historical-Contract-Greeks` | Premium | Day-by-day price history and greeks for ONE option contract, bid/ask/mid, the underlying's price, days to expiry, IV, delta, gamma, theta, vanna. Up to 90 trading days per call. |
| `Historical-Options-Chain` | Premium | The options chain as it stood on a past day: each contract's prices and volume, plus that day's call volume, put volume and put/call ratio. One expiration per call. |
| `Put-Call-Ratio` | Premium | Call against put open interest (plus today's volume) for one stock, over the expirations and strikes you pick, read as which side leads and by how much. |

## Greek Exposure

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Greek-Exposure-Multi-Expiration` | Premium | Net Gamma / Delta / Vanna / Theta exposure DATA grid across MULTIPLE expirations for one symbol, OI-weighted per-strike numbers (no chart). Sibling of Greek-Exposure-Single-Expiration (same data, one date) and Greek-Exposure-Heatmap (same numbers rendered as PNG). |
| `Greek-Exposure-Single-Expiration` | Premium | Greek exposures for ONE expiration date only, guaranteed single-chain fetch. Use when the caller knows the date (0DTE, weekly, monthly OPEX, dated event). |
| `Greek-Exposure-Heatmap` | Premium | Heatmaps for one or more greeks in a single call. Pass greeks=["gamma","delta","vanna","theta"] (any subset). Returns one PNG per requested greek. |
| `Net-Exposure-Charts` | Premium | Net exposure bar charts for one or more greeks. metrics=["net_gex","net_dex","net_vex","net_tex"]. Returns one PNG per metric. |

## Options Flow

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Top-Volume-and-OI-Contracts` | Premium | Top contracts by volume / OI as data. |
| `Volume-and-OI-Charts` | Premium | Top-volume and/or open-interest charts. types=["vol","oi","vol_oi"]. Returns one PNG per requested type. |
| `Options-Flow` | Premium | Stored option-trade tape filtered by side / type / premium / size / time window. Omit symbol for the top-N cross-universe ranking. |
| `Options-Flow-Contract` | Premium | Per-hour premium histogram for ONE contract (open / close stack). Reads strictly from the flow archive cache, never pulls fresh chain. |
| `Unusual-Flow-Ratio` | Premium | Call against put positioning from one day of unusual options trades: which side the big trades leaned to, and by how much. |

## Charts

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Chart-Vision-Analysis` | Premium | AI vision analysis of a chart image. |
| `Multi-Chart-View` | Premium | Multi-timeframe charts side-by-side. |

## Fundamentals

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Balance-Sheet` | Premium | Latest balance sheet. |
| `Financial-Metrics` | Premium | Headline valuation + profitability metrics. |
| `Income-Statement` | Premium | Latest income statement. |

## Estimates

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Analyst-Price-Targets` | Premium | Consensus price targets. |
| `EPS-Estimates` | Premium | Consensus EPS estimates. |
| `EPS-Trend` | Premium | EPS estimate trend. |
| `Growth-Estimates` | Premium | Growth estimates summary. |
| `Revenue-Estimates` | Premium | Consensus revenue estimates. |

## Calendar

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Earnings-Calendar` | Premium | Upcoming earnings releases. |
| `Earnings-Dates` | Premium | Earnings dates for a symbol. |
| `IPO-Calendar` | Premium | Upcoming IPOs. |

## Ownership

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Insider-Transactions` | Premium | Recent insider buys / sells. |
| `Institutional-Holders` | Premium | Top institutional holders. |
| `SEC-Filings` | Premium | Recent SEC filings. |
| `Senate-Lobbying-Data` | Premium | Congressional trading / lobbying activity. |

## Brokerage

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Account-Balances` | Premium | Cash, buying power, equity for an account. |
| `Account-Holdings` | Premium | Positions in one linked account. |
| `Account-Symbol-Lookup` | Premium | Resolve a ticker inside a linked account. |
| `All-Account-Holdings` | Premium | Positions across every linked account. |
| `Broker-Connections` | Premium | List linked brokerage accounts. |
| `Transaction-History` | Premium | Transaction history with optional date range. |

## Trading: Orders

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Cancel-Order` | Free | Cancel one order: a staged one is discarded, a placed one that is still waiting is cancelled at the broker. |
| `List-Preview-Orders` | Free | List staged previews not yet placed. |
| `Place-Order` | Premium | Submit a previously previewed order. |
| `Preview-Multiple-Orders` | Free | Stage several orders at once. |
| `Preview-Order` | Free | Stage an order for review without sending it to the broker. |

## Trading: Triggers

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Create-Trading-Trigger` | Premium | Create a price / condition-based trigger. |
| `Delete-Trading-Trigger` | Premium | Permanently delete a trigger. |
| `List-Fired-Triggers` | Free | List triggers that already fired. |
| `List-Trading-Triggers` | Free | List active and paused triggers. |
| `Preview-Trading-Trigger` | Free | Preview a trigger before creating it. |
| `Reactivate-Trigger` | Premium | Reactivate a fired trigger. |
| `Update-Trading-Trigger` | Premium | Update a trigger (pause / retarget). |

## Plays (signals)

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Signal-Schema` | Free | Read this before posting or taking a play. The shape of a play: every field, what each number is measured in, what happens when one is left out, and worked examples. |
| `Signal-Groups` | Free | The places you can post a play to: the community board, plus every signal group you own or can post in. |
| `Signal-List` | Free | Read the plays on the community board, or the private ones, newest first, with what happened to you on each. One page at a time. |
| `Signal-Show` | Free | Show one play as a card, the same one the Signals tab renders, with every number and what happened to your order. |
| `Signal-Post` | Free | Post a trade play to the community board or one of your groups: the contract, how much, where to get in, where to take profit, where to get out, and when. |
| `Signal-Update` | Free | Change a play that is still live instead of posting a second one. Send only what changes, everything left empty keeps what the play already says. |
| `Signal-Take` | Free / Premium | Take a play: place it in your own account, now. This places a real order. Nothing on the board trades on its own. |
| `Signal-Broker` | Free | See or set the broker account your plays go to, and whether it is used automatically for plays you post and plays you take. |
| `Signal-Discover` | Free | Signal groups other people have made public, with who runs each, how many plays it has posted and how many people follow it. |
| `Signal-Follow` | Free | Follow a public signal group, or stop. Following places nothing by itself: you choose whether its plays are placed for you or wait for your yes. |
| `Signal-Trade-Settings` | Free | See or change how plays are traded for you, for one group or for everything: asked first or placed for you, which account, and the most one trade may spend. Call it empty to read. |
| `Signal-Pending` | Free | The plays sent to you that are waiting for a yes or no. |
| `Signal-Answer` | Free / Premium | Say yes or no to a play that was sent to you. Yes places a real order, sized from your trade settings for that group. |
| `Signal-My-Order` | Free | Change or cancel your own order on someone else's play while it is still waiting to enter. Once it has filled, the way out is Trade-Close. |
| `Signal-Delete` | Free | Take down a play you posted, before anyone is in it. The orders waiting on it are cancelled. |
| `Signal-Group-Create` | Free | Make a signal group: a place of your own to post plays to. It starts private. |
| `Signal-Group-Update` | Free | Rename a signal group you own, make it public or private, or tag it. A public group can be followed by anyone on Atlas, for free. |
| `Signal-Group-Delete` | Free | Delete a signal group you own, with its plays. If people pay for it, their subscriptions are stopped first so nobody is billed again. |
| `Signal-Group-Performance` | Free | The closed trades of one signal group, with win rate and total profit or loss. |

## Strategy

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Autofetch-Strategy` | Free | Auto-pick the best-matching strategy. |
| `Fetch-Strategy` | Free | Load one strategy by id. |
| `List-Strategy` | Free | List your strategies. |
| `Strategy-Create` | Free | Create a new strategy. |
| `Strategy-Import` | Free | Copy a public strategy into your account. |
| `Strategy-Open` | Free | Open the user’s primary strategy. |
| `Strategy-Preview` | Free | Preview proposed strategy edits. |
| `Strategy-Save-Instructions` | Free | Save strategy-selection instructions. |
| `Strategy-Discover` | Free | Browse the strategies other people share. Search by title or content, then import one with Strategy-Import. |
| `Strategy-Duplicate` | Free | Make your own copy of a shared strategy. The same thing as Strategy-Import, under the other name. |
| `Strategy-Update` | Free | Save changes to an existing strategy. |
| `Strategy-Delete` | Free | Delete one of your strategies for good. Anyone who imported it keeps their copy. |

## Workflow

| Ask for | Plan | What it does |
| --- | --- | --- |
| `List-Tool-Safety` | Free | List which tools are read-only / destructive. |
| `Trigger-Workflow-Schema` | Free | Field schema for trigger / workflow rules. |
| `Workflow-Apply-Updates` | Free | Pull the latest revisions from the parent workflow into this subscribed copy. Use when revisions_behind > 0. |
| `Workflow-Create` | Free | Create a new perception workflow. |
| `Workflow-Delete` | Free | Permanently delete a workflow. |
| `Workflow-Export` | Free | Export a workflow's full node-and-edge graph plus a self-describing markdown rendering. Read-only. |
| `Workflow-Import` | Free | Copy a public workflow into your account. |
| `Workflow-List` | Free | Lightweight programmatic discovery, list every workflow you own with id / name / status / schedule. Read-only. Use before Workflow-Export / Workflow-Logs / Workflow-Run when you need an id. |
| `Workflow-Logs` | Free | Read recent workflow runs. |
| `Workflow-Open` | Free | Open a workflow for review / editing. |
| `Workflow-Performance` | Free | Closed-trade performance for a workflow: per-trade PnL rows and aggregate Win Rate / Total PnL / win-loss-flat counts / calendar-style by_day map. |
| `Workflow-Preview` | Free | Preview proposed workflow edits. |
| `Workflow-Run` | Free / Premium | Execute a workflow on demand. |
| `Workflow-Update` | Free | Save changes to a workflow. |
| `Workflow-Discover` | Free | Browse the workflows other people share, most imported first. Search by name, rules, or tool. Import one with Workflow-Import. |
| `Workflow-Duplicate` | Free | Make your own copy of a shared workflow. The same thing as Workflow-Import, under the other name. |
| `Workflow-Journal` | Free | Read or change a workflow's journal. With journalling on, Atlas writes a note after each of its trades finishes and reads those notes back on later runs. |
| `Search-Tools` | Free | Search every tool a workflow can use, Atlas's own and those of your connected servers, with the exact name to put in the workflow. |
| `Workflow-Restore` | Free | Turn a paused workflow back on, with a fresh daily limit. If you are the author, your followers' copies come back with it. |
| `Workflow-Abort` | Free | Stop a workflow run that is in progress. It does not pause the workflow: the next run happens as usual. |
| `Workflow-Agent-Waiting-Runs` | Free | For a workflow your own assistant runs: the runs that came due and are waiting for it, with what started each one. |
| `Workflow-Agent-Report-Progress` | Free | For a workflow your own assistant runs: one short line on the workflow's card saying what it is doing right now. |
| `Workflow-Agent-Hand-In-Run` | Premium | For a workflow your own assistant runs: hand in what it decided. Atlas checks the trade, holds it for review or places it, sends it to followers and logs the run. Uses one request each time. |
| `Workflow-Review` | Free / Premium | For a workflow set to let you review each run: see what is waiting, then place it or throw it away. Placing sends real orders. |
| `Workflow-History` | Free | A workflow's saved versions, newest first. Open one to read it, or go back to it. |
| `Workflow-Follow` | Free | On a copy of someone else's workflow: stop taking the author's changes so the copy is your own, or start taking them again. |
| `Workflow-Operate` | Free | Pause or turn on a workflow whose owner made you an operator. It does what the owner's own pause does, for them and everyone following. |
| `Workflow-Files` | Premium | The files one of the person's workflows keeps: what its calculations saved (Python code, tables, charts, notes). |

## Account

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Get-Instructions` | Free | Read your saved strategy-selection instructions. |
| `Side-Panel-Widgets` | Premium | The widgets under Recents in your side panel on the website and the phone apps: list them, add one, change one, remove one, or move one. |
| `Arrange-Tabs` | Premium | The order of the tabs in the person's website and phone apps, and the ones they put under More: list them, set one bar's, or put a bar back to how it came. |
| `Subscription-Status` | Free | Subscription tier, usage, remaining requests. |
| `Account-Activity` | Free | What has happened on your account lately: every workflow run with its reasoning and any error, plus the trades those runs placed. Newest first. Ask for "open" to see the trades you are in right now. |

## Search

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Connection-Check-Fetch` | Free | A connection check for apps that look for a fetch tool before they connect. It opens no address. To read the web use Web Search. |
| `Connection-Check-Search` | Free | A connection check for apps that look for a search tool before they connect. It searches nothing. For news and facts use Web Search. |
| `Web-Search` | Premium | Live web search for real-time news and facts, today's headlines, macro / geopolitical drivers, earnings, and current events, returned as a dated answer plus the source links it used. |
| `Ticker-Symbol-Lookup` | Premium | Resolve a company name to its ticker. |

## Alerts

| Ask for | Plan | What it does |
| --- | --- | --- |
| `List-Alert-Types` | Free | Catalog of alert types you can create, read this BEFORE Create-Alert to learn the conditions shape for each type. |
| `List-Alerts` | Free | Your streaming alerts. Active-only by default; pass active_only=false to include disarmed / cascade-paused. |
| `Preview-Alert` | Free | Dry-run an alert spec against the live tape, returns what would have matched without creating the alert. |
| `Create-Alert` | Free | Create a streaming alert that DMs Discord on fire and optionally arms a trigger / runs a workflow / places an order. ⚠️ Read List-Alert-Types first. |
| `Update-Alert` | Free | Patch an existing alert in place (rename, change conditions, retarget workflow_id, flip is_active, etc.). |
| `Delete-Alert` | Free | Soft-delete an alert by flipping is_active=false. The row stays for audit. |
| `List-Stream-Subscriptions` | Free | Active streaming subscriptions the worker is holding open (flow tape, option quote feeds), useful for debugging why an alert isn't firing. |
| `Alert-Fires` | Free | The last times your alerts went off, each with the message it sent. Name one alert, or leave it empty for all of them. |

## Workflow: Folders

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Workflow-Folder-List` | Free | List your workflow folders and which workflows are filed in each. Folders only organize the list, they never change how a workflow runs. |
| `Workflow-Folder-Create` | Free | Make a folder to organize your Workflows list. You can file workflows into it right away. |
| `Workflow-Folder-Update` | Free | Rename a folder, change its colour, or move it up or down the list. |
| `Workflow-Folder-Move` | Free | File one or more of your workflows into a folder. A workflow sits in one folder at a time, so this takes it out of any other. |
| `Workflow-Folder-Remove` | Free | Take workflows out of a folder. The workflows are not deleted, they just go back to being loose in your list. |
| `Workflow-Folder-Disband` | Free | Delete a folder. The workflows inside are not deleted, they go back to being loose in your list. |
| `Workflow-Folder-Discover` | Free | Folders of workflows other people have shared. Name one to see what importing it would give you. |
| `Workflow-Folder-Import` | Free | Get your own copy of every shared workflow in a folder. Each copy arrives with no broker chosen, so nothing trades until you pick one and turn it on. |

## Workflow: Working together

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Workflow-Proposal-List` | Free | List the changes people have suggested to a workflow, what each one touches, whether it is still open, and whether it went stale because the author edited since. |
| `Workflow-Proposal-Show` | Free | Read one suggested change in full, with what the workflow said before, what it would say, and what it says right now. |
| `Workflow-Proposal-Comment` | Free | Leave feedback on a suggested change. Name a part of the change to attach the note to that part instead of the whole thing. |
| `Workflow-Collab-Find` | Free | Find someone on Atlas by name or username, to share a workflow with. |
| `Workflow-Collab-Remove` | Free | Take someone off your workflow, or leave one you were added to. |

## Trading: Open trades

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Trade-Close` | Free | Close a position now, everything still open on it, at market. Only the person who owns the trade can close it. A real position needs a market, so outside 9:30 to 4 Eastern this refuses. |
| `Trade-Take-Profit` | Free | Sell the next take profit rung now, without waiting for its price. One rung per call. To take everything at once use Trade-Close. |
| `Trade-Cancel-Entry` | Free | Take an order off before it fills. Only while the entry is still waiting at its price, once it has filled the way out is Trade-Close. |
| `Trade-Edit-Entry` | Free | Move the price an order is waiting to enter at, or turn back on an order that was taken off before it filled. |
| `Trade-Edit-Exit` | Free | Move the stop or the take profit targets on a trade you are in. Only the person whose trade it is can do this, and the move reaches everyone following it. |

## Guide

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Atlas-Guide-Index` | Free | The Atlas guide's table of contents: every topic, grouped, with the id and link for each. Start here, then read the one that matches. |
| `Atlas-Guide-Search` | Free | Search the guide for a word or phrase and get the topics that mention it, each with a snippet and a link. |
| `Atlas-Guide-Read` | Free | Read one topic of the guide in full, by its id. Returns the whole page and its link, the same text the docs site shows. |
| `Atlas-Agent-Guide` | Free | The short manual an AI assistant reads before it uses Atlas: which tool does what, the order to call them in, and the rules that keep a call from placing something by mistake. |

## Your connected servers

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Mcp-Tools` | Free | The servers you have connected to Atlas (Connect, then MCP Servers), and what each of their tools takes. |
| `Mcp-Call` | Free | Run one tool on a server you have connected. Atlas signs in to that server for you with the sign in you saved. |

## Memory

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Memory-Recall` | Free | What Atlas remembers about you that bears on a question, on your profile or on one of your computers. Each memory says who stored it. Ask with a few words. |
| `Memory-List` | Free | Everything Atlas remembers about you, with who stored each memory, what was forgotten and can be brought back, whether Memory sharing is on, and which of your computers are connected. |
| `Memory-Write` | Free | Keep something lasting about you: a correction, a preference, a fact about how you trade. The assistant says who it is, and that name is kept with the memory. Giving it a name replaces the older memory with that name. |
| `Memory-Update` | Free | Change one memory: its words, how important it is, how long it is kept, or pin it so it is never retired. |
| `Memory-Forget` | Free | Forget one memory that is wrong or out of date. It waits in the trash for 30 days, with who forgot it and why, and Memory-Restore brings it back. |
| `Memory-Check-Already-Remembered` | Free | What is already remembered close to a statement, so a new memory replaces the old one instead of sitting beside it. |
| `Memory-Restore` | Free | Bring back a memory that was forgotten, while it is still in the 30 day trash. |

## Phone

| Ask for | Plan | What it does |
| --- | --- | --- |
| `Phone-Notify` | Free | Send a notification to your own phone, in the MindVest Atlas app, from a script, the command line or a chat. It reaches nobody else. |
| `Phone-Notify-Preview` | Premium | Show how a notification will look on the person's phone, on an iPhone and on Android, before it is sent with Phone-Notify. |
| `Phone-Button` | Free | Whether you pressed the button on a notification sent with Phone-Notify, for a script that is waiting on your answer. |

---

<!-- ==== CLI ==== -->

# Atlas CLI

The CLI lets you use Atlas from your computer's terminal. You sign in once, then
run any tool by typing its name.

You never write JSON. You just add settings as simple flags:

```bash
atlas stock-quote --symbol SPY
```

The CLI gets the tool list from the server on its own, so new tools show up
without you doing anything. It comes in two versions that work the same way, one
for Node and one for Python. Both have no extra parts to install and both give
you the `atlas` command.

## Tool names

The command is the tool name in small letters with dashes. `Stock-Quote`
becomes `stock-quote`. Type `atlas tools` to see them all, and
`atlas <tool> --help` to see one tool's settings.

---

# Install

Both versions are named **`mindvest-atlas`** and both give you the `atlas`
command.

| Version | Install | Needs |
| --- | --- | --- |
| Node | `npm i -g mindvest-atlas` | Node 18 or newer |
| Python | `pip install mindvest-atlas` | Python 3.8 or newer |

Check it worked:

```bash
atlas --version
```

---

# Sign in

Sign in the same way the chat apps do. It opens your browser, you log in, and
you are set.

```bash
atlas login       # opens your browser to sign in
atlas whoami      # shows who is signed in
atlas logout      # signs out
```

Your login is saved safely on your computer. It stays signed in and refreshes on
its own, so you rarely log in again.

## No browser (servers and scripts)

You can use a key instead of the browser. Use your dashboard **key** (see
[Sign in and keys](#authentication)):

```bash
atlas login --token <YOUR_KEY>    # save a key
export ATLAS_TOKEN=<YOUR_KEY>     # or set it for this shell
```

If `ATLAS_TOKEN` is set, it is used first.

---

# How to use it

## Find tools

```bash
atlas tools                 # list every tool
atlas tools --search flow   # find tools by word
atlas <tool> --help         # see one tool's settings
```

## Call a tool

Add each setting as a flag:

```bash
atlas stock-quote --symbol SPY
atlas options-chain --symbol SPY --expiration 2026-06-20
atlas price-chart --symbol SPY --out ./charts   # save chart pictures to a folder
```

- Flag names use dashes. `--from-date` becomes `from_date` in the request.
- For a setting inside another setting, use a dot: `--updates.is-active true`.
- For a list, repeat the flag: `--tools Stock-Quote --tools Options-Chain`.

## Build and run automations

```bash
# Workflows (repeat on a schedule)
atlas workflow-list
atlas workflow-create --name "SPY GEX signal" --schedule "30 9 * * 1-5" \
  --tools Stock-Quote --instruction "Every morning, check SPY net gamma" --status active
atlas workflow-run --workflow-id <id>
atlas workflow-review --workflow-id <id>     # a run held for your review: read it, place it or throw it away
atlas workflow-history --workflow-id <id>    # earlier versions, and going back to one

# Alerts
atlas list-alerts
atlas create-alert --name "SPY sweeps" --symbol SPY --alert-type flow \
  --conditions.min-premium 50000 --conditions.side call

# The gamma flip: SPY's price crossing a flip level into negative gamma
atlas create-alert --name "SPY gamma flip" --symbol SPY --alert-type king_node \
  --conditions.metric gamma --conditions.move-mode flip_negative

# The price crossing under the gamma wall (above it is the positive side)
atlas create-alert --name "SPY under the wall" --symbol SPY --alert-type level_approach \
  --conditions.metric gamma --conditions.region-mode flip_negative
```

Both only go off on a real crossing, never because they started on that side.
Add `--conditions.intraday-only true` to ignore moves that happened
overnight.

## Post a play, or take one

A [play](/atlas/setup-guide/concept-signals) is a call you make yourself. Leave
`--group-id` off and it goes to the community board, where anyone paying can
read it and nobody trades it automatically.

```bash
atlas signal-groups                      # where you can post
atlas signal-post --symbol SPY --option-type call --strike 780 \
  --expiration-date 2026-08-21 --targets 50 --targets 100 --stop 40 \
  --reason "Gamma wall at 780, buyers stepping in"
atlas signal-list                        # the board, newest first
atlas signal-take --signal-id <id>       # places a REAL order in your account
```

Add `--trade-for-me true` to take your own call as you post it. You do not
need to name a broker: once you have a default account, every play uses it.

```bash
atlas signal-trade-settings                       # your defaults, accounts and each group's settings
atlas signal-trade-settings --max-per-trade 500   # the most one trade may spend
atlas signal-discover                             # public groups you can follow
atlas signal-follow --group-id <id>               # follow one. Nothing is placed by following
atlas signal-pending                              # plays waiting for your yes
atlas signal-answer --signal-id <id> --accept true   # places a REAL order
```

## Your trades, your memory, your connectors

```bash
atlas account-activity --include open        # the trades you are in right now
atlas trade-close --trade-id <id>            # close one. REAL order
atlas memory-recall --query "position size"  # what Atlas remembers about this
atlas mcp-tools                              # the servers you connected, and their tools
atlas phone-notify --title "Backtest finished"   # a notification on your own phone
```

## Watch live feeds

```bash
atlas alerts --symbol SPY --name greek_exposure
atlas flow stream --symbol NVDA
```

---

# All tools in the CLI

Every tool, grouped by area. Type the command shown and add settings as flags.

## Stocks

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas multi-timeframe-price-overview` | Premium | Daily / weekly / monthly snapshot in one image. |
| `atlas price-data-ohlcv` | Premium | Historical OHLCV bars. |
| `atlas price-chart` | Premium | Candlestick price chart with overlays. |
| `atlas stock-quote` | Premium | Latest quote for a symbol. |

## Options

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas option-expiration-dates` | Premium | Available expirations for a symbol. |
| `atlas options-chain` | Premium | Full options chain for an expiration. |
| `atlas single-option-quote` | Premium | Bid/ask/IV/greeks for one contract. |
| `atlas historical-contract-greeks` | Premium | Day-by-day price history and greeks for ONE option contract, bid/ask/mid, the underlying's price, days to expiry, IV, delta, gamma, theta, vanna. Up to 90 trading days per call. |
| `atlas historical-options-chain` | Premium | The options chain as it stood on a past day: each contract's prices and volume, plus that day's call volume, put volume and put/call ratio. One expiration per call. |
| `atlas put-call-ratio` | Premium | Call against put open interest (plus today's volume) for one stock, over the expirations and strikes you pick, read as which side leads and by how much. |

## Greek Exposure

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas greek-exposure-multi-expiration` | Premium | Net Gamma / Delta / Vanna / Theta exposure DATA grid across MULTIPLE expirations for one symbol, OI-weighted per-strike numbers (no chart). Sibling of Greek-Exposure-Single-Expiration (same data, one date) and Greek-Exposure-Heatmap (same numbers rendered as PNG). |
| `atlas greek-exposure-single-expiration` | Premium | Greek exposures for ONE expiration date only, guaranteed single-chain fetch. Use when the caller knows the date (0DTE, weekly, monthly OPEX, dated event). |
| `atlas greek-exposure-heatmap` | Premium | Heatmaps for one or more greeks in a single call. Pass greeks=["gamma","delta","vanna","theta"] (any subset). Returns one PNG per requested greek. |
| `atlas net-exposure-charts` | Premium | Net exposure bar charts for one or more greeks. metrics=["net_gex","net_dex","net_vex","net_tex"]. Returns one PNG per metric. |

## Options Flow

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas top-volume-and-oi-contracts` | Premium | Top contracts by volume / OI as data. |
| `atlas volume-and-oi-charts` | Premium | Top-volume and/or open-interest charts. types=["vol","oi","vol_oi"]. Returns one PNG per requested type. |
| `atlas options-flow` | Premium | Stored option-trade tape filtered by side / type / premium / size / time window. Omit symbol for the top-N cross-universe ranking. |
| `atlas options-flow-contract` | Premium | Per-hour premium histogram for ONE contract (open / close stack). Reads strictly from the flow archive cache, never pulls fresh chain. |
| `atlas unusual-flow-ratio` | Premium | Call against put positioning from one day of unusual options trades: which side the big trades leaned to, and by how much. |

## Charts

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas chart-vision-analysis` | Premium | AI vision analysis of a chart image. |
| `atlas multi-chart-view` | Premium | Multi-timeframe charts side-by-side. |

## Fundamentals

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas balance-sheet` | Premium | Latest balance sheet. |
| `atlas financial-metrics` | Premium | Headline valuation + profitability metrics. |
| `atlas income-statement` | Premium | Latest income statement. |

## Estimates

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas analyst-price-targets` | Premium | Consensus price targets. |
| `atlas eps-estimates` | Premium | Consensus EPS estimates. |
| `atlas eps-trend` | Premium | EPS estimate trend. |
| `atlas growth-estimates` | Premium | Growth estimates summary. |
| `atlas revenue-estimates` | Premium | Consensus revenue estimates. |

## Calendar

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas earnings-calendar` | Premium | Upcoming earnings releases. |
| `atlas earnings-dates` | Premium | Earnings dates for a symbol. |
| `atlas ipo-calendar` | Premium | Upcoming IPOs. |

## Ownership

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas insider-transactions` | Premium | Recent insider buys / sells. |
| `atlas institutional-holders` | Premium | Top institutional holders. |
| `atlas sec-filings` | Premium | Recent SEC filings. |
| `atlas senate-lobbying-data` | Premium | Congressional trading / lobbying activity. |

## Brokerage

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas account-balances` | Premium | Cash, buying power, equity for an account. |
| `atlas account-holdings` | Premium | Positions in one linked account. |
| `atlas account-symbol-lookup` | Premium | Resolve a ticker inside a linked account. |
| `atlas all-account-holdings` | Premium | Positions across every linked account. |
| `atlas broker-connections` | Premium | List linked brokerage accounts. |
| `atlas transaction-history` | Premium | Transaction history with optional date range. |

## Trading: Orders

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas cancel-order` | Free | Cancel one order: a staged one is discarded, a placed one that is still waiting is cancelled at the broker. |
| `atlas list-preview-orders` | Free | List staged previews not yet placed. |
| `atlas place-order` | Premium | Submit a previously previewed order. |
| `atlas preview-multiple-orders` | Free | Stage several orders at once. |
| `atlas preview-order` | Free | Stage an order for review without sending it to the broker. |

## Trading: Triggers

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas create-trading-trigger` | Premium | Create a price / condition-based trigger. |
| `atlas delete-trading-trigger` | Premium | Permanently delete a trigger. |
| `atlas list-fired-triggers` | Free | List triggers that already fired. |
| `atlas list-trading-triggers` | Free | List active and paused triggers. |
| `atlas preview-trading-trigger` | Free | Preview a trigger before creating it. |
| `atlas reactivate-trigger` | Premium | Reactivate a fired trigger. |
| `atlas update-trading-trigger` | Premium | Update a trigger (pause / retarget). |

## Plays (signals)

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas signal-schema` | Free | Read this before posting or taking a play. The shape of a play: every field, what each number is measured in, what happens when one is left out, and worked examples. |
| `atlas signal-groups` | Free | The places you can post a play to: the community board, plus every signal group you own or can post in. |
| `atlas signal-list` | Free | Read the plays on the community board, or the private ones, newest first, with what happened to you on each. One page at a time. |
| `atlas signal-show` | Free | Show one play as a card, the same one the Signals tab renders, with every number and what happened to your order. |
| `atlas signal-post` | Free | Post a trade play to the community board or one of your groups: the contract, how much, where to get in, where to take profit, where to get out, and when. |
| `atlas signal-update` | Free | Change a play that is still live instead of posting a second one. Send only what changes, everything left empty keeps what the play already says. |
| `atlas signal-take` | Free / Premium | Take a play: place it in your own account, now. This places a real order. Nothing on the board trades on its own. |
| `atlas signal-broker` | Free | See or set the broker account your plays go to, and whether it is used automatically for plays you post and plays you take. |
| `atlas signal-discover` | Free | Signal groups other people have made public, with who runs each, how many plays it has posted and how many people follow it. |
| `atlas signal-follow` | Free | Follow a public signal group, or stop. Following places nothing by itself: you choose whether its plays are placed for you or wait for your yes. |
| `atlas signal-trade-settings` | Free | See or change how plays are traded for you, for one group or for everything: asked first or placed for you, which account, and the most one trade may spend. Call it empty to read. |
| `atlas signal-pending` | Free | The plays sent to you that are waiting for a yes or no. |
| `atlas signal-answer` | Free / Premium | Say yes or no to a play that was sent to you. Yes places a real order, sized from your trade settings for that group. |
| `atlas signal-my-order` | Free | Change or cancel your own order on someone else's play while it is still waiting to enter. Once it has filled, the way out is Trade-Close. |
| `atlas signal-delete` | Free | Take down a play you posted, before anyone is in it. The orders waiting on it are cancelled. |
| `atlas signal-group-create` | Free | Make a signal group: a place of your own to post plays to. It starts private. |
| `atlas signal-group-update` | Free | Rename a signal group you own, make it public or private, or tag it. A public group can be followed by anyone on Atlas, for free. |
| `atlas signal-group-delete` | Free | Delete a signal group you own, with its plays. If people pay for it, their subscriptions are stopped first so nobody is billed again. |
| `atlas signal-group-performance` | Free | The closed trades of one signal group, with win rate and total profit or loss. |

## Strategy

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas autofetch-strategy` | Free | Auto-pick the best-matching strategy. |
| `atlas fetch-strategy` | Free | Load one strategy by id. |
| `atlas list-strategy` | Free | List your strategies. |
| `atlas strategy-create` | Free | Create a new strategy. |
| `atlas strategy-import` | Free | Copy a public strategy into your account. |
| `atlas strategy-open` | Free | Open the user’s primary strategy. |
| `atlas strategy-preview` | Free | Preview proposed strategy edits. |
| `atlas strategy-save-instructions` | Free | Save strategy-selection instructions. |
| `atlas strategy-discover` | Free | Browse the strategies other people share. Search by title or content, then import one with Strategy-Import. |
| `atlas strategy-duplicate` | Free | Make your own copy of a shared strategy. The same thing as Strategy-Import, under the other name. |
| `atlas strategy-update` | Free | Save changes to an existing strategy. |
| `atlas strategy-delete` | Free | Delete one of your strategies for good. Anyone who imported it keeps their copy. |

## Workflow

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas list-tool-safety` | Free | List which tools are read-only / destructive. |
| `atlas trigger-workflow-schema` | Free | Field schema for trigger / workflow rules. |
| `atlas workflow-apply-updates` | Free | Pull the latest revisions from the parent workflow into this subscribed copy. Use when revisions_behind > 0. |
| `atlas workflow-create` | Free | Create a new perception workflow. |
| `atlas workflow-delete` | Free | Permanently delete a workflow. |
| `atlas workflow-export` | Free | Export a workflow's full node-and-edge graph plus a self-describing markdown rendering. Read-only. |
| `atlas workflow-import` | Free | Copy a public workflow into your account. |
| `atlas workflow-list` | Free | Lightweight programmatic discovery, list every workflow you own with id / name / status / schedule. Read-only. Use before Workflow-Export / Workflow-Logs / Workflow-Run when you need an id. |
| `atlas workflow-logs` | Free | Read recent workflow runs. |
| `atlas workflow-open` | Free | Open a workflow for review / editing. |
| `atlas workflow-performance` | Free | Closed-trade performance for a workflow: per-trade PnL rows and aggregate Win Rate / Total PnL / win-loss-flat counts / calendar-style by_day map. |
| `atlas workflow-preview` | Free | Preview proposed workflow edits. |
| `atlas workflow-run` | Free / Premium | Execute a workflow on demand. |
| `atlas workflow-update` | Free | Save changes to a workflow. |
| `atlas workflow-discover` | Free | Browse the workflows other people share, most imported first. Search by name, rules, or tool. Import one with Workflow-Import. |
| `atlas workflow-duplicate` | Free | Make your own copy of a shared workflow. The same thing as Workflow-Import, under the other name. |
| `atlas workflow-journal` | Free | Read or change a workflow's journal. With journalling on, Atlas writes a note after each of its trades finishes and reads those notes back on later runs. |
| `atlas search-tools` | Free | Search every tool a workflow can use, Atlas's own and those of your connected servers, with the exact name to put in the workflow. |
| `atlas workflow-restore` | Free | Turn a paused workflow back on, with a fresh daily limit. If you are the author, your followers' copies come back with it. |
| `atlas workflow-abort` | Free | Stop a workflow run that is in progress. It does not pause the workflow: the next run happens as usual. |
| `atlas workflow-agent-waiting-runs` | Free | For a workflow your own assistant runs: the runs that came due and are waiting for it, with what started each one. |
| `atlas workflow-agent-report-progress` | Free | For a workflow your own assistant runs: one short line on the workflow's card saying what it is doing right now. |
| `atlas workflow-agent-hand-in-run` | Premium | For a workflow your own assistant runs: hand in what it decided. Atlas checks the trade, holds it for review or places it, sends it to followers and logs the run. Uses one request each time. |
| `atlas workflow-review` | Free / Premium | For a workflow set to let you review each run: see what is waiting, then place it or throw it away. Placing sends real orders. |
| `atlas workflow-history` | Free | A workflow's saved versions, newest first. Open one to read it, or go back to it. |
| `atlas workflow-follow` | Free | On a copy of someone else's workflow: stop taking the author's changes so the copy is your own, or start taking them again. |
| `atlas workflow-operate` | Free | Pause or turn on a workflow whose owner made you an operator. It does what the owner's own pause does, for them and everyone following. |
| `atlas workflow-files` | Premium | The files one of the person's workflows keeps: what its calculations saved (Python code, tables, charts, notes). |

## Account

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas get-instructions` | Free | Read your saved strategy-selection instructions. |
| `atlas side-panel-widgets` | Premium | The widgets under Recents in your side panel on the website and the phone apps: list them, add one, change one, remove one, or move one. |
| `atlas arrange-tabs` | Premium | The order of the tabs in the person's website and phone apps, and the ones they put under More: list them, set one bar's, or put a bar back to how it came. |
| `atlas subscription-status` | Free | Subscription tier, usage, remaining requests. |
| `atlas account-activity` | Free | What has happened on your account lately: every workflow run with its reasoning and any error, plus the trades those runs placed. Newest first. Ask for "open" to see the trades you are in right now. |

## Search

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas connection-check-fetch` | Free | A connection check for apps that look for a fetch tool before they connect. It opens no address. To read the web use Web Search. |
| `atlas connection-check-search` | Free | A connection check for apps that look for a search tool before they connect. It searches nothing. For news and facts use Web Search. |
| `atlas web-search` | Premium | Live web search for real-time news and facts, today's headlines, macro / geopolitical drivers, earnings, and current events, returned as a dated answer plus the source links it used. |
| `atlas ticker-symbol-lookup` | Premium | Resolve a company name to its ticker. |

## Alerts

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas list-alert-types` | Free | Catalog of alert types you can create, read this BEFORE Create-Alert to learn the conditions shape for each type. |
| `atlas list-alerts` | Free | Your streaming alerts. Active-only by default; pass active_only=false to include disarmed / cascade-paused. |
| `atlas preview-alert` | Free | Dry-run an alert spec against the live tape, returns what would have matched without creating the alert. |
| `atlas create-alert` | Free | Create a streaming alert that DMs Discord on fire and optionally arms a trigger / runs a workflow / places an order. ⚠️ Read List-Alert-Types first. |
| `atlas update-alert` | Free | Patch an existing alert in place (rename, change conditions, retarget workflow_id, flip is_active, etc.). |
| `atlas delete-alert` | Free | Soft-delete an alert by flipping is_active=false. The row stays for audit. |
| `atlas list-stream-subscriptions` | Free | Active streaming subscriptions the worker is holding open (flow tape, option quote feeds), useful for debugging why an alert isn't firing. |
| `atlas alert-fires` | Free | The last times your alerts went off, each with the message it sent. Name one alert, or leave it empty for all of them. |

## Workflow: Folders

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas workflow-folder-list` | Free | List your workflow folders and which workflows are filed in each. Folders only organize the list, they never change how a workflow runs. |
| `atlas workflow-folder-create` | Free | Make a folder to organize your Workflows list. You can file workflows into it right away. |
| `atlas workflow-folder-update` | Free | Rename a folder, change its colour, or move it up or down the list. |
| `atlas workflow-folder-move` | Free | File one or more of your workflows into a folder. A workflow sits in one folder at a time, so this takes it out of any other. |
| `atlas workflow-folder-remove` | Free | Take workflows out of a folder. The workflows are not deleted, they just go back to being loose in your list. |
| `atlas workflow-folder-disband` | Free | Delete a folder. The workflows inside are not deleted, they go back to being loose in your list. |
| `atlas workflow-folder-discover` | Free | Folders of workflows other people have shared. Name one to see what importing it would give you. |
| `atlas workflow-folder-import` | Free | Get your own copy of every shared workflow in a folder. Each copy arrives with no broker chosen, so nothing trades until you pick one and turn it on. |

## Workflow: Working together

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas workflow-proposal-list` | Free | List the changes people have suggested to a workflow, what each one touches, whether it is still open, and whether it went stale because the author edited since. |
| `atlas workflow-proposal-show` | Free | Read one suggested change in full, with what the workflow said before, what it would say, and what it says right now. |
| `atlas workflow-proposal-comment` | Free | Leave feedback on a suggested change. Name a part of the change to attach the note to that part instead of the whole thing. |
| `atlas workflow-collab-find` | Free | Find someone on Atlas by name or username, to share a workflow with. |
| `atlas workflow-collab-remove` | Free | Take someone off your workflow, or leave one you were added to. |

## Trading: Open trades

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas trade-close` | Free | Close a position now, everything still open on it, at market. Only the person who owns the trade can close it. A real position needs a market, so outside 9:30 to 4 Eastern this refuses. |
| `atlas trade-take-profit` | Free | Sell the next take profit rung now, without waiting for its price. One rung per call. To take everything at once use Trade-Close. |
| `atlas trade-cancel-entry` | Free | Take an order off before it fills. Only while the entry is still waiting at its price, once it has filled the way out is Trade-Close. |
| `atlas trade-edit-entry` | Free | Move the price an order is waiting to enter at, or turn back on an order that was taken off before it filled. |
| `atlas trade-edit-exit` | Free | Move the stop or the take profit targets on a trade you are in. Only the person whose trade it is can do this, and the move reaches everyone following it. |

## Guide

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas atlas-guide-index` | Free | The Atlas guide's table of contents: every topic, grouped, with the id and link for each. Start here, then read the one that matches. |
| `atlas atlas-guide-search` | Free | Search the guide for a word or phrase and get the topics that mention it, each with a snippet and a link. |
| `atlas atlas-guide-read` | Free | Read one topic of the guide in full, by its id. Returns the whole page and its link, the same text the docs site shows. |
| `atlas atlas-agent-guide` | Free | The short manual an AI assistant reads before it uses Atlas: which tool does what, the order to call them in, and the rules that keep a call from placing something by mistake. |

## Your connected servers

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas mcp-tools` | Free | The servers you have connected to Atlas (Connect, then MCP Servers), and what each of their tools takes. |
| `atlas mcp-call` | Free | Run one tool on a server you have connected. Atlas signs in to that server for you with the sign in you saved. |

## Memory

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas memory-recall` | Free | What Atlas remembers about you that bears on a question, on your profile or on one of your computers. Each memory says who stored it. Ask with a few words. |
| `atlas memory-list` | Free | Everything Atlas remembers about you, with who stored each memory, what was forgotten and can be brought back, whether Memory sharing is on, and which of your computers are connected. |
| `atlas memory-write` | Free | Keep something lasting about you: a correction, a preference, a fact about how you trade. The assistant says who it is, and that name is kept with the memory. Giving it a name replaces the older memory with that name. |
| `atlas memory-update` | Free | Change one memory: its words, how important it is, how long it is kept, or pin it so it is never retired. |
| `atlas memory-forget` | Free | Forget one memory that is wrong or out of date. It waits in the trash for 30 days, with who forgot it and why, and Memory-Restore brings it back. |
| `atlas memory-check-already-remembered` | Free | What is already remembered close to a statement, so a new memory replaces the old one instead of sitting beside it. |
| `atlas memory-restore` | Free | Bring back a memory that was forgotten, while it is still in the 30 day trash. |

## Phone

| Command | Plan | What it does |
| --- | --- | --- |
| `atlas phone-notify` | Free | Send a notification to your own phone, in the MindVest Atlas app, from a script, the command line or a chat. It reaches nobody else. |
| `atlas phone-notify-preview` | Premium | Show how a notification will look on the person's phone, on an iPhone and on Android, before it is sent with Phone-Notify. |
| `atlas phone-button` | Free | Whether you pressed the button on a notification sent with Phone-Notify, for a script that is waiting on your answer. |

---

<!-- ==== Web API ==== -->

# Web API

You can call every Atlas tool with a normal web request. This is the way to use
Atlas from your own code or a script.

## Where to send it

```text
https://atlasmcp.finmanagerai.com
```

## How to call any tool

Send a **POST** to `/api/v1/tools/<tool-name>`. Put the tool's settings in the
body as JSON. Add your key in the header.

```bash
export ATLAS_BASE_URL="https://atlasmcp.finmanagerai.com"
export ATLAS_KEY="<your key>"

curl -sS -X POST "$ATLAS_BASE_URL/api/v1/tools/get_stock_quote" \
  -H "Authorization: Bearer $ATLAS_KEY" \
  -H "Content-Type: application/json" \
  -d '{"symbol":"AAPL"}'
```

## What comes back

You get JSON back. Data tools give you the fields for that tool plus the time.
Chart tools give you an `images` list, and each image has its picture data.
If something goes wrong you get an error message and a non-200 code.

## Get the full list in code

```bash
curl -sS -H "Authorization: Bearer $ATLAS_KEY" "$ATLAS_BASE_URL/api/v1/tools"
```

Or open [/atlas-tools.json](/atlas-tools.json).

## Plans and limits

- **Free** tools never use a request. They are the ones that make, change and
  read your own setups: workflows, strategies, plays, folders, alerts, order
  previews, your results, memory.
- **Premium** tools use one of your monthly requests. That is every tool that
  fetches data (quotes, charts, options, company numbers, web search, your
  broker account), plus placing an order and setting up a trigger. Several in a
  row within a few seconds count once.
- See [Plans and how you get charged](#plans-and-billing) for the full picture,
  including how a live trade that Atlas later changes uses one more request.

:::warning
Your key is a secret. Anyone who has it can use tools on your account and, for
trading tools, place real orders with your broker. Never put it in a web page or
share it. You can make a new one anytime from the dashboard.
:::

There are **164 tools**. The list below shows the address for each one,
whether it is free, and what it does.

---

# Let your AI start the sign in

If you are building an assistant, it can get a person signed in to Atlas without
you writing a sign in screen at all. Your assistant asks Atlas for a link, gives
the link to the person, and waits. The person signs in or makes an account in
their own browser. Your assistant then gets a key and saves it.

This is for anything that cannot open the normal sign in window: your own agent,
a terminal tool, a bot. Chat apps like ChatGPT and Claude already do this part
for you when you add the [Atlas link](#connect-overview).

## First, check one thing

**Can your assistant save a token somewhere that outlives the conversation?** A
config file, a keychain, a database row, an environment variable it controls.
The context window does not count.

| | What to do |
| --- | --- |
| **Yes, it can save one** | Use the three steps below. |
| **No, it cannot** | Do not start this flow. Tell the person to add the [Atlas connector](#connect-overview) to their chat app instead, and sign in there once. Their app holds the token for them and every Atlas tool works from then on. |

A token your assistant cannot save is a token it will lose. Worse, it may park
it in the conversation to keep it, and then it is in the transcript and in
every log that transcript touches. The connector exists precisely so a chat
window does not have to solve this.

:::note
If you are an AI assistant reading this: you **are** allowed to do this, and you
should offer to. You never touch the person's password. You hand them a link,
they sign in themselves, and you carry on. Not offering leaves them stuck with
"tools unavailable" and no idea that an account is one link away.
:::

:::warning
Your assistant must **never ask the person for their password**, and Atlas will
not take one here. If you send a `password` field to these addresses you get an
error back, on purpose. The person types their password on the Atlas page and
nowhere else.
:::

## Step 1. Ask for a link

```bash
curl -sS -X POST "https://atlasmcp.finmanagerai.com/oauth/device_authorization" \
  -H "Content-Type: application/json" \
  -d '{"mode":"signup","email":"ada@example.com","first_name":"Ada","last_name":"Lovelace"}'
```

Everything in the body is optional. An empty `{}` works. But if your assistant
already learned the person's name and email in the conversation, send them: the
sign up form comes up filled in, with the password box empty.

| Field | What it does |
| --- | --- |
| `mode` | `signin` (the default) or `signup`. Picks which page opens. |
| `email`, `first_name`, `last_name` | Fills in the sign up form so the person does not retype it. |
| `scope` | `atlas` (the default) or `atlas broker`. Ask for `broker` only if you need their brokerage. |

What you get back:

```json
{
  "device_code": "d604f83d8ab7...",
  "user_code": "5J39-GWVN",
  "verification_uri_complete": "https://atlasmcp.finmanagerai.com/auth/start?code=5J39-GWVN",
  "expires_in": 900,
  "interval": 5,
  "instructions": "Give the person this link and wait: ..."
}
```

`instructions` is a plain sentence written for an AI to follow. If your
assistant reads it, it knows what to do next without any of these docs.

:::note
The link carries the code and nothing else. The name and email you sent are held
on the Atlas server against that code, so nothing personal ends up in the
person's browser history or in any log along the way.
:::

## Step 2. Give the person the link

Hand them `verification_uri_complete`. They land on the normal Atlas sign in
page and can use **Email**, **Apple**, **Google**, or **Discord**. If you asked for
`signup`, the make an account form opens instead, already filled in.

After they sign in they see who is asking, what it wants, and the code they were
given. They press **Authorize**. Signing in is not enough on its own: someone has
to press the button, so a link forwarded to the wrong person cannot connect them
by accident.

The link lasts **15 minutes**. If it runs out, ask for a new one.

## Step 3. Wait for the key

Poll the token address every `interval` seconds:

```bash
curl -sS -X POST "https://atlasmcp.finmanagerai.com/oauth/token" \
  -H "Content-Type: application/json" \
  -d '{
    "grant_type": "urn:ietf:params:oauth:grant-type:device_code",
    "device_code": "d604f83d8ab7...",
    "client_id": "atlas_agent_public"
  }'
```

While you wait you get a 400 with one of these:

| Answer | What it means |
| --- | --- |
| `authorization_pending` | They have not finished yet. Keep waiting. |
| `slow_down` | You are asking too often. Use the new `interval` it sends back. |
| `expired_token` | The link ran out, or it was already used. Go back to step 1. |
| `access_denied` | The person said no. |

When they are done, you get the key:

```json
{
  "access_token": "at_...",
  "token_type": "Bearer",
  "expires_in": 28800,
  "refresh_token": "rt_...",
  "scope": "atlas"
}
```

Save `access_token` and send it on every call from then on:

```bash
curl -sS -X POST "https://atlasmcp.finmanagerai.com/api/v1/tools/get_stock_quote" \
  -H "Authorization: Bearer at_..." \
  -H "Content-Type: application/json" \
  -d '{"symbol":"AAPL"}'
```

A device code buys exactly one key. Asking again with the same `device_code`
gets you `expired_token`.

## Keep it working

`access_token` lasts 8 hours. Use `refresh_token` to get a fresh one without
bothering the person again:

```bash
curl -sS -X POST "https://atlasmcp.finmanagerai.com/oauth/token" \
  -H "Content-Type: application/json" \
  -d '{
    "grant_type": "refresh_token",
    "refresh_token": "rt_...",
    "client_id": "atlas_agent_public"
  }'
```

This is different from the permanent key on the
[Profile tab](#authentication). That one never expires and is meant for your own
scripts. This one belongs to the person who signed in, and it refreshes.

## Your assistant can find all this on its own

Any Web API call with no key, or a key that has run out, answers with a 401 that
says what to do about it:

```json
{
  "error": "not_signed_in",
  "message": "This request has no Atlas account behind it. An Atlas account is free and takes a minute to create.",
  "signin_url": "https://atlasmcp.finmanagerai.com/auth/start",
  "device_authorization_endpoint": "https://atlasmcp.finmanagerai.com/oauth/device_authorization",
  "how": "POST ... give the person the verification_uri_complete ... never ask them for a password ..."
}
```

So an assistant that hits Atlas without a key can offer to get the person signed
in, instead of only reporting that the tools did not work.

---

# All tools over the web

Every tool, grouped by area. Send a **POST** to the address shown, with your key
in the header (see [how to call any tool](#api-overview)).

## Stocks

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/visualize_price_overview` | Premium | Daily / weekly / monthly snapshot in one image. |
| `POST /api/v1/tools/get_price_data` | Premium | Historical OHLCV bars. |
| `POST /api/v1/tools/visualize_price_chart` | Premium | Candlestick price chart with overlays. |
| `POST /api/v1/tools/get_stock_quote` | Premium | Latest quote for a symbol. |

## Options

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/get_option_expirations` | Premium | Available expirations for a symbol. |
| `POST /api/v1/tools/get_options_chain` | Premium | Full options chain for an expiration. |
| `POST /api/v1/tools/get_single_option_quote` | Premium | Bid/ask/IV/greeks for one contract. |
| `POST /api/v1/tools/get_historical_contract_greeks` | Premium | Day-by-day price history and greeks for ONE option contract, bid/ask/mid, the underlying's price, days to expiry, IV, delta, gamma, theta, vanna. Up to 90 trading days per call. |
| `POST /api/v1/tools/get_historical_options_chain` | Premium | The options chain as it stood on a past day: each contract's prices and volume, plus that day's call volume, put volume and put/call ratio. One expiration per call. |
| `POST /api/v1/tools/put_call_ratio` | Premium | Call against put open interest (plus today's volume) for one stock, over the expirations and strikes you pick, read as which side leads and by how much. |

## Greek Exposure

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/analyze_greek_exposures` | Premium | Net Gamma / Delta / Vanna / Theta exposure DATA grid across MULTIPLE expirations for one symbol, OI-weighted per-strike numbers (no chart). Sibling of Greek-Exposure-Single-Expiration (same data, one date) and Greek-Exposure-Heatmap (same numbers rendered as PNG). |
| `POST /api/v1/tools/greek_exposure_single_expiration` | Premium | Greek exposures for ONE expiration date only, guaranteed single-chain fetch. Use when the caller knows the date (0DTE, weekly, monthly OPEX, dated event). |
| `POST /api/v1/tools/greek_exposure_heatmap` | Premium | Heatmaps for one or more greeks in a single call. Pass greeks=["gamma","delta","vanna","theta"] (any subset). Returns one PNG per requested greek. |
| `POST /api/v1/tools/net_exposure_charts` | Premium | Net exposure bar charts for one or more greeks. metrics=["net_gex","net_dex","net_vex","net_tex"]. Returns one PNG per metric. |

## Options Flow

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/get_volume_oi_data` | Premium | Top contracts by volume / OI as data. |
| `POST /api/v1/tools/volume_and_oi_charts` | Premium | Top-volume and/or open-interest charts. types=["vol","oi","vol_oi"]. Returns one PNG per requested type. |
| `POST /api/v1/tools/get_options_flow` | Premium | Stored option-trade tape filtered by side / type / premium / size / time window. Omit symbol for the top-N cross-universe ranking. |
| `POST /api/v1/tools/get_options_flow_contract` | Premium | Per-hour premium histogram for ONE contract (open / close stack). Reads strictly from the flow archive cache, never pulls fresh chain. |
| `POST /api/v1/tools/unusual_flow_ratio` | Premium | Call against put positioning from one day of unusual options trades: which side the big trades leaned to, and by how much. |

## Charts

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/vision_analysis` | Premium | AI vision analysis of a chart image. |
| `POST /api/v1/tools/visualize_multi` | Premium | Multi-timeframe charts side-by-side. |

## Fundamentals

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/get_balance_sheet` | Premium | Latest balance sheet. |
| `POST /api/v1/tools/get_basic_financials` | Premium | Headline valuation + profitability metrics. |
| `POST /api/v1/tools/get_income_statement` | Premium | Latest income statement. |

## Estimates

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/get_analyst_price_targets` | Premium | Consensus price targets. |
| `POST /api/v1/tools/get_earnings_estimates` | Premium | Consensus EPS estimates. |
| `POST /api/v1/tools/get_eps_trend` | Premium | EPS estimate trend. |
| `POST /api/v1/tools/get_growth_estimates` | Premium | Growth estimates summary. |
| `POST /api/v1/tools/get_revenue_estimates` | Premium | Consensus revenue estimates. |

## Calendar

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/get_earnings_calendar` | Premium | Upcoming earnings releases. |
| `POST /api/v1/tools/get_earnings_dates` | Premium | Earnings dates for a symbol. |
| `POST /api/v1/tools/get_ipo_calendar` | Premium | Upcoming IPOs. |

## Ownership

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/get_insider_transactions` | Premium | Recent insider buys / sells. |
| `POST /api/v1/tools/get_institutional_holders` | Premium | Top institutional holders. |
| `POST /api/v1/tools/get_sec_filings` | Premium | Recent SEC filings. |
| `POST /api/v1/tools/get_senate_lobbying` | Premium | Congressional trading / lobbying activity. |

## Brokerage

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/get_account_balances` | Premium | Cash, buying power, equity for an account. |
| `POST /api/v1/tools/get_holdings` | Premium | Positions in one linked account. |
| `POST /api/v1/tools/get_account_symbol` | Premium | Resolve a ticker inside a linked account. |
| `POST /api/v1/tools/get_all_holdings` | Premium | Positions across every linked account. |
| `POST /api/v1/tools/list_broker_connections` | Premium | List linked brokerage accounts. |
| `POST /api/v1/tools/get_transactions` | Premium | Transaction history with optional date range. |

## Trading: Orders

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/cancel_order` | Free | Cancel one order: a staged one is discarded, a placed one that is still waiting is cancelled at the broker. |
| `POST /api/v1/tools/list_preview_orders` | Free | List staged previews not yet placed. |
| `POST /api/v1/tools/place_order` | Premium | Submit a previously previewed order. |
| `POST /api/v1/tools/preview_multiple_orders` | Free | Stage several orders at once. |
| `POST /api/v1/tools/preview_order` | Free | Stage an order for review without sending it to the broker. |

## Trading: Triggers

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/create_trading_trigger` | Premium | Create a price / condition-based trigger. |
| `POST /api/v1/tools/delete_trading_trigger` | Premium | Permanently delete a trigger. |
| `POST /api/v1/tools/list_fired_triggers` | Free | List triggers that already fired. |
| `POST /api/v1/tools/list_trading_triggers` | Free | List active and paused triggers. |
| `POST /api/v1/tools/preview_trading_trigger` | Free | Preview a trigger before creating it. |
| `POST /api/v1/tools/reactivate_trigger` | Premium | Reactivate a fired trigger. |
| `POST /api/v1/tools/update_trading_trigger` | Premium | Update a trigger (pause / retarget). |

## Plays (signals)

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/signal_schema` | Free | Read this before posting or taking a play. The shape of a play: every field, what each number is measured in, what happens when one is left out, and worked examples. |
| `POST /api/v1/tools/signal_groups` | Free | The places you can post a play to: the community board, plus every signal group you own or can post in. |
| `POST /api/v1/tools/signal_list` | Free | Read the plays on the community board, or the private ones, newest first, with what happened to you on each. One page at a time. |
| `POST /api/v1/tools/signal_show` | Free | Show one play as a card, the same one the Signals tab renders, with every number and what happened to your order. |
| `POST /api/v1/tools/signal_post` | Free | Post a trade play to the community board or one of your groups: the contract, how much, where to get in, where to take profit, where to get out, and when. |
| `POST /api/v1/tools/signal_update` | Free | Change a play that is still live instead of posting a second one. Send only what changes, everything left empty keeps what the play already says. |
| `POST /api/v1/tools/signal_take` | Free / Premium | Take a play: place it in your own account, now. This places a real order. Nothing on the board trades on its own. |
| `POST /api/v1/tools/signal_broker` | Free | See or set the broker account your plays go to, and whether it is used automatically for plays you post and plays you take. |
| `POST /api/v1/tools/signal_discover` | Free | Signal groups other people have made public, with who runs each, how many plays it has posted and how many people follow it. |
| `POST /api/v1/tools/signal_follow` | Free | Follow a public signal group, or stop. Following places nothing by itself: you choose whether its plays are placed for you or wait for your yes. |
| `POST /api/v1/tools/trade_settings` | Free | See or change how plays are traded for you, for one group or for everything: asked first or placed for you, which account, and the most one trade may spend. Call it empty to read. |
| `POST /api/v1/tools/signal_pending` | Free | The plays sent to you that are waiting for a yes or no. |
| `POST /api/v1/tools/signal_answer` | Free / Premium | Say yes or no to a play that was sent to you. Yes places a real order, sized from your trade settings for that group. |
| `POST /api/v1/tools/signal_my_order` | Free | Change or cancel your own order on someone else's play while it is still waiting to enter. Once it has filled, the way out is Trade-Close. |
| `POST /api/v1/tools/signal_delete` | Free | Take down a play you posted, before anyone is in it. The orders waiting on it are cancelled. |
| `POST /api/v1/tools/signal_group_create` | Free | Make a signal group: a place of your own to post plays to. It starts private. |
| `POST /api/v1/tools/signal_group_update` | Free | Rename a signal group you own, make it public or private, or tag it. A public group can be followed by anyone on Atlas, for free. |
| `POST /api/v1/tools/signal_group_delete` | Free | Delete a signal group you own, with its plays. If people pay for it, their subscriptions are stopped first so nobody is billed again. |
| `POST /api/v1/tools/signal_group_performance` | Free | The closed trades of one signal group, with win rate and total profit or loss. |

## Strategy

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/autofetch_strategy` | Free | Auto-pick the best-matching strategy. |
| `POST /api/v1/tools/fetch_strategy` | Free | Load one strategy by id. |
| `POST /api/v1/tools/list_strategy` | Free | List your strategies. |
| `POST /api/v1/tools/create_strategy` | Free | Create a new strategy. |
| `POST /api/v1/tools/strategy_import` | Free | Copy a public strategy into your account. |
| `POST /api/v1/tools/open_strategy` | Free | Open the user’s primary strategy. |
| `POST /api/v1/tools/strategy_preview` | Free | Preview proposed strategy edits. |
| `POST /api/v1/tools/save_strategy_instructions` | Free | Save strategy-selection instructions. |
| `POST /api/v1/tools/strategy_discover` | Free | Browse the strategies other people share. Search by title or content, then import one with Strategy-Import. |
| `POST /api/v1/tools/strategy_duplicate` | Free | Make your own copy of a shared strategy. The same thing as Strategy-Import, under the other name. |
| `POST /api/v1/tools/update_strategy` | Free | Save changes to an existing strategy. |
| `POST /api/v1/tools/delete_strategy` | Free | Delete one of your strategies for good. Anyone who imported it keeps their copy. |

## Workflow

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/list_tool_safety` | Free | List which tools are read-only / destructive. |
| `POST /api/v1/tools/trigger_workflow_schema` | Free | Field schema for trigger / workflow rules. |
| `POST /api/v1/tools/workflow_apply_updates` | Free | Pull the latest revisions from the parent workflow into this subscribed copy. Use when revisions_behind > 0. |
| `POST /api/v1/tools/workflow_create` | Free | Create a new perception workflow. |
| `POST /api/v1/tools/workflow_delete` | Free | Permanently delete a workflow. |
| `POST /api/v1/tools/workflow_export` | Free | Export a workflow's full node-and-edge graph plus a self-describing markdown rendering. Read-only. |
| `POST /api/v1/tools/workflow_import` | Free | Copy a public workflow into your account. |
| `POST /api/v1/tools/workflow_list` | Free | Lightweight programmatic discovery, list every workflow you own with id / name / status / schedule. Read-only. Use before Workflow-Export / Workflow-Logs / Workflow-Run when you need an id. |
| `POST /api/v1/tools/workflow_logs` | Free | Read recent workflow runs. |
| `POST /api/v1/tools/workflow_open` | Free | Open a workflow for review / editing. |
| `POST /api/v1/tools/workflow_performance` | Free | Closed-trade performance for a workflow: per-trade PnL rows and aggregate Win Rate / Total PnL / win-loss-flat counts / calendar-style by_day map. |
| `POST /api/v1/tools/workflow_preview` | Free | Preview proposed workflow edits. |
| `POST /api/v1/tools/workflow_run` | Free / Premium | Execute a workflow on demand. |
| `POST /api/v1/tools/workflow_update` | Free | Save changes to a workflow. |
| `POST /api/v1/tools/workflow_discover` | Free | Browse the workflows other people share, most imported first. Search by name, rules, or tool. Import one with Workflow-Import. |
| `POST /api/v1/tools/workflow_duplicate` | Free | Make your own copy of a shared workflow. The same thing as Workflow-Import, under the other name. |
| `POST /api/v1/tools/workflow_journal` | Free | Read or change a workflow's journal. With journalling on, Atlas writes a note after each of its trades finishes and reads those notes back on later runs. |
| `POST /api/v1/tools/search_tools` | Free | Search every tool a workflow can use, Atlas's own and those of your connected servers, with the exact name to put in the workflow. |
| `POST /api/v1/tools/workflow_restore` | Free | Turn a paused workflow back on, with a fresh daily limit. If you are the author, your followers' copies come back with it. |
| `POST /api/v1/tools/workflow_abort` | Free | Stop a workflow run that is in progress. It does not pause the workflow: the next run happens as usual. |
| `POST /api/v1/tools/workflow_agent_waiting_runs` | Free | For a workflow your own assistant runs: the runs that came due and are waiting for it, with what started each one. |
| `POST /api/v1/tools/workflow_agent_report_progress` | Free | For a workflow your own assistant runs: one short line on the workflow's card saying what it is doing right now. |
| `POST /api/v1/tools/workflow_agent_hand_in_run` | Premium | For a workflow your own assistant runs: hand in what it decided. Atlas checks the trade, holds it for review or places it, sends it to followers and logs the run. Uses one request each time. |
| `POST /api/v1/tools/workflow_review` | Free / Premium | For a workflow set to let you review each run: see what is waiting, then place it or throw it away. Placing sends real orders. |
| `POST /api/v1/tools/workflow_history` | Free | A workflow's saved versions, newest first. Open one to read it, or go back to it. |
| `POST /api/v1/tools/workflow_follow` | Free | On a copy of someone else's workflow: stop taking the author's changes so the copy is your own, or start taking them again. |
| `POST /api/v1/tools/workflow_operate` | Free | Pause or turn on a workflow whose owner made you an operator. It does what the owner's own pause does, for them and everyone following. |
| `POST /api/v1/tools/workflow_files` | Premium | The files one of the person's workflows keeps: what its calculations saved (Python code, tables, charts, notes). |

## Account

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/get_instructions` | Free | Read your saved strategy-selection instructions. |
| `POST /api/v1/tools/side_panel_widgets` | Premium | The widgets under Recents in your side panel on the website and the phone apps: list them, add one, change one, remove one, or move one. |
| `POST /api/v1/tools/arrange_tabs` | Premium | The order of the tabs in the person's website and phone apps, and the ones they put under More: list them, set one bar's, or put a bar back to how it came. |
| `POST /api/v1/tools/get_subscription_status` | Free | Subscription tier, usage, remaining requests. |
| `POST /api/v1/tools/account_activity` | Free | What has happened on your account lately: every workflow run with its reasoning and any error, plus the trades those runs placed. Newest first. Ask for "open" to see the trades you are in right now. |

## Search

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/connection_check_fetch` | Free | A connection check for apps that look for a fetch tool before they connect. It opens no address. To read the web use Web Search. |
| `POST /api/v1/tools/connection_check_search` | Free | A connection check for apps that look for a search tool before they connect. It searches nothing. For news and facts use Web Search. |
| `POST /api/v1/tools/web_search` | Premium | Live web search for real-time news and facts, today's headlines, macro / geopolitical drivers, earnings, and current events, returned as a dated answer plus the source links it used. |
| `POST /api/v1/tools/resolve_ticker` | Premium | Resolve a company name to its ticker. |

## Alerts

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/list_alert_types` | Free | Catalog of alert types you can create, read this BEFORE Create-Alert to learn the conditions shape for each type. |
| `POST /api/v1/tools/list_alerts` | Free | Your streaming alerts. Active-only by default; pass active_only=false to include disarmed / cascade-paused. |
| `POST /api/v1/tools/preview_alert` | Free | Dry-run an alert spec against the live tape, returns what would have matched without creating the alert. |
| `POST /api/v1/tools/create_alert` | Free | Create a streaming alert that DMs Discord on fire and optionally arms a trigger / runs a workflow / places an order. ⚠️ Read List-Alert-Types first. |
| `POST /api/v1/tools/update_alert` | Free | Patch an existing alert in place (rename, change conditions, retarget workflow_id, flip is_active, etc.). |
| `POST /api/v1/tools/delete_alert` | Free | Soft-delete an alert by flipping is_active=false. The row stays for audit. |
| `POST /api/v1/tools/list_stream_subscriptions` | Free | Active streaming subscriptions the worker is holding open (flow tape, option quote feeds), useful for debugging why an alert isn't firing. |
| `POST /api/v1/tools/list_alert_fires` | Free | The last times your alerts went off, each with the message it sent. Name one alert, or leave it empty for all of them. |

## Workflow: Folders

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/workflow_folders_list` | Free | List your workflow folders and which workflows are filed in each. Folders only organize the list, they never change how a workflow runs. |
| `POST /api/v1/tools/workflow_folder_create` | Free | Make a folder to organize your Workflows list. You can file workflows into it right away. |
| `POST /api/v1/tools/workflow_folder_update` | Free | Rename a folder, change its colour, or move it up or down the list. |
| `POST /api/v1/tools/workflow_folder_move` | Free | File one or more of your workflows into a folder. A workflow sits in one folder at a time, so this takes it out of any other. |
| `POST /api/v1/tools/workflow_folder_remove` | Free | Take workflows out of a folder. The workflows are not deleted, they just go back to being loose in your list. |
| `POST /api/v1/tools/workflow_folder_disband` | Free | Delete a folder. The workflows inside are not deleted, they go back to being loose in your list. |
| `POST /api/v1/tools/workflow_folder_discover` | Free | Folders of workflows other people have shared. Name one to see what importing it would give you. |
| `POST /api/v1/tools/workflow_folder_import` | Free | Get your own copy of every shared workflow in a folder. Each copy arrives with no broker chosen, so nothing trades until you pick one and turn it on. |

## Workflow: Working together

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/workflow_proposal_list` | Free | List the changes people have suggested to a workflow, what each one touches, whether it is still open, and whether it went stale because the author edited since. |
| `POST /api/v1/tools/workflow_proposal_show` | Free | Read one suggested change in full, with what the workflow said before, what it would say, and what it says right now. |
| `POST /api/v1/tools/workflow_proposal_comment` | Free | Leave feedback on a suggested change. Name a part of the change to attach the note to that part instead of the whole thing. |
| `POST /api/v1/tools/workflow_collab_find` | Free | Find someone on Atlas by name or username, to share a workflow with. |
| `POST /api/v1/tools/workflow_collab_remove` | Free | Take someone off your workflow, or leave one you were added to. |

## Trading: Open trades

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/trade_close` | Free | Close a position now, everything still open on it, at market. Only the person who owns the trade can close it. A real position needs a market, so outside 9:30 to 4 Eastern this refuses. |
| `POST /api/v1/tools/trade_take_profit` | Free | Sell the next take profit rung now, without waiting for its price. One rung per call. To take everything at once use Trade-Close. |
| `POST /api/v1/tools/trade_cancel_entry` | Free | Take an order off before it fills. Only while the entry is still waiting at its price, once it has filled the way out is Trade-Close. |
| `POST /api/v1/tools/trade_edit_entry` | Free | Move the price an order is waiting to enter at, or turn back on an order that was taken off before it filled. |
| `POST /api/v1/tools/trade_edit_exit` | Free | Move the stop or the take profit targets on a trade you are in. Only the person whose trade it is can do this, and the move reaches everyone following it. |

## Guide

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/atlas_guide_index` | Free | The Atlas guide's table of contents: every topic, grouped, with the id and link for each. Start here, then read the one that matches. |
| `POST /api/v1/tools/atlas_guide_search` | Free | Search the guide for a word or phrase and get the topics that mention it, each with a snippet and a link. |
| `POST /api/v1/tools/atlas_guide_read` | Free | Read one topic of the guide in full, by its id. Returns the whole page and its link, the same text the docs site shows. |
| `POST /api/v1/tools/atlas_agent_guide` | Free | The short manual an AI assistant reads before it uses Atlas: which tool does what, the order to call them in, and the rules that keep a call from placing something by mistake. |

## Your connected servers

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/mcp_tools` | Free | The servers you have connected to Atlas (Connect, then MCP Servers), and what each of their tools takes. |
| `POST /api/v1/tools/mcp_call` | Free | Run one tool on a server you have connected. Atlas signs in to that server for you with the sign in you saved. |

## Memory

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/memory_recall` | Free | What Atlas remembers about you that bears on a question, on your profile or on one of your computers. Each memory says who stored it. Ask with a few words. |
| `POST /api/v1/tools/memory_list` | Free | Everything Atlas remembers about you, with who stored each memory, what was forgotten and can be brought back, whether Memory sharing is on, and which of your computers are connected. |
| `POST /api/v1/tools/memory_write` | Free | Keep something lasting about you: a correction, a preference, a fact about how you trade. The assistant says who it is, and that name is kept with the memory. Giving it a name replaces the older memory with that name. |
| `POST /api/v1/tools/memory_update` | Free | Change one memory: its words, how important it is, how long it is kept, or pin it so it is never retired. |
| `POST /api/v1/tools/memory_forget` | Free | Forget one memory that is wrong or out of date. It waits in the trash for 30 days, with who forgot it and why, and Memory-Restore brings it back. |
| `POST /api/v1/tools/memory_check_already_remembered` | Free | What is already remembered close to a statement, so a new memory replaces the old one instead of sitting beside it. |
| `POST /api/v1/tools/memory_restore` | Free | Bring back a memory that was forgotten, while it is still in the 30 day trash. |

## Phone

| Endpoint | Plan | What it does |
| --- | --- | --- |
| `POST /api/v1/tools/phone_notify` | Free | Send a notification to your own phone, in the MindVest Atlas app, from a script, the command line or a chat. It reaches nobody else. |
| `POST /api/v1/tools/phone_notify_preview` | Premium | Show how a notification will look on the person's phone, on an iPhone and on Android, before it is sent with Phone-Notify. |
| `POST /api/v1/tools/phone_button` | Free | Whether you pressed the button on a notification sent with Phone-Notify, for a script that is waiting on your answer. |

---

# Atlas Studio Documentation

Atlas Studio is the Atlas desktop app for Windows and Mac. You chat with a model
(Claude, ChatGPT, Grok, a model on your own computer, or your own key) and it
builds and runs your own projects on your computer: bots, AI agents, and custom
investing and trading tools, each with its own dashboard. This is the complete
user guide as one Markdown file, written for AI assistants to read.

Source: https://www.mind-vest.io/studio-setup-guide
Download: https://www.mind-vest.io/studio

---

<!-- ==== Atlas Studio: Get started ==== -->

# What is Atlas Studio

Atlas Studio is the Atlas app for your own computer. It works on Windows and Mac. [Download it here](/studio#download).

You chat with an AI model in it, the same way you would in ChatGPT or Claude. The
difference is that the chat can also **do things on your computer**: make and run
your own small projects, show them on a dashboard, remember what matters to you,
and, if you allow it, use your screen and mouse.

![Atlas Studio when you open it: the menu on the left and the chat box in the middle](/studio/docs/studio-home.png)

## What you can do with it

- **Chat** with Claude, ChatGPT, Grok, a model you run on your own computer, or a
  team of models working together.
- **Build projects** by describing them. For example: *"every 5 minutes, check SPY
  and message me on Discord if it gets near a big level"*. Atlas writes it, runs
  it on a schedule and gives it a dashboard.
- **Keep memories**, so you do not have to repeat yourself in every chat.
- **Talk to it out loud**, and hear the answer. See [Talk to Atlas](#studio-voice).
- **Connect your other apps and your broker**, like Notion, Stripe or Robinhood,
  so a chat can use them.
- **Let Atlas use your computer** to click and type for you, and watch it happen.
- **Open the Atlas website inside the app** with the **Cloud** switch. See
  [Local and Cloud](#studio-local-cloud).

## Down the left

| Where | What it is for |
| --- | --- |
| **Local / Cloud** (top) | Switch between this app and the Atlas website. See [Local and Cloud](#studio-local-cloud). |
| [Model settings](#studio-model-settings) | Sign in to your models and pick the one a new chat uses. |
| [Projects](#studio-this-computer) | Your projects, their files, dashboards and chats. |
| **More** | Everything else, like [Memory](#studio-memory). The menu shows four buttons and the rest go here. See [Arrange the sidebar](#studio-arrange). |
| **Recents** | Your last three chats. Click one to go back to it. The three round buttons beside the heading are **See more** (every chat, in [Chat Sessions](#studio-past-chats)), [New chat](#studio-new-chat) and Refresh. |
| **Checks** (under Recents) | A line for a project whose [checks](#studio-checks) found something, with **Resolve issue**. |
| **Widgets** (under Recents) | Small live views your projects made for you. See [Widgets in the side panel](#studio-widgets). |
| **Your name** (bottom) | Opens your [Profile](#studio-profile). |
| **...** next to your name | How many requests you have used this month, your accounts on this computer, dark mode, and sign out. |

:::tip
Atlas Studio and the [web dashboard](/atlas/dashboard) use the same Atlas account.
Your alerts, workflows and signals live on the web. Studio is where things run
**on your computer**. If you are looking for how the website works, see the
[web docs](/atlas/setup-guide).
:::

Page: https://www.mind-vest.io/studio-setup-guide

---

# Install and update

## Install

1. Go to the [Atlas Studio page](/studio#download) and press **Download** for your
   computer: **Windows** or **Mac**. Linux is coming soon.
2. **Windows:** double click the file you downloaded. It installs in one click and
   opens.
   **Mac:** open the file and drag **Atlas Studio** into **Applications**.
3. Open **Atlas Studio**.

The models Atlas needs to chat with Claude and ChatGPT come inside the app. You do
not need to install anything else or open a terminal.

:::note
**The first time on a Mac**, macOS may say it cannot check the app. Open **System
Settings → Privacy & Security**, scroll down and press **Open Anyway**, then type
your Mac password. You only do this once.
:::

| Computer | Needs |
| --- | --- |
| Windows | Windows 10 or newer |
| Mac | macOS 13 (Ventura) or newer. One app for Apple chips and Intel. |
| Linux | Coming soon |

## Keeping it up to date

When a newer version is out, a box appears at the bottom of the left menu:
**New update available**, with the version number and an **Update now** button.

- **Windows:** press **Update now**. Atlas downloads it, closes and opens again on
  the new version. That is all.
- **Mac:** press **Update now**. When it is downloaded the box says
  **Downloaded. Drag it into Applications**. Press **Show me**, then drag the new
  Atlas Studio into your Applications folder, the same as when you installed it.

Atlas checks for updates on its own when it opens and every few hours. To check
right now, go to [Profile](#studio-profile) and press **Check for updates**.

:::note
If nothing appears at the bottom of the menu, you are already on the newest
version.
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-install

---

# Sign in and sign out

Atlas Studio uses your **Atlas account**, the same one you use on the website. If
you do not have one yet, you make it during sign in.

## Signing in

When nobody is signed in, the app opens on one screen: **Sign in to Atlas**.

![The Sign in to Atlas screen, with the Sign in or sign up button](/studio/docs/studio-signed-out.png)

1. Press **Sign in or sign up**.
2. Your web browser opens the Atlas sign in page. Sign in there (or create an
   account).
3. Go back to Atlas Studio. The screen goes away on its own, and your name,
   picture show at the bottom of the left menu. How much you have used is in the **...** beside it.

You only do this once. Closing the app does not sign you out.

## More than one account

Press **...** next to your name at the bottom of the menu. It lists every account
signed in on this computer, with a tick on the one in use.

![The account menu: your accounts, Add account, dark mode and Sign out](/studio/docs/studio-account-menu.png)

- **Add account** signs in another one. You can keep up to five.
- Click an account to switch to it. Only the sign in changes: your projects,
  chats and settings on this computer stay as they are.

## Signing out

There are two ways, and both do the same thing:

- **...** next to your name, then **Sign out**.
- **Profile → Danger Zone → Sign Out**.

Atlas asks you to confirm first. If it is the only account on this computer,
signing out removes this computer's access, so **projects on this computer stop
running** until you sign in again. If another account is signed in here, Studio
carries on as that one. Your chats and files stay on the computer either way.

## Deleting your account

**Profile → Danger Zone → Delete Account** opens the website, where you finish
deleting it. This cannot be undone.

Page: https://www.mind-vest.io/studio-setup-guide/studio-sign-in

---

# Your plan and the two free weeks

Atlas Studio needs an Atlas plan (Pro or higher). Every account gets **two free
weeks**, counted from the first time it uses Atlas Studio or the command line, with
everything working.

During the free weeks a line at the top says how many days are left, with **Open my
account**. The **×** hides it until the next day.

![The free week line: Free week, 3 days left, Open my account](/studio/docs/studio-free-week.png)

When the two weeks end without a plan, Atlas Studio stops doing work: chats cannot be
sent, dashboards and widgets are not shown, projects do not run, and no new orders
are placed. You can still read your files, change settings, stop things, sign out
and switch accounts.

![After the free week: Let's get you back in, with Open my account](/studio/docs/studio-locked.png)

**Open my account** opens your account on the Atlas website in your browser. Pick a
plan there, and Atlas Studio opens again by itself within a minute.

Page: https://www.mind-vest.io/studio-setup-guide/studio-plan

---

# Local and Cloud

At the top of the left menu is a switch with two sides: **Local** and **Cloud**.

![The Local and Cloud switch at the top of the left menu](/studio/docs/studio-local-cloud.png)

| Side | What you see |
| --- | --- |
| **Local** | Atlas Studio itself: your chats, projects and models on this computer. |
| **Cloud** | The [Atlas website](/atlas/dashboard), inside the app, already signed in as you. |

Use **Cloud** for the things that live on the web: workflows, signals, alerts,
triggers and the Marketplace. Use **Local** for everything that runs on
your computer. Nothing is lost when you switch: your local screens are exactly as
you left them when you come back.

- To come back from Cloud, use the same **Local | Cloud** switch at the top of the
  website's menu.
- A link that leaves Atlas opens in your normal web browser.
- Light or dark mode is the same on both sides.
- The app remembers which side you were on the next time it opens.

When the left menu is folded, the switch is one round button.

:::note
Cloud needs the internet. If it cannot reach Atlas it says so, with a **Try
again** button. Your local projects keep running either way.
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-local-cloud

---

# Connect your first model

Atlas Studio does not have its own AI brain. It uses a model you already have, like
your **Claude** or **ChatGPT** account. You connect it once.

If no model is connected yet, the chat shows a yellow bar at the top:
*"Claude needs credentials. Open Model settings to sign in or add a key."*

![The yellow bar that shows when a model is not connected yet](/studio/docs/studio-needs-credentials.png)

## The easy way: sign in with your account

1. Click **Model settings** in the left menu (or the link in the yellow bar).
2. Click the model you have an account with, for example **Claude** or **ChatGPT**.
3. Press **Sign in to Anthropic** (for Claude) or **Sign in to OpenAI** (for
   ChatGPT).
4. Your browser opens. Sign in there with your normal account.
5. Come back to Atlas Studio. The model now shows **connected**.

## The other way: paste a key

If you have an API key from the company instead, open the same model, paste it in
the box under **or paste a key**, and press **Save key**.

You can choose where the key is kept: **OS keychain** (your computer's own locked
storage, recommended) or **.env file** (a plain settings file).

## Pick the model a new chat uses

At the top of Model settings, choose one under **Default model**. Every new chat
starts on it. You can still switch in any chat. See [Change the model](#studio-change-model).

:::tip
Want to run a model entirely on your own computer, with no account at all? See
[Models on this computer](#studio-local-models).
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-first-model

---

<!-- ==== Atlas Studio: Chatting ==== -->

# Start a new chat

Click the small **New chat** button beside **Recents** in the left menu (the square with a pen). With the menu folded, it is the pen under the other icons.

## First, pick a project

Every chat belongs to a **project**. A project is simply a folder on your computer
where the chat keeps its work: files it writes, a dashboard, notes. The chat is
also saved with that project, so you can find it again later.

A small window asks: **Which project?**

![Picking a project for a new chat](/studio/docs/studio-project-picker.png)

- **To use one you already have:** click it, or use the arrow keys and press Enter.
- **To make a new one:** type a new name and press Enter.
- **To go back** without starting a chat: press Esc or click outside the window.

## Making a new project

When you type a new name, Atlas asks what kind of project it is:

![Choosing what kind of project to make](/studio/docs/studio-new-project.png)

| Choice | Pick it when |
| --- | --- |
| **Finance and trading** | You want the full Atlas setup: market data, alerts, your broker and a dashboard. |
| **Start from scratch** | You want an empty folder for anything else. No dashboard, nothing about trading. |

Press **Back** if you want to change the name.

## Then just type

The chat opens with your project's name shown in the chat box. Type what you want
and press Enter. See [The chat box](#studio-chat-box) for everything else it can do.

![A chat with Atlas: the question, the tools it used, and the answer](/studio/docs/studio-chat.png)

:::tip
Leaving a chat while the model is still working does **not** stop it. Go to
another chat, come back later, and the answer is there.
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-new-chat

---

# The chat box

The box at the bottom of a chat is where you type. It has a few buttons around it.

## Sending

- **Enter** sends your message.
- **Shift + Enter** starts a new line without sending.
- While the model is working, the send button turns into a **stop** button. Press
  it to stop the answer.
- If you send another message while it is still working, it waits in a short
  list above the box, **Queued**, and goes as soon as the current answer finishes.
  Up to five can wait. Each one has three small buttons: **Send now** (stops the
  current answer and sends this one), **Edit**, and **Remove**.
- When an answer ends, Atlas may suggest what you could send next, written faint
  in the empty box. Press **Tab** to put it in the box. Nothing is sent until you
  press Enter, and you can change it first.

![Two messages waiting in the Queued list above the chat box while the model is still working](/studio/docs/studio-queued.png)

## The buttons, left to right

| Button | What it does |
| --- | --- |
| **+** | Attach files. See below. |
| **Project name** | Shows which project this chat is in. Click it to chat about a different project. |
| **Options** (the sliders) | **Thinking**: how hard the model thinks (see [How hard it thinks](#studio-change-model)). In a chat about a project also **Checks**, **Dashboard**, **Computer use** and **Widgets**, each opened beside the chat (see **Beside the chat** below). |
| **Model name** | Which model is answering. Click it to [change the model](#studio-change-model). |
| **Microphone and a voice name** | Talk instead of typing. See [Talk to Atlas](#studio-voice). |
| **Arrow** | Send. |

## Attaching files and pictures

There are three ways:

1. Press **+** and choose files.
2. **Paste** a picture or screenshot straight into the box.
3. **Drag** files from your computer onto the box.

Pictures and PDFs show as small previews. Click one to see it bigger; from there
you can **Copy image** or **Save** it. Click the small **×** on a preview to remove
it before you send. Pictures are shown to the model, so you can ask things like
*"what does this chart say?"*.

## Shortcuts inside the box

**Type /** to see the model's own commands, for example one that shortens a long
conversation. What is on the list depends on the model.

![Typing / shows the model's commands](/studio/docs/studio-slash.png)

**Type @** to pick either:

- **a model**, which sends just this one message to that model, or
- **a file** in your project, which sends the file along with your message.

![Typing @ lists models first, then your files](/studio/docs/studio-mention.png)

Use the arrow keys to move, Enter to pick, Esc to close the list.

## Reading the answer

- **While Atlas works** you see what it is doing, in words: a short list of its
  steps ("Read notes.md", "Running run.py") with a tick on each one done and a
  timer on the one in progress.
- **Once it has answered** those steps fold into one line ("Looked up stock
  quote for SPY and saved limits.md"). Click it to see each step by name.
- **A file Atlas changed** says so ("Changed limits.md · 1 line added"). Click it
  to see exactly what changed.
- **Charts** from Atlas show right inside the chat, under the answer that made them.
- **Right click** any message and choose **Copy message** to copy it.

## Files the answer names

When an answer points at one of your project's files, the file's name is written
in **blue**, sometimes with the rows or lines it means (*data/fills.csv · row 3*).
Click it and the file opens **beside the chat**, scrolled to those rows or lines and
marked in amber. The left menu folds out of the way while it is open. Press **×**
to close it.

![A file opened beside the chat, with the row the answer named marked](/studio/docs/studio-file-peek.png)

## Beside the chat

In a chat about a project, the **Options** button in the chat box also opens
these beside the chat, so you never leave it:

- **Checks**: the project's [checks](#studio-checks). They also open here by
  themselves when the project's checks start running.
- **Dashboard**: the project's [dashboard](#studio-dashboard).
- **Computer use**: the screen, while Atlas works on the project's dashboard.
- **Widgets**: the charts this chat drew, one tab each.

![The chat box's Options: Thinking, Checks, Dashboard, Computer use and Widgets](/studio/docs/studio-chat-options.png)

![The project's checks beside the chat](/studio/docs/studio-side-checks.png)

## Several jobs at once

A chat can do more than one thing at a time. Claude and ChatGPT start helpers
for parts of a big job, and the other models (with a key, or on this computer) can
start **background tasks**: up to four at once, two for a model on this computer.

- Each one shows in the chat as a card, with what it is doing.
- You can keep typing while they work. With Claude, what you type goes straight
  into the job in progress.
- When they finish, the chat carries on with what they found, even if you said
  nothing.
- The chat's **stop** button stops them all.

## When something goes wrong

A problem, like a model that stopped or lost its connection, shows as a short
notice at the top of the window. It goes away after a few seconds, or press its
**×**. If it says to pick the model again, click the model name and choose it.

Page: https://www.mind-vest.io/studio-setup-guide/studio-chat-box

---

# Talk to Atlas

You can talk to Atlas out loud and hear it answer, instead of typing.

## Start talking

In the chat box, between the model name and the send arrow, is a **microphone**
with a voice's name on it. Press it and start speaking. On a Mac, the system asks
once for permission to use the microphone.

You can also press the small **microphone** on any chat under **Recents** to talk
in that chat.

## While you are talking

A moving wave and a **Stop voice** button show in the left menu.

![A voice conversation: the wave and Stop in the left menu, and what was said written in the chat](/studio/docs/studio-voice.png)

- Press **Stop voice** to end the conversation.
- After about a minute of quiet, the voice goes to sleep and the button becomes
  **Resume voice**.
- What is said is written into the chat, so you can read it back later.
- While the voice is on, the chat does not jump to the newest message by itself.
  Scroll it yourself.
- You can still type. What you type is passed to the voice, and it answers out
  loud.
- You can change your mind while Atlas is working. Say *"stop"*, or *"do this
  instead"*, and it stops what it is doing, even while it is using your
  computer. Messages you typed to wait in the Queued list are still sent.

## Letting the voice press things

The voice can work the app for you: open a project, switch a tab, press a button.
When it wants to, it asks first, with **Decline** and **Allow**.

To change that, go to [Model settings](#studio-model-settings) and set **When the
voice needs to press something** to **Ask for permission** (the default) or
**Fully auto**.

## Choose a voice

Press the small **arrow** next to the microphone. A window opens where you pick:

![Choosing a voice: the voice model on the left, its voice actors and the language on the right](/studio/docs/studio-voice-picker.png)

- the **voice model**: **Atlas voice** is included with your account. **ChatGPT
  voice** uses your ChatGPT sign in. The others use your own OpenAI key, or a
  voice model you added yourself.
- the **voice actor**. Press one to hear a sample.
- the **language**.

Press **Use this voice**. To set the one every new conversation starts with, use
**Default voice** and **Voice actor** in [Model settings](#studio-model-settings).

## How long you can talk

| Limit | How much |
| --- | --- |
| One conversation | 1 hour of speaking |
| The Atlas voice, each day | 2 hours of speaking |

Only the time somebody is speaking counts. Quiet time does not.

:::note
The microphone only shows when you are signed in and a voice is ready to use.
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-voice

---

# Change the model

Click the **model name** in the chat box (for example **Claude Opus 5.5**). A
window opens.

![Choosing a model](/studio/docs/studio-model-picker.png)

- The ones you used last are at the top.
- **Type** to search every model you have, including your own models and model
  groups.
- Click one, or use the arrow keys and press Enter.

**Switching starts a fresh chat** on the new model, in the same project. The old
chat is kept in Recents. If it was still answering, it carries on in the background.

## Only for one message

Want a second opinion without leaving the chat? Type **@** in the chat box and pick
a model. Only that message goes to it. See [The chat box](#studio-chat-box).

## Changing the one a new chat starts with

Go to **Model settings** and choose it under **Default model**. See
[Model settings](#studio-model-settings).

## How hard it thinks

Press the **Options** button (the sliders) next to the model name and choose
**Thinking**. A small window opens, **How hard it thinks**, with a slider and one
button for each level, such as **Low**, **Medium**, **High** and **Max** (some
models have fewer, and some have none, in which case there is no Thinking line). Higher means a slower, more careful answer.
Like changing the model, changing this starts a fresh chat.

![The How hard it thinks window: a slider and one button for each level](/studio/docs/studio-effort.png)

Page: https://www.mind-vest.io/studio-setup-guide/studio-change-model

---

# Find past chats

## Recents

Your last three chats are listed under **Recents** in the left menu, newest first,
with the logo of the model you used. Click one to open it and carry on.

- The chat you are in is highlighted.
- A chat that is **still working** gently flashes, so you can see it at a glance.
- The small **microphone** on a row starts talking in that chat. See
  [Talk to Atlas](#studio-voice).
- Of the three round buttons next to **Recents**, the clock (**See more**) opens
  every chat in Chat Sessions, the pen starts a [new chat](#studio-new-chat), and
  the circle arrow refreshes the list.

**Right click** a chat in Recents for two choices:

![Right click a recent chat to open or delete it](/studio/docs/studio-recents-menu.png)

- **Open**
- **Delete**. This deletes it straight away, with no second question.

## Every chat: Chat Sessions

Recents only shows the last three. For all of them, press **See more** beside
**Recents**, or click your name at the bottom of the menu and choose the **Chat
Sessions** tab.

![Chat Sessions: every conversation, filtered by model](/studio/docs/studio-sessions.png)

- The tabs along the top (**All**, **Claude**, **ChatGPT**...) filter by model.
- The blue button on a row opens that chat. The red one deletes it.
- A chat that is still working says **Agent is working...**

## Search everything you have said

Press **Search** on Chat Sessions and type a few words. Atlas looks through **every
conversation on this computer**, including what the model did, not only what was
said.

![Searching every conversation](/studio/docs/studio-search.png)

Use **Any time / Today / This week / This month** to narrow it down. Click a result
(or press Enter) to open that chat.

:::note
A chat's name comes from what you first asked. There is no way to rename a chat.
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-past-chats

---

# Ask before acting

By default the model just gets on with the job: it looks things up, writes files
and runs your project without stopping to ask.

If you would rather approve each step, turn on **Ask before acting** in
[Model settings](#studio-model-settings).

With it on, whenever the model wants to do something, a window pops up:
**Permission requested. Allow this?** It says what the model wants to do, with
buttons such as **Allow once** or **Always allow**.

- Press one of the allow buttons to let it go ahead.
- Press **Cancel**, press Esc or click outside the window to say **no**. The model
  is told you refused and carries on without it.

:::tip
Turn it on while you are getting to know Atlas, and off once you trust how it
works. It applies to every chat.
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-ask-first

---

# Chat with a team of models

A **model group** is a team of models in one chat. One model, the **Router**, reads
your message and hands parts of the job to the others, the **members**. Each
member can have its own job, like "check every number" or "write the summary".

First make a group in Model settings. See [Make a model group](#studio-model-groups).

## Using it

1. Click the model name in the chat box and pick your group (it is listed by its
   name, with a people icon).
2. Type your message as normal. The Router decides who does what.

A row of tabs shows at the top of the chat:

- **Everyone** shows the whole conversation.
- **Router** shows only the Router.
- **One tab per member** shows only what that member did.

When the Router hands work to a member, you see a line like
**Router → Numbers**. The Router's messages have a blue frame and the members'
have a green one, each with the name on top.

## Talking to one member

Open a member's tab and type there. Your message goes to that member only. The
Router still sees it.

:::note
Group chats are listed first under Recents, as one row. The small arrow on the
row shows each member's own thread.
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-group-chat

---

<!-- ==== Atlas Studio: Models ==== -->

# Model settings

Click **Model settings** in the left menu. This is where you connect the AI models
Atlas talks to.

![Model settings: the default model, the switches and one row per model](/studio/docs/studio-model-settings.png)

## At the top

| Setting | What it does |
| --- | --- |
| **Default model** | The model every new chat starts on. **Pick one** means you choose each time. |
| **Default voice** and **Voice actor** | The voice a spoken conversation starts with. See [Talk to Atlas](#studio-voice). |
| **When the voice needs to press something** | **Ask for permission** (it asks you each time) or **Fully auto**. |
| **Ask before acting** | When on, the model asks you before each step. See [Ask before acting](#studio-ask-first). |
| **Use the model's computer use tool** | Only matters for a model you added with a key. Leave it off unless you know you need it. |

On Windows there is one more switch, **Keep the screen on after Remote Desktop**.
Turn it on if you reach this computer through Remote Desktop and want Atlas to
keep working when you disconnect.

## One row per model

Each row shows the model and a tag on the right:

| Tag | Means |
| --- | --- |
| **connected** | You signed in. Ready to use. |
| **key set** | You pasted a key. Ready to use. |
| **ready** | Installed, but no sign in or key found yet. |
| **not set up** | Not connected yet. |

Click a row to open it:

![A model row opened: sign in, paste a key, or disconnect](/studio/docs/studio-model-row.png)

- **Sign in to Anthropic / OpenAI / xAI** opens your browser so you can sign in with
  your normal account. Once connected it says **Reconnect** instead.
- **or paste a key** lets you use an API key instead. Choose **OS keychain** or
  **.env file**, then **Save key**.
- **Disconnect** (for example **Disconnect Anthropic**) removes the sign in or key
  from this computer.

**Grok** needs one extra step the first time: press **Install Grok**, wait for it
to finish, then sign in. Later the same button says **Update Grok**.

:::note
Signing in to a model does not switch your current chat to it. Pick it in the chat
box or set it as the **Default model**.
:::

## The last four rows

| Row | What it is for |
| --- | --- |
| [Models on this computer](#studio-local-models) | Download free models and run them on your own machine. |
| [Your own model](#studio-own-model) | Add any other AI service you have a key for. |
| **Voice models** | Add a voice model you have a key for, or one on this computer. Fill in its name, web address, key and model, then **Add it**. Atlas tests it first. See [Talk to Atlas](#studio-voice). |
| [Model group](#studio-model-groups) | Make a team of models that work in one chat. |

Page: https://www.mind-vest.io/studio-setup-guide/studio-model-settings

---

# Models on this computer

You can run free, open models **on your own computer**, with no account and no
internet needed once they are downloaded. Atlas uses one of two free programs to
do it: **Ollama** or **LM Studio**.

Open **Model settings** and click **Models on this computer**.

![Models on this computer: your hardware, the programs, and the models you have](/studio/docs/studio-local-models.png)

## Step 1: get Ollama or LM Studio

At the top you see what your computer has (memory, processor, graphics card). Below
that are two cards, **Ollama** and **LM Studio**:

- **Install** puts it on your computer for you.
- **Start** turns it on, if it is installed but not running.
- **server on** means it is ready.

## Step 2: get a model

Type a model name under **Get a model** and press **Fetch**, or pick one from the
**Or pick one** list. Not sure? **llama3.1:8b** is a good place to start, and
**llama3.2:3b** is small and quick.

Before you download, Atlas tells you how big it is and how well it will run on
your computer. **Fetch** then does everything for you: downloads it, sizes it for
your computer, tests it and adds it to the chat's model list.

## Will it run well?

Each model shows a coloured tag:

| Colour | Means |
| --- | --- |
| **Green** | Runs well here. |
| **Amber** | Runs, but slowly. |
| **Grey** | Too big for this computer. |

## Is it working?

Under **Here already**, each model says whether it is **in memory** (loaded and
quick to answer) or **not loaded**, and a line above the list names what is in
memory now.

- **Test** asks the model one short thing and shows its answer and how long it
  took. A model that is not loaded is loaded first, which can take a minute.
- **Stop** takes a model out of memory, to give your computer its memory back.
  Nothing is deleted.

## Other buttons

- **Use up to ...%** is a slider for how much of your computer a model may use.
  Lower it if your computer gets slow while a model is answering.
- **Instructions** gives a model standing orders it follows in every chat, for
  example *"always answer in short bullet points"*.
- **The bin** removes a model to free up space (Ollama only).
- **Look again** re-checks your computer, for example after installing Ollama.

## Using it

Your downloaded model now shows in the chat's model list by its name. Pick it like
any other. See [Change the model](#studio-change-model).

Page: https://www.mind-vest.io/studio-setup-guide/studio-local-models

---

# Add your own model

Have a key for another AI service, like OpenRouter, Groq, Azure or DeepSeek? Add it
here and use it like any other model.

Open **Model settings**, click **Your own model**, then **Add one**.

![The form for adding your own model](/studio/docs/studio-own-model.png)

## Fill it in

| Box | What to put |
| --- | --- |
| **Name** | Any name you like. This is what you see in the chat. |
| **Web address** | The service's address, from its setup page. |
| **Key** | Your key from that service. |
| **Model** | The model's name, spelled exactly how the service spells it. |
| **Thinking levels** (optional) | If the service has levels like low, medium, high. |
| **Their example request, or their setup page** (optional) | Paste the example from the service's docs. |

:::tip
The easiest way: copy the example request from the service's setup page (it
usually starts with **curl**) and paste it into the last box. Atlas reads the
address and details out of it for you. It only reads it; it never runs it.
:::

Press **Add it**. Atlas tests the model before saving it and tells you if
something is wrong. When it says the model **is ready to use**, press **Done**.

## After that

- It shows in the chat's model list under the name you gave it.
- **Edit** changes it. **Remove** deletes it straight away.
- To add a second model from the same service, add another entry.

Page: https://www.mind-vest.io/studio-setup-guide/studio-own-model

---

# Make a model group

A model group puts several models in one chat. The **Router** gets your message
and hands pieces to the **members**. See [Chat with a team of models](#studio-group-chat)
for how it looks in a chat.

Open **Model settings**, click **Model group**, then **Make a group**.

![Making a model group: a name, a Router and its members](/studio/docs/studio-model-group.png)

## Fill it in

1. **Group name**, for example "Research desk".
2. **Router**: pick the model that runs the group. Pick a strong one.
3. **Router brief**: how the Router should run things. It is filled in for you;
   change it only if you want to.
4. **Members**: for each one, give a short **name** (the Router calls them by it),
   pick a **Model**, and say what its **Job** is.
5. **+ Add a member** for more. The bin removes one.
6. Press **Make it**.

## Tips

- Give members names that say what they do, like **Numbers** or **Writer**.
- Mix models. For example one model to check facts and another to write.
- A group cannot contain another group.

Your group now shows in the chat's model list by its name. **Edit** and **Remove**
are on the group in the same row.

Page: https://www.mind-vest.io/studio-setup-guide/studio-model-groups

---

<!-- ==== Atlas Studio: Projects ==== -->

# Projects and Local Mode

Click **Projects** in the left menu. It lists every project on this computer.

![Projects: the Local Mode switch and your projects](/studio/docs/studio-this-computer.png)

## Local Mode

The switch at the top, **Run tasks on this computer from the web**, is Local Mode.

- **On:** your projects can run on this computer, and you can start and watch them
  from the [web dashboard](/atlas/dashboard) or your phone too. If something is
  wrong, a line under the switch says what.
- **Off:** nothing runs on this computer.

:::warn
If your projects are not running, check this switch first.
:::

## Your projects

Each row is one project, with how many files it has. A **Paused** tag means it is
not running on its schedule right now.

| Button on a row | What it does |
| --- | --- |
| **Share** | Share the project with someone. See [Share and import](#studio-sharing). |
| **Bin** | Delete the project and everything in it. Atlas asks first. |

At the top right:

| Button | What it does |
| --- | --- |
| **Download** | Open a project someone shared with you. |
| **Refresh** | Re-read the list, and check shared projects for updates. |

## Where do projects come from?

You make a project by starting a [new chat](#studio-new-chat) and typing a new name.
Then you describe what you want, and the model builds it in that project.

Click a project to open it. See [Inside a project](#studio-project).

:::note
Projects only run while Atlas Studio is open. See [Keep it running](#studio-background).
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-this-computer

---

# Inside a project

Click a project on **Projects** to open it. Along the top are **All projects**
(to go back), the project's name, and a **Keys** button. Under that are the tabs.
A project opens on its first tab.

| Tab | What it shows |
| --- | --- |
| **Dashboard** | The project's own live page. See [A project's dashboard](#studio-dashboard). |
| **Files** | Everything in the project. You can read and edit it. |
| **Checks** | The tests that keep the project right. See [Checks](#studio-checks). |
| **Computer Use** | When Atlas used your screen for this project. See [Let Atlas use your computer](#studio-computer-use). |
| **Notifications** | Which moments send a message to your phone. See [Notifications](#studio-notifications). |
| **Chats** | Every chat you had about this project. |

**Start from scratch** projects have no Dashboard tab. You can put the tabs in your
own order, or hide some: see [Arrange the tabs](#studio-arrange-tabs).

## Files

![The Files tab with a note open](/studio/docs/studio-project-files.png)

- Click a file to open it. Click a folder to open or close it.
- The **pencil** lets you edit the file. **Save** keeps your change, **Cancel** throws
  it away.
- The **bin** deletes the file (Atlas asks first).
- Notes (files ending in .md) open nicely formatted. Switch to **Code** to see the
  plain text.
- **New file** at the top makes a new one.
- A **.csv** or **Excel** file opens as a table, with a tab for each sheet. Up to
  1,000 rows are shown, and it says how many there are. **Text** shows the plain
  file. Drag a column's edge to widen it, and click a row to see all of it.

![A CSV file opened as a table](/studio/docs/studio-file-table.png)

A few files you will often see:

| File | What it is |
| --- | --- |
| **plan.md** | What the project does, in plain words. |
| **main.py** | The steps the project runs. |
| **atlas.json** | When it runs (its schedule). |
| **dashboard.html** | Its dashboard page. |

You do not need to edit any of these yourself. Ask in a chat instead, for example
*"make it run every 10 minutes"*.

## Chats

![The Chats tab: every conversation about this project](/studio/docs/studio-project-chats.png)

Click one to open it and carry on. The **bin** deletes it. Chats started on the
web about this project show up here too.

## Keys

Some projects need a key or password for another service, such as a Discord
webhook. Press **Keys** to add them.

![The Keys window](/studio/docs/studio-keys.png)

- Type the key's name and value at the bottom and press **Add**.
- To change one, type the new value over it and press **Save**.
- The **bin** removes one.

Keys stay on your computer. Once saved, a key is never shown again, and it is never
shared, even if you share the project.

Page: https://www.mind-vest.io/studio-setup-guide/studio-project

---

# Checks

A project is rarely right the first time. **Checks** are small tests Atlas writes for
a project and runs again and again: *do my fill prices match the broker's?*, *is
every trade in?*, *does the Sharpe ratio use the risk-free rate?* While Atlas builds
or changes a project, it runs its checks by itself and tells you. Say *"stop the
checks"* in the chat if you would rather it did not.

Open a project and click the **Checks** tab.

![The Checks tab: counts, filters, and each check with its result](/studio/docs/studio-checks.png)

- Along the top: how many **passed**, **failed**, gave a **warning** or a
  **suggestion**, when they last ran, and **Run all**.
- The filters show only one kind.
- Each check says what it found, with a tag for its result.

## The buttons on a check

| Button | What it does |
| --- | --- |
| **Resolve** | Hands the problem to Atlas in the project's chat, to fix it. |
| **Recheck** | Runs that check again exactly as it ran, with the same data. |
| **Assumptions** | The numbers the check uses. See below. |

## A check's page

Click a check to open it. The newest run is at the top and older runs are below
it, each with when it ran and what started it (its schedule, a change to the
project's files, new data, or you). Click a run to read its full report.

![A check's page: its runs, newest first, each with what started it](/studio/docs/studio-check-page.png)

**Auto-fix** lets Atlas fix a failing check by itself. It stops after three tries
and tells you.

## Assumptions

Some checks depend on numbers you might want to change, such as the risk-free rate,
fees per trade or a start date. Press **Assumptions** on the check.

![The Assumptions window: each number with where it comes from](/studio/docs/studio-assumptions.png)

- Type a new number, or pick from the list. A changed number shows **↺ Reset**,
  which puts it back.
- **Run** runs the check with your numbers. They are kept for later runs.
- **Back to defaults** puts every number back.

## When checks run

When you press **Run all** or **Recheck**, on the project's schedule, and when the
project's files or data change. To change when, ask in the chat, for example
*"run the checks every morning at 8:30"*.

The side panel shows a line for a project whose checks need you, with **Resolve
issue**. Without a plan, checks do not run (see
[Your plan and the two free weeks](#studio-plan)).

Page: https://www.mind-vest.io/studio-setup-guide/studio-checks

---

# Notifications

Each project chooses which moments send a message to your phone (the Atlas phone
app). Open the project and click the **Notifications** tab.

![A project's Notifications tab](/studio/docs/studio-notifications.png)

| Part | What you choose |
| --- | --- |
| **Checks** | Which check results send one: Failed, Warnings, Didn't finish, Auto-fix stopped, Suggestions, Passed. Under **One check its own way**, any check can follow its own choice instead. |
| **Computer use** | When this project's agent starts using your computer, is waiting for you, or has finished. |
| **The agent needs you** | A question or an approval waiting in this project's chat. |
| **How they read** | What each message looks like on your phone. Ask in the chat to word them differently. |

The settings stay on this computer, with the project. What a project's own runs
send (for example *"SPY is near the call wall"*) is part of the project: ask in a
chat to change it.

Page: https://www.mind-vest.io/studio-setup-guide/studio-notifications

---

# A project's dashboard

Most Finance and trading projects have a **Dashboard** tab: a live page showing
what the project is doing. The model builds it when it builds the project. Ask for
changes in a chat, for example *"put the call and put walls at the top"*.

![A project dashboard with the Run control at the top right](/studio/docs/studio-project-dashboard.png)

## Run now and Stop

The control at the top of the dashboard says whether the project is **Idle** or
**Running**.

- **Run now** runs it straight away, whatever its schedule.
- **Stop** stops a run that is going.

## In its own window

Press **Open in a new window** to put the dashboard in a window of its own. Handy
on a second screen.

## On your phone

With [Local Mode](#studio-this-computer) on, the same dashboard shows on the
[web dashboard](/atlas/dashboard) under Local Mode, so you can check it from your
phone.

:::note
No dashboard yet? The tab says so. Ask the model in a chat to build one.
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-dashboard

---

# Share and import projects

## Share one of yours

1. On **Projects**, press the **share** button on the project's row.
2. Write one line under **What is this project?** so people know what it does.
3. Press **Choose** if you want to leave some files out.
4. Press **Yes, share it**.

![Sharing a project](/studio/docs/studio-share.png)

You get a **link**. Press **Copy** and send it to whoever you like.

**Your keys are never shared.** The person who imports it adds their own.

Later on:

- **Publish changes** sends your latest version to everyone who has a copy. You can
  write a note saying what changed.
- The **Shared** switch turns sharing off.

## Open one someone sent you

1. On **Projects**, press the **download** button at the top right.
2. Paste the link and press **Open**.
3. Look through what is in it: the files, the version and who made it.
4. Press **Import**, then confirm. Only import projects from people you trust,
   because the project runs on your computer.

If the project needs keys, Atlas tells you which and gives you an **Open Keys**
button to add them.

## Updates

When the person who shared it publishes a new version, your copy shows
**New changes from author**. Press **Review changes**, then **Update this project**.
Anything you changed yourself is backed up first.

Page: https://www.mind-vest.io/studio-setup-guide/studio-sharing

---

# Let Atlas use your computer

Atlas can use your screen, mouse and keyboard to do things for you, like filling
in a form or clicking through an app. It is **off** until you turn it on.

## Turning it on

1. Open a project on **Projects** and click the **Computer Use** tab.
2. Turn on **Let an agent use this computer**.

![The Computer Use tab](/studio/docs/studio-computer-use.png)

The first time, Atlas gets your computer ready. This can take **30 minutes to an
hour**, and you can leave it running. If it says your computer needs **Python**,
install Python 3 from python.org and turn the switch on again.

On a Mac, the Mac asks you to allow **Screen Recording** for Atlas Studio. Allow it
so Atlas can see and record the screen.

The switch is for the whole computer, not just this project.

## Watching it work

- **Watch it work** opens a big window showing the screen, with a list of each
  thing Atlas did beside it ("Clicked Submit", "Typed 12 characters", "Filled 3
  fields of a form"). What it types is never shown.
- While a chat is using the computer, that window has a small chat box of its
  own, so you can tell it something or stop it without going back. What you type
  there changes what it is doing straight away, like *"not that one, the one
  below"*. It does not wait for the job to finish.
- To look closer, hold **Ctrl** (or **Cmd** on a Mac) and turn the mouse wheel,
  pinch on a trackpad, or double click. This works on recordings too.
- If you have **two screens**, a small bar floats on the other screen while Atlas
  is working. It has a **Stop** button and **Watch from your phone**. With one
  screen there is no bar, so it never gets in the way of what Atlas is doing.
- With more than one screen, **Work on** lets you choose which one Atlas uses.

## Stopping it

Press **Stop** on the floating bar, or stop the chat that asked for it. If you
cannot reach either, push the mouse pointer hard into a corner of the screen and
Atlas stops.

## Recordings

Every time Atlas uses your computer, it keeps a recording and a list of what it did.
Find them under **Computer Use → Recordings**.

![Recordings of past runs](/studio/docs/studio-recordings.png)

- Click one to play it back. The list beside the video follows along, showing
  what had happened by that moment. **Show all** shows the whole list.
- A long recording is split into parts. Pick a part to jump to it.
- The **pencil** gives it a name. The **bin** deletes it (straight away).

Page: https://www.mind-vest.io/studio-setup-guide/studio-computer-use

---

<!-- ==== Atlas Studio: Memory ==== -->

# What Atlas remembers

Atlas keeps short notes about you, like *"wants answers short, with the number
first"* or *"uses Robinhood"*. Every chat, whichever model you use, gets the ones
that matter, so you do not have to repeat yourself.

Click **More** in the left menu, then **Memory**, to see them.

![The Memory screen](/studio/docs/studio-memory.png)

## How long it keeps things

The tabs along the top:

| Tab | What is in it |
| --- | --- |
| **Short term** | Things that matter right now. They fade after a while if they are not used. |
| **Long term** | Things that stay useful for a long time. |
| **Permanent** | Things that never fade. |
| **Forgotten** | What was removed. You can bring any of it back. |

Each memory shows what **kind** it is (like **Preference** or **Fact**), which
**project** it belongs to (if any), and **how long it has left** before it fades.
Memories you use often stay; ones you never use fade away on their own.

## Where memories come from

1. **From your chats.** Atlas reads your recent conversations and picks out what is
   worth keeping. Choose how often with the **Learn daily / weekly / monthly**
   menu, or press **Learn now**. **Never learn** turns this off.
2. **From you.** Press **New memory** and type it. See
   [Add, change and forget](#studio-memory-manage).

**Model: ...** says which model does the reading. Click it to choose another.

## The map

Press **Map** to see your memories as dots, grouped by kind. Bigger dots are more
important. Hover a dot to read it, click it to open it. Press **List** to go back.

![The memory map](/studio/docs/studio-memory-map.png)

## Finding one

- **Search** looks through everything Atlas remembers.
- **Filter** narrows the list by kind, project, how long it is kept, and when it
  was saved. **Clear** resets it.

:::note
Memories are kept on this computer. A memory tagged with a project is used in chats
about that project; one with no project is used everywhere.
:::

## Sharing with the website

What Atlas Studio remembers stays on this computer unless you switch sharing on.
The switch is on the website: **Profile → Memory → Share with my computers**
(use the **Cloud** switch to open it without leaving the app). While it is on,
Atlas in the web chat and the assistants you connected can read the memory on
this computer, add to it or change it, and read your past chats here (only your
words and the AI's, never what a tool read or your files), as long as the app is
open here and Local Mode is on. Switch it off there and they cannot.

Page: https://www.mind-vest.io/studio-setup-guide/studio-memory

---

# Add, change and forget

## Add one yourself

Press **New memory** on the Memory screen.

![Adding a memory](/studio/docs/studio-memory-new.png)

1. Type what Atlas should remember, in plain words.
2. **Kind**: what sort of thing it is (a fact, a preference, something about you...).
3. **Kept for**: Short term, Long term or Permanent.
4. **Project**: leave as **No project** to use it everywhere, or pick one project.
5. **Importance**: slide it up for things that really matter.
6. Press **Add**.

If your new memory replaces an older one that says something different, Atlas
tidies the old one away for you.

## Change one

Click a memory to open it. Change the words, the kind, how long it is kept, the
project or the importance, then press **Save**. If it came from a chat, **Open the
chat it came from** takes you there.

You can also move the **Importance** slider right in the list: Minor, Important or
Essential.

## Forget one

Press **Forget** on the memory.

## Forget several at once

1. Press **Select**.
2. Tick the ones you want, or **Select all shown**.
3. Press **Forget** and confirm.

## Bring one back

Open the **Forgotten** tab and press **Restore** on it.

## When Atlas asks you

Sometimes Atlas is not sure whether to change a memory. It then shows a
**Your call** box above the list with what it wants to do and why. Press **Do it**
or **Leave it**.

Page: https://www.mind-vest.io/studio-setup-guide/studio-memory-manage

---

<!-- ==== Atlas Studio: Make it yours ==== -->

# Arrange the sidebar

The left menu is yours to arrange. You can rename things, change the order, pin
your favourite places and choose which screen Atlas opens on.

## More

The menu shows **four** buttons. Anything after the fourth goes under **More**,
and so does **Memory** to begin with. Click **More** to see them.

![The More menu](/studio/docs/studio-more-menu.png)

## Press and hold

**Press and hold** any button in the menu for half a second, or **right click** it.
A small menu opens:

![Holding a menu button shows what you can do with it](/studio/docs/studio-hold-menu.png)

| Choice | What it does |
| --- | --- |
| **Rename** | Give it your own name (up to 30 letters). |
| **Arrange** | Change the order of everything. See below. |
| **Open this first** | Atlas opens on this screen when it starts. **Stop opening first** undoes it. |
| **Move to More** | Take it off the menu and put it under More. |
| **Move to the rail** | Bring it back from More. |
| **Remove from panel** | Remove one of your own pins. |

**Model settings**, **Projects** and **Memory** can be renamed or moved to
More, but never removed.

## Pin a place you use a lot

You can pin a **project**, one of its **tabs** (like its Dashboard), or a
**Profile** tab (like Chat Sessions) to the menu:

1. Press and hold it (or right click it).
2. Choose **Add to panel**.
3. Give it a name and press **Save**.

![Pinning a project to the menu](/studio/docs/studio-add-to-panel.png)

For example, pin your project's dashboard as "SPY dashboard" and it is one click
away.

## Arrange

Choose **Arrange** from the More menu or the hold menu.

![Changing the order](/studio/docs/studio-arrange.png)

- The **up** and **down** arrows move a button.
- Everything below the **Also in More** line lives under More.
- **To More** / **To the rail** move a button between the two.
- The **bin** removes one of your own pins.
- Press **Done** when you are finished.

## Make the menu smaller

The round button next to "Atlas Studio" at the top folds the menu down to icons.
Press it again to open it. On a small window it folds by itself.

![The menu folded down to icons](/studio/docs/studio-collapsed.png)

:::tip
Your menu is saved to your Atlas account, so it looks the same on every computer
where you use Atlas Studio.
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-arrange

---

# Arrange the tabs

Every row of tabs can be put in your own order: a project's tabs, the projects list,
Profile, Memory, Chat Sessions and Computer Use.

- **Drag** a tab straight to its new place. The others slide aside.
- **Right click** a tab (or press and hold it) and choose **Arrange** for the whole
  row at once.

![Right click a tab: Add to panel, or Arrange](/studio/docs/studio-tab-menu.png)

In **Arrange**, drag a tab by its handle, and use its switch to hide it. Hidden
tabs go under **More** at the end of the row, which only shows when something is
hidden. **Back to how it came** puts the row back, and **Done** closes it.

![Arranging a project's tabs](/studio/docs/studio-arrange-tabs.png)

For a project, the first tab is the one it opens on. Your order is kept on this
computer.

Page: https://www.mind-vest.io/studio-setup-guide/studio-arrange-tabs

---

# Widgets in the side panel

Under **Recents** there is room for small live views: a price you watch, your open
trades, a news briefing, a count. Each one is a **widget**, and you make one by
asking for it in a chat. For example: *"put SPY's price and the call wall in a
widget in my side panel"*.

Atlas builds it inside the chat's project, and it shows under Recents a moment
later. It keeps itself up to date while the project runs.

![Two widgets under Recents: a morning brief and SPY's gamma walls](/studio/docs/studio-widgets.png)

- **Change one** by asking in a chat, like *"show QQQ too"*.
- **Move one** by holding its **...** and dragging it up or down.
- **Remove one** with its **...** → **Remove**.
- When projects are not running on this computer (see
  [Local Mode](#studio-this-computer)), the widget fades and says **As of** the
  last time it was updated.
- With the menu folded, or without a plan, widgets are not shown.

:::tip
Widgets are made in Atlas Studio and stay in Atlas Studio. The website and the
phone apps have their own side panel widgets.
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-widgets

---

# Profile, dark mode and updates

Click **your name** at the bottom of the left menu. Profile has four tabs along
the top: **Profile**, **Chat Sessions** (see [Find past chats](#studio-past-chats)),
**Connectors** (see [Connectors](#studio-connectors)) and **Libraries** (see
[Libraries](#studio-libraries)).

![Your Profile](/studio/docs/studio-profile.png)

## What is on Profile

| Section | What it does |
| --- | --- |
| **Appearance** | The **Dark mode** switch. Turn it on for a dark screen. It is also in the **...** menu next to your name. |
| **Software** | Which version you have. **Check for updates** looks for a newer one now. |
| **Usage** | Your plan and how many requests you have used this month. |
| **Your Atlas key** | A key for connecting other tools to your Atlas account. Treat it like a password. The eye shows it, the copy button copies it, **New key** makes a new one (the old one stops working). |
| **Danger Zone** | **Sign Out** and **Delete Account**. See [Sign in and sign out](#studio-sign-in). |

**↻ Refresh** at the top right reloads your details.

## Dark mode

Profile → **Appearance** → turn on **Dark mode**. It changes the whole app, and
dashboards follow it too.

![Atlas Studio in dark mode](/studio/docs/studio-chat-dark.png)

:::note
Discord is managed on the website, under Profile in the
[web dashboard](/atlas/dashboard). You can open it without leaving the app with
the **Cloud** switch. See [Local and Cloud](#studio-local-cloud). A broker can be
connected here, under [Connectors](#studio-connectors).
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-profile

---

# Connectors

Connectors link Atlas to the other apps you use, like **Notion**, **Stripe**,
**Dropbox** or **PayPal**, and to your **broker**. Once one is connected, you can
ask for things like *"what did Stripe pay out this week?"* in any chat, and your
projects can use it too.

Click your name at the bottom of the menu, then the **Connectors** tab.

![Your connectors](/studio/docs/studio-connectors.png)

## Add one

![Add a connector: app tiles and broker tiles, each broker marked Trading enabled or Read-only](/studio/docs/studio-add-connector.png)

1. Press **+ Add a connector**.
2. Search for the app, for example "notion", and click its tile.
3. Press **Sign in and connect**.
4. Your browser opens. Sign in there and allow access.
5. Come back to Atlas. The connector shows **Connected**.

Nothing needs copying: the sign in comes back to the app on its own.

**Not in the list?** If the app gives you a connector address, press
**Add by address**. Fill in the name and the address, choose how it signs in
(**API key**, **Sign in (OAuth)** or **No sign-in needed**), and press **Connect**.

## Connect a broker

Brokers are in the same list as the apps. Each broker tile is marked **Trading
enabled** or **Read-only**, so you know before you connect whether Atlas can
place orders with it or only look.

There are two kinds:

| Kind | How you connect | Where it lives |
| --- | --- | --- |
| **Topstep** and **OANDA** | Pick **Demo** or **Live**, paste your key, press **Connect**. **Where do I find this?** shows the steps. | On this computer. The key stays in your computer's locked storage, and orders go from this computer. |
| **Every other broker** | Press **Sign in and connect**. Your browser opens, you sign in to your broker there, and it finishes on its own. | On your Atlas account. It is the same broker list you see on the website. |

![Connecting a broker with a key: Demo or Live, your username and API key, and where to find the key](/studio/docs/studio-broker-connect.png)

A connected broker is a row like any other connector, with the same buttons.
Signing out of, or deleting, a broker on your Atlas account removes every account
in that group.

:::warning
A broker marked **Trading enabled** can place **real orders**. With a broker on
this computer, opening a new trade needs a paid plan. Closing a trade and
cancelling an order always work.
:::

## On each connector

Click a connector's row to see everything Atlas can do with it. The round
buttons on the row say what they do when you hold the pointer over them:

| Button | What it does |
| --- | --- |
| **Refresh tools** | Check again for what it can do. |
| **Sign out** | Disconnect it for now. You can **Connect again** later. |
| **Delete** | Remove it completely. |

:::tip
App connectors, and the brokers you connect with a key, live on your computer.
Your sign ins are kept in your computer's locked storage, and Atlas talks to the
app directly, not through our servers. A broker you sign in to through the
browser is connected to your Atlas account instead.
:::

Page: https://www.mind-vest.io/studio-setup-guide/studio-connectors

---

# Libraries

Your projects are written in Python, and Python has free **libraries** for tables,
charts, prices and finance maths. Atlas installs the ones a project needs by itself.
**Libraries** lets you see them and manage them yourself.

Click your name at the bottom of the menu, then the **Libraries** tab.

![The Libraries tab: each library with what it is for, and its tags](/studio/docs/studio-libraries.png)

- Each one says what it is for, and is tagged **Installed**, **Not installed** or
  **Update available**.
- Click one to read more, see its version, and **Install**, **Update** or
  **Remove** it.
- **Auto update** keeps it up to date by itself, checked once a day.
- **Search** finds one by name.

Libraries are installed once, in the Atlas folder, and every project uses them.

Page: https://www.mind-vest.io/studio-setup-guide/studio-libraries

---

# Keep it running

Your projects only run **while Atlas Studio is open**. So what happens when you
close the window matters.

## Closing the window

When you close Atlas Studio, it asks: **Keep Atlas running in the background?**

| Button | What happens |
| --- | --- |
| **Keep running** | The window closes but Atlas keeps going. Your schedules and projects carry on. |
| **Stop and quit** | Everything on this computer stops. |
| **Cancel** | Nothing. The window stays open. |

Either way you stay signed in.

## Finding it again

When Atlas is running in the background, its icon sits in the **system tray** on
Windows (bottom right, near the clock) or the **menu bar** on Mac (top right).
Click or right click it for:

- **Open Atlas Studio**
- **Start at login (run in background)**: Atlas starts on its own, quietly, when
  you turn on your computer. Tick this if your projects should always be running.
- **Quit Atlas Studio**

## If the computer sleeps

A sleeping computer does not run anything. If a project must run at a set time,
keep the computer awake then.

Page: https://www.mind-vest.io/studio-setup-guide/studio-background

---

# Help: something is not working

## The chat says a model "needs credentials"

The model is not connected. Go to **Model settings**, open that model and sign in
or paste a key. See [Connect your first model](#studio-first-model).

## My project is not running

Check these, in order:

1. You have a **plan**, or are in your two free weeks. See [Your plan and the two free weeks](#studio-plan).
2. **Local Mode** is on (Projects, top of the screen).
3. **Atlas Studio is open**, or running in the background. See [Keep it running](#studio-background).
4. You are **signed in** (your name shows at the bottom of the menu).
5. The project is not **Paused**.
6. The project has all its **Keys** filled in.

To test it, open its **Dashboard** and press **Run now**.

## It says "Hello there" instead of my name

Atlas could not load your details, usually because the computer is offline. Check
your internet. If the app shows the **Sign in to Atlas** screen instead, press
**Sign in or sign up**. See [Sign in and sign out](#studio-sign-in).

## Where are my files?

**Projects** → click the project → **Files**. On your disk they are in the
**AtlasStudio** folder in your home folder.

## Where do I put a password or API key for a project?

**Projects** → the project → **Keys**. Never paste keys into a chat.

## Can it use my screen?

Only if you turn it on. See [Let Atlas use your computer](#studio-computer-use).

## Does it work when the app is closed?

Only if you chose **Keep running** when you closed it. If you chose **Stop and
quit**, nothing runs until you open it again.

## I want the newest version

Profile → **Check for updates**. See [Install and update](#studio-install).

## I deleted a chat by mistake

Deleting a chat cannot be undone. Deleted memories, though, can be brought back
from **Memory → Forgotten**.

Page: https://www.mind-vest.io/studio-setup-guide/studio-help

---
