[Bug]: MiniMax Code 3.0.67 macOS arm64 latest disables WeChat IM auto push because listBindingsByAgent is not exposed

Version / 版本号

3.0.67

Platform / 平台

macOS

OS version / 系统版本

macOS Apple Silicon / arm64 (exact macOS version not collected)

Issue area / 问题类型

Startup / install / update

Upload ID / 日志上传 ID

not uploaded; local package/hash evidence included

What happened? / 问题描述

MiniMax Code 3.0.67 on macOS Apple Silicon appears to ship with code that disables WeChat IM automatic push delivery. This does not look like a local installation/configuration/account/database issue.

The specific behavior observed in the packaged code is that cron/delivery.ts deliberately does not expose listBindingsByAgent, so the delivery cron path cannot enumerate the IM bindings for an agent and therefore cannot send automatic WeChat pushes.

Local comparison evidence:

• MiniMax logs show that version 3.0.67 was downloaded from the official update server and latest channel:
  • filecdn.minimax.chat/public/minimax-agent-prod/release
• Installed app package hash:
  • /Applications/MiniMax Code.app/Contents/Resources/app.asar
  • hash prefix: 0a062e9b...a1a21a
• Official updater cache zip contains an app.asar with the same hash:
  • 0a062e9b...a1a21a
• The relevant packaged code path is cron/delivery.ts, where listBindingsByAgent is not exposed, effectively closing the automatic IM push path.

Therefore this can be narrowed to a product-level behavior/regression in the official MiniMax Code 3.0.67 / macOS Apple Silicon / CN prod latest release package, rather than this machine having the wrong database field, wrong WeChat binding, or a locally modified download.

This is different from earlier WeChat QR binding/version-handshake issues. In this case the installed package and official updater cache package are byte-identical for app.asar, and the failure is tied to code shipped in the official 3.0.67 release package.

Steps to reproduce / 复现步骤

1. Install or update to MiniMax Code 3.0.67 from the official CN prod latest update channel on macOS Apple Silicon.
2. Ensure WeChat IM has previously been bound or is expected to receive automatic task/session push notifications.
3. Trigger a workflow that should produce an automatic WeChat IM notification.
4. Observe that the WeChat push is not delivered.
5. Inspect the packaged app.asar / cron/delivery.ts code path and confirm that listBindingsByAgent is not exposed to the delivery logic.

Expected behavior / 预期行为

If a user has successfully bound WeChat IM, MiniMax Code should continue to push task/session notifications automatically through WeChat after upgrading to 3.0.67.

At minimum, if WeChat push is intentionally disabled for this release/channel, the app should surface this as a product state instead of silently failing delivery.

Actual behavior / 实际行为

After upgrading to MiniMax Code 3.0.67, WeChat push delivery fails even though the issue is not caused by local binding state or a corrupted local installation.

The packaged delivery path cannot enumerate bindings because listBindingsByAgent is not exposed to cron/delivery.ts / the delivery logic, so WeChat automatic push has no binding list to send to.

Logs or crash report / 日志或崩溃信息

Relevant package/update evidence only; no private logs attached here.

Update source observed in MiniMax logs:
filecdn.minimax.chat/public/minimax-agent-prod/release

Installed package:
/Applications/MiniMax Code.app/Contents/Resources/app.asar
hash prefix: 0a062e9b...a1a21a

Official updater cache zip app.asar:
hash prefix: 0a062e9b...a1a21a

Verified scope so far:
MiniMax Code 3.0.67 / macOS Apple Silicon / CN prod latest.
Whether Windows, Intel Mac, other regions, or other channels behave the same still needs comparison.

Suggested fix:
Please restore the binding enumeration path used by IM delivery, or otherwise expose the equivalent of listBindingsByAgent to the cron delivery module so WeChat automatic push can find the agent bindings again. If the disabling was intentional for this release/channel, please document it in the UI/release notes and provide a replacement path for users who depend on WeChat push notifications.

Screenshots / 截图

No response

Before submitting / 提交前确认

• I have searched existing issues.
• I am using the latest version available to me.
• I have removed sensitive information from logs/screenshots.

Start by inspecting the packaged app.asar path and the cron/delivery.ts delivery logic described in the report, focusing on whether listBindingsByAgent is exposed and usable. Reproduce on MiniMax Code 3.0.67 for macOS Apple Silicon with a bound WeChat IM account, then compare the relevant package behavior. Done means binding enumeration and automatic WeChat delivery work, or the intentional limitation is surfaced clearly.