Orbital

https://github.com/user-attachments/assets/5f1373bc-2c3e-440b-af52-77ecbd80c27f

Why a project agent?

Is your context actually yours?

You're three rounds into a design discussion with Claude Code when it stops with "You're out of usage credits." Your Codex quota is sitting right there, but Codex knows nothing about this project: the goal, the two decisions you just made, the half-edited files. You'd have to explain all of it again.

It isn't only usage limits. People already use several capable agents at work: for the newest model, the leftover quota, or because a particular tool is better at the job. But the plan you settled with Claude Code, the file Codex left half-edited, the trade-off you decided in Cursor: each one is locked inside its own session. Close the session or switch tools, and that context is out of reach.

So you carry the project between them: restating goals, explaining previous decisions, locating artifacts, and checking what was left unfinished.

You are the agent's intern: copying and pasting, ferrying context, remembering where all the odd files live, while the agent gets the thinking.

Orbital takes the context out of the session and puts it back in your local folder, and changes the unit of work from the session to the project.

A project agent stays responsible for the project across tasks, sessions, and worker agents. It maintains the shared context, decides what needs to happen next, delegates when useful, and records every outcome back into the project.

Individual agents complete tasks. Orbital keeps the project moving.

What it means to own the project

Orbital maintains five things that normally disappear or fragment between agent sessions — all of them as plain files in your project folder:

• State — what is true about the project now (PROJECT_STATE.md)
• Decisions — what was decided and why (DECISIONS.md)
• Lessons — what the project has learned (LESSONS.md)
• Work — what is running, completed, or blocked (queue.json). Every queued task ends Completed or Blocked — an agent that stops without a verdict gets re-prompted, then force-blocked with a reason. Nothing drifts away silently.
• Artifacts — what the agents researched, wrote, or built (the workspace itself, plus orbital/output/)

These stay in the local project and become context for future work. On a cold start, Orbital assembles them into its own system prompt before it acts.

When Orbital delegates, the worker is pointed at those same files and told they are authoritative — that briefing is rendered fresh on every dispatch, not something you paste in. Each worker also keeps its own memory file inside the project, so it accumulates its own experience across dispatches. When the task finishes, Orbital reads the result and records what matters back into the project.

The worker can change. The project continues.

Quick Start

Want the step-by-step version with screenshots? See the Orbital user guide: API keys, projects, switching agents, the task queue, automations and project settings.

1. Launch Orbital — the setup wizard guides you through two steps:

   Step 1 — LLM Provider: In mainland China, tap Sign in with TokenDance, authorize, and start on free tokens. Otherwise pick a provider from the preset cards, follow the key-console link to grab an API key, and paste it in. Supports DeepSeek, Anthropic, OpenAI, Moonshot, and a dozen other providers.

   Step 2 — Connect Your Accounts: Link API connectors (Google Calendar, Drive) and sign in to sites your agents will need (Google, GitHub, etc.) so they can browse without getting blocked by CAPTCHAs. Everything here is optional and can be done later in Settings.

2. Create a project — give it a name, pick a workspace directory, set an autonomy level

3. Chat — type a task in the chat bar and the project agent handles it
4. Walk away — queue the next tasks; each finished one becomes context the next builds on

See the project stay under one manager

How Orbital compares

Memory, scheduling, and sub-agents are table stakes now — every tool below has them. These are the three questions where the answers still differ.

The short version: the difference isn't any one capability — it's that the project, not the session, is the unit that owns state, workers, and governance.

Feature Deep Dives