Extella for developers
Developers
Docs, write-ups, code
Documentation, technical write-ups and examples with code for working with Extella.
01 / Documentation
Documentation
How to use Extella: install it, save a program, prepare a device, call it from code or from an agent.
Your first programInstall Extella, connect a device and call one program twice.ProgramsWhat is stored under a name, how to save code, check the record and pass new parameters.Devices and handlersWhere code runs, what to prepare and how to check a failed run.API and MCPAuthorisation, requests to programs and connecting the tools to an agent.Build an applicationFrom one useful program to a window, an agent or another device, and the handover to a colleague.
02 / Articles and write-ups
Articles and write-ups
Why it is built this way and what our checks showed, with the data behind every number.
Experiments and materialsOne handler, many programs: what changes on an updateSeven experiments in the order of the article: question, conditions, result, limits, code and data.What it shows: One handler edit reaches every program of its language, and so does a mistake; the check before replacement found 35 wrong totals out of 40 in 10 s and kept that version out.Benchmark and calculatorAsk the model every time, or keep the program it wrote onceTwo order-approval tasks on a 9B model, GPT and Claude Sonnet, with a cost calculator at list prices.What it shows: A 9B model answered 14 of 50 orders right but wrote a program that got 50 of 50; a saved program costs about one run to write and nothing after.ArticleCSPL: a program is stored separately from the way it is executedThe expert record, the two calls, declaring a language, what was verified, related work and limits.What it shows: New tools for an agent without changing the server: a program is stored with the name of its language and runs under a handler on any prepared device.Write-upHow Extella is builtThe program and its execution are configured separately; the handler can be changed without touching the program.What it shows: The program and the way it runs are separate: the handler changes, the program text stays the same.Write-upExperiments and limitationsDirections that are not finished yet, with what has and has not been checked.What it shows: Where the boundary is: what is not ready yet and what exactly has not been checked.
All open experiments on GitHub 03 / Examples with code
Examples with code
What to open and how to repeat it: a working example, its code and how to run it yourself.
Site with a brand bookA model writes a site block; the handler on a device checks it. The server code and the handlers are published.What it shows: The model writes, the handler holds the brand rules: a block that breaks the brand book never reaches the page, and one site law re-prices every block at once.
Robot townA delivery robot with town rules written in a few lines. The town law is a handler version.What it shows: Safety rules live in the executor, not in the model: a small model writes a few lines, the handler explains each mistake in words, and with 2 model calls (755 tokens) the robot delivered 6 parcels of 6.
A report on the machine that holds the fileOne saved program runs on two servers. first_program.py saves and runs it on your machine.What it shows: Compute where the data is: the program goes to the file, not the file to the cloud. One saved program runs on any prepared machine chosen in the call, with no model in the run.
Your own language: a 12-line handlerThe tally language of the CSPL article: handler, registrar and one script that saves and runs both.
04 / Sell or publish your app
Sell or publish your app
For app authors: how to put your app in the Extella store, what you earn and how payouts work.