frontrun-cli needs your FrontRun Pro session token to make API calls. The token must be obtained from the FrontRun browser extension, not the web app.
The session token is an HttpOnly cookie, so it can't be accessed via document.cookie or the Application tab. Use the Network tab instead.
Click the FrontRun Pro extension icon in your browser toolbar to open the popup. Make sure you're logged in.
Right-click anywhere on the extension popup → Inspect (or press F12 while the popup is open).
⚠️ This opens DevTools specifically for the extension popup. Regular DevTools on frontrun.pro website won't work — the token is scoped to the extension.
- In the extension DevTools, go to the Network tab
- Trigger any action in the extension (e.g., click "Smart Followers" or refresh the page)
- Click any request to
loadbalance.frontrun.pro - In the request details, go to Headers tab
- Find the Cookie header section
- Look for
__Secure-frontrun.session_token=... - Copy the value after the
=sign
It looks like:
YOUR_SESSION_TOKEN_HERE
cp .env.example .envEdit .env:
FRONTRUN_SESSION_TOKEN=YOUR_SESSION_TOKEN_HERE
node src/cli.js info✅ See account data → done.
❌ See Session token expired → token invalid, repeat steps 1-3.
| Method | Works? | Reason |
|---|---|---|
| Application → Cookies | ❌ | Extension cookies not exposed to page context |
Console → document.cookie |
❌ | HttpOnly flag blocks JS access |
| Network → Headers → Cookie | ✅ | Shows raw request headers |
Session tokens expire after some time. When you see:
✗ Session token expired or invalid.
Update FRONTRUN_SESSION_TOKEN in .env
Just repeat the steps above to grab a fresh token.
| Variable | Required | Default | Description |
|---|---|---|---|
FRONTRUN_SESSION_TOKEN |
✅ | — | Session cookie from extension |
FRONTRUN_BASE_URL |
❌ | https://loadbalance.frontrun.pro |
API base URL |
FRONTRUN_EXTENSION_ORIGIN |
❌ | chrome-extension://kifcal... |
Extension origin header |