Skip to navigation
Connect an agent

Codex app

Hear the Codex desktop app, jump to its threads, and reply from Heard.
View as Markdown

The Codex desktop app runs the same Codex hooks as Codex CLI, so Heard narrates its progress, questions and results. Your Codex app threads also show up in Heard: jump to the right thread, or have Heard type your reply into the Codex composer.

Two ways to run Heard

Heard is one engine with two distributions. The downloadable macOS app is the official managed build: sign in and it works, with managed narration, premium voices and the full voice-input suite on Power. The open source engine (github.com/heardlabs/heard, Apache 2.0) is free forever: clone or fork it and run it yourself with a local voice or your own provider keys. Dictation, spoken replies, hands-free dictation, Heard Parrot, and the iPhone companion exist only in the app.

Managed app setup

1

Connect Codex in Heard

Open Heard Settings, go to Connections, and connect Codex under On this Mac.

2

Approve the hook

If Codex asks you to review the Heard hooks, trust them. Trusting them once in Codex CLI covers the app too.

3

Keep both apps running

Leave Heard running while you use the Codex app under the same macOS account, and start a new task.

4

Jump or reply

Your Codex app threads appear in Heard. Jump to one, or hold right ⌘ and talk to send a reply into its composer (Heard Power).

Open source setup

Terminal
heard install codex

Keep Heard running while Codex writes local session activity. You do not need to run a separate development daemon.

If the Codex app stays quiet

  1. Confirm Heard and Codex run under the same macOS user.
  2. Confirm Codex is enabled in Heard.
  3. Send a new message so there is fresh local activity to observe.
  4. Verify the Mac output is audible and Heard is not paused.

See Privacy and data for the difference between local observation and optional hosted narration or speech.