Proven here: a Linux desktop hosts the machine; Android phones and an Android TV join directly over Iroh. Not claimed: iOS, Cast, AirPlay, arbitrary televisions, or phone-hosted machines.

Proof and specs →

native · desktop, mobile · android, linux

Operate the primary interface with keyboard and pointing input

Proof and specs →

native · desktop, gadget, mobile · android, linux

Let agents present declared interactive documents or application surfaces

Proof and specs →

native · desktop, mobile, machine · android, linux

Work on a repository from the channel that talks about it

Proof and specs →

native · desktop, machine · linux

Run fully interactive terminal processes inside the product

Proof and specs →

partial · desktop, machine, mobile · android, linux

Restore terminal workspace structure after application restart

Proof and specs →

native · desktop · linux

Arrange simultaneous terminal or browser surfaces in split panes

Proof and specs →

Delegate safely

Give tasks independent workspaces, bounded authority, and explicit human decisions.

Explore 7 supported outcomes scope, platform, evidence

native · desktop, machine · linux

Configure a workflow a channel can run, and watch it advance

Proof and specs →

native · machine · linux

Keep simultaneous tasks from changing one another's files and process state

Proof and specs →

native · desktop, machine, mobile, wrist · android, linux, pebble

Review and answer agent tool or execution permission requests

Proof and specs →

native · machine, mobile · android, linux

Keep credentials and remote authority inside a documented trust boundary

Proof and specs →

native · desktop, machine, mobile · android, linux

Organize active work into durable nested workspace, screen, pane, or window structures

Proof and specs →

native · desktop, machine, mobile · android, linux

Keep and switch among several configured projects

Proof and specs →

native · machine · linux

Create or manage a separate repository worktree for a task

Proof and specs →

Connect and extend

Reach remote machines and use supported agent, automation, sharing, and extension boundaries.

Explore 9 supported outcomes scope, platform, evidence

partial · cli, machine · linux

Inspect and control product state from a command line

Proof and specs →

native · machine · linux

Subscribe programmatically to product and agent lifecycle events

Proof and specs →

partial · cli, machine · linux

Control a running instance through a structured local API

Proof and specs →

integration · machine · linux

Connect supported coding agents through official lifecycle integrations

Proof and specs →

partial · gadget, machine · android, linux

Install third-party behavior into a documented product extension runtime

Proof and specs →

partial · desktop, mobile, machine · android, linux

Share a screen or a camera into a huddle, machine to machine

Proof and specs →

native · machine, desktop · linux

Run the relay your channels live on, on your own machine

Proof and specs →

native · machine, mobile · android, linux

Operate agent work running on another machine

Proof and specs →

Recover confidently

Reconnect, replace hosts, inspect diagnostics, and understand current platform availability.

Explore 5 supported outcomes scope, platform, evidence

native · machine · linux

Inspect logs, traces, or health evidence when the product misbehaves

Proof and specs →

partial · desktop, mobile, wrist · android, linux, pebble

Install supported builds and receive product updates

Proof and specs →

partial · desktop, mobile · android, linux

Use a first-party client on more than one desktop operating system

Proof and specs →

native · desktop, machine · linux

Replace a running server version while its terminal processes continue

Proof and specs →

native · desktop, machine, mobile · android, linux

Reconnect to running work without losing its authoritative state

Proof and specs →

Work together

Talk in a channel with the people and agents on the project, follow a thread, and join a huddle.

Explore 4 supported outcomes scope, platform, evidence

native · desktop, mobile, machine · android, linux

Put an agent in a channel and address it like anyone else

Proof and specs →

native · desktop, mobile · android, linux

Talk in a channel with the people and agents who are in it

Proof and specs →

native · desktop, mobile · android, linux

Say something to one person, kept apart from the channels

Proof and specs →

Work with bots

Give each bot its own name, purpose and continuing conversation, convene them into groups, and let them use a browser and desktop you control.

Explore 6 supported outcomes scope, platform, evidence

native · desktop, machine, mobile · android, linux

Convene bots into a group and choose exactly what context they share

Proof and specs →

native · desktop, machine, mobile · android, linux

Keep several bots, each with its own name, purpose and continuing conversation

Proof and specs →

native · desktop, machine, mobile · android, linux

Approve each turn a bot may see or use a screen

Proof and specs →

native · desktop, machine, mobile · android, linux

Give a bot a full desktop on one of your VMs, bound to the exact target you approved

Proof and specs →

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.

Read the behavioral receipt →

01 · Original submitted request
Read the request that started it

The first three paragraphs of the original submitted request, retrieved from Home history. Read the full exact request below. desktop · desktop-window · desktop-x11 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. desktop · desktop-window · desktop-x11 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. desktop · desktop-window · desktop-x11 View evidence
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. android · android-television · android-device 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. android · android-phone-landscape · android-device 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. android · android-phone-landscape · android-device 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.

Read the exact request · Reproduce the setup and controls

Everyone on your relay

Say it to the room, or to the relay.

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.

Proof and specs →

01 · Read the feed
Read what is posted here

The feed opens on everyone posting here, not on an empty screen asking you to find people first. android · android-phone · host-compose 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. android · android-phone · host-compose 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. android · android-phone · host-compose 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.

Proof and specs →

01 · Add a bot
Add a bot with its own purpose

A bot is a name and a working brief, with a private workspace and a conversation that continues. android · android-phone · android-device View evidence
02 · Open its computer
Open the bot's computer

Before anything opens, it says what is shared: one browser profile for your bots, signed in by you. android · android-phone · android-device View evidence
03 · Sign in yourself
Sign in while only you control it

Under private control the bot can't see the screen, so you sign in directly and nothing you type is observed. android · android-phone-landscape · android-device View evidence
04 · Hand control back
Hand control back

Hand it back and the sign-in stays. The bot uses the site one approved turn at a time. android · android-phone-landscape · android-device View evidence

BACKENDS

Bring your agent

integration · linux, android

Pi

Run Pi-backed agent sessions while Dozer owns the durable project, session, and native-client experience around them.

Covers the maintained Pi adapter and recognized session lifecycle; it does not claim every Pi extension as native Dozer behavior.

Proof and specs →

Find the partyou care about.

Supervise agents

Run and monitor several agent sessions at the same time

Coordinate work or messages among agents

Recognize whether an agent is working, blocked, idle, or done

Find the agent session that needs a human decision

Monitor or continue agent work from a phone or wearable

Move directly among active projects, sessions, and attention items

Find and invoke product actions through search or a command palette

Receive a system notification when background work needs attention or completes

Preserve context

See repository, branch, and working-directory context for active work

Attach files or images as durable agent context

Browse and search durable past agent sessions

Carry curated memory or instructions across sessions

Detach every interactive client while owned terminal processes keep running

Resume a recognized agent conversation after restart

Read a structured conversation transcript outside terminal scrollback

Work in full project environments

Use the primary interface with platform accessibility semantics and scalable text

Adapt the interface's colors and appearance

Open a real web browser surface alongside active work

Describe one experience and let Dozer arrange its project, display, and controllers

Operate the primary interface with keyboard and pointing input

Let agents present declared interactive documents or application surfaces

Work on a repository from the channel that talks about it

Run fully interactive terminal processes inside the product

Restore terminal workspace structure after application restart

Arrange simultaneous terminal or browser surfaces in split panes

Delegate safely

Configure a workflow a channel can run, and watch it advance

Keep simultaneous tasks from changing one another's files and process state

Review and answer agent tool or execution permission requests

Keep credentials and remote authority inside a documented trust boundary

Organize active work into durable nested workspace, screen, pane, or window structures

Keep and switch among several configured projects

Create or manage a separate repository worktree for a task

Connect and extend

Inspect and control product state from a command line

Subscribe programmatically to product and agent lifecycle events

Control a running instance through a structured local API

Connect supported coding agents through official lifecycle integrations

Install third-party behavior into a documented product extension runtime

Share a screen or a camera into a huddle, machine to machine

Run the relay your channels live on, on your own machine

Operate agent work running on another machine

Give another person separately authorized access to selected work

Recover confidently

Inspect logs, traces, or health evidence when the product misbehaves

Install supported builds and receive product updates

Use a first-party client on more than one desktop operating system

Replace a running server version while its terminal processes continue

Reconnect to running work without losing its authoritative state

Work together

Put an agent in a channel and address it like anyone else

Talk in a channel with the people and agents who are in it

Say something to one person, kept apart from the channels

Post, follow, reply and read long-form on your machine's own relay

Work with bots

Sign in to any website yourself in your bots' browser, then hand control back

Convene bots into a group and choose exactly what context they share

Keep several bots, each with its own name, purpose and continuing conversation

Approve each turn a bot may see or use a screen

Preview what a bot wrote and share it explicitly

Give a bot a full desktop on one of your VMs, bound to the exact target you approved

Ask an agent. Play together.

Read the request that started it

Keep the handoff visible

Supervise the working project

One emulator on the shared display

Hold direction and action together

Give the other phone its own player

Watch the actual run

Say it to the room, or to the relay.

Read what is posted here

Open a note to its conversation

Write one, with a picture on it

Give a bot a browser, not your password.

Add a bot with its own purpose

Open the bot's computer

Find the part
you care about.