Build together, not alone
Spinini started as a solo tool — one developer, one project, one container. But great software is built by teams. Today we're announcing the Collaborators panel: invite anyone to your project by email, set their role, and work together in real time.
How to invite a collaborator
Click the Users icon in the bottom section of the left sidebar. The Collaborators panel opens.
Enter the email address of the person you want to invite, choose their role, and click Invite. They receive an email with a direct link. When they click it and sign in (or sign up if they're new), they land directly in your project.
You can invite as many collaborators as you need. There's no per-seat limit on shared projects — the project owner's plan determines what features are available.
Roles: View and Edit
View — read-only access. The collaborator can see all files, browse the file tree, see the preview, and watch the terminal. They cannot create or modify files, run the AI agent, or execute terminal commands. Great for clients who want to follow along, or for code reviews where you want someone to look but not touch.
Edit — full access. The collaborator can do everything you can: create files, edit code, use the AI agent, run commands in the terminal. The only thing they can't do is manage collaborators or change project settings — that's reserved for the project owner.
What real-time collaboration looks like
When two people have a project open simultaneously:
- Changes appear in the file tree for all collaborators as soon as files are saved
- The terminal shows output from whichever process is running
- The preview updates for everyone when files change
If two people edit the same file at the same time, the last save wins. For coordinated editing, use the AI Chat to discuss who's working on what — you can both have it open and share context in the same conversation thread.
Use cases
Pair programming — two developers, one working on the frontend, one on the backend, in the same project. No more sending zip files back and forth or fighting with git branches.
Code review — give a reviewer View access so they can read through your code and open the preview to test it, without any risk of accidental changes.
Teaching and mentoring — share your project with a student or mentee. They can watch you work, ask the AI Chat questions about what they see, and then you can bump them to Edit when they're ready to try themselves.
Client demos — give a client View access so they can see the live preview and check the files if they're technical. No need to deploy to a staging server just for a review.
Team projects — multiple builders working on different parts of the same app. Combine with Version History checkpoints so everyone saves before major changes.
Managing collaborators
The Collaborators panel shows everyone who has access to your project, their role, and when they last accessed it. You can change someone's role at any time or remove them entirely. Changes take effect immediately — if they're currently in the editor, they lose access on their next action.
Coming soon
We're working on richer collaboration features: cursor presence (see where collaborators are editing), inline comments on files, and per-file activity logs. If you have specific collaboration features you need, email support@spinini.com — your feedback directly shapes our roadmap.