@shareai-lab/kode 1.1.14 → 1.1.16-dev.1

package/src/tools/BashTool/BashTool.tsx

@@ -1,243 +0,0 @@
-import { statSync } from 'fs'
-import { EOL } from 'os'
-import { isAbsolute, relative, resolve } from 'path'
-import * as React from 'react'
-import { z } from 'zod'
-import { FallbackToolUseRejectedMessage } from '../../components/FallbackToolUseRejectedMessage'
-import { PRODUCT_NAME } from '../../constants/product'
-import { queryQuick } from '../../services/claude'
-import { Tool, ValidationResult } from '../../Tool'
-import { splitCommand } from '../../utils/commands'
-import { isInDirectory } from '../../utils/file'
-import { logError } from '../../utils/log'
-import { PersistentShell } from '../../utils/PersistentShell'
-import { getCwd, getOriginalCwd } from '../../utils/state'
-import { getGlobalConfig } from '../../utils/config'
-import { getModelManager } from '../../utils/model'
-import BashToolResultMessage from './BashToolResultMessage'
-import { BANNED_COMMANDS, PROMPT } from './prompt'
-import { formatOutput, getCommandFilePaths } from './utils'
-import { logEvent } from '../../services/statsig'
-
-export const inputSchema = z.strictObject({
-  command: z.string().describe('The command to execute'),
-  timeout: z
-    .number()
-    .optional()
-    .describe('Optional timeout in milliseconds (max 600000)'),
-})
-
-type In = typeof inputSchema
-export type Out = {
-  stdout: string
-  stdoutLines: number // Total number of lines in original stdout, even if `stdout` is now truncated
-  stderr: string
-  stderrLines: number // Total number of lines in original stderr, even if `stderr` is now truncated
-  interrupted: boolean
-}
-
-export const BashTool = {
-  name: 'Bash',
-  async description() {
-    return 'Executes shell commands on your computer'
-  },
-  async prompt() {
-    const config = getGlobalConfig()
-    // 🔧 Fix: Use ModelManager to get actual current model
-    const modelManager = getModelManager()
-    const modelName =
-      modelManager.getModelName('main') || '<No Model Configured>'
-    // Substitute the placeholder in the static PROMPT string
-    return PROMPT.replace(/{MODEL_NAME}/g, modelName)
-  },
-  isReadOnly() {
-    return false
-  },
-  isConcurrencySafe() {
-    return false // BashTool modifies state/files, not safe for concurrent execution
-  },
-  inputSchema,
-  userFacingName() {
-    return 'Bash'
-  },
-  async isEnabled() {
-    return true
-  },
-  needsPermissions(): boolean {
-    // Always check per-project permissions for BashTool
-    return true
-  },
-  async validateInput({ command }): Promise<ValidationResult> {
-    const commands = splitCommand(command)
-    for (const cmd of commands) {
-      const parts = cmd.split(' ')
-      const baseCmd = parts[0]
-
-      // Check if command is banned
-      if (baseCmd && BANNED_COMMANDS.includes(baseCmd.toLowerCase())) {
-        return {
-          result: false,
-          message: `Command '${baseCmd}' is not allowed for security reasons`,
-        }
-      }
-
-      // Special handling for cd command
-      if (baseCmd === 'cd' && parts[1]) {
-        const targetDir = parts[1]!.replace(/^['"]|['"]$/g, '') // Remove quotes if present
-        const fullTargetDir = isAbsolute(targetDir)
-          ? targetDir
-          : resolve(getCwd(), targetDir)
-        if (
-          !isInDirectory(
-            relative(getOriginalCwd(), fullTargetDir),
-            relative(getCwd(), getOriginalCwd()),
-          )
-        ) {
-          return {
-            result: false,
-            message: `ERROR: cd to '${fullTargetDir}' was blocked. For security, ${PRODUCT_NAME} may only change directories to child directories of the original working directory (${getOriginalCwd()}) for this session.`,
-          }
-        }
-      }
-    }
-
-    return { result: true }
-  },
-  renderToolUseMessage({ command }) {
-    // Clean up any command that uses the quoted HEREDOC pattern
-    if (command.includes("\"$(cat <<'EOF'")) {
-      const match = command.match(
-        /^(.*?)"?\$\(cat <<'EOF'\n([\s\S]*?)\n\s*EOF\n\s*\)"(.*)$/,
-      )
-      if (match && match[1] && match[2]) {
-        const prefix = match[1]
-        const content = match[2]
-        const suffix = match[3] || ''
-        return `${prefix.trim()} "${content.trim()}"${suffix.trim()}`
-      }
-    }
-    return command
-  },
-  renderToolUseRejectedMessage() {
-    return <FallbackToolUseRejectedMessage />
-  },
-
-  renderToolResultMessage(content) {
-    return <BashToolResultMessage content={content} verbose={false} />
-  },
-  renderResultForAssistant({ interrupted, stdout, stderr }) {
-    let errorMessage = stderr.trim()
-    if (interrupted) {
-      if (stderr) errorMessage += EOL
-      errorMessage += '<error>Command was aborted before completion</error>'
-    }
-    const hasBoth = stdout.trim() && errorMessage
-    return `${stdout.trim()}${hasBoth ? '\n' : ''}${errorMessage.trim()}`
-  },
-  async *call(
-    { command, timeout = 120000 },
-    { abortController, readFileTimestamps },
-  ) {
-    let stdout = ''
-    let stderr = ''
-
-    // 🔧 Check if already cancelled before starting execution
-    if (abortController.signal.aborted) {
-      const data: Out = {
-        stdout: '',
-        stdoutLines: 0,
-        stderr: 'Command cancelled before execution',
-        stderrLines: 1,
-        interrupted: true,
-      }
-
-      yield {
-        type: 'result',
-        resultForAssistant: this.renderResultForAssistant(data),
-        data,
-      }
-      return
-    }
-
-    try {
-      // Execute commands
-      const result = await PersistentShell.getInstance().exec(
-        command,
-        abortController.signal,
-        timeout,
-      )
-      stdout += (result.stdout || '').trim() + EOL
-      stderr += (result.stderr || '').trim() + EOL
-      if (result.code !== 0) {
-        stderr += `Exit code ${result.code}`
-      }
-
-      if (!isInDirectory(getCwd(), getOriginalCwd())) {
-        // Shell directory is outside original working directory, reset it
-        await PersistentShell.getInstance().setCwd(getOriginalCwd())
-        stderr = `${stderr.trim()}${EOL}Shell cwd was reset to ${getOriginalCwd()}`
-        logEvent('bash_tool_reset_to_original_dir', {})
-      }
-
-      // Update read timestamps for any files referenced by the command
-      // Don't block the main thread!
-      // Skip this in tests because it makes fixtures non-deterministic (they might not always get written),
-      // so will be missing in CI.
-      if (process.env.NODE_ENV !== 'test') {
-        getCommandFilePaths(command, stdout).then(filePaths => {
-          for (const filePath of filePaths) {
-            const fullFilePath = isAbsolute(filePath)
-              ? filePath
-              : resolve(getCwd(), filePath)
-
-            // Try/catch in case the file doesn't exist (because Haiku didn't properly extract it)
-            try {
-              readFileTimestamps[fullFilePath] = statSync(fullFilePath).mtimeMs
-            } catch (e) {
-              logError(e)
-            }
-          }
-        })
-      }
-
-      const { totalLines: stdoutLines, truncatedContent: stdoutContent } =
-        formatOutput(stdout.trim())
-      const { totalLines: stderrLines, truncatedContent: stderrContent } =
-        formatOutput(stderr.trim())
-
-      const data: Out = {
-        stdout: stdoutContent,
-        stdoutLines,
-        stderr: stderrContent,
-        stderrLines,
-        interrupted: result.interrupted,
-      }
-
-      yield {
-        type: 'result',
-        resultForAssistant: this.renderResultForAssistant(data),
-        data,
-      }
-    } catch (error) {
-      // 🔧 Handle cancellation or other errors properly
-      const isAborted = abortController.signal.aborted
-      const errorMessage = isAborted 
-        ? 'Command was cancelled by user' 
-        : `Command failed: ${error instanceof Error ? error.message : String(error)}`
-      
-      const data: Out = {
-        stdout: stdout.trim(),
-        stdoutLines: stdout.split('\n').length,
-        stderr: errorMessage,
-        stderrLines: 1,
-        interrupted: isAborted,
-      }
-
-      yield {
-        type: 'result',
-        resultForAssistant: this.renderResultForAssistant(data),
-        data,
-      }
-    }
-  },
-} satisfies Tool<In, Out>

package/src/tools/BashTool/BashToolResultMessage.tsx

@@ -1,38 +0,0 @@
-import { Box, Text } from 'ink'
-import { OutputLine } from './OutputLine'
-import React from 'react'
-import { getTheme } from '../../utils/theme'
-import { Out as BashOut } from './BashTool'
-
-type Props = {
-  content: Omit<BashOut, 'interrupted'>
-  verbose: boolean
-}
-
-function BashToolResultMessage({ content, verbose }: Props): React.JSX.Element {
-  const { stdout, stdoutLines, stderr, stderrLines } = content
-
-  return (
-    <Box flexDirection="column">
-      {stdout !== '' ? (
-        <OutputLine content={stdout} lines={stdoutLines} verbose={verbose} />
-      ) : null}
-      {stderr !== '' ? (
-        <OutputLine
-          content={stderr}
-          lines={stderrLines}
-          verbose={verbose}
-          isError
-        />
-      ) : null}
-      {stdout === '' && stderr === '' ? (
-        <Box flexDirection="row">
-          <Text>&nbsp;&nbsp;⎿ &nbsp;</Text>
-          <Text color={getTheme().secondaryText}>(No content)</Text>
-        </Box>
-      ) : null}
-    </Box>
-  )
-}
-
-export default BashToolResultMessage

package/src/tools/BashTool/OutputLine.tsx

@@ -1,49 +0,0 @@
-import { Box, Text } from 'ink'
-import * as React from 'react'
-import { getTheme } from '../../utils/theme'
-import { MAX_RENDERED_LINES } from './prompt'
-import chalk from 'chalk'
-
-function renderTruncatedContent(content: string, totalLines: number): string {
-  const allLines = content.split('\n')
-  if (allLines.length <= MAX_RENDERED_LINES) {
-    return allLines.join('\n')
-  }
-
-  // Show last 5 lines of output by default (matching reference implementation)
-  const lastLines = allLines.slice(-MAX_RENDERED_LINES)
-  return [
-    chalk.grey(
-      `Showing last ${MAX_RENDERED_LINES} lines of ${totalLines} total lines`,
-    ),
-    ...lastLines,
-  ].join('\n')
-}
-
-export function OutputLine({
-  content,
-  lines,
-  verbose,
-  isError,
-}: {
-  content: string
-  lines: number
-  verbose: boolean
-  isError?: boolean
-  key?: React.Key
-}) {
-  return (
-    <Box justifyContent="space-between" width="100%">
-      <Box flexDirection="row">
-        <Text>&nbsp;&nbsp;⎿ &nbsp;</Text>
-        <Box flexDirection="column">
-          <Text color={isError ? getTheme().error : undefined}>
-            {verbose
-              ? content.trim()
-              : renderTruncatedContent(content.trim(), lines)}
-          </Text>
-        </Box>
-      </Box>
-    </Box>
-  )
-}

package/src/tools/BashTool/prompt.ts

@@ -1,174 +0,0 @@
-import { PRODUCT_NAME, PRODUCT_URL } from '../../constants/product'
-import { TOOL_NAME as TASK_TOOL_NAME } from '../TaskTool/constants'
-import { FileReadTool } from '../FileReadTool/FileReadTool'
-import { TOOL_NAME_FOR_PROMPT as GLOB_TOOL_NAME } from '../GlobTool/prompt'
-import { TOOL_NAME_FOR_PROMPT as GREP_TOOL_NAME } from '../GrepTool/prompt'
-import { LSTool } from '../lsTool/lsTool'
-
-export const MAX_OUTPUT_LENGTH = 30000
-export const MAX_RENDERED_LINES = 5
-export const BANNED_COMMANDS = [
-  'alias',
-  'curl',
-  'curlie',
-  'wget',
-  'axel',
-  'aria2c',
-  'nc',
-  'telnet',
-  'lynx',
-  'w3m',
-  'links',
-  'httpie',
-  'xh',
-  'http-prompt',
-  'chrome',
-  'firefox',
-  'safari',
-]
-
-export const PROMPT = `Executes a given bash command in a persistent shell session with optional timeout, ensuring proper handling and security measures.
-
-Before executing the command, please follow these steps:
-
-1. Directory Verification:
-   - If the command will create new directories or files, first use the LS tool to verify the parent directory exists and is the correct location
-   - For example, before running "mkdir foo/bar", first use LS to check that "foo" exists and is the intended parent directory
-
-2. Security Check:
-   - For security and to limit the threat of a prompt injection attack, some commands are limited or banned. If you use a disallowed command, you will receive an error message explaining the restriction. Explain the error to the User.
-   - Verify that the command is not one of the banned commands: ${BANNED_COMMANDS.join(', ')}.
-
-3. Command Execution:
-   - After ensuring proper quoting, execute the command.
-   - Capture the output of the command.
-
-4. Output Processing:
-   - If the output exceeds ${MAX_OUTPUT_LENGTH} characters, output will be truncated before being returned to you.
-   - Prepare the output for display to the user.
-
-5. Return Result:
-   - Provide the processed output of the command.
-   - If any errors occurred during execution, include those in the output.
-
-Usage notes:
-  - The command argument is required.
-  - You can specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). If not specified, commands will timeout after 30 minutes.
-  - VERY IMPORTANT: You MUST avoid using search commands like \`find\` and \`grep\`. Instead use ${GREP_TOOL_NAME}, ${GLOB_TOOL_NAME}, or ${TASK_TOOL_NAME} to search. You MUST avoid read tools like \`cat\`, \`head\`, \`tail\`, and \`ls\`, and use ${FileReadTool.name} and ${LSTool.name} to read files.
-  - When issuing multiple commands, use the ';' or '&&' operator to separate them. DO NOT use newlines (newlines are ok in quoted strings).
-  - IMPORTANT: All commands share the same shell session. Shell state (environment variables, virtual environments, current directory, etc.) persist between commands. For example, if you set an environment variable as part of a command, the environment variable will persist for subsequent commands.
-  - 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.
-  <good-example>
-  pytest /foo/bar/tests
-  </good-example>
-  <bad-example>
-  cd /foo/bar && pytest tests
-  </bad-example>
-
-# Committing changes with git
-
-When the user asks you to create a new git commit, follow these steps carefully:
-
-1. Start with a single message that contains exactly three tool_use blocks that do the following (it is VERY IMPORTANT that you send these tool_use blocks in a single message, otherwise it will feel slow to the user!):
-   - Run a git status command to see all untracked files.
-   - 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. Use the git context at the start of this conversation to determine which files are relevant to your commit. Add relevant untracked files to the staging area. Do not commit files that were already modified at the start of this conversation, if they are not relevant to your commit.
-
-3. Analyze all staged changes (both previously staged and newly added) and draft a commit message. Wrap your analysis process in <commit_analysis> tags:
-
-<commit_analysis>
-- List the files that have been changed or added
-- Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.)
-- Brainstorm the purpose or motivation behind these changes
-- Do not use tools to explore code, beyond what is available in the git context
-- Assess the impact of these changes on the overall project
-- Check for any sensitive information that shouldn't be committed
-- Draft a concise (1-2 sentences) commit message that focuses on the "why" rather than the "what"
-- Ensure your language is clear, concise, and to the point
-- 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.)
-- Ensure the message is not generic (avoid words like "Update" or "Fix" without context)
-- Review the draft message to ensure it accurately reflects the changes and their purpose
-</commit_analysis>
-
-4. Create the commit with a message ending with:
-🤖 Generated with ${PRODUCT_NAME} & {MODEL_NAME}
-Co-Authored-By: ${PRODUCT_NAME} <noreply@${PRODUCT_NAME}.com>
-
-- 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.
-
-   🤖 Generated with ${PRODUCT_NAME} & {MODEL_NAME}
-   Co-Authored-By: ${PRODUCT_NAME} <noreply@${PRODUCT_NAME}.com>
-   EOF
-   )"
-</example>
-
-5. If the commit fails due to pre-commit hook changes, retry the commit ONCE to include these automated changes. If it fails again, it usually means a pre-commit hook is preventing the commit. If the commit succeeds but you notice that files were modified by the pre-commit hook, you MUST amend your commit to include them.
-
-6. Finally, run git status to make sure the commit succeeded.
-
-Important notes:
-- When possible, combine the "git add" and "git commit" commands into a single "git commit -am" command, to speed things up
-- However, be careful not to stage files (e.g. with \`git add .\`) for commits that aren't part of the change, they may have untracked files they want to keep around, but not commit.
-- NEVER update the git config
-- DO NOT push to the remote repository
-- 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.
-- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit
-- Ensure your commit message is meaningful and concise. It should explain the purpose of the changes, not just describe them.
-- Return an empty response - the user will see the git output directly
-
-# 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. Understand the current state of the branch. Remember to send a single message that contains multiple tool_use blocks (it is VERY IMPORTANT that you do this in a single message, otherwise it will feel slow to the user!):
-   - Run a git status command to see all untracked files.
-   - 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 main...HEAD\` to understand the full commit history for the current branch (from the time it diverged from the \`main\` branch.)
-
-2. Create new branch if needed
-
-3. Commit changes if needed
-
-4. Push to remote with -u flag if needed
-
-5. 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 summary. Wrap your analysis process in <pr_analysis> tags:
-
-<pr_analysis>
-- List the commits since diverging from the main branch
-- Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.)
-- Brainstorm the purpose or motivation behind these changes
-- Assess the impact of these changes on the overall project
-- Do not use tools to explore code, beyond what is available in the git context
-- Check for any sensitive information that shouldn't be committed
-- Draft a concise (1-2 bullet points) pull request summary that focuses on the "why" rather than the "what"
-- Ensure the summary accurately reflects all changes since diverging from the main branch
-- Ensure your language is clear, concise, and to the point
-- Ensure the summary accurately reflects the changes and their purpose (ie. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.)
-- Ensure the summary is not generic (avoid words like "Update" or "Fix" without context)
-- Review the draft summary to ensure it accurately reflects the changes and their purpose
-</pr_analysis>
-
-6. 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
-[Checklist of TODOs for testing the pull request...]
-
-🤖 Generated with ${process.env.USER_TYPE === 'ant' ? `[${PRODUCT_NAME}](${PRODUCT_URL})` : PRODUCT_NAME} & {MODEL_NAME}
-EOF
-)"
-</example>
-
-Important:
-- Return an empty response - the user will see the gh output directly
-- Never update git config`

package/src/tools/BashTool/utils.ts

@@ -1,56 +0,0 @@
-import { queryQuick } from '../../services/claude'
-import { extractTag } from '../../utils/messages'
-import { MAX_OUTPUT_LENGTH } from './prompt'
-
-export function formatOutput(content: string): {
-  totalLines: number
-  truncatedContent: string
-} {
-  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}\n\n... [${content.slice(halfLength, -halfLength).split('\n').length} lines truncated] ...\n\n${end}`
-
-  return {
-    totalLines: content.split('\n').length,
-    truncatedContent: truncated,
-  }
-}
-
-export async function getCommandFilePaths(
-  command: string,
-  output: string,
-): Promise<string[]> {
-  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}\nOutput: ${output}`,
-    enablePromptCaching: true,
-  })
-  const content = response.message.content
-    .filter(_ => _.type === 'text')
-    .map(_ => _.text)
-    .join('')
-
-  return (
-    extractTag(content, 'filepaths')?.trim().split('\n').filter(Boolean) || []
-  )
-}