How multiplayer works
The core idea: everything is a shared object, and anyone can extend it.
In most AI products, work happens in a private thread. In Kryttle, work happens in objects that live in the workspace and have members.
The three properties
- Visible. Anyone with access sees the actual running thing: its jobs, its history, its last run. Not a transcript of it.
- Extendable. A teammate can add a job to your agent without asking you, without forking it, and without holding your credentials.
- Shared. When their addition runs, you see it too. It stays one object.
Example. Meera builds an agent that reads vendor mail and keeps a sheet current. Rohan adds a job to it: fetch each vendor's rating. Finance builds a report on the same data. Nobody started over, and nobody sent a screenshot.
Live sessions
When an agent is doing something long (chasing forty vendors, composing a board pack), any teammate can open it mid-run, watch the steps, redirect it, or take over. The same way you would lean over a colleague's shoulder.