Command line
Run a prompt, query the document index, or pipe a file through a local model from a shell, on the machine that already holds the data.
Private betaA local model is a local process. That makes a few things possible that a hosted API cannot offer: no key to leak, no per-call cost, no request leaving the machine, and a filesystem that is simply there.
Run a prompt, query the document index, or pipe a file through a local model from a shell, on the machine that already holds the data.
Private betaA loopback HTTP endpoint so your own scripts and editors can reach the same models, with no key to leak and no request leaving the machine.
PlannedConstrain a response to a schema you supply, so the output can be consumed by software rather than read by a person.
PlannedDeclare which class of task goes to which model, and whether a task is permitted to leave the machine at all.
PlannedMulti-step tasks that stop and ask before any step that writes a file or opens a connection, with the pending action shown in full.
PlannedInference engines sit behind an adapter, so the runtime can adopt a better one without the product being rebuilt around it.
PrototypeNone of the above has shipped. The command line exists as a specification and an early prototype; the local API, structured output and supervised execution are designed and not built. There is no package to install today and no endpoint to point a client at.
On engines: the runtime is built so that inference sits behind an adapter rather than being welded to one implementation. Third-party engines are used under their own licences, with their notices preserved, and are never presented as our work. If you care about that distinction - and if you are reading this page, you probably do - it is written down in the application’s notices rather than being a claim on a marketing site.
If the command line and the local API are the parts you care about, say so in the application - there is a Developer option, and it changes what we build first.
Apply as a developer tester