spacecake: a desktop workspace for Claude Code

What spacecake is for, and who it is actually aimed at

The README describes spacecake as an open-source desktop app for Claude Code that combines an integrated terminal, a visual markdown editor and live task tracking. That sentence is the whole product thesis. The target user is someone who already runs Claude Code, Codex or Gemini CLI from a shell, writes specs and notes in markdown, and keeps a git client open in a third window. spacecake collapses those into one application.

The secondary audience is people who write specs before letting an agent loose. The README points at GitHub Spec Kit as a supported workflow and gives the markdown editor frontmatter, checklists and mermaid diagrams. That is a spec-writing toolchain, not a chat wrapper. If you only ever type prompts into a terminal and never write anything down, most of the editor surface is dead weight for you.

The project is explicitly in public alpha, and the release tags carry the v0.1.0-alpha prefix. That is not marketing hedging: it is the maintainers telling you the shape of the thing can still change between releases.

How the terminal, editor and agent session connect

The mechanism visible in the README is a desktop application with dockable panels. The terminal is Ghostty embedded, not a reimplementation. Panels for the terminal, git and tasks can be docked left, right or bottom, which means the layout is a set of independent views over the same workspace rather than a fixed split.

The Claude Code integration is where the design gets specific. The app tells Claude which file and line you are currently editing, so context follows your cursor instead of you pasting paths. Plan mode is enabled by default when Claude Code runs inside the spacecake terminal. A status line is auto-configured on first launch and reports model, context percentage and cost. A plans panel on ctrl+G lists and manages plans, and Claude can open files directly in the editor and wait for you to save and close before continuing.

That last behaviour is the interesting one. It inverts the usual flow: instead of the agent writing files and you reviewing afterwards, the agent hands control back and blocks. Whether that is pleasant depends on how often you want to be interrupted. The README presents it as a feature without discussing the waiting cost.

Underneath, the editor is CodeMirror, which supplies syntax highlighting, autocompletion, bracket closing, code folding and linting. Workspace search is ripgrep-powered. The repository is a monorepo with spacecake-app/ for the desktop app, website/ for the landing page and docs, and cli/ for a command-line tool.

Installing spacecake and opening a first workspace

There is no package manager install. The README directs you to the latest release on GitHub and asks you to download an installer for your platform. macOS gets a .dmg with separate arm64 and x64 builds, plus a .zip for manual installation. Windows gets an .exe installer. Linux gets a .deb for Debian-based distributions or an .AppImage for everything else.

On Linux and Windows the README recommends installing watchman for best file watching performance, and says spacecake shows a tip in the status bar recommending it. That is a real dependency in practice, not a footnote.

On first launch the app opens the home folder at ~/.spacecake for general notes. To point it at real code, open a project as a workspace:

# macOS
# press Cmd+O in the running app

# Windows / Linux
# press ctrl+O in the running app

The README does not give a shell command for this step, only the keyboard shortcut. Once a workspace is open, the documented shortcuts are Cmd+P for quick open, Cmd+F for find in file, Cmd+Shift+F for workspace-wide ripgrep search, and ctrl+backtick to toggle the terminal. Opening a terminal tab is Cmd+T and cycling tabs is ctrl+Tab.

If you want to build it yourself rather than download a binary, the README defers to CONTRIBUTING.md for prerequisites and setup, so the exact build commands are not in the README itself.

Where spacecake is the wrong tool

The clearest limitation is the release channel. The newest release listed is v0.1.0-alpha.71, and the README states the app is in public alpha and asks you to file issues or join Discord when you find bugs. An alpha desktop app that watches your filesystem, runs git operations and embeds a terminal is a different risk category from an alpha library. It has your repository open and it can commit, stash, push and resolve merge conflicts.

Watchman is the second constraint. The README frames it as a performance recommendation for Linux and Windows, but file watching sits underneath autosave, the git changes panel and workspace search. If your environment cannot install watchman, the app still runs, but you are on the slower path the maintainers chose to warn about in the status bar.

The third case is the one the README never addresses: teams. There is no documented configuration file format, no way to check a shared workspace setup into a repository, and no mention of settings sync. Every developer configures their own app. If your team needs identical editor settings across machines, nothing here suggests that is possible yet.

Finally, the agent integration is Claude Code first. Codex and Gemini CLI are listed as things you can run in the terminal, but context awareness, plan mode, the status line and the plans panel are described as Claude Code features. Running a different agent means you get a terminal and an editor, not the integration.

How spacecake differs from running Claude Code in your existing editor

The obvious alternative is the official Claude Code extension for VS Code, or running Claude Code in a plain terminal next to whatever editor you already use. The difference in approach is structural rather than cosmetic.

In the extension model, the agent is a panel inside an editor that was designed for human editing, and the terminal is a terminal. In spacecake, the terminal is the primary surface and the editor is built around it. Ghostty is embedded rather than simulated, panels dock around it, and the agent session owns the plans panel and the task list. The README's task panel reads live Claude Code tasks from the active session with status filters and sortable columns. That is a view an editor extension does not have because the editor is the host, not the agent.

The other alternative is staying in the terminal entirely and using tmux plus a separate markdown editor and a separate git client. That works and it is stable. What you give up is the context handoff, where Claude knows the file and line you are on without being told, and the open-file-and-wait behaviour. Whether that handoff is worth an alpha dependency is the actual decision, and it depends on how much time you currently spend telling your agent which file you mean.

Licence, maintenance and the cost of upgrading

spacecake is licensed AGPL-3.0. For an individual running the desktop app, that is the same as any other open-source licence in daily use. The copyleft obligations attach when you distribute modified versions or offer the software over a network, which is why AGPL matters to anyone considering embedding spacecake or its cli/ directory into a hosted product. That is a description of the licence terms, not legal advice; if you plan to redistribute, read the LICENSE file in the repository root.

The maintenance signal is mixed and worth stating plainly. The repository is not archived, and the last push was on 2026-05-06. The most recent release listed is v0.1.0-alpha.71 from 2026-04-18, and before that v0.1.0-alpha.70 on 2026-04-11 and v0.1.0-alpha.69 on 2026-04-10. Those three tags span eight days, which suggests bursts of release activity rather than a steady cadence. The README does not explain the gap between the newest release tag and the last push.

Upgrade cost is the alpha tax. There is no documented migration path between alpha releases, no settings schema described in the README, and no statement about backwards compatibility. Expect to re-check your workspace layout and your Claude Code status line configuration after an upgrade, and expect the changelog at spacecake-app/CHANGELOG.md to be the only record of what moved.

Editorial conclusion

Adopt spacecake if you already run Claude Code from a terminal all day and want the editor, git panel and task list in the same window as the agent session. Do not adopt it if you need a stable, versioned tool for a team, or if you work on a Linux or Windows machine where file watching performance matters and you cannot install watchman. Before installing, verify that a build exists for your platform on the releases page, that your Claude Code version behaves with the auto-configured status line, and that you are comfortable running alpha software against your working repositories.

Frequently asked questions

Official sources

1. License: AGPL-3.0
2. Project website
3. README
4. Releases
5. spacecake-labs/spacecake on GitHub