@within-7/minto 0.4.2 → 0.4.3

package/dist/tools/BashTool/prompt.js

@@ -1,496 +0,0 @@
-import { PRODUCT_NAME, PRODUCT_URL } from "../../constants/product.js";
-import { TOOL_NAME as TASK_TOOL_NAME } from "../TaskTool/constants.js";
-import { TOOL_NAME_FOR_PROMPT as GLOB_TOOL_NAME } from "../GlobTool/prompt.js";
-import { TOOL_NAME_FOR_PROMPT as GREP_TOOL_NAME } from "../GrepTool/prompt.js";
-const MAX_OUTPUT_LENGTH = 3e4;
-const MAX_RENDERED_LINES = 5;
-const BANNED_COMMANDS = [
-  // Network tools - data exfiltration risk
-  "curl",
-  "curlie",
-  "wget",
-  "axel",
-  "aria2c",
-  "nc",
-  "netcat",
-  "ncat",
-  "telnet",
-  "lynx",
-  "w3m",
-  "links",
-  "httpie",
-  "xh",
-  "http-prompt",
-  "ftp",
-  "sftp",
-  "scp",
-  "rsync",
-  "socat",
-  "nmap",
-  "tcpdump",
-  "wireshark",
-  "tshark",
-  // Browsers - could open external content
-  "chrome",
-  "chromium",
-  "firefox",
-  "safari",
-  "opera",
-  "brave",
-  "open",
-  // macOS open command could launch apps/URLs
-  // Privilege escalation - dangerous system access
-  "sudo",
-  "su",
-  "doas",
-  "pkexec",
-  "gksudo",
-  "kdesudo",
-  // Shell execution - could bypass restrictions
-  "eval",
-  "source",
-  "exec",
-  "bash",
-  "sh",
-  "zsh",
-  "fish",
-  "csh",
-  "tcsh",
-  "ksh",
-  "dash",
-  "ash",
-  "xargs",
-  // Can execute arbitrary commands
-  "parallel",
-  // GNU parallel can execute commands
-  "xonsh",
-  "powershell",
-  "pwsh",
-  "cmd",
-  // Dangerous file operations - data loss risk
-  "rm",
-  "rmdir",
-  "shred",
-  "srm",
-  "wipe",
-  "dd",
-  // Can overwrite disks
-  "mkfs",
-  // Can format disks
-  "fdisk",
-  "parted",
-  "wipefs",
-  // System modification - could damage system
-  "chmod",
-  "chown",
-  "chgrp",
-  "chattr",
-  "setfacl",
-  "shutdown",
-  "reboot",
-  "poweroff",
-  "halt",
-  "init",
-  "systemctl",
-  "service",
-  "launchctl",
-  // macOS service control
-  // Process control - could affect system stability
-  "kill",
-  "killall",
-  "pkill",
-  // Aliases and functions - could hide malicious commands
-  "alias",
-  "unalias",
-  "function",
-  // Shell builtin bypass - can invoke banned commands by bypassing aliases/functions
-  "command",
-  "builtin",
-  // Bash builtin - can invoke banned commands directly
-  "type",
-  // Can reveal command locations to aid bypass attempts
-  // Cron/scheduling - persistent access
-  "crontab",
-  "at",
-  "atq",
-  "atrm",
-  // User management - privilege escalation
-  "useradd",
-  "userdel",
-  "usermod",
-  "groupadd",
-  "groupdel",
-  "groupmod",
-  "passwd",
-  "chpasswd",
-  // Package managers - could install malware
-  "apt",
-  "apt-get",
-  "aptitude",
-  "dpkg",
-  "yum",
-  "dnf",
-  "rpm",
-  "pacman",
-  "brew",
-  "port",
-  // MacPorts
-  "pip",
-  "pip3",
-  "npm",
-  "yarn",
-  "pnpm",
-  "gem",
-  "cargo",
-  "go",
-  // go install could install packages
-  // Compilers/interpreters with execution capability
-  "python",
-  "python3",
-  "python2",
-  "ruby",
-  "perl",
-  "php",
-  "node",
-  "deno",
-  "bun",
-  "lua",
-  "awk",
-  "gawk",
-  "mawk",
-  "nawk",
-  "sed",
-  // Can execute commands with e flag
-  // Container/VM - could escape sandbox
-  "docker",
-  "podman",
-  "kubectl",
-  "vagrant",
-  "virsh",
-  "qemu",
-  "virtualbox",
-  "vboxmanage",
-  // System info that could aid attacks
-  "env",
-  // Exposes environment variables including secrets
-  // Encryption/keys - could exfiltrate secrets
-  "gpg",
-  "openssl",
-  "ssh-keygen",
-  "ssh-agent",
-  "ssh-add"
-];
-const DANGEROUS_PATTERN_METADATA = [
-  // CRITICAL: Command Injection & Execution Bypass
-  // Note: $(cat <<'EOF'...) HEREDOC pattern is whitelisted — it's the standard
-  // multi-line string idiom used for git commits and is not exploitable.
-  {
-    pattern: /\$\((?!cat\s+<<['"]?EOF)/,
-    name: "command substitution $(...)",
-    severity: "high"
-  },
-  {
-    pattern: /`[^`]+`/,
-    name: "backtick command substitution",
-    severity: "high"
-  },
-  {
-    pattern: /;\s*(rm|chmod|chown|dd|mkfs)\b/i,
-    name: "chained destructive command",
-    severity: "critical"
-  },
-  {
-    pattern: /&&\s*(rm|chmod|chown|dd|mkfs)\b/i,
-    name: "conditional destructive command",
-    severity: "critical"
-  },
-  {
-    pattern: /\|\s*bash\b/i,
-    name: "pipe to bash",
-    severity: "critical"
-  },
-  {
-    pattern: /\|\s*sh\b/i,
-    name: "pipe to sh",
-    severity: "critical"
-  },
-  {
-    pattern: /curl.*\|\s*(bash|sh)\b/i,
-    name: "curl pipe to shell",
-    severity: "critical"
-  },
-  {
-    pattern: /wget.*\|\s*(bash|sh)\b/i,
-    name: "wget pipe to shell",
-    severity: "critical"
-  },
-  {
-    pattern: /eval\s+['"$]/,
-    name: "eval with dynamic input",
-    severity: "critical"
-  },
-  // CRITICAL: Destructive Operations
-  {
-    pattern: /\brm\s+-rf\s+\/(?!\S)/,
-    name: "rm -rf /",
-    severity: "critical"
-  },
-  {
-    pattern: />\s*\/dev\/sd[a-z]/i,
-    name: "write to block device",
-    severity: "critical"
-  },
-  {
-    pattern: />\s*\/dev\/nvme/i,
-    name: "write to NVMe device",
-    severity: "critical"
-  },
-  {
-    pattern: />\s*\/etc\/(passwd|shadow|sudoers)/i,
-    name: "overwrite critical system files",
-    severity: "critical"
-  },
-  {
-    pattern: />\s*\/boot\//i,
-    name: "overwrite boot files",
-    severity: "critical"
-  },
-  // CRITICAL: Fork Bomb & DoS
-  {
-    pattern: /:\(\)\s*\{\s*:\s*\|\s*:\s*&\s*\}\s*;?\s*:/,
-    name: "fork bomb pattern ()",
-    severity: "critical"
-  },
-  {
-    pattern: /\.\s*\(\)\s*\{\s*\.\s*\|\s*\.\s*&\s*\}\s*;?\s*\./,
-    name: "fork bomb pattern (.)",
-    severity: "critical"
-  },
-  // HIGH: Reverse Shell & Data Exfiltration
-  {
-    pattern: /\$\(\s*<\s*\/dev\/tcp/i,
-    name: "TCP socket connection",
-    severity: "high"
-  },
-  {
-    pattern: /\/dev\/tcp\//i,
-    name: "direct TCP device access",
-    severity: "high"
-  },
-  {
-    pattern: /\/dev\/udp\//i,
-    name: "direct UDP device access",
-    severity: "high"
-  },
-  {
-    pattern: /mkfifo.*nc/i,
-    name: "named pipe with netcat",
-    severity: "high"
-  },
-  {
-    pattern: /bash\s+-i\s+>&\s*\/dev\/tcp/i,
-    name: "interactive bash reverse shell",
-    severity: "high"
-  },
-  // HIGH: Data Encoding & Obfuscation
-  {
-    pattern: /base64\s+(-d|--decode).*\|\s*(bash|sh|eval)/i,
-    name: "base64 decode and execute",
-    severity: "high"
-  },
-  {
-    pattern: /xxd\s+-r.*\|\s*(bash|sh|eval)/i,
-    name: "hex decode and execute",
-    severity: "high"
-  },
-  // HIGH: System & Security Manipulation
-  {
-    pattern: /HISTFILE=/i,
-    name: "history file manipulation",
-    severity: "high"
-  },
-  {
-    pattern: /unset\s+HISTFILE/i,
-    name: "disable command history",
-    severity: "high"
-  },
-  {
-    pattern: /history\s+-c/i,
-    name: "clear command history",
-    severity: "high"
-  },
-  {
-    pattern: /LD_PRELOAD=/i,
-    name: "library preload injection",
-    severity: "high"
-  },
-  {
-    pattern: /LD_LIBRARY_PATH=/i,
-    name: "library path injection",
-    severity: "high"
-  },
-  {
-    pattern: /DYLD_INSERT_LIBRARIES=/i,
-    name: "macOS library injection",
-    severity: "high"
-  },
-  // MEDIUM: Suspicious Command Patterns
-  {
-    pattern: /\$\{[^}]*\}/,
-    name: "variable expansion",
-    severity: "medium"
-  }
-];
-function detectDangerousPatterns(command) {
-  const matches = [];
-  for (const { pattern, name, severity } of DANGEROUS_PATTERN_METADATA) {
-    const match = command.match(pattern);
-    if (match) {
-      matches.push({
-        pattern: pattern.toString(),
-        name,
-        match: match[0],
-        severity
-      });
-    }
-  }
-  return matches;
-}
-function matchesDangerousPattern(command) {
-  const criticalMatches = detectDangerousPatterns(command).filter(
-    (m) => m.severity === "critical"
-  );
-  return criticalMatches.length > 0;
-}
-const PROMPT = `Executes a given bash command and returns its output.
-
-The working directory persists between commands, but shell state does not. The shell environment is initialized from the user's profile (bash or zsh).
-
-IMPORTANT: Avoid using this tool to run \`find\`, \`grep\`, \`cat\`, \`head\`, \`tail\`, \`sed\`, \`awk\`, or \`echo\` commands, unless explicitly instructed or after you have verified that a dedicated tool cannot accomplish your task. Instead, use the appropriate dedicated tool as this will provide a much better experience for the user:
-
- - File search: Use ${GLOB_TOOL_NAME} (NOT find or ls)
- - Content search: Use ${GREP_TOOL_NAME} (NOT grep or rg)
- - Read files: Use Read (NOT cat/head/tail)
- - Edit files: Use Edit (NOT sed/awk)
- - Write files: Use Write (NOT echo >/cat <<EOF)
- - Communication: Output text directly (NOT echo/printf)
-While the Bash tool can do similar things, it's better to use the built-in tools as they provide a better user experience and make it easier to review tool calls and give permission.
-
-# Instructions
- - If your command will create new directories or files, first use this tool to run \`ls\` to verify the parent directory exists and is the correct location.
- - Always quote file paths that contain spaces with double quotes in your command (e.g., cd "path with spaces/file.txt")
- - Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of \`cd\`. You may use \`cd\` if the User explicitly requests it.
- - You may specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). By default, your command will timeout after 120000ms (2 minutes).
- - You can use the \`run_in_background\` parameter to run the command in the background. Only use this if you don't need the result immediately and are OK being notified when the command completes later. You do not need to check the output right away - you'll be notified when it finishes. You do not need to use '&' at the end of the command when using this parameter.
- - Write a clear, concise description of what your command does.
- - When issuing multiple commands:
-  - If the commands are independent and can run in parallel, make multiple Bash tool calls in a single message.
-  - If the commands depend on each other and must run sequentially, use a single Bash call with '&&' to chain them together.
-  - Use ';' only when you need to run commands sequentially but don't care if earlier commands fail.
-  - DO NOT use newlines to separate commands (newlines are ok in quoted strings).
- - For git commands:
-  - Prefer to create a new commit rather than amending an existing commit.
-  - Before running destructive operations (e.g., git reset --hard, git push --force, git checkout --), consider whether there is a safer alternative that achieves the same goal. Only use destructive operations when they are truly the best approach.
-  - Never skip hooks (--no-verify) or bypass signing (--no-gpg-sign, -c commit.gpgsign=false) unless the user has explicitly asked for it. If a hook fails, investigate and fix the underlying issue.
- - Avoid unnecessary \`sleep\` commands:
-  - Do not sleep between commands that can run immediately \u2014 just run them.
-  - If your command is long running and you would like to be notified when it finishes \u2013 simply run your command using \`run_in_background\`. There is no need to sleep in this case.
-  - Do not retry failing commands in a sleep loop \u2014 diagnose the root cause or consider an alternative approach.
-  - If waiting for a background task you started with \`run_in_background\`, you will be notified when it completes \u2014 do not poll.
-  - If you must poll an external process, use a check command (e.g. \`gh run view\`) rather than sleeping first.
-  - If you must sleep, keep the duration short (1-5 seconds) to avoid blocking the user.
-
-
-# Committing changes with git
-
-Only create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:
-
-Git Safety Protocol:
-- NEVER update the git config
-- NEVER run destructive git commands (push --force, reset --hard, checkout ., restore ., clean -f, branch -D) unless the user explicitly requests these actions. Taking unauthorized destructive actions is unhelpful and can result in lost work, so it's best to ONLY run these commands when given direct instructions
-- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
-- NEVER run force push to main/master, warn the user if they request it
-- CRITICAL: Always create NEW commits rather than amending, unless the user explicitly requests a git amend. When a pre-commit hook fails, the commit did NOT happen \u2014 so --amend would modify the PREVIOUS commit, which may result in destroying work or losing previous changes. Instead, after hook failure, fix the issue, re-stage, and create a NEW commit
-- When staging files, prefer adding specific files by name rather than using "git add -A" or "git add .", which can accidentally include sensitive files (.env, credentials) or large binaries
-- NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive
-
-1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel, each using the Bash tool:
-  - Run a git status command to see all untracked files. IMPORTANT: Never use the -uall flag as it can cause memory issues on large repos.
-  - Run a git diff command to see both staged and unstaged changes that will be committed.
-  - Run a git log command to see recent commit messages, so that you can follow this repository's commit message style.
-2. Analyze all staged changes (both previously staged and newly added) and draft a commit message:
-  - Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.). Ensure the message accurately reflects the changes and their purpose (i.e. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.).
-  - Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files
-  - Draft a concise (1-2 sentences) commit message that focuses on the "why" rather than the "what"
-  - Ensure it accurately reflects the changes and their purpose
-3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands:
-   - Add relevant untracked files to the staging area.
-   - Create the commit with a message ending with:
-   Co-Authored-By: ${PRODUCT_NAME} <noreply@${PRODUCT_NAME}.com>
-   - Run git status after the commit completes to verify success.
-   Note: git status depends on the commit completing, so run it sequentially after the commit.
-4. If the commit fails due to pre-commit hook: fix the issue and create a NEW commit
-
-Important notes:
-- NEVER run additional commands to read or explore code, besides git bash commands
-- NEVER use the TodoWrite or ${TASK_TOOL_NAME} tools
-- DO NOT push to the remote repository unless the user explicitly asks you to do so
-- IMPORTANT: Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported.
-- IMPORTANT: Do not use --no-edit with git rebase commands, as the --no-edit flag is not a valid option for git rebase.
-- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit
-- In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC, a la this example:
-<example>
-git commit -m "$(cat <<'EOF'
-   Commit message here.
-
-   Co-Authored-By: ${PRODUCT_NAME} <noreply@${PRODUCT_NAME}.com>
-   EOF
-   )"
-</example>
-
-# Creating pull requests
-Use the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed.
-
-IMPORTANT: When the user asks you to create a pull request, follow these steps carefully:
-
-1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged from the main branch:
-   - Run a git status command to see all untracked files (never use -uall flag)
-   - Run a git diff command to see both staged and unstaged changes that will be committed
-   - Check if the current branch tracks a remote branch and is up to date with the remote, so you know if you need to push to the remote
-   - Run a git log command and \`git diff [base-branch]...HEAD\` to understand the full commit history for the current branch (from the time it diverged from the base branch)
-2. Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request!!!), and draft a pull request title and summary:
-   - Keep the PR title short (under 70 characters)
-   - Use the description/body for details, not the title
-3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands in parallel:
-   - Create new branch if needed
-   - Push to remote with -u flag if needed
-   - Create PR using gh pr create with the format below. Use a HEREDOC to pass the body to ensure correct formatting.
-<example>
-gh pr create --title "the pr title" --body "$(cat <<'EOF'
-## Summary
-<1-3 bullet points>
-
-## Test plan
-[Bulleted markdown checklist of TODOs for testing the pull request...]
-
-\u{1F916} Generated with [${PRODUCT_NAME}](${PRODUCT_URL})
-EOF
-)"
-</example>
-
-Important:
-- DO NOT use the TodoWrite or ${TASK_TOOL_NAME} tools
-- Return the PR URL when you're done, so the user can see it
-
-# Other common operations
-- View comments on a Github PR: gh api repos/foo/bar/pulls/123/comments`;
-export {
-  BANNED_COMMANDS,
-  DANGEROUS_PATTERN_METADATA,
-  MAX_OUTPUT_LENGTH,
-  MAX_RENDERED_LINES,
-  PROMPT,
-  detectDangerousPatterns,
-  matchesDangerousPattern
-};
-//# sourceMappingURL=prompt.js.map

package/dist/tools/BashTool/prompt.js.map

@@ -1,7 +0,0 @@
-{
-  "version": 3,
-  "sources": ["../../../src/tools/BashTool/prompt.ts"],
-  "sourcesContent": ["import { PRODUCT_NAME, PRODUCT_URL } from '@constants/product'\nimport { TOOL_NAME as TASK_TOOL_NAME } from '@tools/TaskTool/constants'\nimport { TOOL_NAME_FOR_PROMPT as GLOB_TOOL_NAME } from '@tools/GlobTool/prompt'\nimport { TOOL_NAME_FOR_PROMPT as GREP_TOOL_NAME } from '@tools/GrepTool/prompt'\n\nexport const MAX_OUTPUT_LENGTH = 30000\nexport const MAX_RENDERED_LINES = 5\n\n/**\n * Banned commands for security\n *\n * Categories:\n * - Network tools: Could be used for data exfiltration or network attacks\n * - System modification: Could damage the system or escalate privileges\n * - Shell execution: Could bypass command restrictions\n * - Browsers: Could open external content\n * - Dangerous file operations: Could cause data loss\n */\nexport const BANNED_COMMANDS = [\n  // Network tools - data exfiltration risk\n  'curl',\n  'curlie',\n  'wget',\n  'axel',\n  'aria2c',\n  'nc',\n  'netcat',\n  'ncat',\n  'telnet',\n  'lynx',\n  'w3m',\n  'links',\n  'httpie',\n  'xh',\n  'http-prompt',\n  'ftp',\n  'sftp',\n  'scp',\n  'rsync',\n  'socat',\n  'nmap',\n  'tcpdump',\n  'wireshark',\n  'tshark',\n\n  // Browsers - could open external content\n  'chrome',\n  'chromium',\n  'firefox',\n  'safari',\n  'opera',\n  'brave',\n  'open', // macOS open command could launch apps/URLs\n\n  // Privilege escalation - dangerous system access\n  'sudo',\n  'su',\n  'doas',\n  'pkexec',\n  'gksudo',\n  'kdesudo',\n\n  // Shell execution - could bypass restrictions\n  'eval',\n  'source',\n  'exec',\n  'bash',\n  'sh',\n  'zsh',\n  'fish',\n  'csh',\n  'tcsh',\n  'ksh',\n  'dash',\n  'ash',\n  'xargs', // Can execute arbitrary commands\n  'parallel', // GNU parallel can execute commands\n  'xonsh',\n  'powershell',\n  'pwsh',\n  'cmd',\n\n  // Dangerous file operations - data loss risk\n  'rm',\n  'rmdir',\n  'shred',\n  'srm',\n  'wipe',\n  'dd', // Can overwrite disks\n  'mkfs', // Can format disks\n  'fdisk',\n  'parted',\n  'wipefs',\n\n  // System modification - could damage system\n  'chmod',\n  'chown',\n  'chgrp',\n  'chattr',\n  'setfacl',\n  'shutdown',\n  'reboot',\n  'poweroff',\n  'halt',\n  'init',\n  'systemctl',\n  'service',\n  'launchctl', // macOS service control\n\n  // Process control - could affect system stability\n  'kill',\n  'killall',\n  'pkill',\n\n  // Aliases and functions - could hide malicious commands\n  'alias',\n  'unalias',\n  'function',\n\n  // Shell builtin bypass - can invoke banned commands by bypassing aliases/functions\n  'command',\n  'builtin', // Bash builtin - can invoke banned commands directly\n  'type', // Can reveal command locations to aid bypass attempts\n\n  // Cron/scheduling - persistent access\n  'crontab',\n  'at',\n  'atq',\n  'atrm',\n\n  // User management - privilege escalation\n  'useradd',\n  'userdel',\n  'usermod',\n  'groupadd',\n  'groupdel',\n  'groupmod',\n  'passwd',\n  'chpasswd',\n\n  // Package managers - could install malware\n  'apt',\n  'apt-get',\n  'aptitude',\n  'dpkg',\n  'yum',\n  'dnf',\n  'rpm',\n  'pacman',\n  'brew',\n  'port', // MacPorts\n  'pip',\n  'pip3',\n  'npm',\n  'yarn',\n  'pnpm',\n  'gem',\n  'cargo',\n  'go', // go install could install packages\n\n  // Compilers/interpreters with execution capability\n  'python',\n  'python3',\n  'python2',\n  'ruby',\n  'perl',\n  'php',\n  'node',\n  'deno',\n  'bun',\n  'lua',\n  'awk',\n  'gawk',\n  'mawk',\n  'nawk',\n  'sed', // Can execute commands with e flag\n\n  // Container/VM - could escape sandbox\n  'docker',\n  'podman',\n  'kubectl',\n  'vagrant',\n  'virsh',\n  'qemu',\n  'virtualbox',\n  'vboxmanage',\n\n  // System info that could aid attacks\n  'env', // Exposes environment variables including secrets\n\n  // Encryption/keys - could exfiltrate secrets\n  'gpg',\n  'openssl',\n  'ssh-keygen',\n  'ssh-agent',\n  'ssh-add',\n]\n\n/**\n * Detailed dangerous pattern match information\n */\nexport interface DangerousPatternMatch {\n  pattern: string\n  name: string\n  match: string\n  severity: 'critical' | 'high' | 'medium'\n}\n\n/**\n * Mapping of dangerous patterns with metadata\n */\nexport const DANGEROUS_PATTERN_METADATA: Array<{\n  pattern: RegExp\n  name: string\n  severity: 'critical' | 'high' | 'medium'\n}> = [\n  // CRITICAL: Command Injection & Execution Bypass\n  // Note: $(cat <<'EOF'...) HEREDOC pattern is whitelisted \u2014 it's the standard\n  // multi-line string idiom used for git commits and is not exploitable.\n  {\n    pattern: /\\$\\((?!cat\\s+<<['\"]?EOF)/,\n    name: 'command substitution $(...)',\n    severity: 'high',\n  },\n  {\n    pattern: /`[^`]+`/,\n    name: 'backtick command substitution',\n    severity: 'high',\n  },\n  {\n    pattern: /;\\s*(rm|chmod|chown|dd|mkfs)\\b/i,\n    name: 'chained destructive command',\n    severity: 'critical',\n  },\n  {\n    pattern: /&&\\s*(rm|chmod|chown|dd|mkfs)\\b/i,\n    name: 'conditional destructive command',\n    severity: 'critical',\n  },\n  {\n    pattern: /\\|\\s*bash\\b/i,\n    name: 'pipe to bash',\n    severity: 'critical',\n  },\n  {\n    pattern: /\\|\\s*sh\\b/i,\n    name: 'pipe to sh',\n    severity: 'critical',\n  },\n  {\n    pattern: /curl.*\\|\\s*(bash|sh)\\b/i,\n    name: 'curl pipe to shell',\n    severity: 'critical',\n  },\n  {\n    pattern: /wget.*\\|\\s*(bash|sh)\\b/i,\n    name: 'wget pipe to shell',\n    severity: 'critical',\n  },\n  {\n    pattern: /eval\\s+['\"$]/,\n    name: 'eval with dynamic input',\n    severity: 'critical',\n  },\n\n  // CRITICAL: Destructive Operations\n  {\n    pattern: /\\brm\\s+-rf\\s+\\/(?!\\S)/,\n    name: 'rm -rf /',\n    severity: 'critical',\n  },\n  {\n    pattern: />\\s*\\/dev\\/sd[a-z]/i,\n    name: 'write to block device',\n    severity: 'critical',\n  },\n  {\n    pattern: />\\s*\\/dev\\/nvme/i,\n    name: 'write to NVMe device',\n    severity: 'critical',\n  },\n  {\n    pattern: />\\s*\\/etc\\/(passwd|shadow|sudoers)/i,\n    name: 'overwrite critical system files',\n    severity: 'critical',\n  },\n  {\n    pattern: />\\s*\\/boot\\//i,\n    name: 'overwrite boot files',\n    severity: 'critical',\n  },\n\n  // CRITICAL: Fork Bomb & DoS\n  {\n    pattern: /:\\(\\)\\s*\\{\\s*:\\s*\\|\\s*:\\s*&\\s*\\}\\s*;?\\s*:/,\n    name: 'fork bomb pattern ()',\n    severity: 'critical',\n  },\n  {\n    pattern: /\\.\\s*\\(\\)\\s*\\{\\s*\\.\\s*\\|\\s*\\.\\s*&\\s*\\}\\s*;?\\s*\\./,\n    name: 'fork bomb pattern (.)',\n    severity: 'critical',\n  },\n\n  // HIGH: Reverse Shell & Data Exfiltration\n  {\n    pattern: /\\$\\(\\s*<\\s*\\/dev\\/tcp/i,\n    name: 'TCP socket connection',\n    severity: 'high',\n  },\n  {\n    pattern: /\\/dev\\/tcp\\//i,\n    name: 'direct TCP device access',\n    severity: 'high',\n  },\n  {\n    pattern: /\\/dev\\/udp\\//i,\n    name: 'direct UDP device access',\n    severity: 'high',\n  },\n  {\n    pattern: /mkfifo.*nc/i,\n    name: 'named pipe with netcat',\n    severity: 'high',\n  },\n  {\n    pattern: /bash\\s+-i\\s+>&\\s*\\/dev\\/tcp/i,\n    name: 'interactive bash reverse shell',\n    severity: 'high',\n  },\n\n  // HIGH: Data Encoding & Obfuscation\n  {\n    pattern: /base64\\s+(-d|--decode).*\\|\\s*(bash|sh|eval)/i,\n    name: 'base64 decode and execute',\n    severity: 'high',\n  },\n  {\n    pattern: /xxd\\s+-r.*\\|\\s*(bash|sh|eval)/i,\n    name: 'hex decode and execute',\n    severity: 'high',\n  },\n\n  // HIGH: System & Security Manipulation\n  {\n    pattern: /HISTFILE=/i,\n    name: 'history file manipulation',\n    severity: 'high',\n  },\n  {\n    pattern: /unset\\s+HISTFILE/i,\n    name: 'disable command history',\n    severity: 'high',\n  },\n  {\n    pattern: /history\\s+-c/i,\n    name: 'clear command history',\n    severity: 'high',\n  },\n  {\n    pattern: /LD_PRELOAD=/i,\n    name: 'library preload injection',\n    severity: 'high',\n  },\n  {\n    pattern: /LD_LIBRARY_PATH=/i,\n    name: 'library path injection',\n    severity: 'high',\n  },\n  {\n    pattern: /DYLD_INSERT_LIBRARIES=/i,\n    name: 'macOS library injection',\n    severity: 'high',\n  },\n\n  // MEDIUM: Suspicious Command Patterns\n  {\n    pattern: /\\$\\{[^}]*\\}/,\n    name: 'variable expansion',\n    severity: 'medium',\n  },\n]\n\n/**\n * Check if a command matches any dangerous pattern and return detailed information\n */\nexport function detectDangerousPatterns(\n  command: string,\n): DangerousPatternMatch[] {\n  const matches: DangerousPatternMatch[] = []\n\n  for (const { pattern, name, severity } of DANGEROUS_PATTERN_METADATA) {\n    const match = command.match(pattern)\n    if (match) {\n      matches.push({\n        pattern: pattern.toString(),\n        name,\n        match: match[0],\n        severity,\n      })\n    }\n  }\n\n  return matches\n}\n\n/**\n * Check if a command matches any dangerous pattern (backward compatible)\n */\nexport function matchesDangerousPattern(command: string): boolean {\n  const criticalMatches = detectDangerousPatterns(command).filter(\n    m => m.severity === 'critical',\n  )\n  return criticalMatches.length > 0\n}\n\nexport const PROMPT = `Executes a given bash command and returns its output.\n\nThe working directory persists between commands, but shell state does not. The shell environment is initialized from the user's profile (bash or zsh).\n\nIMPORTANT: Avoid using this tool to run \\`find\\`, \\`grep\\`, \\`cat\\`, \\`head\\`, \\`tail\\`, \\`sed\\`, \\`awk\\`, or \\`echo\\` commands, unless explicitly instructed or after you have verified that a dedicated tool cannot accomplish your task. Instead, use the appropriate dedicated tool as this will provide a much better experience for the user:\n\n - File search: Use ${GLOB_TOOL_NAME} (NOT find or ls)\n - Content search: Use ${GREP_TOOL_NAME} (NOT grep or rg)\n - Read files: Use Read (NOT cat/head/tail)\n - Edit files: Use Edit (NOT sed/awk)\n - Write files: Use Write (NOT echo >/cat <<EOF)\n - Communication: Output text directly (NOT echo/printf)\nWhile the Bash tool can do similar things, it's better to use the built-in tools as they provide a better user experience and make it easier to review tool calls and give permission.\n\n# Instructions\n - If your command will create new directories or files, first use this tool to run \\`ls\\` to verify the parent directory exists and is the correct location.\n - Always quote file paths that contain spaces with double quotes in your command (e.g., cd \"path with spaces/file.txt\")\n - Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of \\`cd\\`. You may use \\`cd\\` if the User explicitly requests it.\n - You may specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). By default, your command will timeout after 120000ms (2 minutes).\n - You can use the \\`run_in_background\\` parameter to run the command in the background. Only use this if you don't need the result immediately and are OK being notified when the command completes later. You do not need to check the output right away - you'll be notified when it finishes. You do not need to use '&' at the end of the command when using this parameter.\n - Write a clear, concise description of what your command does.\n - When issuing multiple commands:\n  - If the commands are independent and can run in parallel, make multiple Bash tool calls in a single message.\n  - If the commands depend on each other and must run sequentially, use a single Bash call with '&&' to chain them together.\n  - Use ';' only when you need to run commands sequentially but don't care if earlier commands fail.\n  - DO NOT use newlines to separate commands (newlines are ok in quoted strings).\n - For git commands:\n  - Prefer to create a new commit rather than amending an existing commit.\n  - Before running destructive operations (e.g., git reset --hard, git push --force, git checkout --), consider whether there is a safer alternative that achieves the same goal. Only use destructive operations when they are truly the best approach.\n  - Never skip hooks (--no-verify) or bypass signing (--no-gpg-sign, -c commit.gpgsign=false) unless the user has explicitly asked for it. If a hook fails, investigate and fix the underlying issue.\n - Avoid unnecessary \\`sleep\\` commands:\n  - Do not sleep between commands that can run immediately \u2014 just run them.\n  - If your command is long running and you would like to be notified when it finishes \u2013 simply run your command using \\`run_in_background\\`. There is no need to sleep in this case.\n  - Do not retry failing commands in a sleep loop \u2014 diagnose the root cause or consider an alternative approach.\n  - If waiting for a background task you started with \\`run_in_background\\`, you will be notified when it completes \u2014 do not poll.\n  - If you must poll an external process, use a check command (e.g. \\`gh run view\\`) rather than sleeping first.\n  - If you must sleep, keep the duration short (1-5 seconds) to avoid blocking the user.\n\n\n# Committing changes with git\n\nOnly create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:\n\nGit Safety Protocol:\n- NEVER update the git config\n- NEVER run destructive git commands (push --force, reset --hard, checkout ., restore ., clean -f, branch -D) unless the user explicitly requests these actions. Taking unauthorized destructive actions is unhelpful and can result in lost work, so it's best to ONLY run these commands when given direct instructions\n- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it\n- NEVER run force push to main/master, warn the user if they request it\n- CRITICAL: Always create NEW commits rather than amending, unless the user explicitly requests a git amend. When a pre-commit hook fails, the commit did NOT happen \u2014 so --amend would modify the PREVIOUS commit, which may result in destroying work or losing previous changes. Instead, after hook failure, fix the issue, re-stage, and create a NEW commit\n- When staging files, prefer adding specific files by name rather than using \"git add -A\" or \"git add .\", which can accidentally include sensitive files (.env, credentials) or large binaries\n- NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive\n\n1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel, each using the Bash tool:\n  - Run a git status command to see all untracked files. IMPORTANT: Never use the -uall flag as it can cause memory issues on large repos.\n  - Run a git diff command to see both staged and unstaged changes that will be committed.\n  - Run a git log command to see recent commit messages, so that you can follow this repository's commit message style.\n2. Analyze all staged changes (both previously staged and newly added) and draft a commit message:\n  - Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.). Ensure the message accurately reflects the changes and their purpose (i.e. \"add\" means a wholly new feature, \"update\" means an enhancement to an existing feature, \"fix\" means a bug fix, etc.).\n  - Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files\n  - Draft a concise (1-2 sentences) commit message that focuses on the \"why\" rather than the \"what\"\n  - Ensure it accurately reflects the changes and their purpose\n3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands:\n   - Add relevant untracked files to the staging area.\n   - Create the commit with a message ending with:\n   Co-Authored-By: ${PRODUCT_NAME} <noreply@${PRODUCT_NAME}.com>\n   - Run git status after the commit completes to verify success.\n   Note: git status depends on the commit completing, so run it sequentially after the commit.\n4. If the commit fails due to pre-commit hook: fix the issue and create a NEW commit\n\nImportant notes:\n- NEVER run additional commands to read or explore code, besides git bash commands\n- NEVER use the TodoWrite or ${TASK_TOOL_NAME} tools\n- DO NOT push to the remote repository unless the user explicitly asks you to do so\n- IMPORTANT: Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported.\n- IMPORTANT: Do not use --no-edit with git rebase commands, as the --no-edit flag is not a valid option for git rebase.\n- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit\n- In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC, a la this example:\n<example>\ngit commit -m \"$(cat <<'EOF'\n   Commit message here.\n\n   Co-Authored-By: ${PRODUCT_NAME} <noreply@${PRODUCT_NAME}.com>\n   EOF\n   )\"\n</example>\n\n# Creating pull requests\nUse the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed.\n\nIMPORTANT: When the user asks you to create a pull request, follow these steps carefully:\n\n1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged from the main branch:\n   - Run a git status command to see all untracked files (never use -uall flag)\n   - Run a git diff command to see both staged and unstaged changes that will be committed\n   - Check if the current branch tracks a remote branch and is up to date with the remote, so you know if you need to push to the remote\n   - Run a git log command and \\`git diff [base-branch]...HEAD\\` to understand the full commit history for the current branch (from the time it diverged from the base branch)\n2. Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request!!!), and draft a pull request title and summary:\n   - Keep the PR title short (under 70 characters)\n   - Use the description/body for details, not the title\n3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands in parallel:\n   - Create new branch if needed\n   - Push to remote with -u flag if needed\n   - Create PR using gh pr create with the format below. Use a HEREDOC to pass the body to ensure correct formatting.\n<example>\ngh pr create --title \"the pr title\" --body \"$(cat <<'EOF'\n## Summary\n<1-3 bullet points>\n\n## Test plan\n[Bulleted markdown checklist of TODOs for testing the pull request...]\n\n\uD83E\uDD16 Generated with [${PRODUCT_NAME}](${PRODUCT_URL})\nEOF\n)\"\n</example>\n\nImportant:\n- DO NOT use the TodoWrite or ${TASK_TOOL_NAME} tools\n- Return the PR URL when you're done, so the user can see it\n\n# Other common operations\n- View comments on a Github PR: gh api repos/foo/bar/pulls/123/comments`\n"],
-  "mappings": "AAAA,SAAS,cAAc,mBAAmB;AAC1C,SAAS,aAAa,sBAAsB;AAC5C,SAAS,wBAAwB,sBAAsB;AACvD,SAAS,wBAAwB,sBAAsB;AAEhD,MAAM,oBAAoB;AAC1B,MAAM,qBAAqB;AAY3B,MAAM,kBAAkB;AAAA;AAAA,EAE7B;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EACA;AAAA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EACA;AAAA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA;AAAA,EACA;AAAA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA;AAAA,EAGA;AAAA;AAAA;AAAA,EAGA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AACF;AAeO,MAAM,6BAIR;AAAA;AAAA;AAAA;AAAA,EAIH;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA;AAAA,EAGA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA;AAAA,EAGA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA;AAAA,EAGA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA;AAAA,EAGA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA;AAAA,EAGA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA,EACA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AAAA;AAAA,EAGA;AAAA,IACE,SAAS;AAAA,IACT,MAAM;AAAA,IACN,UAAU;AAAA,EACZ;AACF;AAKO,SAAS,wBACd,SACyB;AACzB,QAAM,UAAmC,CAAC;AAE1C,aAAW,EAAE,SAAS,MAAM,SAAS,KAAK,4BAA4B;AACpE,UAAM,QAAQ,QAAQ,MAAM,OAAO;AACnC,QAAI,OAAO;AACT,cAAQ,KAAK;AAAA,QACX,SAAS,QAAQ,SAAS;AAAA,QAC1B;AAAA,QACA,OAAO,MAAM,CAAC;AAAA,QACd;AAAA,MACF,CAAC;AAAA,IACH;AAAA,EACF;AAEA,SAAO;AACT;AAKO,SAAS,wBAAwB,SAA0B;AAChE,QAAM,kBAAkB,wBAAwB,OAAO,EAAE;AAAA,IACvD,OAAK,EAAE,aAAa;AAAA,EACtB;AACA,SAAO,gBAAgB,SAAS;AAClC;AAEO,MAAM,SAAS;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,sBAMA,cAAc;AAAA,yBACX,cAAc;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,qBAyDlB,YAAY,aAAa,YAAY;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,+BAO3B,cAAc;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,qBAUxB,YAAY,aAAa,YAAY;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,4BA8BrC,YAAY,KAAK,WAAW;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,gCAMjB,cAAc;AAAA;AAAA;AAAA;AAAA;",
-  "names": []
-}

package/dist/tools/BashTool/utils.js

@@ -1,89 +0,0 @@
-import { queryQuick } from "../../services/claude.js";
-import { extractTag } from "../../utils/messages.js";
-import { getGlobalConfig } from "../../utils/config.js";
-import { MAX_OUTPUT_LENGTH } from "./prompt.js";
-const BASH_SUMMARIZATION_THRESHOLD = 4e3;
-function formatOutput(content) {
-  if (content.length <= MAX_OUTPUT_LENGTH) {
-    return {
-      totalLines: content.split("\n").length,
-      truncatedContent: content
-    };
-  }
-  const halfLength = MAX_OUTPUT_LENGTH / 2;
-  const start = content.slice(0, halfLength);
-  const end = content.slice(-halfLength);
-  const truncated = `${start}
-
-... [${content.slice(halfLength, -halfLength).split("\n").length} lines truncated] ...
-
-${end}`;
-  return {
-    totalLines: content.split("\n").length,
-    truncatedContent: truncated
-  };
-}
-async function summarizeBashOutput(command, stdout, stderr) {
-  try {
-    const config = getGlobalConfig();
-    if (!config.bashOutputSummarization && !process.env.MINTO_BASH_SUMMARIZATION) {
-      return { stdout, stderr, wasSummarized: false };
-    }
-    const combined = stdout + stderr;
-    if (combined.length < BASH_SUMMARIZATION_THRESHOLD) {
-      return { stdout, stderr, wasSummarized: false };
-    }
-    const response = await queryQuick({
-      systemPrompt: [
-        "You summarize bash command output concisely. Respond with ONLY the summary text, no preamble.",
-        "Focus on: key results, errors, warnings, counts, and actionable information.",
-        "Keep the summary under 5 lines. If the output is a list, mention the count and key items."
-      ],
-      userPrompt: `Command: ${command}
-
-Output (${combined.length} chars):
-${combined.slice(0, 8e3)}`
-    });
-    const summaryText = response.message.content.filter((b) => b.type === "text").map((b) => b.text).join("").trim();
-    if (!summaryText) {
-      return { stdout, stderr, wasSummarized: false };
-    }
-    const summarizedStdout = `<output-summary>
-${summaryText}
-</output-summary>
-
-${stdout}`;
-    return { stdout: summarizedStdout, stderr, wasSummarized: true };
-  } catch {
-    return { stdout, stderr, wasSummarized: false };
-  }
-}
-async function getCommandFilePaths(command, output) {
-  const response = await queryQuick({
-    systemPrompt: [
-      `Extract any file paths that this command reads or modifies. For commands like "git diff" and "cat", include the paths of files being shown. Use paths verbatim -- don't add any slashes or try to resolve them. Do not try to infer paths that were not explicitly listed in the command output.
-Format your response as:
-<filepaths>
-path/to/file1
-path/to/file2
-</filepaths>
-
-If no files are read or modified, return empty filepaths tags:
-<filepaths>
-</filepaths>
-
-Do not include any other text in your response.`
-    ],
-    userPrompt: `Command: ${command}
-Output: ${output}`,
-    enablePromptCaching: true
-  });
-  const content = response.message.content.filter((_) => _.type === "text").map((_) => _.text).join("");
-  return extractTag(content, "filepaths")?.trim().split("\n").filter(Boolean) || [];
-}
-export {
-  formatOutput,
-  getCommandFilePaths,
-  summarizeBashOutput
-};
-//# sourceMappingURL=utils.js.map

package/dist/tools/BashTool/utils.js.map

@@ -1,7 +0,0 @@
-{
-  "version": 3,
-  "sources": ["../../../src/tools/BashTool/utils.ts"],
-  "sourcesContent": ["import { queryQuick } from '@services/claude'\nimport { extractTag } from '@utils/messages'\nimport { getGlobalConfig } from '@utils/config'\nimport { MAX_OUTPUT_LENGTH } from './prompt'\n\n/** Threshold in characters above which bash output summarization kicks in */\nconst BASH_SUMMARIZATION_THRESHOLD = 4000\n\nexport function formatOutput(content: string): {\n  totalLines: number\n  truncatedContent: string\n} {\n  if (content.length <= MAX_OUTPUT_LENGTH) {\n    return {\n      totalLines: content.split('\\n').length,\n      truncatedContent: content,\n    }\n  }\n  const halfLength = MAX_OUTPUT_LENGTH / 2\n  const start = content.slice(0, halfLength)\n  const end = content.slice(-halfLength)\n  const truncated = `${start}\\n\\n... [${content.slice(halfLength, -halfLength).split('\\n').length} lines truncated] ...\\n\\n${end}`\n\n  return {\n    totalLines: content.split('\\n').length,\n    truncatedContent: truncated,\n  }\n}\n\n/**\n * Summarize large bash output using the quick model.\n * Returns the original output with a prefixed summary, or the original output\n * unchanged if summarization is disabled, not needed, or fails.\n */\nexport async function summarizeBashOutput(\n  command: string,\n  stdout: string,\n  stderr: string,\n): Promise<{ stdout: string; stderr: string; wasSummarized: boolean }> {\n  try {\n    const config = getGlobalConfig()\n    if (\n      !config.bashOutputSummarization &&\n      !process.env.MINTO_BASH_SUMMARIZATION\n    ) {\n      return { stdout, stderr, wasSummarized: false }\n    }\n\n    const combined = stdout + stderr\n    if (combined.length < BASH_SUMMARIZATION_THRESHOLD) {\n      return { stdout, stderr, wasSummarized: false }\n    }\n\n    const response = await queryQuick({\n      systemPrompt: [\n        'You summarize bash command output concisely. Respond with ONLY the summary text, no preamble.',\n        'Focus on: key results, errors, warnings, counts, and actionable information.',\n        'Keep the summary under 5 lines. If the output is a list, mention the count and key items.',\n      ],\n      userPrompt: `Command: ${command}\\n\\nOutput (${combined.length} chars):\\n${combined.slice(0, 8000)}`,\n    })\n\n    const summaryText = response.message.content\n      .filter(b => b.type === 'text')\n      .map(b => (b as any).text)\n      .join('')\n      .trim()\n\n    if (!summaryText) {\n      return { stdout, stderr, wasSummarized: false }\n    }\n\n    const summarizedStdout = `<output-summary>\\n${summaryText}\\n</output-summary>\\n\\n${stdout}`\n    return { stdout: summarizedStdout, stderr, wasSummarized: true }\n  } catch {\n    // Graceful degradation: return original output if summarization fails\n    return { stdout, stderr, wasSummarized: false }\n  }\n}\n\nexport async function getCommandFilePaths(\n  command: string,\n  output: string,\n): Promise<string[]> {\n  const response = await queryQuick({\n    systemPrompt: [\n      `Extract any file paths that this command reads or modifies. For commands like \"git diff\" and \"cat\", include the paths of files being shown. Use paths verbatim -- don't add any slashes or try to resolve them. Do not try to infer paths that were not explicitly listed in the command output.\nFormat your response as:\n<filepaths>\npath/to/file1\npath/to/file2\n</filepaths>\n\nIf no files are read or modified, return empty filepaths tags:\n<filepaths>\n</filepaths>\n\nDo not include any other text in your response.`,\n    ],\n    userPrompt: `Command: ${command}\\nOutput: ${output}`,\n    enablePromptCaching: true,\n  })\n  const content = response.message.content\n    .filter(_ => _.type === 'text')\n    .map(_ => _.text)\n    .join('')\n\n  return (\n    extractTag(content, 'filepaths')?.trim().split('\\n').filter(Boolean) || []\n  )\n}\n"],
-  "mappings": "AAAA,SAAS,kBAAkB;AAC3B,SAAS,kBAAkB;AAC3B,SAAS,uBAAuB;AAChC,SAAS,yBAAyB;AAGlC,MAAM,+BAA+B;AAE9B,SAAS,aAAa,SAG3B;AACA,MAAI,QAAQ,UAAU,mBAAmB;AACvC,WAAO;AAAA,MACL,YAAY,QAAQ,MAAM,IAAI,EAAE;AAAA,MAChC,kBAAkB;AAAA,IACpB;AAAA,EACF;AACA,QAAM,aAAa,oBAAoB;AACvC,QAAM,QAAQ,QAAQ,MAAM,GAAG,UAAU;AACzC,QAAM,MAAM,QAAQ,MAAM,CAAC,UAAU;AACrC,QAAM,YAAY,GAAG,KAAK;AAAA;AAAA,OAAY,QAAQ,MAAM,YAAY,CAAC,UAAU,EAAE,MAAM,IAAI,EAAE,MAAM;AAAA;AAAA,EAA4B,GAAG;AAE9H,SAAO;AAAA,IACL,YAAY,QAAQ,MAAM,IAAI,EAAE;AAAA,IAChC,kBAAkB;AAAA,EACpB;AACF;AAOA,eAAsB,oBACpB,SACA,QACA,QACqE;AACrE,MAAI;AACF,UAAM,SAAS,gBAAgB;AAC/B,QACE,CAAC,OAAO,2BACR,CAAC,QAAQ,IAAI,0BACb;AACA,aAAO,EAAE,QAAQ,QAAQ,eAAe,MAAM;AAAA,IAChD;AAEA,UAAM,WAAW,SAAS;AAC1B,QAAI,SAAS,SAAS,8BAA8B;AAClD,aAAO,EAAE,QAAQ,QAAQ,eAAe,MAAM;AAAA,IAChD;AAEA,UAAM,WAAW,MAAM,WAAW;AAAA,MAChC,cAAc;AAAA,QACZ;AAAA,QACA;AAAA,QACA;AAAA,MACF;AAAA,MACA,YAAY,YAAY,OAAO;AAAA;AAAA,UAAe,SAAS,MAAM;AAAA,EAAa,SAAS,MAAM,GAAG,GAAI,CAAC;AAAA,IACnG,CAAC;AAED,UAAM,cAAc,SAAS,QAAQ,QAClC,OAAO,OAAK,EAAE,SAAS,MAAM,EAC7B,IAAI,OAAM,EAAU,IAAI,EACxB,KAAK,EAAE,EACP,KAAK;AAER,QAAI,CAAC,aAAa;AAChB,aAAO,EAAE,QAAQ,QAAQ,eAAe,MAAM;AAAA,IAChD;AAEA,UAAM,mBAAmB;AAAA,EAAqB,WAAW;AAAA;AAAA;AAAA,EAA0B,MAAM;AACzF,WAAO,EAAE,QAAQ,kBAAkB,QAAQ,eAAe,KAAK;AAAA,EACjE,QAAQ;AAEN,WAAO,EAAE,QAAQ,QAAQ,eAAe,MAAM;AAAA,EAChD;AACF;AAEA,eAAsB,oBACpB,SACA,QACmB;AACnB,QAAM,WAAW,MAAM,WAAW;AAAA,IAChC,cAAc;AAAA,MACZ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,IAYF;AAAA,IACA,YAAY,YAAY,OAAO;AAAA,UAAa,MAAM;AAAA,IAClD,qBAAqB;AAAA,EACvB,CAAC;AACD,QAAM,UAAU,SAAS,QAAQ,QAC9B,OAAO,OAAK,EAAE,SAAS,MAAM,EAC7B,IAAI,OAAK,EAAE,IAAI,EACf,KAAK,EAAE;AAEV,SACE,WAAW,SAAS,WAAW,GAAG,KAAK,EAAE,MAAM,IAAI,EAAE,OAAO,OAAO,KAAK,CAAC;AAE7E;",
-  "names": []
-}