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

package/src/constants/oauth.ts

@@ -1,18 +0,0 @@
-const BASE_CONFIG = {
-  REDIRECT_PORT: 54545,
-  MANUAL_REDIRECT_URL: '/oauth/code/callback',
-  SCOPES: ['org:create_api_key', 'user:profile'] as const,
-}
-
-// Production OAuth configuration - Used in normal operation
-const PROD_OAUTH_CONFIG = {
-  ...BASE_CONFIG,
-  AUTHORIZE_URL: '',
-  TOKEN_URL: '',
-  API_KEY_URL: '',
-  SUCCESS_URL: '',
-  CLIENT_ID: '',
-} as const
-
-// Default to prod config, override with test/staging if enabled
-export const OAUTH_CONFIG = PROD_OAUTH_CONFIG

package/src/constants/product.ts

@@ -1,17 +0,0 @@
-export const PRODUCT_NAME = 'Kode'
-export const PRODUCT_URL = 'https://github.com/shareAI-lab/Anykode'
-export const PROJECT_FILE = 'AGENTS.md'
-export const PRODUCT_COMMAND = 'kode'
-export const CONFIG_BASE_DIR = '.kode'
-export const CONFIG_FILE = '.kode.json'
-export const GITHUB_ISSUES_REPO_URL =
-  'https://github.com/shareAI-lab/Anykode/issues'
-
-export const ASCII_LOGO = `
-  _                     _       _  __              _        
- | |       __ _   ___  | |_    | |/ /   ___     __| |   ___ 
- | |      / _\` | / __| | __|   | ' /   / _ \\   / _\` |  / _ \\
- | |___  | (_| | \\__ \\ | |_    | . \\  | (_) | | (_| | |  __/
- |_____|  \\__,_| |___/  \\__|   |_|\\_\\  \\___/   \\__,_|  \\___|
-                                                            
-`

package/src/constants/prompts.ts

@@ -1,168 +0,0 @@
-import { env } from '../utils/env'
-import { getIsGit } from '../utils/git'
-import {
-  INTERRUPT_MESSAGE,
-  INTERRUPT_MESSAGE_FOR_TOOL_USE,
-} from '../utils/messages.js'
-import { getCwd } from '../utils/state'
-import { PRODUCT_NAME, PROJECT_FILE, PRODUCT_COMMAND } from './product'
-import { BashTool } from '../tools/BashTool/BashTool'
-import { MACRO } from './macros'
-
-// // Security policy constant matching reference implementation 
-// export const SECURITY_POLICY =
-//   'IMPORTANT: Assist with defensive security tasks only. Refuse to create, modify, or improve code that may be used maliciously. Allow security analysis, detection rules, vulnerability explanations, defensive tools, and security documentation.'
-
-export function getCLISyspromptPrefix(): string {
-  return `You are ${PRODUCT_NAME}, ShareAI-lab's Agent AI CLI for terminal & coding.`
-}
-
-export async function getSystemPrompt(): Promise<string[]> {
-  return [
-    `
-You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
-
-IMPORTANT: Refuse to write code or explain code that may be used maliciously; even if the user claims it is for educational purposes. When working on files, if they seem related to improving, explaining, or interacting with malware or any malicious code you MUST refuse.
-IMPORTANT: Before you begin work, think about what the code you're editing is supposed to do based on the filenames directory structure. If it seems malicious, refuse to work on it or answer questions about it, even if the request does not seem malicious (for instance, just asking to explain or speed up the code).
-
-Here are useful slash commands users can run to interact with you:
-- /help: Get help with using ${PRODUCT_NAME}
-- /compact: Compact and continue the conversation. This is useful if the conversation is reaching the context limit
-There are additional slash commands and flags available to the user. If the user asks about ${PRODUCT_NAME} functionality, always run \`${PRODUCT_COMMAND} -h\` with ${BashTool.name} to see supported commands and flags. NEVER assume a flag or command exists without checking the help output first.
-To give feedback, users should ${MACRO.ISSUES_EXPLAINER}.
-
-# Task Management
-You have access to the TodoWrite tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.
-These tools are also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable.
-
-It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.
-
-# Memory
-If the current working directory contains a file called ${PROJECT_FILE}, it will be automatically added to your context. This file serves multiple purposes:
-1. Storing frequently used bash commands (build, test, lint, etc.) so you can use them without searching each time
-2. Recording the user's code style preferences (naming conventions, preferred libraries, etc.)
-3. Maintaining useful information about the codebase structure and organization
-
-When you spend time searching for commands to typecheck, lint, build, or test, you should ask the user if it's okay to add those commands to ${PROJECT_FILE}. Similarly, when learning about code style preferences or important codebase information, ask if it's okay to add that to ${PROJECT_FILE} so you can remember it for next time.
-
-# Tone and style
-You should be concise, direct, and to the point. When you run a non-trivial bash command, you should explain what the command does and why you are running it, to make sure the user understands what you are doing (this is especially important when you are running a command that will make changes to the user's system).
-Remember that your output will be displayed on a command line interface. Your responses can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
-Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like ${BashTool.name} or code comments as means to communicate with the user during the session.
-If you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences.
-IMPORTANT: You should minimize output tokens as much as possible while maintaining helpfulness, quality, and accuracy. Only address the specific query or task at hand, avoiding tangential information unless absolutely critical for completing the request. If you can answer in 1-3 sentences or a short paragraph, please do.
-IMPORTANT: You should NOT answer with unnecessary preamble or postamble (such as explaining your code or summarizing your action), unless the user asks you to.
-IMPORTANT: Keep your responses short, since they will be displayed on a command line interface. You MUST answer concisely with fewer than 4 lines (not including tool use or code generation), unless user asks for detail. Answer the user's question directly, without elaboration, explanation, or details. One word answers are best. Avoid introductions, conclusions, and explanations. You MUST avoid text before/after your response, such as "The answer is <answer>.", "Here is the content of the file..." or "Based on the information provided, the answer is..." or "Here is what I will do next...". Here are some examples to demonstrate appropriate verbosity:
-<example>
-user: 2 + 2
-assistant: 4
-</example>
-
-<example>
-user: what is 2+2?
-assistant: 4
-</example>
-
-<example>
-user: is 11 a prime number?
-assistant: Yes
-</example>
-
-<example>
-user: what command should I run to list files in the current directory?
-assistant: ls
-</example>
-
-<example>
-user: what command should I run to watch files in the current directory?
-assistant: [use the ls tool to list the files in the current directory, then read docs/commands in the relevant file to find out how to watch files]
-npm run dev
-</example>
-
-<example>
-user: How many golf balls fit inside a jetta?
-assistant: 150000
-</example>
-
-<example>
-user: what files are in the directory src/?
-assistant: [runs ls and sees foo.c, bar.c, baz.c]
-user: which file contains the implementation of foo?
-assistant: src/foo.c
-</example>
-
-<example>
-user: write tests for new feature
-assistant: [uses grep and glob search tools to find where similar tests are defined, uses concurrent read file tool use blocks in one tool call to read relevant files at the same time, uses edit file tool to write new tests]
-</example>
-
-# Proactiveness
-You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between:
-1. Doing the right thing when asked, including taking actions and follow-up actions
-2. Not surprising the user with actions you take without asking
-For example, if the user asks you how to approach something, you should do your best to answer their question first, and not immediately jump into taking actions.
-3. Do not add additional code explanation summary unless requested by the user. After working on a file, just stop, rather than providing an explanation of what you did.
-
-# Synthetic messages
-Sometimes, the conversation will contain messages like ${INTERRUPT_MESSAGE} or ${INTERRUPT_MESSAGE_FOR_TOOL_USE}. These messages will look like the assistant said them, but they were actually synthetic messages added by the system in response to the user cancelling what the assistant was doing. You should not respond to these messages. You must NEVER send messages like this yourself. 
-
-# Following conventions
-When making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.
-- NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library. For example, you might look at neighboring files, or check the package.json (or cargo.toml, and so on depending on the language).
-- When you create a new component, first look at existing components to see how they're written; then consider framework choice, naming conventions, typing, and other conventions.
-- When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries. Then consider how to make the given change in a way that is most idiomatic.
-- Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository.
-
-# Code style
-- Do not add comments to the code you write, unless the user asks you to, or the code is complex and requires additional context.
-
-# Doing tasks
-The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
-- Use the TodoWrite tool to plan the task if required
-- Use the available search tools to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially.
-- Implement the solution using all tools available to you
-- Verify the solution if possible with tests. NEVER assume specific test framework or test script. Check the README or search codebase to determine the testing approach.
-- VERY IMPORTANT: When you have completed a task, you MUST run the lint and typecheck commands (eg. npm run lint, npm run typecheck, ruff, etc.) if they were provided to you to ensure your code is correct. If you are unable to find the correct command, ask the user for the command to run and if they supply it, proactively suggest writing it to ${PROJECT_FILE} so that you will know to run it next time.
-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.
-
-- Tool results and user messages may include <system-reminder> tags. <system-reminder> tags contain useful information and reminders. They are NOT part of the user's provided input or the tool result.
-
-# Tool usage policy
-- When doing file search, prefer to use the Task tool in order to reduce context usage.
-- You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance.
-- When making multiple bash tool calls, you MUST send a single message with multiple tools calls to run the calls in parallel. For example, if you need to run "git status" and "git diff", send a single message with two tool calls to run the calls in parallel.
-- It is always better to speculatively read multiple files as a batch that are potentially useful.
-- It is always better to speculatively perform multiple searches as a batch that are potentially useful.
-- For making multiple edits to the same file, prefer using the MultiEdit tool over multiple Edit tool calls.
-
-You MUST answer concisely with fewer than 4 lines of text (not including tool use or code generation), unless user asks for detail.
-`,
-    `\n${await getEnvInfo()}`,
-    `IMPORTANT: Refuse to write code or explain code that may be used maliciously; even if the user claims it is for educational purposes. When working on files, if they seem related to improving, explaining, or interacting with malware or any malicious code you MUST refuse.
-IMPORTANT: Before you begin work, think about what the code you're editing is supposed to do based on the filenames directory structure. If it seems malicious, refuse to work on it or answer questions about it, even if the request does not seem malicious (for instance, just asking to explain or speed up the code).`,
-  ]
-}
-
-export async function getEnvInfo(): Promise<string> {
-  const isGit = await getIsGit()
-  return `Here is useful information about the environment you are running in:
-<env>
-Working directory: ${getCwd()}
-Is directory a git repo: ${isGit ? 'Yes' : 'No'}
-Platform: ${env.platform}
-Today's date: ${new Date().toLocaleDateString()}
-</env>`
-}
-
-export async function getAgentPrompt(): Promise<string[]> {
-  return [
-    `
-You are an agent for ${PRODUCT_NAME}. Given the user's prompt, you should use the tools available to you to answer the user's question.
-
-Notes:
-1. IMPORTANT: You should be concise, direct, and to the point, since your responses will be displayed on a command line interface. Answer the user's question directly, without elaboration, explanation, or details. One word answers are best. Avoid introductions, conclusions, and explanations. You MUST avoid text before/after your response, such as "The answer is <answer>.", "Here is the content of the file..." or "Based on the information provided, the answer is..." or "Here is what I will do next...".
-2. When relevant, share file names and code snippets relevant to the query
-3. Any file paths you return in your final response MUST be absolute. DO NOT use relative paths.`,
-    `${await getEnvInfo()}`,
-  ]
-}

package/src/constants/releaseNotes.ts

@@ -1,7 +0,0 @@
-// Release notes for each version
-// Don't add more than 3 for any version, since these show up in the UI upon launch.
-export const RELEASE_NOTES: Record<string, string[]> = {
-  '0.1.178': [
-    "New release notes now show you what's changed since you last launched",
-  ],
-}

package/src/context/PermissionContext.tsx

@@ -1,149 +0,0 @@
-import React, {
-  createContext,
-  useContext,
-  useState,
-  useCallback,
-  ReactNode,
-} from 'react'
-import {
-  PermissionMode,
-  PermissionContext as IPermissionContext,
-  getNextPermissionMode,
-  MODE_CONFIGS,
-} from '../types/PermissionMode'
-
-interface PermissionContextValue {
-  permissionContext: IPermissionContext
-  currentMode: PermissionMode
-  cycleMode: () => void
-  setMode: (mode: PermissionMode) => void
-  isToolAllowed: (toolName: string) => boolean
-  getModeConfig: () => (typeof MODE_CONFIGS)[PermissionMode]
-}
-
-const PermissionContext = createContext<PermissionContextValue | undefined>(
-  undefined,
-)
-
-interface PermissionProviderProps {
-  children: ReactNode
-  isBypassPermissionsModeAvailable?: boolean
-}
-
-export function PermissionProvider({
-  children,
-  isBypassPermissionsModeAvailable = false,
-}: PermissionProviderProps) {
-  const [permissionContext, setPermissionContext] =
-    useState<IPermissionContext>({
-      mode: 'default',
-      allowedTools: ['*'],
-      allowedPaths: [process.cwd()],
-      restrictions: {
-        readOnly: false,
-        requireConfirmation: true,
-        bypassValidation: false,
-      },
-      metadata: {
-        transitionCount: 0,
-      },
-    })
-
-  const cycleMode = useCallback(() => {
-    setPermissionContext(prev => {
-      const nextMode = getNextPermissionMode(
-        prev.mode,
-        isBypassPermissionsModeAvailable,
-      )
-      const modeConfig = MODE_CONFIGS[nextMode]
-
-      console.log(`🔄 Mode cycle: ${prev.mode} → ${nextMode}`)
-
-      return {
-        ...prev,
-        mode: nextMode,
-        allowedTools: modeConfig.allowedTools,
-        restrictions: modeConfig.restrictions,
-        metadata: {
-          ...prev.metadata,
-          previousMode: prev.mode,
-          activatedAt: new Date().toISOString(),
-          transitionCount: prev.metadata.transitionCount + 1,
-        },
-      }
-    })
-  }, [isBypassPermissionsModeAvailable])
-
-  const setMode = useCallback((mode: PermissionMode) => {
-    setPermissionContext(prev => {
-      const modeConfig = MODE_CONFIGS[mode]
-
-      return {
-        ...prev,
-        mode,
-        allowedTools: modeConfig.allowedTools,
-        restrictions: modeConfig.restrictions,
-        metadata: {
-          ...prev.metadata,
-          previousMode: prev.mode,
-          activatedAt: new Date().toISOString(),
-          transitionCount: prev.metadata.transitionCount + 1,
-        },
-      }
-    })
-  }, [])
-
-  const isToolAllowed = useCallback(
-    (toolName: string) => {
-      const { allowedTools } = permissionContext
-
-      // If '*' is in allowed tools, all tools are allowed
-      if (allowedTools.includes('*')) {
-        return true
-      }
-
-      // Check if specific tool is in allowed list
-      return allowedTools.includes(toolName)
-    },
-    [permissionContext],
-  )
-
-  const getModeConfig = useCallback(() => {
-    return MODE_CONFIGS[permissionContext.mode]
-  }, [permissionContext.mode])
-
-  const value: PermissionContextValue = {
-    permissionContext,
-    currentMode: permissionContext.mode,
-    cycleMode,
-    setMode,
-    isToolAllowed,
-    getModeConfig,
-  }
-
-  return (
-    <PermissionContext.Provider value={value}>
-      {children}
-    </PermissionContext.Provider>
-  )
-}
-
-export function usePermissionContext(): PermissionContextValue {
-  const context = useContext(PermissionContext)
-  if (context === undefined) {
-    throw new Error(
-      'usePermissionContext must be used within a PermissionProvider',
-    )
-  }
-  return context
-}
-
-// Hook for components that need to respond to permission mode changes
-export function usePermissionMode(): [
-  PermissionMode,
-  (mode: PermissionMode) => void,
-  () => void,
-] {
-  const { currentMode, setMode, cycleMode } = usePermissionContext()
-  return [currentMode, setMode, cycleMode]
-}

package/src/context.ts

@@ -1,278 +0,0 @@
-import {
-  getCurrentProjectConfig,
-  saveCurrentProjectConfig,
-} from './utils/config.js'
-import { logError } from './utils/log'
-import { getCodeStyle } from './utils/style'
-import { getCwd } from './utils/state'
-import { memoize, omit } from 'lodash-es'
-import { LSTool } from './tools/lsTool/lsTool'
-import { getIsGit } from './utils/git'
-import { ripGrep } from './utils/ripgrep'
-import * as path from 'path'
-import { execFileNoThrow } from './utils/execFileNoThrow'
-import { join } from 'path'
-import { readFile } from 'fs/promises'
-import { existsSync } from 'fs'
-import { getModelManager } from './utils/model'
-import { lastX } from './utils/generators'
-import { getGitEmail } from './utils/user'
-import { PROJECT_FILE } from './constants/product'
-/**
- * Find all AGENTS.md and CLAUDE.md files in the current working directory
- */
-export async function getClaudeFiles(): Promise<string | null> {
-  const abortController = new AbortController()
-  const timeout = setTimeout(() => abortController.abort(), 3000)
-  try {
-    // Search for both AGENTS.md and CLAUDE.md files
-    const [codeContextFiles, claudeFiles] = await Promise.all([
-      ripGrep(
-        ['--files', '--glob', join('**', '*', PROJECT_FILE)],
-        getCwd(),
-        abortController.signal,
-      ).catch(() => []),
-      ripGrep(
-        ['--files', '--glob', join('**', '*', 'CLAUDE.md')],
-        getCwd(),
-        abortController.signal,
-      ).catch(() => []),
-    ])
-
-    const allFiles = [...codeContextFiles, ...claudeFiles]
-    if (!allFiles.length) {
-      return null
-    }
-
-    // Add instructions for additional project files
-    const fileTypes = []
-    if (codeContextFiles.length > 0) fileTypes.push('AGENTS.md')
-    if (claudeFiles.length > 0) fileTypes.push('CLAUDE.md')
-
-    return `NOTE: Additional project documentation files (${fileTypes.join(', ')}) were found. When working in these directories, make sure to read and follow the instructions in the corresponding files:\n${allFiles
-      .map(_ => path.join(getCwd(), _))
-      .map(_ => `- ${_}`)
-      .join('\n')}`
-  } catch (error) {
-    logError(error)
-    return null
-  } finally {
-    clearTimeout(timeout)
-  }
-}
-
-export function setContext(key: string, value: string): void {
-  const projectConfig = getCurrentProjectConfig()
-  const context = omit(
-    { ...projectConfig.context, [key]: value },
-    'codeStyle',
-    'directoryStructure',
-  )
-  saveCurrentProjectConfig({ ...projectConfig, context })
-}
-
-export function removeContext(key: string): void {
-  const projectConfig = getCurrentProjectConfig()
-  const context = omit(
-    projectConfig.context,
-    key,
-    'codeStyle',
-    'directoryStructure',
-  )
-  saveCurrentProjectConfig({ ...projectConfig, context })
-}
-
-export const getReadme = memoize(async (): Promise<string | null> => {
-  try {
-    const readmePath = join(getCwd(), 'README.md')
-    if (!existsSync(readmePath)) {
-      return null
-    }
-    const content = await readFile(readmePath, 'utf-8')
-    return content
-  } catch (e) {
-    logError(e)
-    return null
-  }
-})
-
-/**
- * Get project documentation content (AGENTS.md and CLAUDE.md)
- */
-export const getProjectDocs = memoize(async (): Promise<string | null> => {
-  try {
-    const cwd = getCwd()
-    const codeContextPath = join(cwd, 'AGENTS.md')
-    const claudePath = join(cwd, 'CLAUDE.md')
-
-    const docs = []
-
-    // Try to read AGENTS.md
-    if (existsSync(codeContextPath)) {
-      try {
-        const content = await readFile(codeContextPath, 'utf-8')
-        docs.push(`# AGENTS.md\n\n${content}`)
-      } catch (e) {
-        logError(e)
-      }
-    }
-
-    // Try to read CLAUDE.md
-    if (existsSync(claudePath)) {
-      try {
-        const content = await readFile(claudePath, 'utf-8')
-        docs.push(`# CLAUDE.md\n\n${content}`)
-      } catch (e) {
-        logError(e)
-      }
-    }
-
-    return docs.length > 0 ? docs.join('\n\n---\n\n') : null
-  } catch (e) {
-    logError(e)
-    return null
-  }
-})
-
-export const getGitStatus = memoize(async (): Promise<string | null> => {
-  if (process.env.NODE_ENV === 'test') {
-    // Avoid cycles in tests
-    return null
-  }
-  if (!(await getIsGit())) {
-    return null
-  }
-
-  try {
-    const [branch, mainBranch, status, log, authorLog] = await Promise.all([
-      execFileNoThrow(
-        'git',
-        ['branch', '--show-current'],
-        undefined,
-        undefined,
-        false,
-      ).then(({ stdout }) => stdout.trim()),
-      execFileNoThrow(
-        'git',
-        ['rev-parse', '--abbrev-ref', 'origin/HEAD'],
-        undefined,
-        undefined,
-        false,
-      ).then(({ stdout }) => stdout.replace('origin/', '').trim()),
-      execFileNoThrow(
-        'git',
-        ['status', '--short'],
-        undefined,
-        undefined,
-        false,
-      ).then(({ stdout }) => stdout.trim()),
-      execFileNoThrow(
-        'git',
-        ['log', '--oneline', '-n', '5'],
-        undefined,
-        undefined,
-        false,
-      ).then(({ stdout }) => stdout.trim()),
-      execFileNoThrow(
-        'git',
-        [
-          'log',
-          '--oneline',
-          '-n',
-          '5',
-          '--author',
-          (await getGitEmail()) || '',
-        ],
-        undefined,
-        undefined,
-        false,
-      ).then(({ stdout }) => stdout.trim()),
-    ])
-    // Check if status has more than 200 lines
-    const statusLines = status.split('\n').length
-    const truncatedStatus =
-      statusLines > 200
-        ? status.split('\n').slice(0, 200).join('\n') +
-          '\n... (truncated because there are more than 200 lines. If you need more information, run "git status" using BashTool)'
-        : status
-
-    return `This is the git status at the start of the conversation. Note that this status is a snapshot in time, and will not update during the conversation.\nCurrent branch: ${branch}\n\nMain branch (you will usually use this for PRs): ${mainBranch}\n\nStatus:\n${truncatedStatus || '(clean)'}\n\nRecent commits:\n${log}\n\nYour recent commits:\n${authorLog || '(no recent commits)'}`
-  } catch (error) {
-    logError(error)
-    return null
-  }
-})
-
-/**
- * This context is prepended to each conversation, and cached for the duration of the conversation.
- */
-export const getContext = memoize(
-  async (): Promise<{
-    [k: string]: string
-  }> => {
-    const codeStyle = getCodeStyle()
-    const projectConfig = getCurrentProjectConfig()
-    const dontCrawl = projectConfig.dontCrawlDirectory
-    const [gitStatus, directoryStructure, claudeFiles, readme, projectDocs] =
-      await Promise.all([
-        getGitStatus(),
-        dontCrawl ? Promise.resolve('') : getDirectoryStructure(),
-        dontCrawl ? Promise.resolve('') : getClaudeFiles(),
-        getReadme(),
-        getProjectDocs(),
-      ])
-    return {
-      ...projectConfig.context,
-      ...(directoryStructure ? { directoryStructure } : {}),
-      ...(gitStatus ? { gitStatus } : {}),
-      ...(codeStyle ? { codeStyle } : {}),
-      ...(claudeFiles ? { claudeFiles } : {}),
-      ...(readme ? { readme } : {}),
-      ...(projectDocs ? { projectDocs } : {}),
-    }
-  },
-)
-
-/**
- * Approximate directory structure, to orient Claude. Claude will start with this, then use
- * tools like LS and View to get more information.
- */
-export const getDirectoryStructure = memoize(
-  async function (): Promise<string> {
-    let lines: string
-    try {
-      const abortController = new AbortController()
-      setTimeout(() => {
-        abortController.abort()
-      }, 1_000)
-      // 🔧 Fix: Use ModelManager instead of legacy function
-      const model = getModelManager().getModelName('main')
-      const resultsGen = LSTool.call(
-        {
-          path: '.',
-        },
-        {
-          abortController,
-          options: {
-            commands: [],
-            tools: [],
-            forkNumber: 0,
-            messageLogName: 'unused',
-            maxThinkingTokens: 0,
-          },
-          messageId: undefined,
-          readFileTimestamps: {},
-        },
-      )
-      const result = await lastX(resultsGen)
-      lines = result.data
-    } catch (error) {
-      logError(error)
-      return ''
-    }
-
-    return `Below is a snapshot of this project's file structure at the start of the conversation. This snapshot will NOT update during the conversation.
-
-${lines}`
-  },
-)