Guide
Connect the right wallet before trading or funding actions.
Omni Terminal supports wallet and email/Google sessions, but wallet connection remains authoritative for ownership, signing, and funding actions. The chooser supports common injected wallets and WalletConnect while keeping session and wallet authority separate.
At a glance
- Wallets
- Injected + mobile The login surface can expose injected wallets and mobile wallet connection options.
- Session
- Host-scoped Sessions are resolved against the current host to avoid cross-host ambiguity.
- Funding
- Reconnect Funding actions are blocked until the selected primary wallet is connected.
Why It Matters
What traders and researchers should take away
- Choosing the intended wallet matters for account ownership and action authority.
- Email or Google sessions can trade with stored agents but still need a connected wallet for funding movement.
- Public documentation can explain the flow without showing real wallet addresses.
How it works
What the product uses behind the scenes
- Authentication routes own login and wallet verification.
- Wallet linking docs define the primary master wallet model and legacy compatibility.
- Playwright wallet harnesses verify injected-wallet chooser behavior without relying on real extension UI.
Notes
Things to know
- Never publish private keys, wallet seeds, API keys, or Cloudflare Access headers.
- Screenshots should use redacted or demo addresses.
- Wallet availability can vary by browser, mobile app, and extension setup.
- If a session expired, predates host-bound sessions or was created on another DEV/PROD host, sign in again on the current host. Reconnecting a wallet or switching Hyperliquid networks does not renew the Omni session.
- A public wallet being observed is not the connected wallet, a trading agent, or an execution subaccount.
Guide
Steps
- Open the login surface
Use the terminal login action or
/auth/loginto open the wallet connection flow. - Choose the intended wallet
Select MetaMask, Rabby Wallet, OKX Wallet, Coinbase Wallet, Keplr, or WalletConnect for the wallet that owns the Hyperliquid account you intend to use.
- Approve the session
Sign the login message. If you enabled two-factor authentication, enter your authenticator code or an unused recovery code before expecting a full session. Then verify that the terminal shows the expected account context. Login remains separate from Enable Trading.
- Return from your mobile wallet
Approve the requested account and network in your wallet app, then return to the same browser or PWA. Let that connection attempt finish before starting another. A login signature proves ownership; it is not a trade or a transfer.
- Reconnect for funding when needed
If funding or collateral controls ask for a scoped wallet, reconnect the selected primary wallet before signing.
Safety
Before using this workflow
- Do not reveal wallet seeds or private keys.
- Confirm the wallet row before signing.
- Use redacted addresses in documentation images.
Next
Open the workflow
- Connect Wallet Open the login flow.
Screenshots
Real UI references
These are captured from Omni Terminal routes with public-safe state. Private balances, wallet secrets, access headers, and live private positions are not used.
/auth/login 2026-06-13 - docs-v1Session expectations
Wallet login and app session state are related but not the same thing.
- Wallet signing proves account ownership for login.
- Email/Google sessions may still require wallet reconnection for funding actions.
- Host-scoped sessions avoid dev/prod cookie ambiguity.
Mobile connection and recovery
Use the account approved in your wallet app, not an unrelated installed extension.
- After approval, return to the browser or PWA that started the request. Closing or backgrounding the chooser during wallet handoff does not by itself mean the request was rejected.
- If you cancelled, rejected, or let the request expire, start a fresh attempt. A superseded attempt must not complete a later wallet selection.
- If the account or network genuinely changed, explicitly select the intended wallet and reconnect. Never approve a different account just to dismiss an error.
- Login uses the approved session account and chain. Trading and collateral actions still enforce their own required signing network.
Observe a public wallet without connecting it
The eye-shaped Observe wallet control opens public inspection in the main terminal.
- Open Observe wallet in the header, enter a complete wallet address, or choose a saved wallet. Supported public data can be inspected while signed out.
- The observed address and Read-only state identify whose public records you are viewing. Missing public balance or risk data is unavailable, not your connected account balance.
- Observation does not select a signer, validate a WalletConnect account, or authorize orders, cancellations, margin changes, or funding. Incompatible action drafts are discarded when execution context changes.
- Use View performance for the dedicated statistics page. Exit observation or View my account returns to your connected account, or public market browsing when signed out, while keeping useful market context.
Do not repeat an uncertain funding action
A missing response is not proof that an approved transaction failed.
- Check the original wallet, network, amount and destination before approving. Changing account or execution scope requires reviewing the action again.
- A request already handed to your wallet or the exchange cannot be recalled just by switching accounts or entering observation.
- If a submitted action has an uncertain outcome, inspect the original wallet transaction and exchange history before retrying. Some pending-action fences survive same-tab refresh, but automatic receipt recovery and multi-step conversion reconciliation are not guaranteed.
- An EVM transaction receipt does not by itself prove that Hyperliquid has credited the deposit. Confirm the destination balance separately.
References
Implementation references
Wallet testing guide
omni-terminal/docs/WALLET_PLAYWRIGHT_TESTING.mdDocuments the repeatable wallet chooser and injected-provider test harness.
Wallet linking model
omni-terminal/docs/WALLET_LINKING_MODEL.mdDocuments user, wallet, and Hyperliquid account relationships.