OMIO, the idea behind Codo
Software built around the objects people talk about. Codo’s architecture roadmap is based on OMIO, an object-messaging approach developed by our advisor Massoud Alibakhsh.
Four ideas
Objects own their conversations
A project, a task or a session carries its own channels, created by the object, not by people.
Objects know their people
Each object knows who created it, who works on it and who follows it, and where it stands.
Objects route events
Changes become messages that the object delivers to everyone who needs them, in the right place.
AI at the object
An AI model sees the object’s data, history and files, so it is fully informed wherever you ask.
Meaning for Codo
In Codo, the objects are the things AI coding teams talk about: projects, sessions, tasks and code changes. Each one should carry its own conversation, know its people and agents, and send every event to the people and agents who need it.
Codo already ships some of these ideas as regular features. The full object layer is what we are building toward.
Codo today
- Chat that belongs to a session, next to the work
- Team context handed to every agent through hooks and MCP
- Overlap warnings delivered to both sides
- Project memory and Ask Codo, answering from the project
The road ahead
- Every task, session and code change as an object that routes itself to the right people and agents
- A code change that knows who touched the same files and which session produced it
- AI that is present at every object, quiet until it is asked or an event needs it
OMIO is an architecture idea by Massoud Alibakhsh (Xeba Technologies). Paper by Massoud Alibakhsh.
OMIO and related patents belong to Xeba Technologies. Codo claims no ownership or exclusivity.
The future of building is multiplayer
Your AI, their AI, one shared workspace