07When a server ships 100 tools
Call every server
from one snippet.
The model reaches your MCP servers, your past conversations, and the decision engine by writing Python in one code tool. The tool definitions never change when a server connects, so the prompt cache holds, and a snippet returns only what the model needs to read.



One tool for every MCP server
The model never sees an MCP tool definition. It calls your servers from Python, and a snippet can call several tools at once. A server that connects, fails, or changes its tools never changes the tool definitions or the system prompt.
Filter before the model reads
A snippet can filter, join, and summarise results before the model reads anything. Only what it prints and the value of its last expression come back, so a list of 500 issues can come back as three lines.
Python in an isolated worker
coderuns snippets in a separate worker with no file system, network, environment variables, or subprocesses. A snippet that calls nothing outside the worker runs without a prompt, and each call it makes, such as a search of your past conversations, is checked on its own.timeoutSecbounds the whole run, waits included.Judgement inside the snippet
decisions.decide()anddecisions.rerank()judge what a snippet gathered before any of it reaches the model.Past conversations from Python
A snippet can search the history of this project or of every project to find an earlier decision or a command that worked.
JavaScript when the meaning holds
A snippet written in JavaScript or TypeScript runs as Python when every part of it has a Python form that keeps its meaning. Anything else does not run, so a translation never guesses.