Orbit Code documentation
How to use Orbit Code, how it runs Claude Code, and how the engine behind it works.
New here?
Install Orbit Code, then learn to read the view.
Get started
- Using Orbit
Reading the view, navigating, prompting Claude, answering permissions, the file card, the Flat view and the tour.
Editors and apps
- VS Code extension
An open-source, live 3D visual alternative to Claude Code in the terminal, for programmers and vibe coders alike: your codebase as a dependency graph in…
- Desktop app
Orbit Code as a desktop app: an open-source, live 3D visual alternative to Claude Code in the terminal, for programmers and vibe coders alike, in a window…
- Settings and commands
Every command and setting the VS Code extension adds, read from its manifest (version 0.2.1). The desktop app reads the same settings from its own…
- Indexer CLI
Indexes a workspace into the dependency graph Orbit Code draws: files are nodes, imports are edges, and directories group them.
Guides
- Claude in Orbit
How the `claude` CLI is run, conversations, permissions, questions, MCP, skills, files, history and subagents.
- Troubleshooting
Logs, caches, and the failures with a known cause.
How it works
- Architecture
The three bundles, the services, and how a graph, a layout and a Claude turn flow between them.
- The graph pipeline
Indexing, language coverage, the graph hash, live updates and the layout.
- The webview
The three.js scene, focus and levels, GPU picking, the frame loop, colours, the HUD, and the constraints it is built under.
- Hosts
What VS Code and the desktop app each provide, and what a third editor would have to.
- The monorepo
Projects, tags, boundaries, TypeScript per runtime, Nx targets and caching.
- Contributing
The dev loop, where a change goes, the checks, CI and the commit conventions.
- Releasing
Version plans, release groups, tags, and publishing to the Marketplace, Open VSX, GitHub releases and npm.