An agent's execution loop and session machinery shape its behavior as much as its tool list. Making those components replaceable plugins puts orchestration itself within reach, which matters when a team's workflow outgrows the defaults of an assistant.
What Sets It Apart
- Model adapters, tools and the agent loop are configurable plugins, so customization can change how work runs.
- Cordis reverses a plugin's registered effects when it unloads, giving extensions a defined lifecycle.
- Web, headless and SDK profiles use layered plugin composition, connecting interactive work with programmatic integration.
- An append-only session log underpins model history, resume and transcripts, providing a shared record for investigating behavior.
Who It Suits and the Trade-offs
A strong fit for developers building a tailored assistant and users who want coding, research and file tasks in one extensible workspace. The desktop and Web interfaces offer an entry point before writing plugins. Teams requiring stable integration contracts should allow for migration work: the project remains a developer preview and explicitly warns of compatibility-breaking changes.