Work lives heremachine solomon→project kristen-art→session Ship dashboard 2.4
Desktop clientSupervise the work from its durable project session: what the agent ran, and what it is waiting on. View evidence
Android clientAnswer the exact decision from Android without leaving the session behind. View evidence
Work stays on the machine.Desktop and Android are two clients of the same session.
Runs onLinux desktop and machine
Reach it fromLinux desktop · Android companion · Pebble companion
AgentsPi
Out of scopeAirPlay · arbitrary TVs · Cast · iOS · phone-hosted machines
Not another terminal tab
The work lives on your machine. Every screen is a window onto it.
Dozer organizes work by machine → project → session. The agent does the coding; Dozer makes the whole system understandable from desktop or Android.
machineOne explicit machine owns the work; clients do not form proxy chains.
→ projectThe durable place that attention, permissions, terminals, recovery, and agent backends stay attached to.
→ sessionYour project and session remain a place you can return to.
One loop, three acts
Leave the desk. Not the work.
Three moves. The same machine-owned session the whole way through.
01
Watch
See parallel work and the exact session asking for attention.
machine / project / session
solomon → kristen-art → Ship dashboard 2.4desktop
See the one session that needs you without losing the rest of the work. View evidence
02
Respond
Open the same machine-owned session on Android and reach the environment it is running in.
machine / project / session
solomon → kristen-art → Ship dashboard 2.4android
Reach the running environment from Android and check the work before you answer. View evidence
03
Return
Come back to the canonical project and session—history, place, and state intact.
machine / project / session
solomon → kristen-art → Ship dashboard 2.4desktop
Return to the same machine-owned session without rebuilding context. View evidence
Past the terminal
Your machine can do more than code.
A real request. A supervised run.
Ask an agent. Play together.
From a request in Dozer Home to one NES emulator, a shared display and two independent phone controllers. This worked example includes the original prompt, actual supervision, recorded play and reproduction notes.
Recorded on a Linux desktop with one display emulator and two Android phone emulators, joined directly over Iroh. Controller touches were driven by the supervising operator.
The first three paragraphs of the original submitted request, retrieved from Home history. Read the full exact request below. View evidence
02 · Real agent progress
Keep the handoff visible
Home tool progress and the supervising operator’s handoff instruction, captured during the actual run. View evidence
03 · Supervision and notes
Supervise the working project
The project agent updates its notes after supervised Stop, rejoin and teardown checks. The source capture shows reported checks; the recording and retained observations supply the play evidence. View evidence
Show all 6 stepsShow fewer steps
04 · Display emulator
One emulator on the shared display
Super Tilt Bro runs in one JSNES instance. Both phone emulators control distinct player ports in this same game. View evidence
05 · Player one phone emulator
Hold direction and action together
Player one’s landscape touch controls support simultaneous direction and action, release, and local Stop. View evidence
06 · Player two phone emulator
Give the other phone its own player
Player two has its own accepted role and held controls. Both phones were exercised independently and concurrently. View evidence
Watch the actual run
75 continuous seconds of play, recorded at about 20 frames per second. Both player inputs were tested independently and together. Stop cleared held input in about three seconds; rejoining kept the player role and returned the game to its title screen. This recording does not show a completed round.
A channel is what is said between the members of one room. The feed is what is said to everyone your machine's relay serves — read it, answer one of it, and post your own, in the app you supervise your agents in.
Shown here: the Android client of one machine, on a relay that machine serves. The device never dials the relay; a note's media and link previews arrive over its own machine's gateway.
The feed opens on everyone posting here, not on an empty screen asking you to find people first. View evidence
02 · Open a conversation
Open a note to its conversation
Open a note to its conversation. It has its own address, so a thread is something you can hand to somebody. View evidence
03 · Post one of your own
Write one, with a picture on it
Write a note and attach a picture. The machine signs it and carries the media; the device never dials the relay. View evidence
Bots that keep working
Give a bot a browser, not your password.
Each bot has its own name, purpose and continuing conversation. When one needs a website, you open its computer, sign in yourself while the bot can't see, and hand control back; it then uses that site one approved turn at a time.
Shown here: the Android app on a phone, recorded against a real machine and its real shared browser. The bots share one browser profile on that machine; signing in gives access through it and does not connect an API or MCP service.
