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
Japanese Developers Were Early to Spot AG-UI's Potential
What Happened
CopilotKit tweeted that a lot of early interest in their AG-UI protocol came from Japanese tech Twitter, before it gained wider attention elsewhere.
What AG-UI Actually Does
AG-UI is an open protocol that lets AI agents talk to user interfaces. It works over HTTP with 16 different event types for things like syncing state between agents and UIs, coordinating tools, and keeping humans in the loop when needed. It’s designed to work with frameworks like CopilotKit without locking you into a specific vendor.
Why Japan Got There First
CopilotKit has been shipping steadily—their v1.50 release added thread persistence and a useAgent hook for React and Angular apps. Japanese developers picked up on AG-UI early, with tutorials showing up on Qiita and Zenn.dev for integrations with Bedrock and ADK Chat UI.
It’s hard to say exactly why Japan moved faster on this. Maybe it’s the dev community’s preference for modular, well-documented tools. Maybe it’s just that the right people happened to notice it at the right time. Either way, the interest was real—specific tweets about AG-UI embedding, working code examples, the whole thing.
What This Suggests
Open protocols that don’t lock you in tend to spread through developer communities organically. AG-UI seems to be following that pattern. The Japan-first adoption is interesting but probably says more about how tech trends move through different communities than anything specific about the protocol itself.
CopilotKit’s tweet mentioned a “USA-Japan Twitter crossover” but didn’t point to any specific event, so it’s likely they’re just describing the general pattern they noticed.
Impact Assessment