Skip to content

Away missions

An away mission is a job the AI works through on its own, in the background: "find three robot vacuums under $300, compare them and add the best one to my shopping list". It plans the steps, uses one tool at a time, reads each answer before the next step, and writes a report from only what the tools gave it (what it couldn't find, it says). Every step shows in Ops → Away missions as it goes, with its sources.

Starting one

  • Ask for a job with a few steps and the AI offers to run it as a mission; say yes.
  • Or start it outright: "away mission: check the weather and my shopping list", "run that as an away mission".
  • Scripts are missions too: "write me a PowerShell script that backs up my Documents". The Code model writes it, and it's saved to your Files. (A one-liner, a function or a regex is answered right in the conversation.)
  • Quick lookups (the weather, a search, reading a link) are answered at once and kept in Ops as Looked up.
  • AI Assist on a task or project row.

Missions never start from a private conversation, and never use your mail.

The plan, approved once

Before it does anything, the AI plans the mission: each step, the tool, and whether it changes something.

  • A mission that only looks starts at once.
  • One that changes something (adding to a list, turning something on, a command on a PC) shows you the whole plan, in the conversation and in Ops, and waits in Waiting on you for your OK and PIN. That covers its planned changes for the whole mission.
  • A change it didn't plan, or a serious one, stops and asks again. Say no and it carries on without it. No answer in 24 hours: the mission is dropped, with what it found by then.

Repeating jobs: schedules

"Every weekday at 7, check the weather and my shopping list." The AI offers a schedule, saying when, before anything is saved. Schedules run every day, every weekday, every weekend day or on a day of the week, in your own time zone. A schedule is planned and approved once when it's set up, and every run carries that approval. In Ops: Run now, Pause, Delete.

The AI goes away

A mission can run on a bigger thinking model (Engineering → Neural Net → the Deep job). If that model can't share the graphics card with the AI's own, the AI tells you it's heading out. While it's away, a bar shows it on every page, and the ship's computer answers anyone who talks to it, plainly: it's away and will answer when it's back. Timers, lists and a waiting OK still work, and what you said is kept for when it's back.

Recall (or "recall Celestra") brings it back early: the mission pauses after the step it's on, and Resume in Ops (or "carry on with the mission") sends it back out. With room on the card for both models, it never has to go away.

When it's done

The AI tells you in the conversation the mission came from, in its own voice, with what it found, and the bell has a notification. Each mission's report is checked against everything the tools said: names or numbers that aren't there are rewritten once, and anything still not there is listed for you to double-check.

Whose missions

A mission runs as the person who sent it: only the tools they could use themselves, with their own safe search. Each person's missions are their own. The Captain can look at everyone's (Mine / Everyone), never change them. One mission runs at a time, behind anyone who's talking.