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
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Pre-IPOs
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.
GateRouter
Smartly choose from 40+ AI models, with 0% extra fees
Claude Desktop raises the wall: Gateway update blocks non-Claude models, community gameplay becomes useless in two weeks
According to Beating monitoring, Claude Desktop pushed version 1.6259.1 on May 6, adding model ID whitelist filtering to the third-party inference (3P) Gateway mode. Previously, the community used Gateway interfaces to connect to gateways like OpenRouter and run non-Claude models such as GPT, Grok, and DeepSeek, but after the update, all of those methods failed.
After the update, the model discovery interface in Gateway mode checks every model ID returned by /v1/models, keeping only entries that start with claude or anthropic. Ollama users reported that the gateway returned 39 models, but after filtering in Claude Desktop, 0 available models were shown. Manually configuring non-Anthropic models in the inferenceModels configuration also caused errors: “configured model is not an Anthropic model. Gateway deployments require an Anthropic model from the provider catalog.” Some users set up a local proxy and mapped the IDs of models like Kimi K2.6 into the claude-sonnet-4-6 format, restoring normal operation—proving that the restriction is at the model ID filtering layer and does not involve protocol or capability detection.
On the same day, the Claude Code CLI 2.1.129 release also tightened Gateway integration. Model discovery changed from the default automatic behavior in version 2.1.126 to opt-in, and users must manually set the environment variable CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY=1 to query the gateway’s model list.