Silo

Appearance

SiloTerminal-first workspace manager

Switch between your projects like browser tabs — except each tab is a full workspace with live terminals, running agents, and preserved layout.

Download for macOS →
View on GitHub
🗂️

Workspace tabs

Each project gets its own persistent tab. Switch instantly — terminals, layout, and editor state all stay exactly as you left them. Nothing reloads.

⚡

Live backgrounds

Terminals keep running and agents keep working when you switch away. Come back and everything is exactly where you left it.

>_

Terminal-first

Shells and AI coding agents are the primary surface. File editing is secondary — the inverse of VS Code's model.

🔒

Local-first

Everything runs on your machine. No cloud sync, no telemetry, no account required.

🧩

Extension SDK

A small stable core with a public API. First-party features — terminal, editor, git, themes — ship as extensions against the same SDK you get.

📄

MIT licensed

100% open source. Build on it, fork it, contribute to it.

Switching between three live workspaces in Silo

Built for the multi-agent era ​

VS Code and Cursor are file-first editors built around a single active workspace. That made sense when you were writing the code.

Now you're coordinating multiple AI coding agents simultaneously across different projects. Every time you switch context in a traditional editor, you lose your terminal state. Your agents get interrupted. You spend more time rebuilding context than doing actual work.

Silo is built around the opposite model. Open as many project workspaces as you need and tab between them instantly. Each workspace keeps its terminals running, its layout intact, and its agents working — exactly as you left it.

Download ​

macOS (v0.4.0) — Windows and Linux coming soon.

BuildLink
Apple Silicon (M1/M2/M3)Silo_0.4.0_aarch64.dmg
Intel MacSilo_0.4.0_x64.dmg

Or build from source — see the GitHub repo.

Building extensions ​

Silo has a public extension SDK (@silo-code/sdk), modeled on VS Code and Obsidian. Every first-party feature — terminal, file explorer, git, themes — is built as an extension against the same API you get. If a built-in can do it, so can you.