How it works

One Mission, end to end.

Undernap has one flow, and it is always the same. That is deliberate: a workspace whose flow you know is a workspace whose result you can judge.

The flow

Five steps — three of them yours

  1. You Give the request You describe the outcome, not the route.
  2. You Approve the plan You see the plan before anything starts.
  3. Undernap Let it execute Specialists work over your Fleet.
  4. Undernap Let it be checked Only the check decides what “done” means.
  5. You Receive the result You close it, not the system.

You describe the outcome, not the route.

You decide
The flow

Step by step

Scroll through a Mission: on the left what happens at each step — on the right what you see in the app meanwhile.

  1. Give the request

    You describe the outcome, not the route.

    You write, in your own words, what should exist at the end — and which limits apply: read-only, nothing deleted, which project, which budget. Up to here, nothing happens outside your machine.

    Step 1 as a design preview of Undernap’s dark interface: the request field with a note that everything stays local and no provider has been contacted yet.
    Step 1 — the request. Everything stays local until you approve. Design preview · Dark mode
  2. Approve the plan

    You see the plan before anything starts.

    Undernap breaks the request into tasks, proposes roles, names success criteria and shows the limits. You can change tasks, drop them, or discard the whole plan. Only your approval starts execution.

    Step 2 as a design preview of Undernap’s dark interface: plan review with an editable task list and the note “Sie behalten die Kontrolle” (you stay in control).
    Step 2 — the plan as a task list. Editable, discardable, and inert without your approval. Design preview · Dark mode
  3. Let it execute

    Specialists work over your Fleet.

    Each task is staffed from your connected AI accounts and runs in a bounded session. Every session leaves structured evidence: what was read, changed and checked. Tasks without dependencies can run in parallel.

    Step 3 as a design preview of Undernap’s dark interface: the Task Wall with the running mission, its progress and the executing connection.
    Step 3 — execution. Which task is running, over which connection, what is waiting. Design preview · Dark mode
  4. Let it be checked

    Only the check decides what “done” means.

    Verification holds the claims against the evidence and the request against the result. Then an independent review checks against the goal — by an instance that did not execute and never runs on the account that did the work.

    Step 4 as a design preview of Undernap’s dark interface: the independent review’s PASS verdict above the result.
    Step 4 — the check. Only the independent review turns “done” into a finding. Design preview · Dark mode
  5. Receive the result

    You close it, not the system.

    You see the result, the evidence behind it and the open points. Your acceptance closes the delivery — consciously, not automatically.

    Step 5 as a design preview of Undernap’s dark interface: the result with its file- and line-level evidence.
    Step 5 — the result. Binding, with the evidence it stands on. Design preview · Dark mode
Step 1 as a design preview of Undernap’s dark interface: the request field with a note that everything stays local and no provider has been contacted yet.
Step 1 — the request. Everything stays local until you approve. Design preview · Dark mode
Step 2 as a design preview of Undernap’s dark interface: plan review with an editable task list and the note “Sie behalten die Kontrolle” (you stay in control).
Step 2 — the plan as a task list. Editable, discardable, and inert without your approval. Design preview · Dark mode
Step 3 as a design preview of Undernap’s dark interface: the Task Wall with the running mission, its progress and the executing connection.
Step 3 — execution. Which task is running, over which connection, what is waiting. Design preview · Dark mode
Step 4 as a design preview of Undernap’s dark interface: the independent review’s PASS verdict above the result.
Step 4 — the check. Only the independent review turns “done” into a finding. Design preview · Dark mode
Step 5 as a design preview of Undernap’s dark interface: the result with its file- and line-level evidence.
Step 5 — the result. Binding, with the evidence it stands on. Design preview · Dark mode
The limits

What cannot happen while it runs

Limits are not an afterthought — they are part of the plan you approve.

Your request Analyse our three main competitors and show me where we stand out. Read onlyNothing deletedWith a budget limitOnly your accounts
Waiting for your approval
Progress Nothing started yet — no AI was asked.
  • Nothing runs before approvalWithout an approved plan there is no execution and no provider contact.
  • No account you did not connectThe Fleet is exactly what you set up. Nothing gets added to it.
  • No quiet spendingPaid execution needs a limit and your agreement — not merely an opportunity.
  • No project hopping in the backgroundMissions, tasks and results are scoped to one project. A result from project A does not surface in project B.

And when something gets stuck?

That is part of the flow too, and it is not hidden.

A judgement call comes back

Where a decision is yours, the mission waits visibly for you instead of guessing.

An account hits its limit

Undernap waits or re-staffs within your rules. Your providers’ limits are respected, never circumvented.

The review says no

Then the mission is not done. An unconfirmed outcome does not become the Result — it is shown as what it is.

The most interesting part is the end

How work turns into a dependable result is on the Result chain page.

Undernap for macOS (Apple Silicon, macOS 15+) is planned to relaunch on November 20, 2026. From then on it is a monthly subscription, for businesses only; your first subscription starts with a free 14-day trial. Until the relaunch we take no orders and offer no download.