Vespryx HELP Account Checking your session… Settings →

Setting up the desktop token, one step at a time.

Five steps, and the first one is checking whether you need any of them. Most people do not: this exists only for the tools/ scripts, which run outside Chrome and so cannot see the session the extension already uses.

00 · DO YOU NEED THIS

Start here: you probably do not need this

Two different things use your Vespryx login, and only one of them needs a token file. Answer one question and you will know which you are.

I use TradingView in Chrome You need nothing. Stop here. The extension already has your login. It reads it straight from the vespryx.com tab you signed in on. If your walls show open interest, it is working, and a token file would change nothing.
I use the TradingView desktop app Probably still nothing. Turn on Keep tickers dressed in settings instead. TradingView syncs drawings through your account, so Chrome paints and the desktop app just opens charts that are already painted.
I run the tools/ scripts myself Yes. Carry on below. watch.mjs, preload.mjs and td-mcp.mjs run in Node, outside Chrome. Nothing outside Chrome can read Chrome's storage, so they need their own copy.

Without a token the tools still work, and still paint walls. What you lose is open interest, the apex scores and the gamma flip, because /apex is the one endpoint that needs a paid session. Walls drawn without it read 0 OI, which looks like real data unless you know to check.

00 · WHAT IT IS FOR

What a token actually gets you

The token is a copy of your website login, saved to a file so that programs running outside your browser can use it. That is the whole of it. It is not a separate account, an API key, or an upgrade, and it unlocks nothing the extension cannot already do inside Chrome.

What it buys is automation. The extension paints the chart you are looking at, when you are looking at it. The tools/ scripts do it without you there.

watch.mjs keeps the desktop app painted. It watches TradingView Desktop for a symbol change and repaints the walls within a second or two, so the levels are correct on every chart you flick through instead of the one you last painted by hand.

preload.mjs paints ahead for your phone. The TradingView mobile app can only show drawings your account already has, so it can view walls but never create them. Run this before you leave your desk and a whole watchlist is dressed when you open it on the train.

td-mcp.mjs lets an AI agent read the numbers. It serves your dealer data as MCP tools, so an assistant can answer questions about strikes and open interest rather than just draw them.

All four run on your own machine and talk to nothing but Vespryx. The token file is written with owner-only permissions, outside the repository, so it is never committed. Delete the file and everything above simply stops; nothing else changes.

01 · SIGN IN

Step 1: be signed in

1

The token is your website login. There is nothing separate to create.

If the badge at the top of this page is green you have already done this step. If it is not, open Vespryx, log in, and come back.

02 · HAND IT OVER

Step 2: pick one of these two

Both end with the same file on disk. The first needs no copying and no pasting, so try it first.

Easiest

A. Let the extension hand it over

2

Start the local helper. In a terminal, in the repo folder:

node tools/gui.mjs

Leave it running. It listens on 127.0.0.1:7777 and nowhere else, so nothing outside this machine can reach it.

3

Click the Vespryx icon in your Chrome toolbar.

That is the whole step. Opening the popup makes the extension push your token to the helper. It also does this by itself every five minutes, so if you would rather wait, you can.

4

Check it landed.

If you would rather not run the helper

B. Copy it across by hand

2

Put the token on your clipboard.

This is your live session, in plain text, on your clipboard. Paste it in the next step and do not paste it anywhere else. Anything that can read your clipboard can read your account until you log out.

3

Run this, paste, then press Ctrl-D:

node tools/td-token.mjs

Ctrl-D is what ends the paste. Enter alone will not do it, and the command will sit there looking frozen, which is the single most common way this step goes wrong.

03 · CONFIRM

Step 3: confirm it worked

5

Ask the tools what they can see:

node tools/td-token.mjs --check

It makes no network call, so it is safe to run any time. ABSENT means nothing was installed. Anything else prints the expiry.

The real proof is on a chart: paint a symbol and look for OI on the labels. Levels reading 0 OI mean the tools are running without a session, which is exactly what this page exists to fix.

04 · WHEN IT FAILS

If it did not work

The four failures that actually happen, and what each one looks like.

It says ABSENT even though I pasted it

Almost always Ctrl-D. Pressing Enter does not end the paste, so the command waits forever and writes nothing. Run it again and finish with Ctrl-D.

"Check the handover" says the helper is not running

node tools/gui.mjs is not running, or it stopped. It must stay open in its terminal. Closing the window closes the helper.

Copy says there is no refresh token

The copy still worked, but that token cannot renew itself and will stop working within the hour. Log out of Vespryx, log back in, and copy again.

The token was fine yesterday and the walls now read 0 OI

The refresh token expired or was revoked. Nothing is broken; repeat Step 2. This is the ordinary reason a chart that used to show open interest stops.

The file lives at ~/.cache/vespryx/td-token.json, outside this repo so it can never be committed, and is written readable only by you. Deleting it logs the tools out and affects nothing else.