Client guide

Docs

Everything a client needs: the install, the first run, your limits, your alerts, where your data lives, and what to do when something looks wrong.

/

Requirements

A Mac on macOS 14 or later, the client code from your welcome note, and about ten minutes. For live prices and, later, real money you need a brokerage account in your own name. Alpaca works from most countries, and a free Alpaca paper account covers the practice period.

You do not need an admin password, a terminal habit, or Node installed. The installer brings what it needs and keeps it in its own folder.

The one-line install

Sign in on the client page with your code and email. It shows your personal install line with both filled in. Paste it into Terminal and press return.

$curl -fsSL https://teloson.com/install.sh | bash -s -- TL-XXXX-XXXX-XXXX you@example.com

What it does, in order:

  1. Checks that your account exists and is active. It refuses anyone without one.
  2. Downloads the desk.
  3. Installs Node into ~/Teloson/node if your Mac has none.
  4. Sets the desk up under the mandate you signed.
  5. Starts it on practice money and opens the dashboard in your browser.
Running the same line again later updates the desk and keeps your settings, your keys and your data.

First run

The installer asks for your own keys as it goes: your broker, the reasoning model, and any data services you use. Blank is allowed, and you can add them later. Keys are written to your home folder and never sent to us.

When it finishes, the dashboard opens on the Floor. Press Send test alert once to check every channel you chose.

Practice

The desk starts on practice: real prices, real news, fake money, for a couple of weeks. Practice is the one place the floor trades on its own, so you can watch its judgement. Nothing touches your real account. At the end you get a summary, and real money only switches on if you say so.

The floor

Seventy-four seats in seven departments: Research & Validation (10), Risk & Compliance (10), Trading & Execution (6), Portfolio Management (18), Data & Intelligence (16), Digital Assets (8) and Cross-Asset & Macro (6). Fourteen of them can veto a plan on their own. Click any seat to see what it watches for and what it is reading.

Plans and approvals

A plan arrives with the size against your cap, the limit price, the reasoning, the dissent and forty-five minutes on the clock. Approve it and the order goes to your broker at your limit. Do nothing and it expires; nothing is sent. Revive an expired plan and it is re-priced and re-checked before it comes back.

ActionWhat happens
ApproveOrder sent at your limit price. The fill is reported on every channel.
Let it expireNothing is sent. The plan stays in your history.
Ask a questionThe seat that objected answers under the plan.
ReviveRe-priced, limits and vetoes re-checked, then back to you.

The research chat

Ask the whole floor, or type @ and a name to ask one seat. Answers cite their sources and how fresh they are. On a client desk the chat cannot place an order; typing "buy" does nothing.

Limits

Every limit comes from the questionnaire you signed and is checked before any order reaches your broker.

LimitChoicesWhat it does
Emergency brake5 · 10 · 15 · 20%Fall from the high-water mark at which all trading halts. You hear at the halfway point too.
Position cap3 · 5 · 10%The most of your account any one name can be, counting orders in flight.
Bad-day halt2 · 3 · 5%The loss in one day that stops trading until the next New York session.
Exit flag5 · 8 · 12%The drop in one position that flags it for exit. On a real account it is a flag, not a sale.
Losing streak3 then 5 · 5 then 8Brakes that slow the floor down after a run of losing trades.
Daily capsOrders and dollarsThe most it may place in a day.
Appetite0 to 100How readily the floor tables plans at all.

Halts

The bad-day halt stops trading for the rest of the session and cannot be released early. The emergency brake stops everything until you release it yourself, from the dashboard. Neither sells anything on your behalf. Halt messages repeat every two hours until you acknowledge them.

Changing a limit

Ask for the change and it is applied to your desk. The dashboard shows the new value next to the one you signed, and the audit trail keeps both.

Channels

Email, WhatsApp, Telegram, iMessage and plain text, any mix at once. The floor sends five kinds of message: a plan waiting on you, a fill, a halt, a stop-loss flag, and the daily summary at 17:05 New York time.

Test alerts

Press Send test alert on the dashboard. It sends one test down every channel and shows which arrived.

Where it lives

Everything runs on your Mac, under your user, in the ~/Teloson folder. The record, your settings and your keys stay there. We cannot see your desk.

Your keys

Your broker and data keys are stored in your home folder. They are used from your Mac to talk to those services directly. They are never sent to Teloson.

Exporting the record

The audit trail exports to CSV from the dashboard. It includes every plan, approval, fill, veto, halt, limit change and message, with times.

Updating

Run your install line again. It updates the desk and keeps your settings, keys and data.

If it crashes

It comes back on its own, halted, and messages you to say so. The brakes, the high-water mark and the daily counts survive a restart. Release the halt yourself once you have looked.

Asking us

Reply to any message from the desk, or write to us here. A person reads every note.

A small number of clients at a time.

Tell us a little about you. We reply personally, usually within a few days. If it is a fit, the questionnaire comes next, and your account after that.

Already a client? Sign in to get your install line