mirror of
https://github.com/tiennm99/ccs.git
synced 2026-10-05 00:13:20 +00:00
resolveImageAnalysisRuntimeStatus defaulted to DEFAULT_IMAGE_ANALYSIS_CONFIG when callers omitted the config argument. That constant ships empty profile_backends and a gemini fallback_backend, so the launch paths that call it without a config (settings profile dispatch and headless delegation) never saw user-configured mappings. A profile mapped to another backend still resolved to gemini, failed the Gemini auth check, and silently dropped to native Read. Profiles whose model has no vision support could not read images at all, even with a reachable CLIProxy and an authenticated backend. getImageAnalysisHookEnv already reads the saved config, so the launch env and the runtime status disagreed on the same launch: CCS_IMAGE_ANALYSIS_BACKEND_ID carried the mapped backend while the status object reported native-read. Default to getImageAnalysisConfig() so both read the same source. Callers that pass an explicit config keep their existing behavior. Co-Authored-By: Claude <noreply@anthropic.com>