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)	662485c3eb	experiment(desktop): static-import sidecars + drop src/ + node_modules/ from bundle ... Cuts the macOS .app from 435MB → 152MB (-65%) and the DMG from 113MB → 60MB (-47%) by inlining src/server and src/entrypoints/cli into the bun-compiled sidecar binaries instead of dynamic-importing them from disk at runtime. Architectural change ==================== Before: desktop/sidecars/server-launcher.ts → bun build --compile (≈57MB shell) └─ at runtime: dynamic file:// import of <appRoot>/src/server/index.ts which transitively requires ALL of src/ + the entire root node_modules/ to be shipped as Resource. tauri.conf.json copied 254M of node_modules and 47M of src/ into Contents/Resources/app/ on every build. After: desktop/sidecars/server-launcher.ts → bun build --compile (≈65MB) └─ uses `await import('../../src/server/index.ts')` with a literal specifier so bun's bundler walks the whole graph statically and inlines everything into the binary. Same treatment for cli-launcher.ts → src/entrypoints/cli.tsx. Resolver gymnastics =================== This fork carries dozens of ant-internal feature() gated require/import calls referencing modules that simply don't exist on disk (cachedMicrocompact, devtools, proactive, coordinator, etc). Bun's resolver walks the static dep graph BEFORE bun:bundle macro DCE, so even though the dead branches never execute at runtime, they still fail to resolve at compile time. Two complementary mechanisms: 1. desktop/scripts/scan-missing-imports.ts walks src/, regex-greps every relative import / require / type-import specifier, and writes a Proxy noop stub for any target that doesn't exist on disk. Stubs are tagged with "@generated stub from scan-missing-imports" for idempotency. Text resources (.md / .txt / .json) get appropriate format-specific stubs. Runs as a pre-step inside build:sidecars. 2. desktop/scripts/build-sidecars.ts adds an `external: [...]` list for bare-package optional deps not in package.json (OTLP exporters, @aws-sdk/*, @anthropic-ai/{bedrock,vertex,foundry,mcpb}-sdk, @azure/identity, fflate, turndown, sharp, react-devtools-core). These remain runtime imports, fail benignly when their gating env var or feature flag is off. Tauri side ========== - desktop/src-tauri/tauri.conf.json: dropped all `resources` entries. Was 7 entries totaling ≈301MB. Now `{}`. - desktop/src-tauri/src/lib.rs `resolve_app_root` no longer calls BaseDirectory::Resource (the app/ resource dir doesn't exist anymore); instead returns the directory of the current sidecar exe. The launchers still accept --app-root for backward compat with conversationService's CLI subprocess spawn. Optimisations ============= - bun build now uses minify whitespace+identifiers+syntax. Saved another ≈16MB across both binaries (server: 72MB→65MB, cli: 75MB→66MB). Bonus fix ========= src/services/remoteManagedSettings/index.ts had a typo importing './securityCheck.jsx' instead of '.js'. Bun's runtime resolver tolerated it; bun build didn't. Verification ============ - Both binaries boot successfully in /tmp with no src/ or node_modules/ on disk. Verified `claude-cli --version` returns the build version, `claude-cli --help` prints the full Commander spec, and claude-server starts CronScheduler + listens on the requested port. - bun test on src/ shows 358 pass / 45 fail / 2 errors vs main baseline of 359 / 44 / 2 — net 0 new failures (1 different flake direction). All 44 baseline failures pre-exist on main and are unrelated. - Full DMG round-trip via build-macos-arm64.sh succeeds; new bundle installs cleanly in /Volumes/. Bundle size summary =================== metric baseline after P0 delta Resources/app/ 301 MB 0 MB -301 MB MacOS/claude-server 57 MB 65 MB +8 MB MacOS/claude-cli 57 MB 66 MB +9 MB MacOS/claude-code-desktop 18 MB 18 MB — ───────────────────────────────────────────── .app total 435 MB 152 MB -283 MB (-65%) .dmg 113 MB 60 MB -53 MB (-47%) Generated stub files (173 of them under src/) are committed for reproducibility — the scanner is idempotent and will re-create them identically on every build, but tracking them avoids dirty working trees on first compile. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-12 00:05:39 +08:00