Code Buddy v0.1.4

Code Buddy v0.1.4 is the macOS host fix release for managed Codex launch reliability.

Changes:

• Managed Codex sessions launch the saved real Codex executable instead of relying on launchd PATH lookup.
• Setup records the shell PATH used to resolve Codex, and managed Codex subprocesses receive that PATH plus common macOS/Homebrew locations. This covers npm-installed Codex scripts that require node.
• Managed app-server processes now run in their own process group and are terminated by process group, preventing node wrapper child processes from lingering after bridge stop or startup timeout.
• Added regression coverage for launchd-style minimal PATH, setup PATH persistence, managed bridge process env, and process-group startup.

No firmware or native BLE helper changes are required for this release; the v0.1.2 helper artifact remains compatible.

Code Buddy v0.1.3

Code Buddy v0.1.3 is a macOS host fix release.

Changes:

• Managed Codex sessions now launch the saved real Codex executable instead of relying on launchd PATH lookup.
• Setup records the shell PATH used to resolve Codex, and managed Codex subprocesses receive that PATH plus common macOS/Homebrew locations. This covers npm-installed Codex scripts that require node.
• Added regression coverage for launchd-style minimal PATH, setup PATH persistence, and managed bridge process env.

No firmware or native BLE helper changes are required for this release; the v0.1.2 helper artifact remains compatible.

Code Buddy v0.1.2

Code Buddy v0.1.2

Code Buddy v0.1.2 is a bug-fix release focused on session-state accuracy and StickS3 state rendering.

Install

1. Download code-buddy-sticks3-v0.1.2-full.bin from this release.
2. Flash it to the StickS3 at 0x0.
   If a web flasher page is published for this release, you can use it.
   Fallback:

esptool --chip esp32s3 --port /dev/cu.usbmodem101 --baud 460800 write_flash 0x0 code-buddy-sticks3-v0.1.2-full.bin

3. Install the Mac client:

brew install CharlexH/tap/code-buddy

4. Run first-time setup:

code-buddy

Daily Use

Open a new shell after setup, then use Codex normally:

codex

Code Buddy will keep the StickS3 linked and show approval prompts on the device.

What Changed In v0.1.2

• Fixed readonly Codex Desktop session parsing so a new turn that starts in the same second as the previous turn completed stays visible as running.
• Aligned the StickS3 base persona mapping with the documented state table: disconnected -> sleep, approval pending -> attention, active sessions -> busy, otherwise connected -> idle.
• Kept celebrate, dizzy, and heart as one-shot effects instead of treating them as steady bridge states.
• Added a dedicated firmware test for the persona-state mapping.
• Updated the serial helper scripts to detect both /dev/cu.usbmodem* and /dev/cu.usbserial-* devices on macOS.

Notes

• code-buddy does not install Codex itself; Codex CLI must already be installed on the Mac.
• Codex Desktop session discovery remains status-only in this release. Approval proxying is scoped to managed CLI sessions.

Code Buddy v0.1.1

Code Buddy v0.1.1

Code Buddy v0.1.1 is the first fully published GitHub + Homebrew release for using an M5Stack StickS3 as a Bluetooth approval device for Codex CLI on macOS.

Install

1. Download code-buddy-sticks3-v0.1.1-full.bin from this release.
2. Flash it to the StickS3 at 0x0.
   If a web flasher page is published for this release, you can use it.
   Fallback:

esptool --chip esp32s3 --port /dev/cu.usbmodem101 --baud 460800 write_flash 0x0 code-buddy-sticks3-v0.1.1-full.bin

3. Install the Mac client:

brew install CharlexH/tap/code-buddy

4. Run first-time setup:

code-buddy

Daily Use

Open a new shell after setup, then use Codex normally:

codex

Code Buddy will keep the StickS3 linked and show approval prompts on the device.

What Changed In v0.1.1

• Published the GitHub repository, tagged release assets, and Homebrew tap under CharlexH.
• Kept code-buddy as the public host command and codex as the normal daily-use entrypoint.
• Added single-file firmware release artifacts as code-buddy-sticks3-v{version}-full.bin.
• Added recovery commands: code-buddy doctor, code-buddy repair, and code-buddy uninstall.
• Moved runtime data to ~/.code-buddy, with migration from older ~/.codex-buddy state when available.
• Made non-native BLE imports lazy so packaged macOS installs can rely on the native helper path without importing bleak up front.
• Same-turn read-only verification commands after an approved mutating command still avoid the extra approval prompt.

Notes

• code-buddy does not install Codex itself; Codex CLI must already be installed on the Mac.
• Codex Desktop session discovery remains status-only in this release. Approval proxying is scoped to managed CLI sessions.

Code Buddy v0.1.0

Code Buddy v0.1.0

Code Buddy v0.1.0 is the first productized release for using an M5Stack StickS3 as a Bluetooth approval device for Codex CLI on macOS.

Install

1. Download code-buddy-sticks3-v0.1.0-full.bin from this release.
2. Flash it to the StickS3 at 0x0.
   If a web flasher page is published for this release, you can use it.
   Fallback:

esptool --chip esp32s3 --port /dev/cu.usbmodem101 --baud 460800 write_flash 0x0 code-buddy-sticks3-v0.1.0-full.bin

3. Install the Mac client:

brew install CharlexH/tap/code-buddy

4. Run first-time setup:

code-buddy

Daily Use

Open a new shell after setup, then use Codex normally:

codex

Code Buddy will keep the StickS3 linked and show approval prompts on the device.

What Changed In v0.1.0

• Public host command is now code-buddy.
• First launch runs setup automatically; later launches show a concise status view instead of pairing again.
• First-time setup now installs the native Bluetooth helper, pairs the StickS3, syncs device time, installs the launchd agent, installs the local codex shim, and adds ~/.code-buddy/bin to ~/.zprofile.
• Daily use no longer requires codex-buddy run; the normal codex CLI path is now the primary approval flow.
• Runtime data moved to ~/.code-buddy, with migration from older ~/.codex-buddy state when available.
• Added recovery commands: code-buddy doctor, code-buddy repair, and code-buddy uninstall.
• Firmware release artifacts now ship as a single merged full.bin.
• Same-turn read-only verification commands after an approved mutating command no longer trigger an extra approval prompt.

Notes

• code-buddy does not install Codex itself; Codex CLI must already be installed on the Mac.
• Codex Desktop session discovery remains status-only in this release. Approval proxying is scoped to managed CLI sessions.