Tutti

A desktop workspace that puts several coding agents in the same room instead of asking you to carry context between them. The README names Claude Code, Codex and Hermes as supported, with OpenClaw in development; Cursor and Gemini also appear in the shipped provider icons and probes. They share one workspace: a mention reaches another agent’s past conversations, files, app invocations and tasks, and a reference adds a local file or something an app produced. Tutti ships its own app center — image generation, UI design, documents, decks — that people and agents both call, with every output left in the workspace for the next step. Agents keep running on the subscription their owner already pays for, and the daemon, its SQLite state and the workspace stay on the machine. A second, multi-user product, Tutti · VM, is in Early Access: each agent still runs on its owner’s machine behind a managed local VM while the working state is shared into a cloud Room. The repository is Apache-2.0 and holds 5,361 commits.

Who built itAn organisation account rather than a person. Twenty-six accounts have committed to the repository, and 5,166 of its 5,361 commits carry a linked account. The line is led by SingleMai with 1,256 commits, then devRickyyy 898, jomeswang 798, rv4no 505, hugozhou-ai 488, chovy-ai 364 and copper6666 336; another 195 commits have no linked account at all. Of the 1,088 co-author trailers, 760 name a model or an agent tool rather than a person — “Claude Opus 4.8 (1M context)” on 239, “Claude Fable 5” on 215, “Cursor” on 146 and “Claude Sonnet 5” on 60 — and the largest trailer naming a contributor is rv4no, on 237.

1. 01

   Three months, 5,361 commits, and a release with nothing after it

   The repository was created on 2026-06-12T12:29:05Z, and its oldest commit is dated about seventeen hours earlier: feat: init project for tutti open source, 2026-06-11T19:38:27Z. The published history is 5,361 commits, distributed 1,467 in June, 2,862 in July, 1,029 in August and 3 in September. The newest is fix(agent): require current Codex CLI (#2643) at 2026-09-05T06:07:25Z, and the last push to the default branch is 2026-09-05T07:16:52Z — nine seconds after release v0.2.33 appeared, which is why that release reads as the end of the visible line of work rather than a point along it. At the 2026-10-01 snapshot the repository showed 3,791 stars, 384 forks, 114 watchers and 192 open issues, and this record files it as maintained rather than active: four weeks without a push, after a month that produced 1,029 commits and a September that produced three, is a pause, and nothing about the repository is archived. The queue kept moving after the commits stopped, since four pull requests dated 2026-09-13 and 2026-09-14 are still open.

2. 02

   Three places code may live, and one package that owns the rules

   AGENTS.md opens by naming the shape — a local-first desktop monorepo — and then does something more useful than a diagram: it says which area owns what and closes the usual escapes. services/tuttid holds daemon product rules, durable local state and adapters; packages/agent/host owns provider-neutral agent lifecycle; apps/desktop is the Electron shell and “must not become a second business core”; and packages may not be called shared, common, utils or client-sdk. The lifecycle rule is written as a question rather than a preference — if a change defines when a session, turn, goal or runtime operation is created, when it may be sent or when it is terminal, it belongs in the host package; if it is transport, query or presentation, it is an adapter concern — and new lifecycle semantics must first gain a scenario under packages/agent/host/conformance. pnpm check:agent-host-boundary ratchets against new coordinator, worker or actor orchestration surfaces appearing in the adapter. The document cites its own enforcement: GetSession, UpdateSettings, UpdatePin and DeleteSession were added to the host in PR #1329 after a downstream consumer surfaced the need, rather than reimplemented inside that consumer.

3. 03

   What actually travels between the agents

   The README describes the problem as being the messenger between agents, and the fix as one real-time shared workspace where context, files, running tasks and app output are connected. Three mechanisms carry it. The first is a mention, which the README calls “Big @”: inside one agent you can reference another agent’s past conversations, files, app invocations and tasks, and you can ask one agent to direct another. The second is a reference added from the chat box, which pulls in a local file or something an app produced. The third is the app center itself — image generation, UI/UX design, documents and decks — which people and agents both call, run on the owner’s existing agent subscriptions rather than on resold model access, and whose output stays in the workspace for the next step. Underneath, provider differences are kept out of the interface: the Agent GUI refactor handoff records that Claude Code arrives through an SDK sidecar, Codex through its own app-server protocol, and OpenCode and Cursor through standard ACP, with the Tutti Agent on its own protocol family and Nexight, Hermes and OpenClaw on ACP, unavailable ones explicitly disabled — so that a transport protocol is not treated as a seam of the interface, and a new provider cannot require an identity branch in the controller, composer or view.

4. 04

   An 800-line ceiling and a ratchet that only turns one way

   Business files are capped at 800 lines by a repository lint rule that excludes blank and comment-only lines, and the cap is treated as a signal to decompose rather than a target to argue with. Around it sits a validation stack that is itself part of the product: pre-commit runs staged-file formatting plus eight boundary checks, and pre-push runs pnpm check:changed -- --push-ready, which selects lanes from the changed file set instead of running everything. Each lane stores a fingerprint of its inputs, so a failed run can be retried with --failed-only and only the lanes whose inputs moved will run again. Full validation is a small orchestration script with preparation, preflight and validation phases, compact output by default and per-task logs under .tmp/check-full-runs. The sharpest rule is the Agent GUI degradation ratchet: a committed 17 KB baseline is compared against entropy metrics on every run, and the check fails on any increase, or on a decrease that was not locked in by updating the baseline in the same change. The refactor that made this possible is documented in the repository in Chinese: a handoff note dated 2026-07-11 records a controller falling from 2,034 lines to under 800 across seven slices, with a single private persisted-state reader deliberately left behind until a client coverage window closes.

5. 05

   A release that is not allowed to publish itself

   The desktop release convention describes three shapes — a stable release that becomes Latest, and -rc.<n> and -beta.<n> prereleases. The twenty most recent releases run from v0.2.6 on 2026-07-30 to v0.2.33 on 2026-09-05: twenty in thirty-seven days, three of them on 2026-07-30 itself. Release candidates and betas promote themselves after staging; a stable release stops as a candidate and needs a separate promotion run plus approval from a desktop-stable-release environment whose required reviewers are three named accounts, self-review allowed. Promotion rechecks the candidate manifest, the checksum file, the locked runtime version for every supported platform and that the public channel does not move backwards, then copies assets to an immutable path, creates the formal tag, writes the channel pointer and changelog and refreshes the stable alias; it never rebuilds installers. Release notes come from a model when a key is configured and from a deterministic commit summary when it is not; operators edit only a marked bilingual review section, which promotion turns into the reviewed summary. Nightly releases, S3 runtime artifacts, Linux artifacts and Microsoft Store prereleases are excluded by design, and on 2026-09-02 a pull request removed the daily scheduled build trigger, describing that as having no documentation impact.

6. 06

   What outside contributors found

   An external pull request cannot merge until a member of the tutti-rd team approves the current head commit, and a new push refreshes it. The findings are specific. One contributor showed that imported sessions were identified by provider session id alone, which collapsed 427 transcript files into 33 sessions: the import wizard rendered 769 rows with 375 distinct identities and 397 duplicate React keys; the fix joins the source path into the hash, leaving one identity rule for every import source. Another found that the locale check discovered modules through a hardcoded list of three names while the convention called those names non-exhaustive examples, so four shipped manifests had silently been excluded from every translation check. A third traced a Cursor answer arriving as one line — 2,662 characters with no newline — to strings.HasPrefix(text, ""), which is always true after trimming, so whitespace-only chunks carrying paragraph breaks were dropped as duplicates. A fourth explained a Gemini CLI failure as the CLI relaunching itself and installing empty SIGINT, SIGTERM and SIGHUP handlers, after which the ACP probe could finish initialisation and still report that the process did not exit. A fifth fixes a click that opened two browser tabs, because two handlers both took the gesture; the fix drops the second activation of the same address inside 80 milliseconds.