Squad is a desktop app that visualizes your codebase as a 3D city. Files become buildings, directories become districts, and AI agents appear as characters flying through the scene as they work. It's built for developers using AI coding assistants like Claude Code or Codex — especially useful when running multiple agents in parallel.

No. Squad sits beside your editor (VS Code, Cursor, etc.) as an observability layer. Click any building to open the file in your editor. It shows you what's happening; your editor is where you make changes.

Spatial layouts build muscle memory — after a few sessions, you'll know where things are without searching. Lenses let you color the city by different metrics: Structure (lines of code), Git Dirty (uncommitted changes), Diff Bands (additions/deletions), File Type, and TODO Debt. Each lens answers a different question about your code. More lenses coming soon.

Squad supports Claude Code and Codex. Both tools write session logs to local JSONL files, and Squad watches these files to extract tool calls, file operations, and token usage. No configuration needed — if you're using these tools normally, Squad automatically detects and tracks their activity.

Not yet. Currently Squad is observation-only. Orchestration controls (pause, resume, assign tasks) are planned for a future release. Even with a single agent, you still get visibility into file changes, git status, and a spatial overview of your codebase.

Yes. Squad is entirely local-first — your code is indexed on your machine and never transmitted anywhere. Squad only reads files; it never modifies your code. There's no automatic telemetry or analytics. If you need support, you can manually export logs, but nothing is sent without your explicit action.

macOS only, Apple Silicon (M1/M2/M3/M4). The app is under 100MB; cache grows with codebase size. RAM usage: ~200-400MB for small projects, up to 1GB+ for large ones during indexing. 16GB RAM recommended for smooth performance. Intel Macs, Windows, and Linux are not currently supported.

Squad handles codebases up to hundreds of thousands of lines — tested with Three.js (~800K LOC). It indexes all text files with special support for TypeScript, JavaScript, Rust, Python, Go, Java, and 15+ other languages. Works with monorepos. Use .squadignore (same syntax as .gitignore) to exclude files.

One-time purchase: $29 (early access).

After purchase, you receive a license key via email. Enter it in Squad's settings — it's stored securely in your macOS Keychain. Device limits depend on your purchase; manage activations from the customer portal. Payments handled by Polar (major credit cards accepted).

Download the DMG from the site, drag Squad to Applications, and launch. You'll authorize a workspace directory (your project root). Indexing takes a few seconds for small projects, 1-3 minutes for large ones. You can add multiple workspaces and switch between them.

WASD to fly, left-click drag to orbit, scroll to zoom. Click any building to select it and view details in the inspector. Use 1-6 to switch lenses, T to toggle agent trails, Escape to deselect. Right-click buildings for quick actions like "Open in Editor" or "Reveal in Finder."

Make sure Claude Code or Codex is running and has created session files. Check that telemetry directories exist: ~/.claude/projects/ for Claude Code, ~/.codex/sessions/ for Codex.

For slow performance: open a subdirectory instead of the full repo, add large directories to .squadignore, or close heavy apps during indexing. Gray buildings mean the file couldn't be read or is binary. Missing buildings may be excluded by ignore patterns. For crashes, check Console.app — try deleting ~/Library/Application Support/squad/ and relaunching.

Planned features: additional lenses (Churn, Complexity, Coverage, Age), LSP integration, agent orchestration controls, and dependency graph visualization. Reach out on Twitter/X to request features.