Collaborator: an infinite canvas for terminals, files and coding agents

What problem Collaborator is trying to solve

Agentic coding splits attention. One window holds the agent's terminal, another holds the file it keeps editing, a third holds the notes you wrote about what it should do next. Collaborator's answer is spatial: put all of it on one surface and stop switching. The README describes the app as "an end-to-end environment for agentic development", and the repository topics (agents, ai, claude-code, codex-cli, ide, terminal) point at the same audience: people who drive agents from a shell rather than from an autocomplete box. The target user is one person on one machine. The README states the app operates primarily on local files with no accounts required, and that all application state lives as JSON files in ~/.collaborator/. There is no server component described, no team workspace, no shared session. That narrowness is the design, not an accident.

The canvas, the navigator and how tiles stay bound to disk

The window has two regions. The navigator is a resizable left sidebar with a file tree and a workspace switcher. The main area is the canvas, an infinite pan-and-zoom surface with a dot grid, and it also hosts the viewer, which renders whichever file is selected in the navigator. Tiles are the unit of arrangement: each has a title bar for dragging, eight resize handles, and a z-index so clicking brings a tile forward. The important detail is that tiles are live views rather than containers. A file tile is bound to a file on disk by absolute path, so renaming the file makes the tile follow the new path, deleting it closes the tile, and editing it on disk reloads the tile. Terminal tiles bind to a persistent PTY session backed by a node-pty sidecar. The README says each terminal tile creates and manages its own session, which persists independently of the tile's lifecycle on the canvas. In practice that means closing a terminal tile does not necessarily end the process behind it, and the README does not document how to reach an orphaned session again. That is a gap worth knowing about before you rely on it.

Installing Collaborator and opening a first workspace

The README points at the releases page for macOS, Windows and Linux builds. Windows users take the .exe installer. macOS and Linux also get a command-line path, which the README gives as a curl pipe into bash:

curl -fsSL https://raw.githubusercontent.com/collaborator-ai/collab-public/main/install.sh | bash

That is the whole install step for those two platforms. The script lives at the repository root as install.sh, so you can read it before piping it into a shell. If you prefer not to run it, the releases page carries the same builds as direct downloads. Nothing in the README describes a package manager formula, a Homebrew tap, or an apt repository, so expect to update by downloading a new build rather than by running an upgrade command.

A first real use: one workspace, one terminal, one file tile

The quickstart in the README is four steps and assumes nothing beyond a local folder. Open the app, add a workspace through the dropdown in the navigator or with Cmd+Shift+O, double-click empty canvas space to create a terminal, then drag files from the navigator onto the canvas to open them as tiles. The terminal's working directory is set to the active workspace path, so an agent started there sees the project without a cd. There is no config file to write and no command to memorize beyond the shortcut. The screenshot in the repository root, screenshot.png, is the only visual reference the README offers, so expect to learn the layout by clicking rather than by reading.

Where Collaborator gets in the way

Three constraints stand out. Zoom is capped at 100%, with a rubber-band effect past the limits and a percentage indicator that appears briefly in the bottom-right corner; anyone used to zooming far out to survey a large board will find the ceiling low. Tile positions and sizes snap to the grid, so you cannot place things arbitrarily. Scroll events go to tiles, and the README notes that holding Shift while scrolling passes them through to the canvas, a modifier you will either internalize or keep rediscovering. The larger issue is maturity. The README says the app is early-stage and in active development, and the newest release listed is Collaborator 0.8.4 from 2026-06-16, with 0.8.2 and 0.8.1 before it in June 2026. The repository's last push was on 2026-08-08. The README does not document rollback, migration between versions, or what happens to ~/.collaborator/ JSON state when you downgrade. If your workflow depends on a stable file format for that state, that silence matters.

How Collaborator differs from a tiling terminal or a plain editor

The obvious comparison is a tiling terminal multiplexer such as tmux or a tiling window manager. Those give you panes and persistence, and they are scriptable, but they have no notion of a file tile bound to a path, no viewer, and no markdown or image rendering. Collaborator trades that composability for a graphical arrangement you manipulate with a mouse. The other comparison is an editor with an integrated terminal, which keeps files and shell in one window but stacks them in tabs and splits rather than placing them freely in two dimensions. Collaborator's canvas is the differentiator: a terminal, the file the agent is editing, and a note about the next step can sit next to each other at chosen sizes. What you give up is text-only control. There is no documented CLI for creating tiles, and the README describes the app as single-window, so anything you want to automate around it stays outside the app.

Licence, maintenance and what an upgrade costs you

The repository carries LICENSE.md and NOTICE.md, and the licence identifier is reported as NOASSERTION, which means the licence could not be classified automatically. Read LICENSE.md and NOTICE.md yourself before you depend on the code or redistribute a build; this is a description of the files present, not legal advice. The stack is Electron 40, React 19, Tailwind CSS 4, xterm.js, Monaco Editor, BlockNote/TipTap, D3, sharp and KaTeX, with electron-vite as the build tool, and the source lives under collab-electron/. Upgrading means installing a new desktop build; the README does not describe an auto-update channel or a data migration step, so the practical cost of an upgrade is the risk to whatever sits in ~/.collaborator/. The app also collects anonymous, non-identifying usage analytics via PostHog, which the README states plainly. If that is unacceptable in your environment, this is not the tool for you, and no setting to disable it is documented in the README.

Editorial conclusion

Adopt Collaborator if you already run agents in a terminal and want their sessions, context files and diffs visible at once instead of buried in tabs; the local-only storage in ~/.collaborator/ and the anonymous PostHog analytics are both documented, so decide whether that trade suits you. Skip it if you need a stable, versioned tool for a team, since the README calls the app early-stage and the newest release it lists is 0.8.4 from 2026-06-16. Before committing, verify two things yourself: that the install.sh URL resolves, and that the release page actually carries a build for your platform.

Frequently asked questions

Official sources

1. collabs-inc/collab-public on GitHub
2. Issues
3. Project website
4. README
5. Releases