我们为人类设计的语言，第一个真实用户却是编程智能体

At our first hackathon the loudest complaint was that coding agents didn't know our language. They made up syntax and gave bad suggestions, which made a new language harder to pick up. We'd spent a long time making it easy for humans to learn, and it turned out the first developer showing up was an agent.

So we wrote agent-facing docs, a set of skill files and an MCP server. The MCP server lets the agent run its code through the real compiler, so it gets actual errors back instead of guessing. By the next event 73% of teams were building with a coding agent plus those, and the share who called getting started easy went from 23.5% to 76.9%. The syntax stayed the same, the agents just got better at it once they had something to work from.

That changed how we think about language design. Agents copy whatever pattern is most common, so if the normal way to build a login page is a route file, a model file, a schema, a migration and a frontend component, you'll get all of those every time. Each one is a spot where the agent can drift or invent something. Vibe coding is great, and we think the next speedup comes from making fewer things need deciding in the first place.

Our bet is to put as much as possible in one place, so persistence, API and logic live together by default. Fewer layers of glue means fewer places for an agent to wander off, and less for you to review when you want to read what it wrote.

We'd love to know what you've seen. When your agent gets something wrong, do you blame the model or the stack?