Sessions do not disappear into hard work. They disappear into re-running work that was mis-specified the first time, on a reasoning tier that was never needed. Choose the coding tool you use; Metis decides how to spend its intelligence and writes the prompt.
Half-formed is the correct input. That is where the routing decision actually gets made, and it is the state your tool never sees you in.
Plenty of tools will make your sentence more polite and put "you are an expert" in front of it. That is not the problem.
They take a request you have already decided on and rewrite it more formally. They cannot tell you it should have been three requests, that it belongs in a fresh session, or that it should not be built yet.
Works on the decision, not the wording. What the task actually is, where it runs, at what tier, whether it is ready at all, and what your tool will get wrong. The prompt is the last step, not the product.
A confident plan built on a vague thought is the expensive failure, because you find out four corrections later. When the work is not ready, Metis says so instead of guessing.
Real and scoped. You get the route, the split, the criteria, and prompts you can paste.
Only what lives in your head, never what your repo could answer. Tap the options and the plan builds itself from your answers.
"Simplify this without losing features" is a design problem in implementation clothing. Metis says so, and tells you what the spec has to pin down.
Nobody keeps up with which tier suits what, when a goal beats a prompt, or when a fresh session costs less than dragging context. Metis picks, and shows its reasoning.
No checkout, account, or subscription. The beta is intentionally small until repeat use proves it deserves more infrastructure.
Failed requests do not use the allowance. The counter resets at 00:00 UTC.
Metis never reads or connects to your repository. It sends the thought you type, plus any selected Project context and Tool notes, to Cloudflare Workers AI to produce the brief. Do not paste credentials, secrets, personal data, or confidential source code.
Plan mode plans the request you already gave it. Metis works on whether that was the right request, on the right tool, at the right tier, in the right session. It runs before the tool opens, which is also why it can tell you not to build something yet.
No. Routers sit in the request path and classify traffic a machine already understands. Metis sits in front of you, on work that is not a request yet, where the intent is still in your head and the wrong call costs a rerun rather than a few cents.
Yes. It is judgement, not arithmetic. The reasoning is shown for every call so you can overrule it, and tiers and limits change often enough that it flags where you should confirm against current docs rather than pretending to know.
The opposite. Lazy, fragmentary and unpunctuated is the intended input. If a thought is too vague to route, you get tappable questions rather than a confident guess.
Metis is built to need little data and no account.
Your briefs, Project context, Tool notes, and preferences are stored in this browser. “Delete local data” removes them from the device.
The thought and any selected context or Tool notes are processed by Cloudflare Workers AI. Metis does not send your repository because it never has access to it.
There are no accounts, ads, analytics, or tracking cookies. To enforce the free allowance, Metis stores short-lived, bucket-specific hashes derived from the request IP—not the raw IP. An optional useful/not-useful vote is tied only to an anonymous run token. Operational records are automatically pruned.