22 · 4 states
What is real
Part of all this works today, part is half done, part is design and part is direction.
Mixing what already works with what the project proposes is the easiest way to overstate without lying. So here it is, split into four states.
- State 1 Available Works today, in the commit analysed
- State 2 Evolving Exists and will change, possibly breaking things
- State 3 Architecture Proven design, not a feature you press
- State 4 Future A possible direction, not a product and not a promise
Available
Works today, in the commit analysed.
| What | State |
|---|---|
| Install and launch with one command | works |
| Web interface, headless mode and Python SDK | works |
| Any OpenAI-compatible server | works |
| Permissions and isolation as two separate settings | works |
| Complete session log | works |
| The agent loop replaceable by configuration | works |
Plugin composition is real. The agent loop is replaced by configuration, and that is not a promise: it is what the system does at boot.
Evolving
Exists and will change.
It is a developer preview, and the authors warn in capital letters that there will be compatibility breaking changes. At the time of writing there is no tagged stable version.
There is no official terminal interface. It appears in the documentation only as a hypothetical example.
Some providers ship loaded but inactive, and the base package still drags dependencies the maintainers themselves mark as pending cleanup.
When you modify a piece, your configuration replaces theirs entirely, so you have to rewrite what you did not want to change as well.
Isolation is not always complete, and the system says so: there are environments where it can only guarantee part of it. The Python SDK does not run everywhere, and its example composition does not support Windows.
Architecture
This is proven design, not a feature you press.
Revertible effects, reactive coeffects and the five theorems describe properties of the composition system. They are proved in the paper and there is a correspondence between its symbols and the interfaces in the code.
The theory existing does not mean you can use it directly. It means that when you load and unload pieces at runtime, somebody has formally checked that the result does not depend on the order and leaves no residue.
Future
This is direction, not product.
A harness that modifies itself while it works is what the architecture makes possible, not what the repository ships today. Nothing we have read claims that behaviour exists.
Two warnings that do not depend on the state
The curve
The architecture documentation opens by warning that it assumes the framework underneath, and recommends using an agent to explore the code.
A repository recommending that says something. It is not necessarily a defect, but it is a warning worth taking seriously before committing a team.