cc-viewer 1.6.282 → 1.6.284

package/server/proxy.js

@@ -6,26 +6,26 @@ import { homedir } from 'node:os';
 import * as interceptor from './interceptor.js';
 import { setupInterceptor } from './interceptor.js';
 import { extractApiErrorMessage, formatProxyRequestError } from './lib/proxy-errors.js';
+import { getProxyDispatcher } from './lib/proxy-env.js';
 import { getClaudeConfigDir } from '../findcc.js';
 
 // Setup interceptor to patch fetch
 setupInterceptor();
 
-// Node bundled undici 在 22.15 之前不识 zstd；上游若选 zstd 压缩，response.body 会被原样
-// 透传给 Claude CLI，触发 "Failed to parse JSON"。在转发前从 accept-encoding 摘掉 zstd，
-// 让上游回退到 gzip/deflate/br——所有 Node 版本都能正确解。
-export function stripZstdAcceptEncoding(headers) {
+// 强制上游返回未压缩响应，取代仅剥 zstd 的旧策略。
+// 原因：链路中的网关/代理（典型是本地 MITM 网络代理）可能把上游的压缩 body 原样透传，
+// 却把 content-encoding 响应头剥掉。undici 看不到 content-encoding 就不会解压，于是把一坨
+// gzip 字节当明文交回；本代理再把它当 SSE 透传给 Claude CLI →
+// "API returned an empty or malformed response (HTTP 200)"。
+// 让上游直接不压缩，整条链路就没有可被剥离/错配的 content-encoding，从根上消除这类问题。
+export function forceIdentityAcceptEncoding(headers) {
   if (!headers) return headers;
-  const key = Object.keys(headers).find(k => k.toLowerCase() === 'accept-encoding');
-  if (!key) return headers;
-  const val = headers[key];
-  if (typeof val !== 'string' || !/\bzstd\b/i.test(val)) return headers;
-  const filtered = val
-    .split(',')
-    .map(s => s.trim())
-    .filter(s => s && !/^zstd(\s*;.*)?$/i.test(s))
-    .join(', ');
-  return { ...headers, [key]: filtered || 'gzip, deflate, br' };
+  const out = {};
+  for (const k of Object.keys(headers)) {
+    if (k.toLowerCase() !== 'accept-encoding') out[k] = headers[k];
+  }
+  out['accept-encoding'] = 'identity';
+  return out;
 }
 
 // 代理会改写请求 body（interceptor 的模型替换 JSON.parse→改 model→JSON.stringify），
@@ -97,7 +97,7 @@ export function startProxy() {
         // Convert incoming headers
         let headers = { ...req.headers };
         delete headers.host; // Let fetch set the host
-        headers = stripZstdAcceptEncoding(headers);
+        headers = forceIdentityAcceptEncoding(headers); // 让上游不压缩，规避网关剥 content-encoding 头导致的 body 错配
         headers = stripContentLengthHeader(headers); // body 会被改写，旧 content-length 必须丢弃
 
         const buffers = [];
@@ -119,6 +119,14 @@ export function startProxy() {
           fetchOptions.body = body;
         }
 
+        // 走用户的网络代理：Node 内置全局 fetch 既不读 http_proxy/https_proxy，也看不到
+        // userland undici 的 setGlobalDispatcher，必须把代理 dispatcher 显式传进来，否则
+        // 上游请求会绕过代理直连 api.anthropic.com（详见 lib/proxy-env.js 注释）。
+        const proxyDispatcher = getProxyDispatcher();
+        if (proxyDispatcher) {
+          fetchOptions.dispatcher = proxyDispatcher;
+        }
+
         // 拼接完整 URL，保留 originalBaseUrl 中的路径前缀
         const cleanBase = originalBaseUrl.endsWith('/') ? originalBaseUrl.slice(0, -1) : originalBaseUrl;
         const cleanReq = req.url.startsWith('/') ? req.url.slice(1) : req.url;

package/server/routes/ultra-agents.js

@@ -0,0 +1,20 @@
+// ultraplan 预设专家路由 —— 枚举随包发布的 ultraAgents/*.json 供前端「添加预设专家」弹窗使用。
+// 无参数、不读项目目录：listUltraAgents() 默认 dir = ULTRA_AGENTS_DIR（包内置目录），
+// 不接受任何 query/body，杜绝路径穿越与越权读取被查看项目的风险。
+import { listUltraAgents } from '../lib/ultra-agents-api.js';
+
+async function ultraAgentsList(req, res) {
+  try {
+    const agents = listUltraAgents();
+    res.writeHead(200, { 'Content-Type': 'application/json' });
+    res.end(JSON.stringify({ ok: true, agents }));
+  } catch (err) {
+    console.error('[api/ultra-agents]', err);
+    res.writeHead(500, { 'Content-Type': 'application/json' });
+    res.end(JSON.stringify({ error: 'internal_error' }));
+  }
+}
+
+export const ultraAgentsRoutes = [
+  { method: 'GET', match: 'exact', path: '/api/ultra-agents', handler: ultraAgentsList },
+];

package/server/server.js

@@ -21,6 +21,7 @@ import { pluginsRoutes } from './routes/plugins.js';
 import { logsRoutes } from './routes/logs.js';
 import { voicePackRoutes } from './routes/voice-pack.js';
 import { skillsRoutes } from './routes/skills.js';
+import { ultraAgentsRoutes } from './routes/ultra-agents.js';
 import { filesContentRoutes } from './routes/files-content.js';
 import { filesFsRoutes } from './routes/files-fs.js';
 import { workspacesRoutes } from './routes/workspaces.js';
@@ -510,6 +511,7 @@ const _routes = [
   ...logsRoutes,
   ...voicePackRoutes,
   ...skillsRoutes,
+  ...ultraAgentsRoutes,
   ...filesContentRoutes,
   ...filesFsRoutes,
   ...workspacesRoutes,

package/ultraAgents/README.md

@@ -0,0 +1,62 @@
+# ultraAgents — 预设专家 (Preset ultraplan experts)
+
+本目录随 cc-viewer 包发布。其中每个 `*.json` 文件定义一个「预设专家」，会出现在
+**UltraPlan → 自定义专家编辑器 → 「载入模版」** 弹窗中，供用户选中后将名称与内容
+一键载入编辑面板（再按需改写并另存为自己的自定义专家）。
+
+> 加载入口：服务端 `GET /api/ultra-agents`（只读本目录、无参数），实现见
+> `server/lib/ultra-agents-api.js`。本目录中的非 `*.json` 文件（如本 README）会被忽略。
+
+## JSON 格式
+
+```jsonc
+{
+  "id": "code-expert",          // 必填。唯一标识,仅 [A-Za-z0-9._-]、长度 ≤200、不以 . 开头。
+                                //       仅作去重键(同 id 取文件名排序靠前者),不参与拼路径。
+  "version": 1,                 // 可选。前向兼容标记,当前加载器忽略(不读不校验)。
+  "title":       { "zh": "代码专家", "en": "Code Expert" },  // 必填。专家名称,内联本地化,见下。
+  "description": { "zh": "资深工程师…", "en": "Senior engineer…" }, // 可选。一句话描述,内联本地化。
+  "content":     "<system-reminder>\n…\n</system-reminder>"  // 必填。单语言正文,见下「content」。
+}
+```
+
+### title / description：在 JSON 协议层内联本地化
+
+`title` 与 `description` 两个字段都支持两种写法，**本地化在 JSON 协议层内联完成**（不依赖外部 i18n）：
+
+- **纯字符串**：所有语言都用同一份文本。
+- **本地化对象** `{ "zh": "…", "en": "…", "zh-TW": "…" }`：前端按当前界面语言解析，
+  回退顺序为 **精确语言 → 去区域的主语言（`zh-TW`→`zh`、`pt-BR`→`pt`）→ `en` → `zh`
+  → 首个非空值**（解析逻辑见 `src/utils/resolveLocalized.js`）。
+
+因此一个文件即可覆盖任意多种语言；未列出的界面语言走上述回退。
+
+### content：单语言
+
+`content` 是**单语言字符串**（不做本地化）。载入并保存后，发送给 Claude Code 时被当作 ultraplan
+的作用域指令；若 `content`（trim 后）以 `<system-reminder>` 开头，则原样使用、**不会被二次包裹**
+（见 `buildCustomTemplate`，`src/utils/ultraplanTemplates.js`）。因此预设 `content` 建议以
+`<system-reminder>`、`[SCOPED INSTRUCTION]` 风格书写。
+
+> 内置 `code-expert` / `research-expert` 的 `content` **直接取自**
+> `src/utils/ultraplanTemplates.js` 的 `ULTRAPLAN_VARIANTS.codeExpert` / `researchExpert`，
+> 并由 `test/ultra-agents-api.test.js` 钉死逐字节一致——改正文请改那个源文件后重新生成本目录 JSON，
+> 不要在此手写另一份。
+
+## 校验与限制
+
+加载时对每个文件做防御性校验，不合法者仅 `console.warn` 跳过、不影响其它文件：
+
+- 必须是合法 JSON 的**普通对象**（非数组/标量）。
+- `id` 通过上述规则；`title`、`content` 为「非空字符串」或「至少含一个非空字符串值的对象」。
+- 单文件 **≤ 256KB**，超出跳过；有效专家 **≤ 100** 个，超出忽略。
+- `description` 缺失或非法时按空串处理。
+
+## 现有 demo
+
+| 文件 | 专家 | `title` / `description` | `content` 来源 |
+| --- | --- | --- | --- |
+| `code-expert.json` | 代码专家 / Code Expert | 内联本地化(全 18 语言) | `ULTRAPLAN_VARIANTS.codeExpert` |
+| `research-expert.json` | 调研专家 / Research Expert | 内联本地化(全 18 语言) | `ULTRAPLAN_VARIANTS.researchExpert` |
+
+新增预设：在本目录放一个新的 `*.json`（建议文件名与 `id` 一致），重启/刷新即可在弹窗中看到。

package/ultraAgents/code-expert.json

@@ -0,0 +1,45 @@
+{
+  "id": "code-expert",
+  "version": 1,
+  "title": {
+    "zh": "代码专家",
+    "en": "Code Expert",
+    "zh-TW": "程式碼專家",
+    "ko": "코드 전문가",
+    "ja": "コード専門家",
+    "de": "Code-Experte",
+    "es": "Experto en código",
+    "fr": "Expert en code",
+    "it": "Esperto di codice",
+    "da": "Kodeekspert",
+    "pl": "Ekspert ds. kodu",
+    "ru": "Эксперт по коду",
+    "ar": "خبير الأكواد",
+    "no": "Kodeekspert",
+    "pt-BR": "Especialista em código",
+    "th": "ผู้เชี่ยวชาญด้านโค้ด",
+    "tr": "Kod uzmanı",
+    "uk": "Експерт із коду"
+  },
+  "description": {
+    "zh": "资深工程师：多智能体探索 + 计划评审 + 高质量实现，专注代码审查、重构、性能与可维护性。",
+    "en": "Senior engineer: multi-agent exploration, plan review and high-quality implementation — code review, refactor, performance, maintainability.",
+    "zh-TW": "資深工程師：多智能體探索 + 計畫評審 + 高品質實作，專注程式碼審查、重構、效能與可維護性。",
+    "ko": "시니어 엔지니어: 멀티 에이전트 탐색 + 계획 검토 + 고품질 구현 — 코드 리뷰, 리팩터링, 성능, 유지보수성에 집중.",
+    "ja": "シニアエンジニア：マルチエージェント探索 + 計画レビュー + 高品質な実装 — コードレビュー、リファクタリング、性能、保守性に注力。",
+    "de": "Senior-Ingenieur: Multi-Agent-Exploration, Planprüfung und hochwertige Umsetzung – Code-Review, Refactoring, Performance, Wartbarkeit.",
+    "es": "Ingeniero sénior: exploración multiagente, revisión de planes e implementación de alta calidad: revisión de código, refactorización, rendimiento y mantenibilidad.",
+    "fr": "Ingénieur senior : exploration multi-agents, revue de plan et implémentation de haute qualité — revue de code, refactorisation, performance, maintenabilité.",
+    "it": "Ingegnere senior: esplorazione multi-agente, revisione del piano e implementazione di alta qualità — revisione del codice, refactoring, prestazioni, manutenibilità.",
+    "da": "Senioringeniør: multi-agent-udforskning, plangennemgang og implementering af høj kvalitet – kodegennemgang, refaktorering, ydeevne, vedligeholdelse.",
+    "pl": "Starszy inżynier: eksploracja wieloagentowa, przegląd planu i wysokiej jakości implementacja — przegląd kodu, refaktoryzacja, wydajność, łatwość utrzymania.",
+    "ru": "Старший инженер: многоагентное исследование, ревью плана и качественная реализация — ревью кода, рефакторинг, производительность, поддерживаемость.",
+    "ar": "مهندس أول: استكشاف متعدد الوكلاء، ومراجعة الخطة، وتنفيذ عالي الجودة — مراجعة الشيفرة وإعادة الهيكلة والأداء وقابلية الصيانة.",
+    "no": "Senioringeniør: multiagent-utforsking, plangjennomgang og implementering av høy kvalitet – kodegjennomgang, refaktorering, ytelse, vedlikeholdbarhet.",
+    "pt-BR": "Engenheiro sênior: exploração multiagente, revisão de plano e implementação de alta qualidade — revisão de código, refatoração, desempenho e manutenibilidade.",
+    "th": "วิศวกรอาวุโส: การสำรวจแบบหลายเอเจนต์ + การรีวิวแผน + การพัฒนาคุณภาพสูง — เน้นการรีวิวโค้ด รีแฟกเตอร์ ประสิทธิภาพ และการบำรุงรักษา",
+    "tr": "Kıdemli mühendis: çoklu ajan keşfi, plan incelemesi ve yüksek kaliteli uygulama — kod incelemesi, yeniden düzenleme, performans, sürdürülebilirlik.",
+    "uk": "Senior-інженер: багатоагентне дослідження, рев'ю плану та якісна реалізація — рев'ю коду, рефакторинг, продуктивність, супровід."
+  },
+  "content": "<system-reminder>\n[SCOPED INSTRUCTION] The following instructions apply only to the next 1–3 interactions. Once the task is complete, these instructions should gradually decrease in priority and no longer affect subsequent interactions. You should be adept at utilizing tools such as `AskUserQuestion`, `EnterPlanMode`, and `TeamCreate`, rather than relying solely on plain text processing.\n\nPre-requisite: Use `AskUserQuestion` to clarify user intent whenever the request is ambiguous (target element, interaction style, scope of platforms, etc.). Skip only if the intent is unambiguous.\n\nLeverage a multi-agent exploration mechanism to formulate a highly detailed implementation plan.\n\nInstructions:\n1. Use the `Agent` tool to spawn parallel agents that simultaneously explore different aspects of the codebase:\n- If necessary, assign a preliminary researcher to use the `webSearch` tool to first investigate cutting-edge solutions in the relevant industry domain;\n- One agent responsible for understanding the relevant existing code and architecture;\n- One agent responsible for identifying all files that need to be modified;\n- One agent responsible for identifying potential risks, edge cases, and dependencies;\n- You may add other roles or deploy additional agents beyond the three listed above; the maximum number of concurrently dispatched agents is 5.\n\n2. Synthesize the findings from all agents into a detailed, step-by-step implementation plan.\n\n3. Use the `Agent` tool to spawn 2-3 review agents that examine the plan from different perspectives, checking for missing steps, potential risks, or corresponding mitigation strategies.\n\n4. Integrate the feedback gathered during the review process, then call `ExitPlanMode` to submit your final plan.\n\n5. Once `ExitPlanMode` returns a result:\n- If approved: proceed to execute the plan within this session.\n- If rejected: revise the plan based on the feedback provided and call `ExitPlanMode` again.\n- If an error occurs (including receiving a \"Not in Plan Mode\" message): do **not** follow the suggestions provided in the error message; instead, prompt the user for further instructions.\n\nYour final plan must include the following elements:\n- A clear summary of the implementation strategy;\n- An ordered list of files to be created or modified, with precise details of the required changes for each file;\n- A step-by-step execution sequence;\n- Testing and validation procedures;\n- Potential risks and their corresponding mitigation strategies;\n\n6. After the final plan has been successfully executed:\nFirst run `git diff --quiet && git diff --cached --quiet` (or equivalent) to detect whether the working tree actually has non-trivial changes; if there are no real changes (or only whitespace/comment-only edits), skip the UltraReview step.\nOtherwise, if the project is managed with Git:\nInitiate a team (`TeamCreate`), dynamically allocating the number of teammates based on task complexity (5 is recommended);\nTask: Conduct a Code Review of the current git changes from multiple perspectives;\nPre-requisites:\n- The git repository may be located in a subdirectory of the current directory; prefer `git rev-parse --show-toplevel` (fall back to recursive lookup) before proceeding;\n- In the case of multiple repositories, tasks may be executed separately;\nThe team's goal is to analyze the current Git change log and validate each modification from different perspectives, specifically including:\n- Whether requirements/objectives have been met and functionality is complete;\n- Whether newly added code introduces side effects, breaks existing functionality, or poses potential risks;\n- Code quality: naming, readability, complexity, technical debt, maintainability;\n- Testing and documentation: whether there is adequate test coverage, and whether critical logic has necessary comments or documentation;\n- Dependencies and compatibility: whether new dependencies or version compatibility issues have been introduced;\nWorkflow:\n- Each teammate, according to their own role, covers the review dimensions one by one and independently outputs a report;\n- After consolidating the reports, perform a cross-review to identify conflicts or shared concerns;\n- Distill specific, actionable modification suggestions and annotate them with priority levels (P0/P1/P2/P3);\n- Upon completion, adopt P0 items, and selectively adopt P1 items when they are concrete and low-risk; defer P2/P3 to backlog;\n- After execution is complete, close the team (`TeamDelete`);\n</system-reminder>"
+}

package/ultraAgents/research-expert.json

@@ -0,0 +1,45 @@
+{
+  "id": "research-expert",
+  "version": 1,
+  "title": {
+    "zh": "调研专家",
+    "en": "Research Expert",
+    "zh-TW": "調研專家",
+    "ko": "리서치 전문가",
+    "ja": "リサーチ専門家",
+    "de": "Recherche-Experte",
+    "es": "Experto en investigación",
+    "fr": "Expert en recherche",
+    "it": "Esperto di ricerca",
+    "da": "Researchekspert",
+    "pl": "Ekspert ds. badań",
+    "ru": "Эксперт по исследованиям",
+    "ar": "خبير الأبحاث",
+    "no": "Researchekspert",
+    "pt-BR": "Especialista em pesquisa",
+    "th": "ผู้เชี่ยวชาญด้านการวิจัย",
+    "tr": "Araştırma uzmanı",
+    "uk": "Експерт із досліджень"
+  },
+  "description": {
+    "zh": "资深调研分析师：多源检索 + 交叉求证 + 结构化产出，适合行业调研、竞品分析与可信报告撰写。",
+    "en": "Senior research analyst: multi-source search, cross-verification and structured deliverables — industry research, competitive analysis, credible reports.",
+    "zh-TW": "資深調研分析師：多源檢索 + 交叉求證 + 結構化產出，適合行業調研、競品分析與可信報告撰寫。",
+    "ko": "시니어 리서치 분석가: 다중 출처 검색 + 교차 검증 + 구조화된 산출물 — 산업 리서치, 경쟁사 분석, 신뢰할 수 있는 보고서.",
+    "ja": "シニアリサーチアナリスト：多源検索 + クロス検証 + 構造化された成果物 — 業界調査、競合分析、信頼できるレポート。",
+    "de": "Senior-Research-Analyst: Multi-Quellen-Suche, Kreuzverifizierung und strukturierte Ergebnisse – Branchenrecherche, Wettbewerbsanalyse, glaubwürdige Berichte.",
+    "es": "Analista de investigación sénior: búsqueda multifuente, verificación cruzada y entregables estructurados: investigación de mercado, análisis de la competencia e informes fiables.",
+    "fr": "Analyste de recherche senior : recherche multi-sources, vérification croisée et livrables structurés — étude de marché, analyse concurrentielle, rapports fiables.",
+    "it": "Analista di ricerca senior: ricerca multi-fonte, verifica incrociata e deliverable strutturati — ricerca di settore, analisi della concorrenza, report affidabili.",
+    "da": "Senior researchanalytiker: multikildesøgning, krydsverificering og strukturerede leverancer – brancheresearch, konkurrentanalyse, troværdige rapporter.",
+    "pl": "Starszy analityk badawczy: wyszukiwanie wieloźródłowe, weryfikacja krzyżowa i ustrukturyzowane wyniki — badania branżowe, analiza konkurencji, wiarygodne raporty.",
+    "ru": "Старший аналитик-исследователь: многоисточниковый поиск, перекрёстная проверка и структурированные результаты — отраслевые исследования, анализ конкурентов, достоверные отчёты.",
+    "ar": "محلل أبحاث أول: بحث متعدد المصادر، وتحقق متقاطع، ومخرجات منظمة — أبحاث السوق وتحليل المنافسين وتقارير موثوقة.",
+    "no": "Senior researchanalytiker: multikildesøk, kryssverifisering og strukturerte leveranser – bransjeresearch, konkurrentanalyse, troverdige rapporter.",
+    "pt-BR": "Analista de pesquisa sênior: busca multifonte, verificação cruzada e entregáveis estruturados — pesquisa de mercado, análise da concorrência e relatórios confiáveis.",
+    "th": "นักวิเคราะห์วิจัยอาวุโส: การค้นหาหลายแหล่ง + การตรวจสอบไขว้ + ผลงานเชิงโครงสร้าง — เหมาะกับการวิจัยอุตสาหกรรม การวิเคราะห์คู่แข่ง และการเขียนรายงานที่น่าเชื่อถือ",
+    "tr": "Kıdemli araştırma analisti: çok kaynaklı arama, çapraz doğrulama ve yapılandırılmış çıktılar — sektör araştırması, rekabet analizi, güvenilir raporlar.",
+    "uk": "Senior-аналітик досліджень: багатоджерельний пошук, перехресна перевірка та структуровані результати — галузеві дослідження, аналіз конкурентів, надійні звіти."
+  },
+  "content": "<system-reminder>\n[SCOPED INSTRUCTION] The following instructions are intended for the next 1–3 interactions. Once the task is complete, these instructions should be gradually deprioritized and no longer influence subsequent interactions.You should be adept at utilizing tools such as `AskUserQuestion`, `EnterPlanMode`, `WebSearch` and `TeamCreate`, rather than relying solely on plain text processing.\n\nPre-requisite: Use `AskUserQuestion` to clarify the research scope, target audience, and deliverable format whenever the user's intent is ambiguous. Skip only if the intent is unambiguous.\n\nLeverage a multi-agent exploration mechanism to formulate an exceptionally detailed implementation plan.\n\nInstructions:\n1. Utilize the Agent tool to spawn parallel agents that simultaneously explore various facets of the requirements:\n- If necessary, deploy a preliminary investigator to conduct an initial survey of industry-specific solutions using `webSearch`;\n- If necessary, deploy a specialized investigator to research authoritative sources—such as academic papers, news articles, and research reports—using `webSearch`;\n- Assign an agent to synthesize the target solution, while simultaneously verifying the rigor and credibility of the gathered papers, news, and research reports;\n- If necessary, assign an agent to analyze competitor data to provide supplementary analytical perspectives;\n- If necessary, assign an agent to handle the implementation of a product demo (generating outputs such as HTML, Markdown, etc.);\n- If the task is sufficiently complex, you may assign additional teammates to the roles defined above, or introduce other specialized roles; you are permitted to schedule up to 5 teammates concurrently.\n\n2. Synthesize the findings from the aforementioned agents into a comprehensive, step-by-step implementation plan.\n\n3. Utilize the Agent tool to spawn a set of parallel review agents; these agents shall scrutinize the plan from multiple roles and perspectives to identify any omitted steps and to propose reasonable additions or optimizations.\n\n4. Consolidate the feedback received from the review agents, then invoke `ExitPlanMode` to submit your final plan.\n\n5. Upon receiving the result from `ExitPlanMode`:\n- If Approved: Proceed to execute the plan within this current session.\n- If Rejected: Revise the plan based on the provided feedback, and then invoke `ExitPlanMode` once again.\n- If an Error Occurs (including the message \"Not in Plan Mode\"): Do *not* follow the suggestions provided by the error message; instead, prompt the user for further instructions.\n\nYour final plan must include the following elements:\n- A clear summary of the proposed implementation strategy;\n- An ordered list of files to be created or modified, specifying the exact changes required for each;\n- A step-by-step sequence for executing the implementation;\n- Identification of potential risks and corresponding mitigation strategies;\n- Creative ideation and suggestions for advanced enhancements;\n- If a product demo was generated, place the corresponding demo output in an appropriate location and notify the user.\n</system-reminder>"
+}