Suite Home Beta Guide
Beta Tester Documentation

WEN Terminal Suite
Beta Guide

Read this first. Everything you need to know about the five tools, how they connect, and what to test — before you open a single tab.

Start with Terminal Suite Home
The Suite
Five tools. One machine. No cloud.
:8080
WEN Terminal
The Gunbot trading dashboard. Live P&L, open positions, trade history, balances, and strategy configuration — all in one browser tab with zero CORS friction.
Read the beta guide
:8081
Webhook Portal
A smart signal gatekeeper. Receives webhooks from TradingView or scripts, runs them through 10 rule types and 30+ live indicator filters, then routes approved signals to Gunbot.
Read the beta guide
◎ :8082
HL Copy Trading
Watches Hyperliquid wallet addresses via live WebSocket. When a watched wallet trades, mirrors it through Gunbot on your exchange. Score wallets on 30-day analytics before copying.
Read the beta guide
𝕏 :8083
Twitter Monitor
Watches public Twitter/X accounts for keywords. When a match fires, it sends a trading signal — through the Webhook Portal (with all your gate rules) or directly to Gunbot.
Read the beta guide
Tax
WEN Tax
ATO-compliant crypto tax engine. Import trade history from multiple exchanges, add manual transactions, calculate CGT and income events for any Australian financial year, export a report for your accountant.
Guide coming soon
Architecture
How the tools connect
Source
TradingView
Alert webhook
Gate
Webhook Portal
:8081
Execution
Gunbot
:3001
Market
Exchange
Binance · Bybit…
Source
Twitter/X
Keyword match
Optional Gate
Webhook Portal
:8081
Execution
Gunbot
:3001
Market
Exchange
Binance · Bybit…
Source
Hyperliquid
Wallet WebSocket
Analyser
HL Copy Trading
:8082
Execution
Gunbot
:3001
Market
Exchange
Binance · Bybit…

WEN Terminal (:8080) is a dashboard only — it reads Gunbot data and allows manual orders. It does not send signals.

Access
How to open each tool

Your WEN installation starts automatically with Gunbot. Open any tool in a browser on the same machine — no login required.

URLToolWhat it does
http://localhost:8080/landingSuite HomeMaster landing page — live status of all four tools, signal flow diagram, links to every app
http://localhost:8080WEN TerminalGunbot dashboard — positions, P&L, balances, trade history, manual orders
http://localhost:8081Webhook PortalSignal receiver — live log, gate rules, indicator filters, config
http://localhost:8082HL Copy TradingCopy engine — wallet management, analytics, discovery, live signal log
http://localhost:8083Twitter MonitorSocial signals — account list, keywords, log, start/stop controls
If a page does not load
That tool's server is not running. Check the Suite Home status bar — a red dot next to a tool name means it is offline. Contact your setup contact to restart it.
Beta Testing
What to focus on
Accuracy
Does the data on screen match Gunbot or your exchange? P&L figures, open positions, balances — report any mismatch with the specific pair and exchange.
Reliability
Does anything stop working after running for a few hours? Does the app recover correctly when Gunbot restarts mid-session?
Edge Cases
No open positions. Market closed. Signal for a pair that isn't configured. Gunbot returns an unexpected error. What happens?
Gate Accuracy
Does the Webhook Portal block signals that fail your rules? Does it pass signals that should pass? Document any case where the gate behaved unexpectedly.
Analytics
Are the HL Copy Trading analytics correct for wallets you can verify? Does the A–F grading seem reasonable for the traders you test?
Tax Calculations
Does WEN Tax's CGT output match what you'd calculate manually? Does the 50% discount apply correctly to long-term holdings? Does switching cost basis method change totals as expected?
Usability
Could a Gunbot user who hasn't read the docs figure out each screen? Note anything confusing, mislabelled, or that needed multiple attempts.
Feedback
What to include in a bug report
  • Which tool (Terminal / Webhook Portal / HL Copy Trading / Twitter Monitor / WEN Tax)
  • What you were doing — step by step, not just "it broke"
  • What you expected to happen
  • What actually happened — paste the exact error text, not a paraphrase
  • Whether the problem was repeatable (happened once / every time)
  • Health check response — paste the JSON from http://localhost:PORT/health
  • Screenshot of the UI at the moment of failure — the whole page, not just the error
  • Browser name and version (Chrome 125, Firefox 126, etc.)
  • Approximate time it happened (so server logs can be checked)
Quick Reference
Individual beta guides
:8080
Terminal Beta Guide
Dashboard, manual orders, connection setup, 15-item test checklist, troubleshooting.
Open guide
:8081
Webhook Portal Guide
All 10 gate rules, all 31 indicators, TradingView setup, HMAC warning, 12-item test checklist.
Open guide
◎:8082
HL Copy Trading Guide
Scaling modes, all entry/exit gates, analytics metrics, A–F grading, 12-step test sequence.
Open guide
𝕏:8083
Twitter Monitor Guide
Bearer Token setup, keyword config, rate limit tiers, routing modes, 11-step test sequence.
Open guide