Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
GUI for Humans, CLI for Agents: A Practical Split
Headline
AI Engineer Argues for Splitting Interfaces: GUIs for Humans, CLIs for Agents
Summary
In a recent tweet, AI prompt engineer @dotey (宝玉) made a straightforward argument: humans naturally gravitate toward graphical interfaces like OpenAI’s Codex GUI, while AI agents work more efficiently with command-line tools like Feishu’s newly open-sourced lark-cli. The upshot? Users can direct agents without touching the command line themselves. He was responding to another user’s tweet about Feishu’s CLI launch, which gives agents access to enterprise functions like messaging and calendars through text commands with dry-run previews. This matters because it points to a practical design pattern for human-AI collaboration that could make agent-based workflows more viable in enterprise settings.
Analysis
@dotey runs a blog (baoyu.io) and YouTube channel covering AI programming and coding agents. His posts regularly discuss tools like Claude Code and Anthropic’s models, which gives his take on interface design some weight—he’s been tracking these shifts closely.
Looking at the actual tools: OpenAI’s Codex offers both a GUI for human coding assistance and a lighter CLI for agent automation. Feishu’s lark-cli focuses on context-saving, composable commands designed for agents. The pattern here is that GUIs handle the messiness of human intuition and exploration, while CLIs give agents the precision and scriptability they need.
The original tweet @dotey responded to wasn’t available, but thread context suggests it sparked discussion around Feishu’s CLI launch.
What this might mean going forward: more open-source CLI standards built specifically for agents, reduced context overhead for models, maybe something like “skills-as-a-service” emerging. The risk is obvious—if teams focus too heavily on CLI tooling, non-technical users get left behind unless GUI layers keep pace. Early comparisons suggest lark-cli improves on existing multi-command protocols for flexibility, which could give it legs in the enterprise automation space.
Impact Assessment