Mussh

See how the app works

Your agent stays on your computer. These are the screens you use to read its work and decide what happens next.

Actual Android emulator and iPhone simulator captures, using fictional projects on an isolated demo host. No interface elements have been redrawn. Tap a screenshot to open the larger image.

Pick a conversation, then switch projects

Tap an agent in the fleet to read its replies. The drawer groups work by workspace, tab and session; switching here does not move the view on your computer.

  1. Android fleet: one approval, one done, two working and two idle agents on studio.
    1. Find the agent that needs you.
  2. Android chat: Cart rounding, folded Edit and Bash calls, TypeScript and the result of 14 tests.
    2. Read the answer, code and tool results.
  3. Android drawer groups six demo sessions by project; Cart rounding is selected.
    3. Open the drawer to choose another session.

Follow a file path from the chat

File paths in an agent's answer are active: tap one to open that file on the connected computer. Web links are active too and open in your browser. The reader keeps the conversation behind it.

  1. An Android answer contains active README.md and src/cart.ts:12 paths and an underlined reference guide web link.
    1. Tap README.md in the answer.
  2. README.md opened from the chat path in Android's reader, with a quick-start code block and endpoint table.
    2. Read the file without copying its path into a terminal.

A reader for the files on your computer

Browse the current project and open Markdown, highlighted code, diff files or images. The panel is read-only: reading a file does not edit it or switch your checkout.

  • Android project browser lists src, tests, package.json and README.md in checkout-api.
    Browse the project from the files button.
  • Android Markdown reader renders headings, a shell code block, an endpoint table and a task list.
    Markdown keeps headings, code blocks, tables and checklists.
  • Android reads src/cart.ts with TypeScript highlighting, line numbers and the project breadcrumb.
    Code has syntax highlighting and line numbers.
  • Android displays cart.diff with green plus lines, red minus lines and a diff hunk header.
    A saved diff shows additions and removals.
  • Android opens checkout.png, a demo checkout image with an overlapping order button, and shows its dimensions and size.
    Inspect an image from the host.

Choose a model for a supported session

Tap the model in the chat header. The choices come from that agent, not a shared list for every harness. This example switches a Claude Code demo session from Opus to Sonnet.

  1. Android model picker with Opus selected, Sonnet and Haiku alternatives, and reasoning levels.
    1. Open the model choices.
  2. Android switch confirmation explains that Sonnet will re-read the history and use more tokens on the next message.
    2. Read the confirmation before switching.
  3. Android header now shows sonnet-5-5 and the chat records the model sonnet command.
    3. The header shows the confirmed model.

Read the request before you approve

Expand the approval panel to see the command and the agent's choices. The app checks that the same question is still on screen before sending your answer.

  • Android approval asks to run npm test for webhooks and offers Yes, a persistent folder permission, or No.
    The expanded request shows exactly what you are answering.

Review the diff and recent history

Open the changes button to inspect the working tree. Expand the file you need, then use the history tab to read recent commit summaries.

  1. Android changes view expands the cart.ts diff and lists two other modified files.
    1. Read the changed lines, file by file.
  2. Android history lists nine demo commits with hashes, author Alex and relative dates.
    2. Check recent commits without changing branches.

Use the terminal and its extra keys

The SSH terminal also works without Herdr. Keep frequently used keys in its bar, or open the full key panel. Chat has its own controls for sending keys to the agent's live panel.

  • Android SSH terminal displays a coloured git graph and working-tree status with a compact key bar.
    Open a shell on the connected computer.
  • Android terminal key panel shows navigation keys, Ctrl shortcuts, paste, upload and bar customization.
    Expand the panel for navigation and shortcuts.
  • Android chat with agent keys: Ctrl, Alt, Esc, Tab, Ctrl-C, arrows and Enter.
    Show agent keys without leaving the conversation.

Queue a follow-up while the agent works

In a session that supports a queue, your next message waits for the current turn. The queued label tells you it has not been processed yet; Send now lets you interrupt rather than wait. This Android example uses a Claude Code demo session.

  • Android chat labels a request for a zero-quantity test queued, beside Send now, while the agent is thinking.
    A queued follow-up stays visible in the conversation.

Attach an image before sending

Open the plus button and choose a photo from the gallery. The thumbnail lets you check the attachment or remove it before sending your prompt. This example is a fictional checkout screen, uploaded to the isolated demo computer over SSH.

  • Android chat input contains a checkout image thumbnail with a remove button before the prompt is sent.
    Inspect the attachment in the input bar.

Open the agent from its notification

While the app is connected, an approval alert shows which project needs you. On Android, expand the notification to read the command and your prompt, then tap it to open that agent. Background limits differ on iPhone; check the notification limits.

  1. Android notification shade shows Waiting for you: payments, the webhook test command and the original prompt.
    1. Read the approval notification.
  2. Tapping the notification opened Webhook retries on Android, with the matching npm test approval controls.
    2. Continue in the matching conversation.

Preview a palette before you choose

Open Settings, then Color palette. The app's built-in sample shows message text, code and agent states together. Chat, terminal and code fonts have separate settings and ship with the app.

  • Android palette settings with the built-in chat and code preview, Terracotta and sand selected and other dark palettes below.
    This sample is the app's own settings preview, captured without alteration.

The same workflow on iPhone

The controls follow the platform. These are actual iPhone simulator captures of the same demo host, not Android screens inside an iPhone frame.

  1. iPhone fleet on studio, with six agents grouped by working, waiting for approval, done and idle states.
    1. Choose a session from the fleet.
  2. iPhone chat with the Cart rounding answer, TypeScript snippet and folded tool results.
    2. Read the answer and its code.
  3. iPhone workspace drawer with Cart rounding selected and Checkout tests in the same project.
    3. Open the workspace drawer.
  4. iPhone now shows the Codex Checkout tests conversation about a flaky Playwright test.
    4. Continue in another agent's conversation.
  • iPhone approval sheet shows npm test for webhooks, with Yes, persistent folder permission and No choices.
    Read an approval request before answering.
  • iPhone Files sheet lists the demo project's source and tests folders, an image and a diff file.
    Browse the project in the Files sheet.
  • iPhone SSH terminal displays the demo project's git graph and an Esc, Ctrl, Tab and arrow key bar.
    Use the shell when you need the terminal.

Start on the phone, pair with your computer

Add a computer and choose QR pairing. Copy the command shown in your app, run it on your computer, then scan its QR code. The command includes a checksum check. You review the connection before saving it.

  • iPhone pairing instructions with a computer command, Copy, Paste code and From image buttons; no live pairing code is displayed.
    The first step on iPhone. Use your app's command, not text copied from this screenshot.

Listen to replies or dictate the next prompt

The speaker button below a completed answer starts the phone's system voice. The microphone in the input bar starts system dictation; review the text before sending. An image can show these controls, not the sound or speech recognition itself.

Both controls are visible in the chat screenshot above. Dictation depends on the speech recognition available on your phone.

Need connection instructions or details about notifications? Read the FAQ or open support.