The pitch is multi-user, the open-source table is single-user
Where people and agents build in tune.
At a glance
- What is it?
- Tutti is a real-time shared workspace where several AI agents work from the same context, and it was recently opened up. The comparison table in its own README gives every collaborative capability to a separate VM edition, which is the first thing to read before planning around it.
- Who is it for?
- Tutti is worth evaluating if you run two or more coding agents and keep losing the thread between them, since the shared workspace and the Big @ mechanism attack exactly that problem. Three things to check first.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 38 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- tutti-os/tutti3,916 ★ · +209
| Repository | 2026-09-10 | 2026-11-15 |
|---|---|---|
| tutti-os/tutti | 3.7k | 3.9k |
209 Stars in the last 66 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Three rows say yes and seven say no
The README is built around a comparison table, and the table has two columns: Tutti Open-source and Tutti VM. Only three capabilities are ticked in both. You can connect existing agents in either. You can use existing subscription credits in either. And the built-in apps exist in both. Everything else is marked for the VM edition alone, with a dash in the open-source column: group chat, work with others, work with others' agents, simultaneous editing, agent borrowing, use across devices, and no-deploy sharing. One row is the clearest statement of the difference. Big @ works across your own agents in the open-source build and across others' agents in the VM. The headline sentence above the table calls this the first multi-user, multi-agent, real-time collaboration space, and the multi-user half of that sentence belongs to the other download.
One release tag is named stable
The three most recent releases are not all version numbers. v0.2.32 was published 2026-09-03, v0.2.33 at 07:16:43 on 2026-09-05, and between them, at 07:16:54 the same morning, a tag named simply stable with the title Stable (Recommended). That is eleven seconds after the versioned release it presumably points at, and unlike a semver tag it does not identify a build. Anyone pinning Tutti by version can use v0.2.33 and know what they got. Anyone following the recommended channel is following a moving name, which is the normal arrangement for a stable channel and worth knowing before a surprise upgrade. The last push to the default branch main is dated 2026-09-05, the same day.
Five Go builds chained with cd in one script
The repository is TypeScript at the root with a Go workspace beside it, and the build script shows both. The build entry point runs the recursive workspace build, then a generate:builtin-apps step, and then five separate directory changes each followed by go build ./...:
cd packages/appcli/core && go build ./... && cd ../../workspace/files && go build ./... && cd ../../workbench/service && go build ./... && cd ../../../services/tuttid && go build ./... && cd ../../apps/cli && go build ./...Every relative path depends on the one before it, so a directory rename breaks the tail of the chain rather than one step, and there is a second script, build:go, that repeats the same five builds without the npm half. A go.work file and a go.work.sum at the root are what tie those five modules into one workspace. Splitting the script so the Go half can run alone is sensible; expressing five module builds as a chain of directory changes is the fragile part.
The Makefile opens with a shell program
Three make targets exist here, and the work is in the variable above them. NODE_PATH_PREFIX is assigned the output of a shell pipeline that reads .node-version, strips whitespace, then searches $HOME/.nvm/versions/node for directories matching that major version, prints each candidate's major, minor, patch and path, sorts numerically on all three version fields, and takes the last line. Only if that result is an executable node does it print a directory prefix. The next line uses that prefix to invoke corepack pnpm at a pinned version. So the Makefile exists to make sure the developer and the CI run the same Node and the same package manager, and it does it by shelling out to nvm's directory layout from inside a variable assignment. The three targets then delegate to pnpm dev:cli, a shell script for the GUI, and pnpm dev:web.
Node 24 is the floor and two packages are pinned twice
The root manifest requires node >=24 and names pnpm 10.11.0 as its package manager, with the same version required under engines. The workspace globs are apps/*, packages/*/*, one explicit service path for the onboarding builtin app, and tools/fixtures/*. That last one puts test fixtures inside the workspace, which means fixture packages participate in recursive installs and builds alongside real ones. Under a pnpm overrides block, two dependencies are pinned to exact versions across the whole tree: @radix-ui/react-slot at 1.2.5 and yauzl at 3.4.0. A workspace-level override like that is the blunt instrument for a transitive problem, and it applies to every package in every workspace, including the fixtures.
Four custom checks, two with a staged variant
The scripts are mostly repository-specific checks rather than framework commands, and two of them have a second form. check:backdrop-filter-authoring and check:css-has-performance each exist twice, once over the tree and once with a --staged argument, which is the shape you use when you want the rule applied to what you are about to commit rather than to everything. Two more are one-offs with names that describe a policy: check:agent-protocol-enums and check:agent-activity-runtime-boundaries. There is also a generated-code gate, check:api-generated, which runs a script that regenerates the OpenAPI output with --check, then a script that validates agent protocol enums, then a script that checks the Go market client is in sync, each of which fails if the generated form drifts from the checked-in form. A codebase with this many bespoke rules has decided that its conventions are not expressible in the linter's language.
Two refactor handoffs sit at the repository root
The top level of this repository contains working notes. There is AGENTS.md, two translated versions of the contributing guide, a CONTEXT.md, and two files whose names are status reports: AGENT_GUI_CONTROLLER_REFACTOR_HANDOFF.md and AGENT_GUI_REFACTOR_REMAINING_ISSUES.md. Those two are the kind of document written for one person or one agent to pick up a refactor mid-flight, and they live at the same level as LICENSE and SECURITY. Alongside them sit a .codex/ directory, a plan/ directory, a skills-lock.json, design-assets/, config/, and a NOTICE file next to the Apache-2.0 licence. Three translated README files and three translated contributing guides make the documentation bilingual, and the docs themselves live in a docs/ directory whose own README is linked from the header.
An invite code gates one action and not the download
The distribution story is three downloads and one gate. The quick start offers Tutti Local for macOS as a universal dmg, Tutti Local for Windows as an x64 executable, and Tutti VM for macOS or Windows. The gate is narrow: creating a Room requires an invite code, while downloading the VM or joining someone else's Room does not. The README says the VM edition is available during Early Access, and the comparison table gives its entry point as creating a Room with an invite code against the open-source entry point, which is straight to GitHub. So the barrier to running the open-source build is nothing at all, and the barrier to hosting a room for other people is an invitation. That is the same split the capability table draws, stated once more in the distribution flow.
Editorial conclusion
Tutti is worth evaluating if you run two or more coding agents and keep losing the thread between them, since the shared workspace and the Big @ mechanism attack exactly that problem. Three things to check first. Which edition you are actually installing, because the multi-user rows of the comparison table belong to the VM build rather than the open-source one. Whether your Node version qualifies, since the manifest asks for 24 or newer. And what the pinned overrides are protecting you from, since two packages are forced to specific versions at the workspace root.
Frequently asked questions
What is Tutti?
An Apache-2.0 licensed real-time shared workspace for AI agents, described as the first multi-user, multi-agent, real-time collaboration space where context, files, apps and tasks are connected. Its own README says it is not a replacement for your coding agent but a workspace for your agents, and it now has its own app ecosystem for image generation, UI and UX design, docs and presentations.
What can the open-source Tutti build do that the VM edition cannot?
The comparison table shows only three capabilities in both: connecting existing agents, using existing subscription credits, and the built-in apps. Group chat, working with others and with others' agents, simultaneous editing, agent borrowing, across-devices use and no-deploy sharing appear only in the VM column, and Big @ reaches across your own agents in the open-source build rather than others'.
How do you download Tutti?
The quick start links Tutti Local for macOS as a universal dmg, Tutti Local for Windows as an x64 executable, and Tutti VM for macOS or Windows. Creating a Room requires an invite code, while downloading the VM or joining someone else's Room does not.
What is Big @ in Tutti?
A way to @ past conversations, files, app invocations and tasks from inside Codex, including Claude Code's, and to ask Codex to direct Claude Code to do the work, without copying context by hand. In the open-source edition that reach is limited to your own agents.
What does Tutti require to build?
Node 24 or newer with pnpm 10.11.0, which is also the declared packageManager, and the repository pins two workspace overrides, @radix-ui/react-slot at 1.2.5 and yauzl at 3.4.0. The build runs a recursive npm build and then compiles five Go modules listed in a go.work at the root.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/tutti-os-tutti)Star history chart for your README
[](https://hysenlabs.com/projects/tutti-os-tutti)Was this useful?