Orbit Chat, the Planner
Orbit Chat is the planning surface. It is a full conversation panel in the main dashboard that talks to any provider you’ve configured — Anthropic, Google, OpenAI, or a local model — and it is the counterpart to Apollo: Chat is where you decide what to build; Apollo is where you run it.
Multi-provider, one conversation
Section titled “Multi-provider, one conversation”Chat keeps a single conversation history while letting you switch models mid-thread. Start a plan on a fast, cheap model and escalate to a stronger one for the hard part without losing the thread. Every message shows its cost, and the whole conversation is injected with the active project’s context so the model is reasoning about your code, not a generic stand-in.
From thinking to docs
Section titled “From thinking to docs”Any message in a Chat conversation can be saved straight to your project’s docs with “Save to Docs,” so a good plan or explanation becomes a durable context file instead of scrolling out of history. This is the natural bridge between a planning conversation and the context that future sessions — and future prompts — will read.
When to use Chat vs. Apollo
Section titled “When to use Chat vs. Apollo”Reach for Orbit Chat when you’re still figuring out what to do: weighing approaches, drafting a spec, thinking through a design. Reach for Apollo when you know what you want and need it done: queue this prompt, generate that icon, read that file, check what shipped. They share your project context, so moving between them doesn’t cost you continuity.