Skip to content

Louder Bridge v0.3.1

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 08 Aug 06:00
· 5 commits to main since this release
0d58bd1

Louder Bridge 0.3.1

This prerelease finishes the Ghostty controls introduced in 0.3.0.

What changed

  • Agent Keys now focus the correct Ghostty window, tab, or split in mixed-agent
    sessions.
  • Claude Code and Hermes use their hold-Space push-to-talk control when MIC is
    held.
  • Codex CLI uses macOS Dictation when MIC is held.
  • The send key sends Return to the focused terminal.
  • First-run setup requests permission to control Ghostty, and status reports
    that permission separately.
  • Local development builds can use a stable signing identity so macOS keeps
    their permissions between rebuilds.

Hardware result

A locally built v0.3.1 candidate passed a mixed-pane USB test on August 8,
2026. One Ghostty pane ran Claude Code and another ran Codex CLI. Agent Keys
switched to the correct pane, both voice routes inserted speech, send submitted
each prompt once, and the key and exterior lighting followed both sessions.

Component Version or result
macOS 26.5.2 (25F84)
Ghostty 1.3.1
Claude Code 2.1.226
Codex CLI 0.147.0
Embedded Node.js 22.23.1
Codex Micro firmware v0.4.1
Connection USB
Automated tests 355 passed

Install

Download the Apple Silicon ZIP, move Louder Bridge.app to Applications,
and open it once. If macOS blocks it, open System Settings → Privacy &
Security
and choose Open Anyway. Approve Input Monitoring and
Accessibility for Louder Bridge. Ghostty may also ask for Automation permission
the first time an Agent Key selects a terminal.

The GitHub build uses an ad-hoc signature, so macOS may ask for permissions
again after an upgrade.

Privacy

Louder Bridge runs locally. It collects no telemetry, audio, transcripts,
prompt content, project names, or session identifiers. Local diagnostics require
a private authentication token.

This remains a prerelease. Ghostty labels its AppleScript API as a preview, and
the device driver uses an independently documented protocol.