A day with amoOS

A working day where the work keeps going when you stop.

This is how amoOS actually runs day to day. It’s a real routine across a phone, a laptop and two always-on machines.

The model

Telegram is the remote control

Briefs, decisions, dispatch and capture from the phone, wherever the day goes.

The laptop is the cockpit

One coordinator session plans, dispatches and reviews. Judgment happens here.

Two machines are the engine room

An always-on Linux box and a Mac mini run the agents, day and night.

The Brain is the ledger

Everything writes back: tasks, decisions, handoffs and lessons.

The day

07:30

Telegram · 2 minutes

The morning brief

Before coffee: what shipped overnight, today’s top priorities, the calendar and any decisions that are due. The brief learns from the feedback buttons and reshapes itself over time.

amoOS

online · your fleet

Message

09:00

Cockpit · 5 minutes

Plan once, dispatch in parallel

One coordinator session restores full context in a single call, picks the sprint, and sends parallel tasks to the fleet. Each worker gets its own isolated worktree, the right model for the difficulty, and one to three curated lessons.
claude — coordinator

11:42

Telegram · one tap

Decide from anywhere

A worker hits a real judgment call. Instead of guessing, it asks. The question arrives with options, one tap answers it, and the worker picks up exactly where it stopped.

amoOS

online · your fleet

Message

14:05

Telegram · capture

Capture the moment it matters

An article, an X thread, a YouTube talk or a half-formed idea goes to the bot. It becomes a cited source in the Brain and surfaces on the next task that needs it.

amoOS

online · your fleet

Message

16:20

Voice · macOS

Just ask

Hold a key and talk. amoOS answers from the Brain and the live fleet, out loud, with no dashboard needed.

Hold to talk

amoOS for macOS

You · “What shipped overnight, and is anything waiting on me?”

amo · Four PRs merged overnight, all verified. One decision is waiting: the digest layout. Want it now?

18:30

Web · command center

The evening review

The evening brief closes the loop: what moved, what’s blocked, what’s verified, and what the fleet runs overnight. The command center has the detail when it’s needed.

Command center

3 nodes online

Sprint

18 / 24

tasks done

Fleet

7 live

sessions

Capacity

62%

weekly used

brain-recall-eval

amonode · Opus 5.5

running

gateway-rate-limits

amomini · Codex

verifying

voice-latency-pass

amonode · Sonnet 5.5

running

digest-composition

amomini · Opus 5.5

needs you

usage-pacing-v2

amonode · Codex

merged

Merged this sprint

57

Illustrative data

02:00

Engine room

The fleet keeps shipping

Always-on machines keep executing, verifying and handing off while everyone sleeps. Long sessions recycle cleanly, work is paced against subscription limits, and destructive actions wait for a human.

The habit that compounds

Every session ends with a bounded handoff: what happened, which lessons helped, and up to two new ones. It takes seconds and it’s the highest-leverage habit in the system, because it’s how tomorrow’s agents start ahead of today’s.

See the learning loop

Continue

Capabilities

Everything the system can do