JARVIS UltraManualv1.31

Concepts

Missions and approvals

JARVIS Ultra's core loop is simple: you give a goal, the team plans and does the work, and nothing leaves in your name until you say so.

YOUTHE TEAMSTATUSWrite a goalWork › Missions › Launch missionApprove the planor replan, or cancelOutbound draftswait for your OKReview the resultaccept or send backOrchestrator plansthe steps and who does eachSpecialists work the steps123each hands its result to the nextPublished in Docsthe finished documentlaunchplan readyapprovedall steps doneacceptedreplansend backdraftsPlanningAwaiting approvalRunningIn reviewDelivered
A mission passes back and forth between you and the team. Solid arrows move it forward, and dashed ones send it back a stage. The status on the right is what the mission card shows at each stage.

A mission's life

Status What is happening
Planning The Orchestrator is writing the plan, in one turn
Awaiting approval The plan waits for you on Home and on the mission's card
Running Each step runs once every step it waits for is done. The agent gets the results of the earlier steps, and each handoff is recorded.
In review Every step is done; the result is in Docs as In review and waits for you
Delivered You accepted it (or review was off) and the result is Published in Docs
Stopped You stopped or cancelled it
Failed Something went wrong; the card says what. Replan starts again.

Each step is done by one agent. The time limit is checked between steps, so a step that has started always finishes. If the server restarts while a mission is planning or running, the mission becomes Failed: nothing runs unseen after a restart.

What needs your approval

Several things wait in the Decision queue on Home:

  • Mission plans and results, as above.
  • Drafts an agent wants to send: email drafts, social posts, calendar changes. Every agent has a skill that tells it to file anything outbound for your approval instead of sending it.
  • Tool calls the tools lock stopped: a change to a connected app or MCP server that needs your approval first (The tools lock).
  • Automation results from rules set to Approval Inbox.
  • Sign-ins: an app or MCP server that needs you to sign in.

Each one is a card with three answers. Approve and the agent carries it out exactly as approved, within 15 minutes. Send back and the agent writes a new draft from your note. Reject and nothing happens. The outcome, with any link the app gave back, is kept in Decision history.

A request is claimed the moment you answer it. If you answer the same card in two windows, the second is told it was already decided, so nothing is ever carried out twice.

Where requests show up

A request appears in the queue on Home, in the conversation it came from (pinned above the message box), in the top bar's Needs you count, and as an alert on your phone or in Telegram if you set them up (Get alerts). Answering in any of these places clears all of them.

One requesta plan, draft, tool callor sign-inHome · Decision queuea card with three answersThe conversationpinned above the message boxNeeds youthe count in the top barPhone or Telegramif you set up alertsAnswer in any one place and all four clear.
The same request waits in four places. The first answer claims it, so a second window is told it was already decided.

See Run a mission and Decide what the team asks for the steps.