Skip to content
Describes how WilsonOS is designed to work.What works today →

A day with your agents

The other examples each follow one workflow. This one follows a day, because that is how the work actually arrives: several workflows in flight at once, some waiting on you, some running on a schedule, and most of them needing nothing at all. The items in it are the ones from the other example pages.

Goal

Start the day knowing exactly what needs you, spend your time on judgement, and let everything else run.

Who does the work
Mia, who coordinates across brands, and Scout, Code Pineapple's brand agent.
Where you see it
ChatTasksWorkbenchSchedules
What came back
A short list of decisions, each one a click or a sentence; the rest moves without you.
  • Open one conversation and see what is waiting on you, across every brand.
  • Clear the review queue in the Workbench: approve, redirect in a sentence, or reject.
  • Let scheduled work run, and see what it did afterwards.
  • Approve the paid and irreversible steps when they reach you — and only then.
MMiaPrivate conversation

Morning. Three things need you today; everything else is moving.

1. The Halloween pins are at version 3 — the pin with two characters is fixed. Ready for review.
2. Two mysteries from the latest batch were escalated: a child might miss the key clue. Your call on each.
3. The new trailer storyboard is approved; the video render is a paid step and is waiting for your go.

Overnight, Scout's scheduled run drafted the gift-window emails. They are in review; nothing has been sent.

Work cardYour review queue3 items · Code PineappleOpen in Workbench →
Illustration, not a screenshot. A morning brief of this shape; the items are the ones from the other example pages.
  1. The brief — Chat

    Your agent starts each conversation already knowing your brands, your goals and what is on the plate, so the first message is the list, not a question.

  2. The review queue — Tasks, Workbench

    Each item opens on the version waiting for you. You approve, redirect in a sentence, or reject; a redirect comes back as the next version.

  3. Scheduled work — Schedules

    Some work runs on its own clock — a weekly Pinterest batch, an overnight draft, the nightly consolidation of what was learned. Each run has a record of what it did and where its output went.

  4. The paid step — Chat

    When a run reaches a paid step — a video render, a batch of images — it stops in the conversation it belongs to and waits for approval. Scheduled or not.

  5. The end of the day — Chat

    What moved, what is waiting, and what will run overnight. Tomorrow’s brief starts from it.

  • Your time goes on judgement. Three decisions, each with the reason it needs you.
  • Nothing expensive happened by itself. The render waited; the emails were drafted, not sent.
  • One brief covers every brand. The examples here are one publisher; the same brief carries the others.

Knowing you, your brands and your plate at the start of a conversation is available, as are scheduled automations with a run record. The personal area that coordinates priorities and commitments is Limited. Details and evidence: What works today.

Sources: docs/architecture/agents-runtime.md, brands/code-pineapple/pipeline (task records referenced on the other example pages) · Last verified 2026-10-06