Omniscio

Agent Missions hub (pick a guided job and an AI does it for you)

Agent Missions is the one chat-first home for Omniscio's guided do-it-for-me missions: pick one and an AI does the whole task in a normal session, driving the app's own tools. It also holds the starter mission and tour agents from first-run setup — the Onboarding Hub folded into it on 2026-10-14. A sidebar entry nested under Prompt Tools, reachable from its row or the Agent Missions toolbar button.

On this page

What it is

The Agent Missions hub (named "Missions" until 2026-10-14) is a permanent, chat-first home for Omniscio's guided "do-it-for-me" missions — pick one and an AI does the whole task for you in a normal chat session, driving Omniscio's built-in tools (CLI endpoints). It is a sidebar integration (__missions__) nested under Prompt Tools, reachable from its sidebar row OR the Agent Missions toolbar button. It is SEPARATE from the onboarding mission surfaces (the empty-state upsell + the old mission picker) that were retired 2026-08-26 behind MISSION_UPSELL_SURFACES_ENABLED = false. Since 2026-10-14 it is also where first-run onboarding puts its agents: the pre-spawned starter mission, the real-agent tour's agents and the setup assistant's "ask Omniscio" sessions. The separate Onboarding Hub was folded in — its existing sessions move here on the next launch and keep their chat history, and its sidebar row is gone. The Training Hub (tutorial videos and docs) stays its own thing. Missions are the same MISSION_REGISTRY entries onboarding pre-spawn already uses; the hub is a new front door to launch them on demand.

Three things called "mission" — say which one

  • Agent Mission (this page) — a guided do-it-for-me job in the Agent Missions hub. Say Agent Missions every time; the hub was named "Missions" until 2026-10-14 and that retired label must not come back.
  • A crew's mission — the outcome at the top of a crew's task tree, above its deliverables. Different thing, documented in Agent Crews; the crew word is qualified by "crew" whenever the two could be confused.
  • Mission Control — the project-management product name; it owns no missions at all. See Mission Control.

Where to find it

UI surface

  • A sidebar row under Prompt Tools (Rocket icon) opens the gallery (MissionsView.tsx) as a PANEL in the main area — the hubs sidebar stays visible. It is the Clean Room shape, NOT panelOwnsLayout: the hub HOSTS the sessions its cards launch, so desktop Pane 2 is the standard SessionsSidebar listing past missions, and mobilePrefersPanel with no sidebarComponent/panelOwnsLayout makes the gallery ride the mobile session list's landing slot (isMobileLandingOverSessions) rather than replacing it. A shouldYieldToSessionChat on displayedSessionInActiveProject hands the pane to the mission chat once one is displayed. panelOwnsLayout: true was correct only while each card launched into the user’s ACTIVE project (the flag literally declares "a project with no sessions at all"); left on after the hub became the spawn target it makes computeOverlayKey return 'missions' unconditionally and the gallery covers the chat the user just started — the Workflows split-view defect.
  • The "Agent Missions" toolbar button (Sparkles) opens the same panel — it is a STATIC toolbar item retargeted to setCurrentView('dashboard') + activateVirtualProject(MISSIONS_PROJECT_ID) (the arij / file-converter idiom). Keeping it static is deliberate: a static TOOLBAR_ITEMS entry SUPPRESSES the derived integration:missions button, which both preserves an existing pinnedToolbarItems entry of 'missions' (no settings migration) and prevents a duplicate second button. For the same reason its active-highlight uses isMissionsActive (computed in App.tsx from activeProjectFolderPath, like isArijActive), NOT activeIntegrationToolbarId — that id never resolves for a suppressed derived button, so the highlight would silently never fire.
  • Start launches the mission as a chat session the user lands in (the existing launchSession(source=missionId) path). launchSession already moves the active project to the launched session and selects it, so the panel needs no navigate-away callback — the view takes NO props. No bespoke per-mission UI — the interface IS the chat.
  • A mission always spawns IN THIS HUB, never in whatever project the user was standing in. __missions__ is in SPAWNABLE_VIRTUAL_PROJECT_SENTINELS with a MANAGED_WORKDIR_SUBDIRS row (<userData>/missions-agent), so the hub hosts the sessions its own cards launch. All three launch sites resolve the __missions__ row: the gallery, the in-session nudge picker (SessionPanel.tsx), and the inbox trickle card's "Run it" (mission-launch-plan.ts). Previously each picked an ambient target — the active project, session.projectId, or "the first spawnable project" — so one mission landed somewhere different every time and guided personal errands opened sessions inside unrelated code repos. If the __missions__ row has not hydrated yet, Start is DISABLED and the inbox plan returns error; neither falls back to another project. Onboarding's first-mission is the one exception — it deliberately runs in the project the user just created in the legacy wizard's ProjectStep (deleted 2026-10-08), which is the point of that step.
  • The gallery lists visibleMissionsForPlatform(settings, envEnabled, platform) — the feature-gated visible set INTERSECTED with the host platform, so a Linux-absent or unreleased mission (e.g. the gated build-chrome-extension) never leaks in. An empty state shows when none apply.
  • Mobile: declared mobile: { status: 'ready' } in the ui-registry — as a sidebar integration it is reachable from the mobile sidebar like its siblings, and the gallery is a simple card list.

How it behaves

The missions

Data-driven from MISSION_REGISTRY. Each mission is promptAsset-backed (a bundled markdown template under resources/missions/<id>/) OR superPromptId-backed (a bundled Super Prompt). The hub launches them immediately (the model runs the prompt on turn 1); onboarding pre-spawn launches a subset deferred (parked on a <first_response> opener) — see onboarding.md.

  • Clean up my email inbox — inbox-concierge (NEW). The guided Gmail cleanup, run as a chat: it checks GET /gmail/status, walks a first-time user through connecting Gmail, then scans with the built-in Email Cleanup engine (GET /gmail/cleanup/analysis) and clears the noise one sender at a time — protecting bank / security / people-you-reply-to first, archiving (never deleting) with an auto-archive filter for "make it stop," everything reversible. Prompt: mission-prompt.md. It is EXCLUDED from onboarding pre-spawn (onboarding-prespawn.ts) — it needs Gmail connected and does its own runtime status-check + scan, so it carries no static opener to park on.
  • Give my projects real icons — project-icon-stylist (NEW). The guided sidebar cleanup, run as a chat: it reads the real project list (GET /projects, which now returns iconPath + iconColor), learns the available vocabulary (GET /project/icon-options), proposes an emoji / Lucide / brand-logo mark per project with an optional colour, and applies only what the user approves (POST /project/:id/icon). Prompt: mission-prompt.md. EXCLUDED from onboarding pre-spawn (onboarding-prespawn.ts) for the same reason as inbox-concierge — it must read live state before it has anything to say, so it carries no static opener to park on, and a brand-new account has no projects to style yet.
  • Find tools that make your work easier — tool-scout (ToolScout). Tell it what you do and it researches the specialized tools, software and services that top performers in your field actually use. Super-Prompt-backed (superPromptId: 'find-the-chainsaw-tool-research'), telemetry feature tool_discovery, all platforms. It is one of the missions onboarding DOES pre-spawn — it is deliberately absent from ONBOARDING_PRESPAWN_EXCLUDED_MISSION_IDS (onboarding-prespawn.ts).
  • Find local events near me — find-local-events. "A quick scan for upcoming events and activities near you — concerts, markets, meetups, and more." Prompt-backed (resources/missions/find-local-events/mission-prompt.md), telemetry feature find_local_events, all platforms.
  • Plus the remaining registry missions: first-mission (Tidy my computer), unclaimed-money-check, ai-workflow-integration-planner, and the gated build-chrome-extension.

The first-run offer card

A brand-new user meets the missions through the Inbox's pinned "Want to start your first mission?" card, deliberately kept to four things: the line "Your first mission", the recommended mission's icon, name and one-sentence blurb, one Start button, and a quiet See other missions link that opens this gallery. Own-account users see four extra words ("Uses your AI account") so a mission is never implied free when their own account pays. Choosing Start creates that mission as a deferred, zero-cost session on the free lane. The offered set is derived in main (onboarding-mission-ask-card.ts), which is also what validates a requested mission id. Unclaimed money is offered only in the United States — the rule applies to this gallery too, so the region comes from main (host-region.ts) and an unknown region counts as not-US; see the onboarding mission-start contract.

The offer is asked once. Archiving the card, pressing its Not now, the inbox auto-dismissing it after a day unanswered, or turning the alert type off all end it for good, and Restore from Recently dismissed brings it back. Only when the app pulls the card itself (the free lane went down, or nothing is left on offer) does it come back on its own, once the lane serves again. The missions stay reachable from this gallery either way.

Email Cleanup panel — retired

The standalone Email Cleanup sidebar panel (__email_cleanup__) was RETIRED in favor of the inbox-concierge mission: its sidebar row is hidden for everyone (the Dashboard visibility filter), and any stale pointer redirects to the Inbox. The /gmail/cleanup/* routes, the cleanup ENGINE, and the in-Gmail ✨ Clean Up button are unchanged — see email-cleanup.md.

See also

  • onboarding.md — the missions registry, onboarding pre-spawn, and the retired onboarding mission surfaces
  • email-cleanup.md — the Gmail cleanup engine (still powering the in-Gmail button + the mission's /gmail/cleanup/* calls)
  • INDEX.md

Last verified 2026-10-14