Repository navigation
cmux-imessage: the connector's status, opt-in and thread list over the app FFI (step A) - #33660
Conversation
…e app FFI (step A) Rust half of #33152 (Connect iMessage in Session Info): the app FFI's 'imessage' operation over the merged cmux-imessage reader. No Swift change; #33152 pins the published release (step B). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-0d5c4da7f9d103143c0b
|
cmux status (one comment, edited in place; each line is updated by the job that owns it) Review App of this head (app.zip, kept 1 day)
web and size checks: green Shipped in:
|
|
Found 1 test failure on Blacksmith runners: Failure
|
|
Review (codex, router-review): SHIP at 7709d19 Reviewer: codex gpt-6-astra high, fast tier. SHIP at 7709d19 No actionable correctness findings. All 24 Python tests and the release-path check passed; Rust compilation was unavailable in this box. Follow-ups: none |
A newer verdict blocks eb78631 (no independent SHIP at the head).
![Fix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/fix-with-codesmith-light-3x.png)
Leo-ask: ask-c41eed1aa4
Leo:
Step A of the Connect iMessage connector (#33152): only the Rust side, so this push to feat-cmux-next publishes a new app FFI release, and #33152 then pins it (step B), the same split as #32564/#33313.
cmux-layout-reducer-ffi/src/imessage.rs: theimessageJSON op over the mergedcmux-imessagereader (cmux-imessage: read-only Messages database reader for the opt-in Messages mirror #32891). Status needs no opt-in and reads nothing. Threads (titles and participants only, never message bodies) needimessage.enabledplus Full Disk Access, with Automation granted or skipped. Connect, disconnect and skip return the setting writes for the app to commit.No Swift or web change. Until #33152 pins this, nothing calls the op.
Agent session: agent session
🤖 Generated with Claude Code