bingocode 1.1.126 → 1.1.128

package/.claude/settings.local.json

@@ -7,7 +7,14 @@
       "Bash(curl -s \"https://docs.anthropic.com/en/api/messages-streaming\" --max-time 30 -A \"Mozilla/5.0\")",
       "Bash(curl -sv \"https://docs.anthropic.com/en/api/messages\" --max-time 30)",
       "Bash(curl -sv \"https://raw.githubusercontent.com/anthropics/anthropic-sdk-python/main/api.md\" --max-time 30)",
-      "Bash(curl -s \"https://raw.githubusercontent.com/anthropics/anthropic-sdk-python/refs/heads/main/README.md\" --max-time 30)"
+      "Bash(curl -s \"https://raw.githubusercontent.com/anthropics/anthropic-sdk-python/refs/heads/main/README.md\" --max-time 30)",
+      "Bash(findstr /i goal)",
+      "Bash(bun run:*)",
+      "Bash(bunx tsc:*)",
+      "Bash(node_modules/.bin/tsc --noEmit --skipLibCheck)",
+      "WebFetch(domain:www.npmjs.com)",
+      "Bash(npm info:*)",
+      "Bash(npm pack:*)"
     ]
   }
 }

package/bin/bingo

@@ -18,10 +18,44 @@ fi
 
 cd "$ROOT_DIR"
 
+# ── bun 检测与自动安装 ──
+if ! command -v bun &>/dev/null && [[ ! -x "$HOME/.bun/bin/bun" ]]; then
+  echo "[bingocode] bun 未检测到，正在通过 npm 安装..."
+  _TMP_DIR="$(mktemp -d)"
+  _ARCH="$(uname -m)"
+  if [[ "$_ARCH" == "aarch64" || "$_ARCH" == "arm64" ]]; then
+    _BUN_PKG="@oven/bun-linux-aarch64"
+  else
+    _BUN_PKG="@oven/bun-linux-x64"
+  fi
+
+  if npm install "$_BUN_PKG" --prefix "$_TMP_DIR" --no-save --loglevel error; then
+    _BUN_SRC="$_TMP_DIR/node_modules/$_BUN_PKG/bin/bun"
+    if [[ -f "$_BUN_SRC" ]]; then
+      mkdir -p "$HOME/.bun/bin"
+      cp "$_BUN_SRC" "$HOME/.bun/bin/bun"
+      chmod +x "$HOME/.bun/bin/bun"
+      export PATH="$HOME/.bun/bin:$PATH"
+      echo "[bingocode] bun 安装完成，正在启动..."
+    else
+      echo "[bingocode] 安装失败：未找到 $_BUN_SRC" >&2
+      rm -rf "$_TMP_DIR"
+      exit 1
+    fi
+  else
+    echo "[bingocode] npm install $_BUN_PKG 失败，请手动安装 bun: https://bun.sh" >&2
+    rm -rf "$_TMP_DIR"
+    exit 1
+  fi
+  rm -rf "$_TMP_DIR"
+fi
+
+BUN_BIN="$(command -v bun 2>/dev/null || echo "$HOME/.bun/bin/bun")"
+
 if [[ -f .env ]]; then
   ENV_FILE_FLAG="--env-file=.env"
 else
   ENV_FILE_FLAG=""
 fi
 
-exec bun --preload ./preload.ts $ENV_FILE_FLAG ./src/entrypoints/manager.tsx "$@"
+exec "$BUN_BIN" --preload ./preload.ts $ENV_FILE_FLAG ./src/entrypoints/manager.tsx "$@"

package/bin/bingo-win.cjs

@@ -72,26 +72,44 @@ function bunExists() {
   }
 }
 
-// 安装 bun
+// 安装 bun（通过 npm 拉取官方包，不走 GitHub/bun.sh）
 function installBun() {
-  console.log('[bingocode] bun 未检测到，正在自动安装...');
+  console.log('[bingocode] bun 未检测到，正在通过 npm 安装...');
+
+  // 用 npm install 拉取平台对应包，安装到临时目录后复制 bun.exe
+  const tmpDir = path.join(os.tmpdir(), 'bingocode-bun-install');
   try {
-    const result = spawnSync(
-      'powershell',
-      ['-NoProfile', '-ExecutionPolicy', 'Bypass', '-Command',
-       'irm bun.sh/install.ps1 | iex'],
-      { stdio: 'inherit', shell: false }
+    fs.mkdirSync(tmpDir, { recursive: true });
+
+    // npm install @oven/bun-windows-x64 到临时目录
+    const npmResult = spawnSync(
+      'npm',
+      ['install', '@oven/bun-windows-x64', '--prefix', tmpDir, '--no-save', '--loglevel', 'error'],
+      { stdio: 'inherit', shell: true }
     );
-    if (result.status !== 0) {
-      throw new Error(`Exit code ${result.status}`);
+    if (npmResult.status !== 0) {
+      throw new Error(`npm install 失败，exit code ${npmResult.status}`);
     }
+
+    // 从 node_modules 复制 bun.exe → ~/.bun/bin/bun.exe
+    const src = path.join(tmpDir, 'node_modules', '@oven', 'bun-windows-x64', 'bin', 'bun.exe');
+    if (!fs.existsSync(src)) {
+      throw new Error(`未找到 ${src}`);
+    }
+    const destDir = path.dirname(bunPath);
+    if (!fs.existsSync(destDir)) fs.mkdirSync(destDir, { recursive: true });
+    fs.copyFileSync(src, bunPath);
+
     console.log('[bingocode] bun 安装完成，正在启动...');
+    return true;
   } catch (err) {
     console.error(`[bingocode] bun 自动安装失败: ${err.message}`);
-    console.log('[bingocode] 请手动从 https://bun.sh 安装 Bun 后重试。');
+    console.log('[bingocode] 请手动安装 bun: npm install -g @oven/bun-windows-x64');
     return false;
+  } finally {
+    // 清理临时目录（非阻塞）
+    try { fs.rmSync(tmpDir, { recursive: true, force: true }); } catch (_) {}
   }
-  return true;
 }
 
 if (!bunExists()) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bingocode",
-  "version": "1.1.126",
+  "version": "1.1.128",
   "type": "module",
   "bin": {
     "claude": "bin/claude-win.cjs",

package/scripts/install-skills.cjs

@@ -46,3 +46,4 @@ for (const skill of skills) {
     console.warn(`[bingocode] could not install skill ${skill}: ${err.message}`)
   }
 }
+

package/src/constants/prompts.ts

@@ -230,8 +230,9 @@ function getSimpleDoingTasksSection(): string {
     `In general, do not propose changes to code you haven't read. If a user asks about or wants you to modify a file, read it first. Understand existing code before suggesting modifications.`,
     `Do not create files unless they're absolutely necessary for achieving your goal. Generally prefer editing an existing file to creating a new one, as this prevents file bloat and builds on existing work more effectively.`,
     `Avoid giving time estimates or predictions for how long tasks will take, whether for your own work or for users planning projects. Focus on what needs to be done, not how long it might take.`,
-    `If an approach fails, diagnose why before switching tactics—read the error, check your assumptions, try a focused fix. Don't retry the identical action blindly, but don't abandon a viable approach after a single failure either. Escalate to the user with ${ASK_USER_QUESTION_TOOL_NAME} only when you're genuinely stuck after investigation, not as a first response to friction.`,
+    `On failure: diagnose before switching tactics. Don't retry blindly or abandon after one failure. Escalate with ${ASK_USER_QUESTION_TOOL_NAME} at objective thresholds: same error 3×, same file edited 4×, non-zero exit after 2 distinct fixes.`,
     `Be careful not to introduce security vulnerabilities such as command injection, XSS, SQL injection, and other OWASP top 10 vulnerabilities. If you notice that you wrote insecure code, immediately fix it. Prioritize writing safe, secure, and correct code.`,
+    `Done = outcome verified + no new regressions + result stated. If unverifiable, say so. Never claim done on "looks right".`,
     ...codeStyleSubitems,
     `Avoid backwards-compatibility hacks like renaming unused _vars, re-exporting types, adding // removed comments for removed code, etc. If you are certain that something is unused, you can delete it completely.`,
     // @[MODEL LAUNCH]: False-claims mitigation for Capybara v8 (29-30% FC rate vs v4's 16.7%)
@@ -255,15 +256,21 @@ function getSimpleDoingTasksSection(): string {
 function getActionsSection(): string {
   return `# Executing actions with care
 
-Carefully consider the reversibility and blast radius of actions. Generally you can freely take local, reversible actions like editing files or running tests. But for actions that are hard to reverse, affect shared systems beyond your local environment, or could otherwise be risky or destructive, check with the user before proceeding. The cost of pausing to confirm is low, while the cost of an unwanted action (lost work, unintended messages sent, deleted branches) can be very high. For actions like these, consider the context, the action, and user instructions, and by default transparently communicate the action and ask for confirmation before proceeding. This default can be changed by user instructions - if explicitly asked to operate more autonomously, then you may proceed without confirmation, but still attend to the risks and consequences when taking actions. A user approving an action (like a git push) once does NOT mean that they approve it in all contexts, so unless actions are authorized in advance in durable instructions like CLAUDE.md files, always confirm first. Authorization stands for the scope specified, not beyond. Match the scope of your actions to what was actually requested.
+Two axes govern every action — reversibility and blast radius:
+- Local + reversible (edit files, run tests): proceed freely.
+- Hard-to-reverse OR affects shared state OR risky/destructive: confirm with user first.
 
-Examples of the kind of risky actions that warrant user confirmation:
-- Destructive operations: deleting files/branches, dropping database tables, killing processes, rm -rf, overwriting uncommitted changes
-- Hard-to-reverse operations: force-pushing (can also overwrite upstream), git reset --hard, amending published commits, removing or downgrading packages/dependencies, modifying CI/CD pipelines
-- Actions visible to others or that affect shared state: pushing code, creating/closing/commenting on PRs or issues, sending messages (Slack, email, GitHub), posting to external services, modifying shared infrastructure or permissions
-- Uploading content to third-party web tools (diagram renderers, pastebins, gists) publishes it - consider whether it could be sensitive before sending, since it may be cached or indexed even if later deleted.
+The cost of asking is near zero; the cost of an unwanted action (lost work, deleted branches, sent messages) can be very high.
 
-When you encounter an obstacle, do not use destructive actions as a shortcut to simply make it go away. For instance, try to identify root causes and fix underlying issues rather than bypassing safety checks (e.g. --no-verify). If you discover unexpected state like unfamiliar files, branches, or configuration, investigate before deleting or overwriting, as it may represent the user's in-progress work. For example, typically resolve merge conflicts rather than discarding changes; similarly, if a lock file exists, investigate what process holds it rather than deleting it. In short: only take risky actions carefully, and when in doubt, ask before acting. Follow both the spirit and letter of these instructions - measure twice, cut once.`
+Risk categories requiring confirmation:
+- Destructive: deleting files/branches, dropping tables, killing processes, rm -rf, overwriting uncommitted changes
+- Hard-to-reverse: force-push, git reset --hard, amending published commits, removing or downgrading packages/dependencies, modifying CI/CD pipelines
+- Shared-state visible: pushing code, creating/closing/commenting on PRs or issues, sending messages (Slack, email, GitHub), posting to external services, modifying shared infrastructure or permissions
+- Third-party upload: diagram renderers, pastebins, gists — may be cached or indexed even if deleted later
+
+Authorization: one-time approval covers only that scope — confirm again outside it, unless CLAUDE.md says otherwise. If asked to operate autonomously, proceed but remain risk-aware.
+
+Obstacles: diagnose root causes; do not use destructive actions as shortcuts (e.g. --no-verify). Investigate unexpected state (unfamiliar files, branches, lock files) before deleting or overwriting — it may be in-progress work. Measure twice, cut once.`
 }
 
 function getUsingYourToolsSection(enabledTools: Set<string>): string {
@@ -415,21 +422,26 @@ These user-facing text instructions do not apply to code or tool calls.`
   }
   return `# Output efficiency
 
-IMPORTANT: Go straight to the point. Try the simplest approach first without going in circles. Do not overdo it. Be extra concise.
-
-Keep your text output brief and direct. Lead with the answer or action, not the reasoning. Skip filler words, preamble, and unnecessary transitions. Do not restate what the user said — just do it. When explaining, include only what is necessary for the user to understand.
+Lead with the answer. Be concise. Skip preamble, filler, and restatement.
 
 Focus text output on:
 - Decisions that need the user's input
 - High-level status updates at natural milestones
 - Errors or blockers that change the plan
 
+Format by situation:
+- Direct question or simple task → single sentence or one short paragraph, no headers
+- Multi-step result with distinct outcomes → bullet list, no prose wrapper
+- Explanation of a decision or tradeoff → two sentences max, lead with conclusion
+- Error report → one line: what failed, why, what you'll try next
+
 If you can say it in one sentence, don't use three. Prefer short, direct sentences over long explanations. This does not apply to code or tool calls.`
 }
 
 function getSimpleToneAndStyleSection(): string {
   const items = [
     `Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.`,
+    `Mirror the user's language in all responses unless a language preference is configured.`,
     process.env.USER_TYPE === 'ant'
       ? null
       : `Your responses should be short and concise.`,
@@ -838,7 +850,7 @@ function getFunctionResultClearingSection(model: string): string | null {
 Old tool results will be automatically cleared from context to free up space. The ${config.keepRecent} most recent results are always kept.`
 }
 
-const SUMMARIZE_TOOL_RESULTS_SECTION = `When working with tool results, write down any important information you might need later in your response, as the original tool result may be cleared later.`
+const SUMMARIZE_TOOL_RESULTS_SECTION = `When working with tool results, write down any important information you might need later in your response, as the original tool result may be cleared later. After compaction: don't assume prior state holds — re-read files and re-run verifications before continuing.`
 
 function getBriefSection(): string | null {
   if (!(feature('KAIROS') || feature('KAIROS_BRIEF'))) return null

package/src/utils/goalEvaluator.ts

@@ -19,7 +19,10 @@ export async function evaluateGoal(
   goalCondition: string,
   messages: MessageType[],
 ): Promise<GoalEvalResult> {
-  const client = new Anthropic()
+  const client = new Anthropic({
+    baseURL: process.env.ANTHROPIC_BASE_URL ?? undefined,
+    apiKey: process.env.ANTHROPIC_API_KEY ?? 'dummy',
+  })
 
   const recentAssistantTexts = messages
     .filter(m => m.type === 'assistant' || m.role === 'assistant')