Bots & Automation on Desk
Desk expands beyond vault access to support bot-driven workflows, strategy automation, and a cleaner control layer for Hyperliquid users, with connected CEX trading paths such as Bitget and MEXC where supported.
Desk resources
Move between overview, features, vaults, bots, AI workflows, FAQ, and how-it-works pages without losing the product story.
Desk Overview
Start with the full product story for Hyperliquid vaults, bots, AI workflows, automation, and connected trading desk controls.
Explore ->Desk Features
See the main product layers across vaults, bots, AI-assisted support, automation, visibility, and supported exchange execution.
Explore ->Hyperliquid Vaults
Understand the vault-first product layer, allocation context, and connected strategy workflows.
Explore ->Bots & Automation
Explore bot-driven workflows, automation patterns, and user-friendly controls on Desk.
Explore ->AI Workflows
Learn how AI-assisted signals, context, and decision support fit into the Desk product experience.
Explore ->How It Works
Follow the Desk path from discovery and action to monitoring, connected workflows, and ongoing control.
Explore ->Desk FAQ
Review common questions about access, vaults, bots, AI workflows, automation, and positioning.
Explore ->How bots and automation fit
Desk should make bot-driven workflows feel usable, understandable, and connected to the rest of the product path, including supported exchange execution where relevant.
Bot-driven workflows
Desk should help users work with bots through productized flows instead of operator-style execution consoles.
Automation with guardrails
Users should be able to understand what is automated, what they control, and where strategy guardrails live.
Strategy-linked execution
Bots and automation should connect naturally to strategy discovery, allocation context, performance visibility, and supported connected execution.
User-friendly controls
The control surface should stay approachable even when the underlying workflows are advanced.
Explore Desk before requesting access.
Start with the Desk overview, then request access when the bot and automation path fits what you want to do.