Futures
Access hundreds of perpetual contracts
CFD
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
CFD
U.S. stock CFD derivatives
US Stocks
Access real US stocks and ETFs
HK Stocks
Trade quality Hong Kong-listed stocks
Korean Stocks
SK Hynix
Real Korean stocks and top assets
Stock Futures
High leverage, 24/7 trading
Tokenized Stocks
Backed by real stock assets
IPO Access
Unlock full access to global stock IPOs
GUSD
Mint GUSD for Treasury RWA yields
Stocks Activities
Trade Popular Stocks and Unlock Generous Airdrops
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
IPO Access
Unlock full access to global stock IPOs
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Promotions
AI
Gate AI
Your all-in-one conversational AI partner
Gate AI Bot
Use Gate AI directly in your social App
GateClaw
Gate Blue Lobster, ready to go
Gate for AI Agent
AI infrastructure, Gate MCP, Skills, and CLI
Gate Skills Hub
10K+ Skills
From office tasks to trading, the all-in-one skill hub makes AI even more useful.
Augment Code actual test of AGENTS.md's impact on code generation: the best is equivalent to upgrading the model by one tier, the worst is worse than not writing it.
ME News, April 23 (UTC+8), according to Beating monitoring, AI programming tool company Augment Code extracted dozens of AGENTS.md files from its own monorepo, and used its internal evaluation suite AuggieBench to measure their real-world impact on the outputs of coding agents. The method was to use already-merged high-quality PRs as benchmarks, then have the agent redo the same task under two conditions—with and without AGENTS.md—and compare the scores. The gap was much larger than expected. The best-written AGENTS.md improved quality by an amount comparable to upgrading the model from Haiku to Opus, while the worst-written version was still worse than having no AGENTS.md at all.
Moreover, the same document could have opposite effects on different tasks: it increased compliance for a bug-fix specification by 25%, but reduced completion of a complex feature in the same module by 30%. There are several effective writing approaches: keeping the main file to between 100 and 150 lines, pairing it with a few focused reference documents, and in medium-sized modules with around a hundred core files, achieving an overall improvement of 10% to 15%. Writing the process as numbered steps works best—using a 6-step deployment process reduced PRs with missing files from 40% to 10%, and increased accuracy by 25%. Using decision tables to help the agent choose the right approach before acting also improved compliance by 25%. For prohibitions, alternative solutions must be provided; simply writing “don’t” makes the agent indecisive, and performance noticeably deteriorates with more than 15 consecutive warnings.
The easiest way for this to go wrong is having too many documents. Once the agent is pulled into a large amount of architecture documentation, after loading hundreds of thousands of tokens, its output actually gets worse. In one module, 226 documents totaled over 2MB, and even the best AGENTS.md was useless. Additionally, AGENTS.md is the only document location that the agent reads 100% of the time; documents under _docs/ that are not referenced have a discovery rate of less than 10%. (Source: BlockBeats)