v1.3.4 — Windows hotfix for v1.3.3 (#1376)

v1.3.4 — Windows hotfix for v1.3.3

Emergency single-fix release. If you're on Windows running the claudecode agent, upgrade now.

Linux / macOS users and users running non-claudecode agent runtimes are not affected by the v1.3.3 bug below; this release is still safe (and a no-op behavior-wise) to pick up.

What this fixes

Windows: messages silently never reply on v1.3.3 (#1376)

After upgrading to v1.3.3 on Windows, all incoming messages stopped producing a reply:

• Bot sees the message but session never starts → no reply ever arrives
• Windows event log / stderr shows GBK-encoded 命令行太长。 (command line too long)
• ❌ 错误: session process is not running may appear in user-visible cards

Root cause: v1.3.3 expanded core.AgentSystemPrompt() from 2,707 bytes to 9,055 bytes (added cron/timer detailed instructions + an ASCII table). cc-connect spawned claude.exe with --append-system-prompt <inline 9 KB>, which busted Windows cmd.exe's 8,192-byte total command-line limit → claude.exe refused to start → every session immediately died. Linux / macOS exec argv has no such limit, so the regression was Windows-only.

Fix: the claudecode agent now passes the system prompt to claude.exe via a file on disk (--append-system-prompt-file <path>) instead of inline on the command line.

• Default 99 % path: cc-connect writes a single shared file at <data_dir>/agent-prompts/cc-connect-system.md (~/.cc-connect/agent-prompts/cc-connect-system.md by default) at startup; all sessions reuse it.
• Edge 1 % path (Slack / Weixin / MAX / when you configure append_system_prompt): per-spawn temp file.
• Prompt content is byte-identical to v1.3.3 — only the delivery mechanism changed. Agent behavior does not regress.
• The cmdline now carries only the short file path (~80 bytes), so this class of regression cannot recur even if the prompt grows further.

What's NOT in this release

Strictly hotfix scope. No new features, no other bug fixes, no behavior changes outside of the cmdline delivery mechanism above. If you were waiting on something else, it'll land in v1.3.5 or later.

Upgrade notes

• No config changes required. Existing config files keep working unchanged.
• A new file <data_dir>/agent-prompts/cc-connect-system.md will be generated on first startup. Safe to delete — cc-connect rewrites it next startup.
• If you set append_system_prompt in your claudecode config, behavior is unchanged (still merged into the prompt, just delivered via file).
• Downgrade is safe (config-compatible with v1.3.3 and earlier).

Verification

• Owner-driven Windows e2e on the fixed binary:
  • Feishu plain message → MiniMax M3 reply OK
  • Feishu 3 分钟后看 ipconfig → timer written to data/timers/jobs.json
  • Feishu 每天早上 6 点提醒吃药 → cron written to data/crons/jobs.json
  • Shared prompt file generated correctly at startup (8,918 bytes, byte-identical to v1.3.3 prompt content)
• Automated: claudecode package full suite 10.3 s green; core package full suite green (modulo an unrelated H2 flake); 4 new unit tests covering file-based prompt 99 % path + 1 % edge + auto-refresh on upgrade + empty ccDataDir fallback; go build + go vet green.

Compatibility

• Windows / macOS / Linux: all green (Linux/macOS were unaffected; Windows is fixed).
• All agent runtimes: claudecode fixed; codex / opencode / qoder / cursor / gemini / kimi / pi / others unaffected (they don't use cmdline delivery).
• All platforms: unaffected (the bug was in agent process spawn, not in platform code).

Diff size

3 files changed, +323 / -9, all in agent/claudecode/. No changes elsewhere.

Install

# npm (latest)
npm install -g cc-connect@1.3.4
# or
npm install -g cc-connect@latest

# Verify
cc-connect --version  # → cc-connect v1.3.4

Credits

Reporters who unblocked us within hours of v1.3.3 going stable:

• @secountAiAccount (Feishu + claudecode, reported "session process is not running")
• @softxyz1 (Feishu + WeChat ilink, had already downgraded to v1.3.2)

→ See #1376.

Full changelog: changelogs/v1.3.4.md · v1.3.3...v1.3.4