Mode map

ModeBest forContract
CometTiny, obvious, easy-to-undo workThe detected Sol, Luna, or Astra primary works directly at its observed effort and performs one self-review.
Orbit (default)Normal changes and projectsThe primary plans, a bounded Astra, Luna, or Sol lane implements, and a fresh Sol reviewer checks the result.
Event HorizonCredentials, payments, private data, production, migrations, or major changesA compact dependency graph, necessary confirmation gates, targeted checks, and one concise workspace-write review-and-repair pass.
Singularity (explicit opt-in)Meaningful low- or medium-risk work larger than CometOne verified Sol, Luna, or Astra primary completes one compact card at its observed effort, with no subagents or fresh reviewer.
Pulsar (explicit opt-in)A deliberately evidence-oriented requestThe primary freezes one canonical graph and may fan out ready independent items before one integrated review.
Morph (explicit opt-in)A bounded card needing a user-selected routed or native modelThe detected session remains primary; the chosen worker route is proven, and a fresh Sol review remains required.
Constellation (explicit opt-in)Several independent ready cardsThe primary proves ownership and capacity, launches cost-aware waves, integrates, and requests a fresh Sol review.
Hypernova (explicit opt-in)Maximum native throughputThe detected primary launches Sol Max workers by default or configured Astra workers and requires fresh review.

Astral raises safeguards when a request is riskier than the selected mode. It does not broaden the work you asked for. Orbit remains the default; Singularity, Pulsar, Morph, Constellation, and Hypernova are never automatic.

Singularity and Hypernova are opposites

Singularity

One verified Sol, Luna, or Astra primary, one compact card, targeted context, no subagents, no fresh reviewer, and one proportional self-review.

Hypernova

An observed Sol, Luna, or Astra primary uses as many safe native child lanes as capacity permits, followed by mandatory fresh review. Sol Max is the default child route; Astra uses its configured effort.

Neither mode replaces the current primary or changes its effort. Hypernova child routes remain exact and independently verified.

Hypernova: the exact performance-first contract

Hypernova is an explicit opt-in and the opposite of Singularity. It keeps the observed Sol, Luna, or Astra primary at its current effort. Every implementation lane uses exact gpt-6-sol Max by default or gpt-6-astra at the configured Astra effort.

It uses the maximum safely available concurrency from observed host-advertised capacity. The primary consumes one slot; each child has non-overlapping ownership, a unique lowercase task name, and fork_turns: "none". Wave size is the smaller of ready independent cards and observed available slots after that primary slot, and capacity is recalculated between waves. Workers cannot delegate or invent new work.

After integration, a mandatory fresh built-in-default reviewer uses the same selected Sol Max or configured Astra route. Hypernova is native MultiAgentsV2 only. It has no legacy exact-process fallback, no process or portable route, no serial fallback for missing capacity or route proof, no self-review fallback, and no model or effort downgrade. A mismatched lane is discarded. Dependent or safety-sensitive cards can still be sequenced serially inside the exact native route; that sequencing is not a substitute route.

Choose Hypernova for speed and throughput over token efficiency. High-risk cards inherit Event Horizon confirmation gates. “Go nuts” does not bypass safety or authorization, does not expand scope, and does not approve publishing, deployment, credential use, or destructive work.

Legacy prompt migration

The former names remain advisory prompt aliases: Quick maps to Comet; Guided maps to Orbit; Careful maps to Event Horizon; and Measured maps to Pulsar. A legacy alias never changes the corresponding route or safeguards. New prompts and documentation use the cosmic names.

Copy-ready mode starters

  • Comet: Use Astral Orchestrator in Comet mode to correct this one typo and run the relevant check.
  • Orbit: Use Astral Orchestrator in Orbit mode to add a search box, update its tests, and report the checks.
  • Event Horizon: Use Astral Orchestrator in Event Horizon mode to rotate the staging credential reference; show the plan and wait for confirmation.
  • Singularity: Use Astral Orchestrator in Singularity mode to complete this eligible cleanup in the current verified primary session.
  • Pulsar: Use Astral Orchestrator in Pulsar mode to freeze one card and acceptance checks, then record observed route evidence.
  • Morph: Use Astral Orchestrator in Morph mode for this bounded card using the worker model and effort I specify, then have Sol review it.
  • Constellation: Use Astral Orchestrator in Constellation mode for these independent cards only when ownership and capacity are proven.
  • Hypernova: Use Astral in Hypernova mode with the detected primary, configured workers, mandatory status, and exact-route checks.