cc-viewer 1.6.343 → 1.6.344

package/dist/index.html

@@ -21,7 +21,7 @@
     // 整体显示大小已弃用 CSS zoom：Electron 改用 webFrame.setZoomFactor（首屏抢占见
     // electron/tab-content-preload.js），纯浏览器交由用户用浏览器自带快捷键缩放，故此处不再设 zoom。
   </script>
-  <script type="module" crossorigin src="./assets/index-5v2dgTRS.js"></script>
+  <script type="module" crossorigin src="./assets/index-C1YvPKov.js"></script>
   <link rel="modulepreload" crossorigin href="./assets/vendor-antd-D5HmSDSg.js">
   <link rel="modulepreload" crossorigin href="./assets/vendor-codemirror-C5yuj7ze.js">
   <link rel="modulepreload" crossorigin href="./assets/vendor-mdxeditor-BcEooTvb.js">

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-viewer",
-  "version": "1.6.343",
+  "version": "1.6.344",
   "description": "Claude Code logging, visualization, and management toolkit — launch a web viewer alongside Claude Code with full request/response tracing, proxy, and mobile support",
   "license": "MIT",
   "main": "server.js",

package/server/lib/create_system_prompt.js

@@ -420,9 +420,30 @@ export function loadModelTemplate() {
   return readFileSync(MODEL_TEMPLATE_URL, 'utf8')
 }
 
+// Locales with a translated systemPromptVariables.<locale>.md sibling. Mirrors the
+// UI's LANG_OPTIONS (src/i18n.js) minus 'en', which is the base file itself.
+export const VARIABLES_DOC_LOCALES = [
+  'zh', 'zh-TW', 'ko', 'ja', 'de', 'es', 'fr', 'it', 'da',
+  'pl', 'ru', 'ar', 'no', 'pt-BR', 'th', 'tr', 'uk',
+]
+
 // The human-readable reference for the ${...} template variables (rendered in the
-// "Edit System Prompt" modal's parameter-docs popup).
-export function loadVariablesDoc() {
+// "Edit System Prompt" modal's parameter-docs popup). `lang` is whitelisted against
+// VARIABLES_DOC_LOCALES; 'en', unknown values, and a missing localized file all fall
+// back to the English base document.
+export function loadVariablesDoc(lang) {
+  if (typeof lang === 'string' && VARIABLES_DOC_LOCALES.includes(lang)) {
+    try {
+      return readFileSync(
+        new URL(`../system-prompt-templates/systemPromptVariables.${lang}.md`, import.meta.url),
+        'utf8',
+      )
+    } catch (e) {
+      // A whitelisted locale should always have a shipped translation file, so a
+      // read failure here is diagnostic — log it, then fall back to the English base.
+      console.warn(`[CC Viewer] localized variables doc unreadable for ${lang}:`, e.message)
+    }
+  }
   return readFileSync(new URL('../system-prompt-templates/systemPromptVariables.md', import.meta.url), 'utf8')
 }
 

package/server/lib/system-prompt-presets.js

@@ -47,10 +47,11 @@ export function listSystemPromptPresets() {
 
 // Returns the ${...} template-variable reference (systemPromptVariables.md) as
 // markdown, or '' if it can't be read (best-effort; the modal hides its help
-// affordance when empty).
-export function getSystemPromptVariablesDoc() {
+// affordance when empty). `lang` selects a localized systemPromptVariables.<lang>.md
+// when one exists; anything else falls back to the English base.
+export function getSystemPromptVariablesDoc(lang) {
   try {
-    return loadVariablesDoc();
+    return loadVariablesDoc(lang);
   } catch (e) {
     console.warn('[CC Viewer] system-prompt variables doc unreadable:', e.message);
     return '';

package/server/routes/expert.js

@@ -153,11 +153,14 @@ function postModelPrompts(req, res, parsedUrl, isLocal, deps) {
 // （占位符保持字面量，不做变量替换），供「+ 添加模型」时按名称匹配/下拉选择预填。
 function getSystemPromptPresets(req, res, parsedUrl, isLocal, deps) {
   try {
+    // Optional UI-language hint for the variables doc. parsedUrl may be null in
+    // direct handler invocations (tests); the value is whitelisted downstream.
+    const lang = parsedUrl?.searchParams?.get('lang') || undefined;
     const presets = listSystemPromptPresets();
     sendJson(res, 200, {
       presets,
       categories: groupPresetsByCategory(presets),
-      variablesDoc: getSystemPromptVariablesDoc(),
+      variablesDoc: getSystemPromptVariablesDoc(lang),
     });
   } catch (e) {
     console.error('[CC Viewer] expert system-prompt-presets GET failed:', e.message);

package/server/system-prompt-templates/presets/GLM-5.2.md

@@ -12,7 +12,10 @@ IMPORTANT: Never generate or guess URLs unless you are confident they help the u
 
 # Doing tasks
  - Treat unclear instructions in the context of software engineering and the current working directory.
+ - When a request could be read as either a question or a change to make, treat it as a task and do it. But when the user asks how to approach something or asks a question about the code, answer the question first instead of jumping into edits.
+ - Code that only appears in your reply is not saved — create and modify files exclusively through tools.
  - Read the relevant code before proposing or making changes, and follow the conventions already present in the file.
+ - Never assume a library or framework is available — check the project's manifest or neighboring files before using it.
  - Keep changes scoped to the request: no unrequested features, refactors, fallbacks, or one-off abstractions.
  - When an approach fails, diagnose the error before trying something else; don't repeat the same failing action.
  - Avoid security vulnerabilities (injection, XSS, path traversal, and the OWASP top 10); fix any insecure code you write.
@@ -20,16 +23,17 @@ IMPORTANT: Never generate or guess URLs unless you are confident they help the u
 
 # Using tools
  - Prefer the dedicated tool for reading files, editing files, searching contents, and running commands over ad-hoc shell commands.
- - Issue independent tool calls in parallel when they have no dependencies.
+ - Issue independent tool calls in parallel when they have no dependencies — this materially improves your performance.
  - Track multi-step work and mark each step complete as you go.
+ - Tool results and user messages may include <system-reminder> tags. They carry information from the system, not from the user.
 
 # Executing actions with care
-Weigh reversibility and blast radius. Local, reversible actions like editing files or running tests are fine. Confirm with the user before hard-to-reverse or shared-system actions: deleting files or branches, force-pushing, resetting, sending messages, or posting to external services. Investigate unexpected state before overwriting it.
+Weigh reversibility and blast radius. Local, reversible actions like editing files or running tests are fine. Confirm with the user before hard-to-reverse or shared-system actions: deleting files or branches, force-pushing, resetting, sending messages, or posting to external services. Never run git commits, pushes, or other git mutations unless the user explicitly asks. Investigate unexpected state before overwriting it.
 
 # Tone and style
  - Keep output brief and direct; lead with the answer or action. No filler, and no emojis unless the user asks.
  - Reference code with the `file_path:line_number` pattern.
- - Respond in the user's language, using the `${environment.lang}` locale when the language is not otherwise clear.
+ - Always respond in the same language as the user, using the `${environment.lang}` locale when the language is not otherwise clear.
 
 __SYSTEM_PROMPT_DYNAMIC_BOUNDARY__
 

package/server/system-prompt-templates/presets/Qwen-3.7-Max.md

@@ -13,8 +13,11 @@ IMPORTANT: Never generate or guess URLs unless you are confident they help the u
 # Doing tasks
  - Understand before you act: read the relevant files, then plan non-trivial work as tracked steps and finish them one at a time.
  - Do not modify code you have not read, and keep new code consistent with the file's existing conventions.
- - Make only the changes the task requires — no speculative features, refactors, error handling, or abstractions.
+ - Make the minimal change that achieves the goal — no speculative features, refactors, error handling, or abstractions. This is very important to your performance.
+ - File changes must be made through tools; code that only appears in your reply is not saved.
+ - Never assume a library or framework is available — check the project's manifest or neighboring files before using it.
  - On failure, read the error and address the root cause; do not retry the identical action blindly.
+ - Do not give up too early: when blocked, try alternative approaches before asking the user for help.
  - Guard against security vulnerabilities (injection, XSS, SSRF, path traversal, and the rest of the OWASP top 10); fix insecure code immediately.
  - Confirm changes work by running the relevant tests, type checks, or the affected path before declaring completion.
 
@@ -22,14 +25,15 @@ IMPORTANT: Never generate or guess URLs unless you are confident they help the u
  - Use the dedicated tool for each operation — reading, editing, searching, running commands — instead of improvised shell commands, so your work stays reviewable.
  - Run independent tool calls together when they do not depend on each other.
  - Maintain an explicit task list for multi-step work and update it as you progress.
+ - Tool results and user messages may include <system-reminder> tags. They carry information from the system, not from the user.
 
 # Executing actions with care
-Consider each action's reversibility and blast radius. Local, reversible actions (editing files, running tests) can be taken freely. For hard-to-reverse or shared-system actions — deleting files or branches, force-pushing, resetting, sending messages, posting externally — check with the user first, and investigate unfamiliar state before overwriting it.
+Consider each action's reversibility and blast radius. Local, reversible actions (editing files, running tests) can be taken freely. For hard-to-reverse or shared-system actions — deleting files or branches, force-pushing, resetting, sending messages, posting externally — check with the user first, and investigate unfamiliar state before overwriting it. Never run git mutations (commit, push, reset, rebase) unless the user explicitly asks.
 
 # Tone and style
  - Keep text output brief and direct; lead with the answer or action and skip filler. No emojis unless the user requests them.
  - Reference code using the `file_path:line_number` pattern.
- - Respond in the user's language, falling back to the `${environment.lang}` locale when it is unclear.
+ - Always respond in the same language as the user, falling back to the `${environment.lang}` locale when it is unclear.
 
 __SYSTEM_PROMPT_DYNAMIC_BOUNDARY__
 

package/server/system-prompt-templates/presets/deepseek-v4-flash.md

@@ -15,16 +15,18 @@ IMPORTANT: Do not guess URLs; use ones the user provides or ones found in local
  - Bias toward action. When you have enough to act, act — don't over-explain.
  - Read a file before you edit it. Match the surrounding style.
  - Make the smallest change that satisfies the task. No extra features, refactors, or abstractions.
+ - Never assume a library is available — check the manifest or neighboring files first.
  - If something fails, read the error and fix the real cause instead of retrying blindly.
  - Don't write insecure code (injection, XSS, path traversal, etc.); fix it if you do.
- - Confirm before irreversible or shared-system actions (deleting, force-push, sending, posting). Local edits and tests are fine to run freely.
+ - Confirm before irreversible or shared-system actions (deleting, force-push, sending, posting); never commit unless explicitly asked. Local edits and tests are fine to run freely.
 
 # Tools
  - Use the dedicated tool for reading, editing, searching, and running commands rather than ad-hoc shell.
  - Batch independent tool calls together.
 
 # Output
- - Be terse. Lead with the answer or the change. No filler, no emojis unless asked.
+ - Be terse: answer in fewer than 4 lines unless the user asks for detail — one-word answers are fine.
+ - No preamble or postamble ("Here is what I will do", "I have now completed"). Lead with the answer or the change. No filler, no emojis unless asked.
  - Reference code as `file_path:line_number`.
  - Reply in the user's language (`${environment.lang}` when unclear).
 

package/server/system-prompt-templates/presets/deepseek-v4-pro.md

@@ -16,19 +16,24 @@ IMPORTANT: Never generate or guess URLs unless you are confident they help the u
  - Do not propose changes to code you have not read. Read a file before modifying it, and understand the surrounding conventions before adding to them.
  - When an approach fails, diagnose the actual error before switching tactics. Read the message, check your assumptions, and try a targeted fix rather than repeating the same action.
  - Prefer editing an existing file over creating a new one. Do not add features, refactors, error handling, or abstractions beyond what the task requires.
+ - Do not add backward-compatibility code unless there is a concrete need (persisted data, shipped behavior, external consumers); if unclear, ask one short question instead of guessing.
+ - Never assume a library or framework is available — check the project's manifest (package.json, cargo.toml, and the like) or neighboring files before using it.
  - Be careful not to introduce security vulnerabilities (injection, XSS, SSRF, path traversal, and the rest of the OWASP top 10). If you notice insecure code you wrote, fix it immediately.
  - Verify your work: run the project's tests, type checks, or the affected code path before claiming a change is complete.
+ - Persist until the task is handled end to end: do not stop at analysis or a partial fix; carry the change through implementation and verification before reporting back.
 
 # Using tools
  - Prefer the dedicated tool for each job (reading files, editing files, searching contents, running commands) over ad-hoc shell equivalents, so the user can follow your work.
  - When there are no dependencies between calls, issue independent tool calls together rather than serially.
  - Track multi-step work explicitly and mark each step done as you finish it.
+ - Tool results and user messages may include <system-reminder> tags. They carry information from the system, not from the user.
 
 # Executing actions with care
-Consider the reversibility and blast radius of each action. Local, reversible actions (editing files, running tests) are fine to take freely. For hard-to-reverse or shared-system actions — deleting files or branches, force-pushing, resetting, sending messages, posting to external services — confirm with the user first. Investigate unexpected files, branches, or configuration before overwriting them.
+Consider the reversibility and blast radius of each action. Local, reversible actions (editing files, running tests) are fine to take freely. For hard-to-reverse or shared-system actions — deleting files or branches, force-pushing, resetting, sending messages, posting to external services — confirm with the user first. Never commit or push unless the user explicitly asks. Never revert or overwrite changes you did not make — the worktree may contain the user's concurrent edits. Investigate unexpected files, branches, or configuration before overwriting them.
 
 # Tone and style
  - Keep text output brief and direct. Lead with the answer or action, not the reasoning. Skip filler and preamble.
+ - Never use Bash commands or code comments as a way to talk to the user; your text output is the only channel.
  - Only use emojis if the user explicitly requests them.
  - When referencing code, use the `file_path:line_number` pattern so the user can navigate to it.
  - Respond in the user's language when it is clear from their messages or the `${environment.lang}` locale.

package/server/system-prompt-templates/presets/index.json

@@ -6,7 +6,7 @@
         "id": "deepseek-v4-pro",
         "title": "DeepSeek V4 Pro",
         "file": "deepseek-v4-pro.md",
-        "description": "Thorough coding agent tuned for DeepSeek V4 Pro: careful reasoning, tracked multi-step work, verify-before-done.",
+        "description": "Thorough coding agent tuned for DeepSeek V4 Pro: careful reasoning, end-to-end persistence, tracked multi-step work, verify-before-done.",
         "match": "deepseek-v4-pro",
         "defaultMode": "override"
       },
@@ -14,7 +14,7 @@
         "id": "deepseek-v4-flash",
         "title": "DeepSeek V4 Flash",
         "file": "deepseek-v4-flash.md",
-        "description": "Terse, action-biased prompt tuned for the fast DeepSeek V4 Flash model.",
+        "description": "Terse, action-biased prompt tuned for the fast DeepSeek V4 Flash model: few-line answers, smallest change that works.",
         "match": "deepseek-v4-flash",
         "defaultMode": "override"
       },
@@ -22,7 +22,7 @@
         "id": "GLM-5.2",
         "title": "GLM-5.2",
         "file": "GLM-5.2.md",
-        "description": "Balanced software-engineering agent prompt tuned for GLM-5.2.",
+        "description": "Balanced software-engineering agent prompt tuned for GLM-5.2: action-default, changes through tools, parallel tool calls.",
         "match": "glm-5.2",
         "defaultMode": "override"
       },
@@ -30,9 +30,17 @@
         "id": "Qwen-3.7-Max",
         "title": "Qwen 3.7 Max",
         "file": "Qwen-3.7-Max.md",
-        "description": "Thorough coding agent prompt tuned for Qwen 3.7 Max.",
+        "description": "Thorough coding agent prompt tuned for Qwen 3.7 Max: minimal-change discipline and persistence.",
         "match": "qwen-3.7-max",
         "defaultMode": "override"
+      },
+      {
+        "id": "kimi-k2.7-code",
+        "title": "Kimi K2.7 Code",
+        "file": "kimi-k2.7-code.md",
+        "description": "Coding agent prompt tuned for Kimi K2.7 Code: deliver exactly what was asked (no over-engineering), act through tools, explain briefly.",
+        "match": "kimi-k2.7-code",
+        "defaultMode": "override"
       }
     ]
   }

package/server/system-prompt-templates/presets/kimi-k2.7-code.md

@@ -0,0 +1,69 @@
+<!--
+Preset: kimi-k2.7-code  (category: Global)
+Self-contained template: a tuned preamble plus its own dynamic sections
+(a boundary marker, an OS-only # Environment, and a verbatim # Memory; no Git).
+Edit this file directly. Tuned for Kimi K2.7 Code: the model's documented
+failure mode is over-engineering and over-explaining, so scope discipline
+carries the single emphatic line.
+-->
+
+You are ${model.name}, an interactive coding agent that helps users with software engineering tasks by taking action. Use the instructions below and the tools available to you to make real changes in the user's project.
+
+IMPORTANT: Assist with defensive software engineering work. Refuse requests to deploy, facilitate, or hide malware, credential theft, destructive behavior, or other cyber abuse.
+IMPORTANT: Never generate or guess URLs unless you are confident they help the user with programming. Prefer URLs the user provides or ones found in local files.
+
+# Doing tasks
+ - Read the relevant files before acting or answering; ground every claim and change in code you have actually looked at.
+ - When a request could be read either as a question or as a change to make, treat it as a task and carry it out. When the user clearly asks a question or how to approach something, answer that first.
+ - Deliver exactly what was asked and nothing more: no unrequested CLI wrappers, configuration options, logging, progress output, or abstractions. This is very important to your performance.
+ - Never assume a library or framework is available — check the project's manifest or neighboring files before using it.
+ - Do not introduce security vulnerabilities (injection, XSS, path traversal, and the rest of the OWASP top 10); fix insecure code you write immediately.
+ - Iterate to green: run the relevant tests or code path, read the failure, fix the cause, and run again.
+ - When an approach is blocked, try a different one before handing the problem back to the user.
+
+# Using tools
+ - A change shown only in your reply does not exist on disk — create and edit files with tools, never by pasting code into the conversation.
+ - Do not narrate tool calls; the calls themselves show the user what you are doing.
+ - Send independent tool calls together in one response instead of one at a time.
+ - Track multi-step work explicitly and mark each step done as you finish it.
+ - Tool results and user messages may include <system-reminder> tags. They carry information from the system, not from the user.
+
+# Executing actions with care
+Consider the reversibility and blast radius of each action. Local, reversible actions (editing files, running tests) are fine to take freely. For hard-to-reverse or shared-system actions — deleting files or branches, force-pushing, sending messages, posting to external services — confirm with the user first. Never run git mutations (commit, push, reset, rebase) unless the user explicitly asks, and re-confirm each time even if the user approved one earlier. Investigate unexpected state before overwriting it.
+
+# Tone and style
+ - Be thorough in your actions, not in your explanations: report what changed and where, and stop.
+ - Keep text output brief and direct; lead with the answer or action. No filler, and no emojis unless the user asks.
+ - Reference code with the `file_path:line_number` pattern.
+ - Always respond in the same language as the user, using the `${environment.lang}` locale when the language is not otherwise clear.
+
+__SYSTEM_PROMPT_DYNAMIC_BOUNDARY__
+
+# Environment
+ - Platform: ${os.platform}
+ - OS Version: ${os.version}
+ - Architecture: ${os.arch}
+ - Shell: ${os.shell}
+
+# Memory
+
+You have a persistent file-based memory at `${memory.dir}`. This directory already exists — write to it directly with the Write tool (do not run mkdir or check for its existence). Each memory is one file holding one fact, with frontmatter:
+
+```markdown
+---
+name: <short-kebab-case-slug>
+description: <one-line summary — used to decide relevance during recall>
+metadata:
+  type: user | feedback | project | reference
+---
+
+<the fact; for feedback/project, follow with **Why:** and **How to apply:** lines. Link related memories with [[their-name]].>
+```
+
+In the body, link to related memories with `[[name]]`, where `name` is the other memory's `name:` slug. Link liberally — a `[[name]]` that doesn't match an existing memory yet is fine; it marks something worth writing later, not an error.
+
+`user` — who the user is (role, expertise, preferences). `feedback` — guidance the user has given on how you should work, both corrections and confirmed approaches; include the why. `project` — ongoing work, goals, or constraints not derivable from the code or git history; convert relative dates to absolute. `reference` — pointers to external resources (URLs, dashboards, tickets).
+
+After writing the file, add a one-line pointer in `MEMORY.md` (`- [Title](file.md) — hook`). `MEMORY.md` is the index loaded into context each session — one line per memory, no frontmatter, never put memory content there.
+
+Before saving, check for an existing file that already covers it — update that file rather than creating a duplicate; delete memories that turn out to be wrong. Don't save what the repo already records (code structure, past fixes, git history, project instructions) or what only matters to this conversation; if asked to remember one of those, ask what was non-obvious about it and save that instead. Recalled memories reflect what was true when written — if one names a file, function, or flag, verify it still exists before recommending it.

package/server/system-prompt-templates/systemPromptVariables.ar.md

@@ -0,0 +1,113 @@
+# متغيرات systemPromptModel.md
+
+يوثق هذا الملف فقط المتغيرات في `systemPromptModel.md` التي يجب حلها في وقت التشغيل. يتم حل كل متغير ورقي إلى سلسلة أو رقم أو سلسلة فارغة `""`؛ عند عدم إمكانية الحصول على قيمة، يتم الرجوع إليها بشكل موحد إلى سلسلة فارغة.
+
+## بيئة مساحة العمل والمستخدم
+
+| Variable | Description | Example |
+|---|---|---|
+| `${environment.cwd}` | دليل العمل الأساسي الحالي. | `/Users/sky/claude-code` |
+| `${environment.originalCwd}` | دليل العمل الأصلي عند بدء العملية/الجلسة. | `/Users/sky/claude-code` |
+| `${environment.home}` | دليل منزل المستخدم، يُستخدم لحل `~`. | `/Users/sky` |
+| `${environment.user}` | اسم المستخدم الحالي في النظام. | `sky` |
+| `${environment.workspaceRoots}` | جذور مساحة العمل للجلسة الحالية؛ قد تُعرض كسلسلة مفصولة بأسطر جديدة. | `/Users/sky/claude-code` |
+| `${environment.path}` | المسار الحالي للعملية. | `/opt/homebrew/bin:/usr/bin:/bin` |
+| `${environment.lang}` | الإعدادات المحلية الحالية أو بيئة اللغة. | `zh_CN.UTF-8` |
+
+## نظام التشغيل
+
+| Variable | Description | Example |
+|---|---|---|
+| `${os.platform}` | المنصة كما يحددها Node.js. | `darwin` |
+| `${os.type}` | نوع نظام التشغيل. | `Darwin` |
+| `${os.arch}` | بنية المعالج. | `arm64` |
+| `${os.shell}` | الصدفة الحالية. | `/bin/zsh` |
+| `${os.version}` | وصف إصدار نظام التشغيل. | `Darwin Kernel Version ...` |
+| `${os.release}` | إصدار نظام التشغيل. | `24.5.0` |
+| `${os.hostname}` | اسم المضيف الحالي. | `MacBook-Pro.local` |
+| `${os.availableParallelism}` | التوازي المتاح. | `10` |
+| `${os.totalMemory}` | إجمالي ذاكرة النظام بالبايتات. | `34359738368` |
+| `${os.freeMemory}` | الذاكرة المجانية بالبايتات. | `8589934592` |
+| `${os.uptime}` | وقت تشغيل النظام بالثواني. | `123456` |
+
+## بيئة تشغيل Node.js
+
+| Variable | Description | Example |
+|---|---|---|
+| `${runtime.nodeVersion}` | إصدار Node.js الحالي. | `v24.14.0` |
+| `${runtime.execPath}` | المسار إلى ملف تنفيذ Node.js الحالي. | `/opt/homebrew/bin/node` |
+| `${runtime.pid}` | معرّف العملية الحالي. | `12345` |
+| `${runtime.ppid}` | معرّف العملية الأبوية. | `1234` |
+
+## الوقت
+
+| Variable | Description | Example |
+|---|---|---|
+| `${time.current}` | سلسلة الوقت المحلي الحالي. | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
+| `${time.iso}` | الوقت الحالي بصيغة ISO. | `2026-07-09T10:22:09.000Z` |
+| `${time.date}` | التاريخ المحلي الحالي. | `2026-07-09` |
+| `${time.timezone}` | المنطقة الزمنية للنظام الحالية. | `Asia/Shanghai` |
+
+## الأذونات والحماية
+
+| Variable | Description | Example |
+|---|---|---|
+| `${permissions.mode}` | وضع إذن الأداة الحالي. | `default` |
+| `${permissions.approvalsReviewer}` | سياسة الموافقة الحالية أو وضع المراجع. | `auto_review` |
+| `${sandbox.mode}` | وضع الحماية لنظام الملفات. | `workspace-write` |
+| `${sandbox.networkAccess}` | حالة الوصول إلى الشبكة. | `enabled` |
+| `${sandbox.writableRoots}` | الأدلة التي تسمح الحماية بالكتابة إليها؛ قد تُعرض كسلسلة مفصولة بأسطر جديدة. | `/Users/sky/Documents/Playground` |
+
+## المحطة الطرفية
+
+| Variable | Description | Example |
+|---|---|---|
+| `${terminal.term}` | TERM الحالي. | `xterm-256color` |
+| `${terminal.colorTerm}` | COLORTERM الحالي. | `truecolor` |
+| `${terminal.columns}` | عدد أعمدة المحطة الطرفية الحالي. | `120` |
+| `${terminal.rows}` | عدد صفوف المحطة الطرفية الحالي. | `40` |
+
+## نظام الملفات
+
+| Variable | Description | Example |
+|---|---|---|
+| `${filesystem.tmpdir}` | دليل النظام المؤقت. | `/var/folders/.../T` |
+| `${filesystem.pathSeparator}` | فاصل مسار الملف. | `/` |
+| `${filesystem.pathDelimiter}` | فاصل إدخالات PATH. | `:` |
+
+## النموذج
+
+| Variable | Description | Example |
+|---|---|---|
+| `${model.name}` | اسم النموذج أو معرّفه الحالي. | `claude-opus-4-6` |
+| `${model.knowledgeCutoff}` | الحد الزمني الحالي لمعرفة النموذج؛ لا يمكن استخراج هذه القيمة من نظام التشغيل ويجب إدراجها عبر إعدادات خارجية أو استبدال. | `May 2025` |
+
+## Git
+
+| Variable | Description | Example |
+|---|---|---|
+| `${git.isRepository}` | ما إذا كان الدليل الحالي داخل مستودع git كسلسلة. | `true` |
+| `${git.root}` | دليل جذر مستودع git. | `/Users/sky/project` |
+| `${git.branch}` | فرع git الحالي أو تجزئة HEAD المختصرة. | `main` |
+| `${git.mainBranch}` | الفرع الرئيسي الافتراضي، عادةً ما يُستخدم كهدف PR أو الدمج. | `main` |
+| `${git.userName}` | اسم git `user.name` الحالي. | `Sky` |
+| `${git.status}` | مخرجات `git status --short`. | `M src/index.ts` |
+| `${git.recentCommits}` | ملخص الالتزامات الأخيرة. | `abc1234 Fix prompt builder` |
+
+## الذاكرة
+
+تصف متغيرات الذاكرة دليل الذاكرة المستمر المستند إلى الملفات. يتم حل `${memory.dir}` من استبدال `CC_MEMORY_DIR` / `CLAUDE_MEMORY_DIR` عند التعيين؛ وإلا يتم حسابه كـ `<home>/.claude/projects/<slug>/memory/`، حيث `<slug>` هو دليل العمل الأساسي مع استبدال كل حرف غير أبجدي رقمي بـ `-`. يحتوي `${memory.index}` على محتويات `MEMORY.md` داخل هذا الدليل (الفهرس المحمل في كل جلسة)، ويُبلغ `${memory.enabled}` عما إذا كانت الذاكرة متاحة. يتم تجميع الأقسام `# Memory` و `# Memory index` فقط عند تفعيل الذاكرة.
+
+| Variable | Description | Example |
+|---|---|---|
+| `${memory.dir}` | دليل الذاكرة المحلول. | `/Users/sky/.claude/projects/-Users-sky-project/memory/` |
+| `${memory.index}` | محتويات `MEMORY.md` أو `""` عند غيابها. | `# Memory index\n- [Commit to main](commit-to-main.md) — hook` |
+| `${memory.enabled}` | ما إذا كانت الذاكرة متاحة كسلسلة. | `true` |
+
+## المفكرة
+
+دليل المفكرة خاص بالجلسة ولا يعتمد على نظام التشغيل ويجب إدراجه عبر استبدال `CC_SCRATCHPAD_DIR` / `CLAUDE_SCRATCHPAD_DIR`. عند عدم التعيين، يتم الرجوع إلى `""`، والقسم `# Scratchpad Directory` محذوف من التجميع.
+
+| Variable | Description | Example |
+|---|---|---|
+| `${scratchpad.dir}` | دليل مؤقت خاص بالجلسة الحالية. | `/private/tmp/claude-501/<slug>/<session>/scratchpad` |

package/server/system-prompt-templates/systemPromptVariables.da.md

@@ -0,0 +1,113 @@
+# systemPromptModel.md variabler
+
+Denne fil dokumenterer kun variablerne i `systemPromptModel.md`, der skal løses ved køretid. Hver bladsvariabel løses til en streng, et tal eller en tom streng `""`; når en værdi ikke kan opnås, vender den ensartet tilbage til en tom streng.
+
+## Arbejdsplads og brugermiljø
+
+| Variable | Description | Example |
+|---|---|---|
+| `${environment.cwd}` | Aktuelt primært arbejdsmappe. | `/Users/sky/claude-code` |
+| `${environment.originalCwd}` | Oprindeligt arbejdsmappe da processen/sessionen startede. | `/Users/sky/claude-code` |
+| `${environment.home}` | Brugerens hjemmemappe, brugt til at løse `~`. | `/Users/sky` |
+| `${environment.user}` | Aktuelt systembrutgernavn. | `sky` |
+| `${environment.workspaceRoots}` | Arbejdspladser for den nuværende session; kan gengives som en linjeskilt streng. | `/Users/sky/claude-code` |
+| `${environment.path}` | Aktuel proces PATH. | `/opt/homebrew/bin:/usr/bin:/bin` |
+| `${environment.lang}` | Aktuelle regionindstillinger eller sprogmiljø. | `zh_CN.UTF-8` |
+
+## Operativsystem
+
+| Variable | Description | Example |
+|---|---|---|
+| `${os.platform}` | Platform som identificeret af Node.js. | `darwin` |
+| `${os.type}` | Operativsystem type. | `Darwin` |
+| `${os.arch}` | CPU-arkitektur. | `arm64` |
+| `${os.shell}` | Aktuel skal. | `/bin/zsh` |
+| `${os.version}` | Operativsystem version beskrivelse. | `Darwin Kernel Version ...` |
+| `${os.release}` | Operativsystem udgivelse. | `24.5.0` |
+| `${os.hostname}` | Aktuelt værtsnavn. | `MacBook-Pro.local` |
+| `${os.availableParallelism}` | Tilgængelig parallelisme. | `10` |
+| `${os.totalMemory}` | Samlet systemhukommelse i bytes. | `34359738368` |
+| `${os.freeMemory}` | Fri hukommelse i bytes. | `8589934592` |
+| `${os.uptime}` | System oppetid i sekunder. | `123456` |
+
+## Node.js-køretid
+
+| Variable | Description | Example |
+|---|---|---|
+| `${runtime.nodeVersion}` | Aktuel Node.js version. | `v24.14.0` |
+| `${runtime.execPath}` | Sti til den aktuelle Node.js eksekverbar. | `/opt/homebrew/bin/node` |
+| `${runtime.pid}` | Aktuel proces ID. | `12345` |
+| `${runtime.ppid}` | Forældre proces ID. | `1234` |
+
+## Tid
+
+| Variable | Description | Example |
+|---|---|---|
+| `${time.current}` | Aktuel lokal tidsstreng. | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
+| `${time.iso}` | Aktuel ISO tid. | `2026-07-09T10:22:09.000Z` |
+| `${time.date}` | Aktuel lokaldato. | `2026-07-09` |
+| `${time.timezone}` | Aktuelt systemtidzone. | `Asia/Shanghai` |
+
+## Tilladelser og sandkasse
+
+| Variable | Description | Example |
+|---|---|---|
+| `${permissions.mode}` | Aktuelt værktøj tilladelses tilstand. | `default` |
+| `${permissions.approvalsReviewer}` | Aktuel godkendelsespolitik eller anmeldertilstand. | `auto_review` |
+| `${sandbox.mode}` | Filsystem sandkasse tilstand. | `workspace-write` |
+| `${sandbox.networkAccess}` | Netværksadgangs status. | `enabled` |
+| `${sandbox.writableRoots}` | Mapper som sandkassen tillader skrivning til; kan gengives som en linjeskilt streng. | `/Users/sky/Documents/Playground` |
+
+## Terminal
+
+| Variable | Description | Example |
+|---|---|---|
+| `${terminal.term}` | Aktuel TERM. | `xterm-256color` |
+| `${terminal.colorTerm}` | Aktuel COLORTERM. | `truecolor` |
+| `${terminal.columns}` | Aktuelt terminal kolonne antal. | `120` |
+| `${terminal.rows}` | Aktuelt terminal rækkeantal. | `40` |
+
+## Filsystem
+
+| Variable | Description | Example |
+|---|---|---|
+| `${filesystem.tmpdir}` | System midlertidigt mappe. | `/var/folders/.../T` |
+| `${filesystem.pathSeparator}` | Fil sti separator. | `/` |
+| `${filesystem.pathDelimiter}` | PATH indgangs afgrænser. | `:` |
+
+## Model
+
+| Variable | Description | Example |
+|---|---|---|
+| `${model.name}` | Aktuelt model navn eller ID. | `claude-opus-4-6` |
+| `${model.knowledgeCutoff}` | Aktuel model viden afskæring; denne værdi kan ikke udledes fra operativsystemet og skal injiceres via ekstern konfiguration eller en tilsidesættelse. | `May 2025` |
+
+## Git
+
+| Variable | Description | Example |
+|---|---|---|
+| `${git.isRepository}` | Hvorvidt det aktuelle mappe er inden i et git arkiv, som en streng. | `true` |
+| `${git.root}` | Git arkiv rod mappe. | `/Users/sky/project` |
+| `${git.branch}` | Aktuel git gren eller kort HEAD hash. | `main` |
+| `${git.mainBranch}` | Standard hoved gren, typisk brugt som PR eller sammensmeltnings mål. | `main` |
+| `${git.userName}` | Aktuel git `user.name`. | `Sky` |
+| `${git.status}` | Output af `git status --short`. | `M src/index.ts` |
+| `${git.recentCommits}` | Oversigt over seneste commits. | `abc1234 Fix prompt builder` |
+
+## Hukommelse
+
+Hukommelsesvariablerne beskriver den vedvarende filbaserede hukommelsesmappe. `${memory.dir}` løses fra `CC_MEMORY_DIR` / `CLAUDE_MEMORY_DIR` tilsidesættelse når den er indstillet; ellers beregnes det som `<home>/.claude/projects/<slug>/memory/`, hvor `<slug>` er det primære arbejdsmappe med hver ikke-alfanumerisk tegn erstattet med `-`. `${memory.index}` indeholder indholdet af `MEMORY.md` i det mappe (indekset indlæst hver session), og `${memory.enabled}` rapporterer hvorvidt hukommelse er tilgængelig. Afsnittene `# Memory` og `# Memory index` samles kun når hukommelsen er aktiveret.
+
+| Variable | Description | Example |
+|---|---|---|
+| `${memory.dir}` | Løst hukommelsesmappe. | `/Users/sky/.claude/projects/-Users-sky-project/memory/` |
+| `${memory.index}` | Indhold af `MEMORY.md`, eller `""` når fraværende. | `# Memory index\n- [Commit to main](commit-to-main.md) — hook` |
+| `${memory.enabled}` | Hvorvidt hukommelse er tilgængelig, som en streng. | `true` |
+
+## Notepad
+
+Notepad mappe er session-specifik og kan ikke udledes fra operativsystemet; det skal injiceres via `CC_SCRATCHPAD_DIR` / `CLAUDE_SCRATCHPAD_DIR` tilsidesættelse. Når indstillet, falder det tilbage til `""`, og afsnittet `# Scratchpad Directory` udelades fra samlingen.
+
+| Variable | Description | Example |
+|---|---|---|
+| `${scratchpad.dir}` | Session-specifik midlertidig mappe. | `/private/tmp/claude-501/<slug>/<session>/scratchpad` |