2 Commits

Author	SHA1	Message	Date
程序员阿江(Relakkes)	e58ec4f649	experiment(desktop): add adapters mode to claude-sidecar (Feishu + Telegram) ... The Feishu and Telegram IM adapters used to be standalone Bun processes that the user had to launch manually with bun + .ts source on disk — which meant they were effectively unreachable from the bundled desktop app, since the user wouldn't have bun or the source tree. This adds them as a third mode of the merged claude-sidecar binary: claude-sidecar adapters --app-root <path> [--feishu] [--telegram] The launcher pre-checks credentials via the same `loadConfig()` the adapters use internally, then conditionally `await import()`s each enabled adapter whose creds are present. Adapters with missing creds are warned and skipped, so a partially-configured user (e.g. only Feishu set up, no Telegram bot token) still gets the working adapter started cleanly instead of having Telegram's top-level `process.exit(1)` kill the whole process. Adapter source code is unchanged — the adapters still self-start at top-level via Lark.WSClient.start() / grammy bot.start(). Their SIGINT handlers also still register independently. The only thing gating runtime is whether bun's static-import follows the dynamic specifier into adapters/feishu/index.ts and adapters/telegram/index.ts, which it does. Bundle impact ============= metric P0+P2 only +adapters mode delta claude-sidecar 66 MB 68 MB +2 MB .app total 87 MB 88 MB +1 MB .dmg 37 MB 37 MB 0 MB Both adapter SDKs (@larksuiteoapi/node-sdk and grammy) statically inline into the binary at a +2 MB cost, fully absorbed by DMG compression. Compared to the alternative (a separate ~60 MB sidecar binary per adapter, or even one combined ~60 MB adapter binary) this is essentially free. Verification ============ * `claude-sidecar server` regression test still passes (boots, /api/sessions → 200, CronScheduler runs) * `claude-sidecar cli --version` returns 999.0.0-local * `claude-sidecar adapters` (no flags) → exit 2 with usage error * `claude-sidecar adapters --feishu --telegram` (no creds) → both warned and skipped, exit 1 * `claude-sidecar adapters --feishu` (FEISHU_APP_ID=cli_fake creds) → Feishu adapter boots, Lark client `client ready`, attempts API connect, fails with 400 from feishu API and gracefully retries (correct behavior — fake creds) * `claude-sidecar adapters --telegram` (TELEGRAM_BOT_TOKEN=fake:token) → grammy bot.start() called, getMe API hits with 404, throws GrammyError (correct — fake creds) * `bun test adapters/` → 299 pass / 0 fail * `bun test src/` → 358 pass / 45 fail / 2 errors, identical to baseline Scanner change ============== desktop/scripts/scan-missing-imports.ts now also walks adapters/ in addition to src/, so any future feature() gated stubs in the adapter tree get auto-stubbed. As of this commit, adapters/ has 0 missing imports — all clean. Next step (UI integration, not done here) ========================================== To actually wire this into the desktop UX, the Tauri main process needs: - A "Configure IM adapters" settings page (App ID/Secret, bot token, allowed users) that writes ~/.claude/adapters.json - A "Start/stop Feishu" / "Start/stop Telegram" toggle that spawns `claude-sidecar adapters --feishu` (or both) as a managed sidecar, monitors lifecycle, restarts on crash The runtime infrastructure is now in place — that work is purely UI + Rust spawn glue and can be done independently. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-12 00:44:35 +08:00
程序员阿江(Relakkes)	3c5549e221	experiment(desktop): merge server + cli into one sidecar binary ... Replaces the two ~65MB bun-compiled sidecar binaries with a single ~66MB merged binary. The bun runtime + shared dependency code (anthropic SDK, MCP SDK, ws, undici, etc) was previously duplicated across both — merging eliminates that duplication entirely. Combined with the previous P0 commit (static-import inlining + drop src/ + node_modules/ from Resources), this brings the macOS .app from the original 435MB baseline down to 87MB (-80%), and the DMG from 113MB to 37MB (-67%). Final breakdown of the 87MB .app: Contents/MacOS/claude-sidecar 66MB (was 57+57=114MB) Contents/MacOS/claude-code-desktop 18MB (Tauri Rust main) Contents/Resources/icon.icns 2MB + plist + frameworks ~1MB This is essentially the floor — bun runtime + Tauri main + minimum overhead. Going lower would require swapping toolchains. Implementation ============== * desktop/sidecars/claude-sidecar.ts (new): single entrypoint that takes a positional mode argument ("server" or "cli") then dispatches via `await import('../../src/server/index.ts').startServer()` or `await import('../../src/entrypoints/cli.tsx')`. Same env / argv setup pattern as the old launchers. * desktop/sidecars/server-launcher.ts + cli-launcher.ts: deleted. * desktop/scripts/build-sidecars.ts: compiles only claude-sidecar now. * desktop/src-tauri/tauri.conf.json: externalBin → ["binaries/claude-sidecar"] * desktop/src-tauri/src/lib.rs: spawns sidecar with leading "server" positional arg. * src/server/services/conversationService.ts resolveBundledCliPath / resolveCliArgs: when current process is claude-sidecar, reuses the same exe and spawns it with leading "cli" positional arg. Backward compat path for old claude-server / claude-cli pair preserved for the bin/claude-haha dev mode. Verification ============ * claude-sidecar cli --version → 999.0.0-local (Claude Code) ✓ * claude-sidecar cli --help → full Commander spec ✓ * claude-sidecar server --port N → HTTP listening, CronScheduler running ✓ * All three above run in /tmp with no src/ or node_modules/ on disk * bun test on src/ → 358 pass / 45 fail / 1 error, identical to baseline (44 fails are pre-existing on main, unrelated to this change) * Full DMG round-trip via build-macos-arm64.sh succeeds; new .app installs cleanly in /Volumes/ Bundle size summary (vs original baseline) ========================================== metric baseline final delta .app total 435 MB 87 MB -348 MB (-80%) .dmg 113 MB 37 MB -76 MB (-67%) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-12 00:10:47 +08:00