Show it, say it, send it
to Claude Code

Comms turns what you show and say into a brief your agent can execute. Send it in one click, to any agent.

Download for Mac

Free during beta. Works with macOS 26 or later.

Any agent

Bring your own agent

If it can run a terminal, it can take a brief.

Agents

claude-backend~/Dev/Comms · up 4h
claude-frontend~/Dev/Comms · up 12m
Connect an agent…
00:07
Claude CodeCursorCodexConductoryour own harness

An agent connects with one command — comms listen — and shows up in AGENTS. Stop a recording, pick it, and the brief lands in its session while you keep working.

How it works

Explain it like you would to your developer

  1. 01

    Record

    Start a session. Comms captures your screen, your voice, and system audio. Whatever is on it: Figma, a staging URL, a native app.

  2. 02

    Draw and talk

    Circle the button. Underline the copy. Say what should change while you point at it.

  3. 03

    Send it

    Hit send, pick an agent. The brief lands in its session — structured, not a video — and it goes to work.

Or from any terminal — the comms CLI ships inside the app: listen, session, transcript, frames, search.

$ comms session "~/Comms/2026-08-16_214447.comms"
2026-08-16_214447.comms — 12s, 3024×1964, 2 annotations
  a01    3.7–  5.6s  bbox 1252,673,317,295  annotations/a01.png
       “make this the primary action”
  a02    8.6– 10.4s  bbox 592,1392,256,56  annotations/a02.png
       “and move this”

  said:
     3.7– 5.6    make this the primary action
     8.6–10.4    and move this

$ comms search "primary action"
~/Comms/2026-08-16_214447.comms
     3.7s  make this the primary action

Use it for

Bug reports, handoffs, polish

One recording each. Your agent does the rest.

  • Bug reportsCircle what broke, say what you expected. The agent gets the region, your words, and the app you were in.
  • Design handoffPut the Figma or Paper design next to the build. Circle each gap and talk through it. Every difference lands as its own annotation.
  • Polish passesThe tweaks that never become tickets: this grey, that spacing, drop that word. Record once, and your agent ships them one by one.

Local only

Nothing leaves your Mac

Transcription runs on-device. Sessions are folders on your disk. No account, no upload, no cloud. Use it on client work you could never paste into someone else’s server.

  • On-device transcription
  • No login, no account
  • Sessions saved on disk
  • Works offline

Pricing

Free while it’s in beta

Freeuntil Oct 1
  • Every feature, no watermark, no limits during beta
  • File a real bug, or a feature request we ship, and your license is free forever
  • One-time purchase after launch. No subscription.
Download for MacmacOS 26 or later · Apple Silicon or Intel

Questions

Short answers

Which agents does it work with?

Anything that can run a terminal. Paste one line — comms listen — into Claude Code, Codex, Cursor, Conductor, or your own harness, and it appears in AGENTS. Stop a recording, pick it, and the brief lands in its session. The agent reads session.json, the transcript, and the cropped frames with the bundled comms CLI. It never watches the video.

Is my recording uploaded anywhere?

No. Recording, transcription, and the brief all happen on your machine. There is no server to upload to.

What does Comms need permission for?

Two: Screen Recording and Microphone. macOS will ask on first run. Both are standard for this category of app; the drawing overlay needs nothing extra.

Does transcription work in my language?

Transcription uses Apple's on-device speech models, so language support follows macOS (around thirty locales; no Norwegian yet). English works great. The first time you transcribe in a language, macOS downloads that speech model once; after that it works fully offline.

What happens when the beta ends?

On October 1 Comms becomes a one-time purchase. Everyone who filed a genuine bug report during the beta — or made a feature request that made it into production — keeps a free license.