1. Access & First Run
Open http://localhost:8080 in any browser on the machine where WEN is running. There is no login screen — the app loads immediately.
The first thing to check is the connection status dot in the top-right corner of the app. This shows whether WEN Terminal can reach Gunbot:
| Dot colour | Meaning | What to do |
|---|---|---|
| ● Green | Gunbot is reachable and responding | Nothing — you're connected |
| ● Amber | Attempting to connect | Wait 10–15 seconds |
| ● Red | Cannot reach Gunbot | Check Gunbot is running; verify the Host URL in Settings |
2. Dashboard Tab
The Dashboard is the first screen you see. It shows a live snapshot of everything Gunbot is currently managing.
Balance Display
Your account balance is shown per currency. The display updates approximately every 10 seconds. If a balance looks wrong, compare it directly against your exchange account — this is a key thing to test and report.
Open Positions
A table of every position Gunbot currently has open, with these columns:
| Column | What it shows |
|---|---|
| Pair | The trading pair, e.g. USDT-BTC |
| Side | LONG (bought, expecting price to rise) or SHORT (sold, expecting price to fall) |
| Size | How much of the base currency is held |
| Entry Price | The average price at which the position was opened |
| Current Price | Live mark price |
| Unrealised P&L | Profit or loss if the position were closed right now (mark price − entry price size) |
Refresh Behaviour
The dashboard polls Gunbot for fresh data approximately every 10 seconds. You do not need to reload the page. If data stops updating, check the connection status dot — if it's gone red, Gunbot may have restarted.
3. Trades Tab
Shows the history of recently closed trades (fills) from Gunbot. Each row represents one executed order.
| Column | What it shows |
|---|---|
| Time | When the order was filled |
| Pair | Trading pair (e.g. USDT-ETH) |
| Side | BUY or SELL |
| Qty | Amount of base currency traded |
| Price | Fill price |
| Fee | Exchange fee charged for this trade |
What to check: Cross-reference a recent trade from Gunbot's own interface against what appears here. Price, qty, and timestamp should match. Report any discrepancies.
4. Analytics Tab
Aggregated performance metrics calculated from your trade history. These help you understand how your Gunbot strategies are performing overall — win rate, P&L trend, fee impact, and similar.
What to test: After at least a few trades are visible in the Trades tab, switch to Analytics and verify the metrics look plausible. If win rate shows 0% but the trades tab shows profitable trades, that's a bug to report.
5. Config / Settings Tab
This is where you connect WEN Terminal to your Gunbot instance. Two fields matter:
| Field | What to enter | Default |
|---|---|---|
| Host URL | http://localhost:8080 — the WEN proxy address, NOT Gunbot's port directly | http://localhost:8080 |
| Token | Your Gunbot API token, found in Gunbot Settings API | (empty) |
http://localhost:3001 directly bypasses the proxy and will cause CORS errors in the browser. Always use http://localhost:8080.After entering your token, click Save. The connection dot should turn green within a few seconds. If it stays red, double-check the token — copy it fresh from Gunbot settings.
6. Manual Orders
You can place a trade directly from WEN Terminal without going through Gunbot's own interface. Find the order form — usually accessible from the Dashboard or a dedicated Orders panel.
| Field | Required | What to enter |
|---|---|---|
| Exchange | Yes | Gunbot exchange name — e.g. binance, bybit |
| Pair | Yes | Gunbot format: USDT-BTC, USDT-ETH |
| Amount | Yes | Trade size in base currency |
| Side | Yes | BUY or SELL |
Order type is always MARKET — limit orders are not supported in this version. After submitting, the response from Gunbot appears immediately. A successful order will show a confirmation message; a failure will show the error Gunbot returned.
7. Testing Checklist
Work through each item below. Tick it if the behaviour is correct; report it if something is wrong or missing.
- Page loads at http://localhost:8080 without errors in the browser console
- Connection status dot turns green after entering the Gunbot token
- Dashboard balance matches what you see in Gunbot or on your exchange
- Open positions count matches Gunbot's actual open trades
- P&L for an open position roughly matches what your exchange shows
- Dashboard data refreshes automatically (numbers change) without page reload
- Trades tab shows recent fills from Gunbot
- A trade in the Trades tab matches Gunbot's own trade log (price, qty, timestamp)
- Manual order submits successfully with a small test amount
- Submitting an order with a missing field (e.g. no pair) shows a clear error, not a crash
- Stop Gunbot — connection dot turns red within ~15 seconds
- Restart Gunbot — connection dot recovers to green automatically
- Health check returns valid JSON: http://localhost:8080/health
- Analytics tab shows plausible values (not all zeros) after trades are present
- Config settings persist after closing and reopening the browser tab
8. Known Limitations
| Limitation | Detail |
|---|---|
| Market orders only | Limit, stop-limit, and other order types are not supported in this version |
| Local access only | The proxy binds to 127.0.0.1 — it is not reachable over a network without a reverse proxy (nginx, etc.) |
| No authentication | Anyone on the same machine can access the app — no password or login screen |
| Gunbot dependency | All data comes from Gunbot. If Gunbot is offline or has no trades, the dashboard will show empty or stale data |
9. Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| 502 Bad Gateway | Gunbot is not running, or is on a different port | Start Gunbot; check that it runs on port 3001; verify the Host URL in Settings is http://localhost:8080 |
| Connection dot stays red | Gunbot offline, or wrong API token | Confirm Gunbot is running; re-enter the token from Gunbot Settings API |
| Data is stale / not refreshing | SSE connection dropped | Reload the page. If it persists, report it with how long the session had been open |
| Token invalid error | Token expired or miscopied | Copy a fresh token from Gunbot settings and re-enter |
| Open positions shows 0 | Possible data field mismatch | Report as a bug — include exchange name, pair names, and a screenshot of your exchange's positions |
| Page does not load at all | serve.js not running | The WEN server is offline — contact your setup contact to restart it |
10. Bug Report Checklist
When reporting a bug with WEN Terminal, include all of the following:
- Tool: WEN Terminal (:8080)
- Step-by-step description of what you were doing
- What you expected to happen
- What actually happened — paste the exact error text from the UI
- Health check JSON: paste the output of http://localhost:8080/health
- Screenshot of the full WEN Terminal page at the moment of failure
- Browser and version (e.g. Chrome 125, Windows 11)
- Approximate time it happened
- For data accuracy bugs: screenshot of Gunbot or exchange showing the correct value
- For order bugs: the exchange name, pair, amount, and side you entered