SiloWorkspaces
Each project a click away
Switch with a keystroke. Terminals keep running, agents keep working, layout stays put — nothing reloads.
Close a workspace and come back weeks later; everything is still in its place.
FOR DEVELOPERS JUGGLING CODING AGENTS
One window —
every project, every agent
Terminals, agents, and layout stay intact — switch between them instantly. 100% open source, free forever.
Runs the agents you already use.
Claude, Cursor, Codex, Copilot, Grok, and anything else that talks to a terminal.
Git
Worktrees without leaving the workspace
Create a worktree on a branch, open it alongside your main folder, remove it when you're done — the branch stays. Stage, commit, and manage worktrees from the same Git panel.
Terminals
Agents and terminals come first
Most editors are file-first — the terminal is a drawer, the agent a side panel. Silo flips it: coding agents and terminals are the main surface; the editor shares the stage when you need it.
Extensions
Build the tool this project needs
Notice a friction, ask Claude to scaffold an extension, use it minutes later. Same public SDK the first-party features use — optional, uninstallable, shareable via the registry.
100% open source. Free forever.
MIT licensed. No account. No telemetry. Nothing to lose by trying it.
Common questions
Is Silo really free?
Yes. MIT licensed, free forever — no subscription, no trial, no enterprise tier. Fork it, read the source, build on it.
Do I need an account?
No. Download it and run. Everything stays on your machine — no cloud sync, no sign-in, no telemetry.
How is this different from VS Code or Cursor?
Those are file-first editors built around one active workspace. Silo is built around many workspaces that stay alive at once — terminals, agents, and layout intact when you switch. You don't rebuild context every time you change projects.
How is this different from agent orchestrators?
Orchestrators organize agent tasks (often one worktree per task). Silo organizes your whole project — agents, terminals, editors, panels — as a workspace you can switch, close, and resurrect. Worktrees are git tooling inside that model, not the unit of work.
Is the editor as good as Zed or VS Code?
Not yet — and that's intentional honesty. The workspace layer is the point today. Editor and terminal keep improving in the open; you pick Silo so you never rebuild context, not for the best single-buffer editing.