Work together, in the same project
Share a project with a link. Everyone sees the same scene, the same cursors and the same changes as they happen — and a guest you invited to look cannot change it.
A link, not a file
You share a project by generating a link, or by inviting someone directly. They open it and they are in — no copy to send, no version to merge back, no "final_v3_REAL" in anyone's downloads folder. Everyone who has been given access sees the project as it is now.
Two roles, and the read-only one is real
Each collaborator is set to edit or to view. A viewer sees presence, cursors and the chat, and can leave comments — and that is all they can do. It is not a hidden button: the server refuses the messages that would change the document, so a read-only guest is read-only even to someone who knows how the protocol works.
- Edit — full access to the project
- View — presence, cursors, chat and comments only, enforced server-side
- Access can be withdrawn at any time
Locks, so you are not fighting over the same object
When someone starts moving an object, it is locked for the others until they let go. Locks are released when they disconnect and expire on their own if a tab dies, so nobody can accidentally take a piece of your scene hostage by closing their laptop.
Comments where the work is
Feedback lives in the project rather than in a chat thread somewhere else, so a note about a model is attached to the model. Reviewers can be given view access and still say everything they need to say.
The same room carries the AI teammate
Aukimi AI drives your editor through this same collaboration channel. That is why the read-only rule matters as much as it does: the messages that let the AI act are the ones a viewer may never send, so a guest cannot act by proxy through an agent.