savant-code 0.0.19 → 0.0.20

package/packages/agent-runtime/src/system-prompt/prompts.ts

@@ -1,215 +0,0 @@
-import {
-  flattenTree,
-  getLastReadFilePaths,
-} from '@savant-code/common/project-file-tree'
-import { createMarkdownFileBlock } from '@savant-code/common/util/file'
-import { truncateString } from '@savant-code/common/util/string'
-import { closeXml } from '@savant-code/common/util/xml'
-
-import { truncateFileTreeBasedOnTokenBudget } from './truncate-file-tree'
-
-import type { Logger } from '@savant-code/common/types/contracts/logger'
-import type { ProjectFileContext } from '@savant-code/common/util/file'
-
-export const knowledgeFilesPrompt = `
-# Knowledge files
-
-Knowledge files are your guide to the project. Knowledge files (files ending in "knowledge.md", "AGENTS.md", or "CLAUDE.md") within a directory capture knowledge about that portion of the codebase. They are another way to take notes in this "Memento"-style environment.
-
-Knowledge files were created by previous engineers working on the codebase, and they were given these same instructions. They contain key concepts or helpful tips that are not obvious from the code. e.g., let's say I want to use a package manager aside from the default. That is hard to find in the codebase and would therefore be an appropriate piece of information to add to a knowledge file.
-
-Each knowledge file should develop over time into a concise but rich repository of knowledge about the files within the directory, subdirectories, or the specific file it's associated with.
-
-There is a special class of user knowledge files that are stored in the user's home directory, e.g. \`~/.knowledge.md\`, \`~/.AGENTS.md\`, or \`~/.CLAUDE.md\`. These files are available to be read, but you cannot edit them because they are outside of the project directory. Do not try to edit them.
-
-When should you update a knowledge file?
-- If the user gives broad advice to "always do x", that is a good candidate for updating a knowledge file with a concise rule to follow or bit of advice so you won't make the mistake again.
-- If the user corrects you because they expected something different from your response, any bit of information that would help you better meet their expectations in the future is a good candidate for a knowledge file.
-
-What to include in knowledge files:
-- The mission of the project. Goals, purpose, and a high-level overview of the project.
-- Explanations of how different parts of the codebase work or interact.
-- Examples of how to do common tasks with a short explanation.
-- Anti-examples of what should be avoided.
-- Anything the user has said to do.
-- Anything you can infer that the user wants you to do going forward.
-- Tips and tricks.
-- Style preferences for the codebase.
-- Technical goals that are in progress. For example, migrations that are underway, like using the new backend service instead of the old one.
-- Links to reference pages that are helpful. For example, the url of documentation for an api you are using.
-- Anything else that would be helpful for you or an inexperienced coder to know
-
-What *not* to include in knowledge files:
-- Documentation of a single file.
-- Restated code or interfaces in natural language.
-- Anything obvious from reading the codebase.
-- Lots of detail about a minor change.
-- An explanation of the code you just wrote, unless there's something very unintuitive.
-
-Again, DO NOT include details from your recent change that are not relevant more broadly.
-
-Guidelines for updating knowledge files:
-- Be concise and focused on the most important aspects of the project.
-- Integrate new knowledge into existing sections when possible.
-- Avoid overemphasizing recent changes or the aspect you're currently working on. Your current change is less important than you think.
-- Remove as many words as possible while keeping the meaning. Use command verbs. Use sentence fragments.
-- Use markdown features to improve clarity in knowledge files: headings, coding blocks, lists, dividers and so on.
-
-Once again: BE CONCISE!
-
-If the user sends you the url to a page that is helpful now or could be helpful in the future (e.g. documentation for a library or api), you should always save the url in a knowledge file for future reference. Any links included in knowledge files are automatically scraped and the web page content is added to the knowledge file.
-`.trim()
-
-const compactPrompt = `
-User has typed "compact". Summarize the current conversation and prepare it to replace the existing message history.
-
-1. Summarize the entire conversation up to this point (excluding this 'compact' command).
-2. The summary should be detailed and must capture the key decisions, analysis, changes, and outcomes.
-`.trim()
-
-const exportPrompt = `
-User has typed "export". Export the current conversation. (It's ok to proceed even if in "Ask" mode because of user change to "Export" mode).
-
-1. Summarize the entire conversation up to this point from the message history (excluding this 'export' command) into a new file.
-2. The summary MUST be in Markdown format.
-3. The summary MUST include:
-   - All key decisions made during the conversation.
-   - All significant file changes. If you have access to write_file blocks from our history, reproduce their paths and content accurately. If you only have diffs or descriptions of changes, summarize those.
-   - The reasoning behind those decisions and changes.
-4. Use the 'write_file' tool to save this Markdown summary to a new file with a generated name starting with the prefix 'savant-code-export-' like 'savant-code-export-topic-of-conversation.md' in the project root directory.
-
-Write file tool format:
-
-<write_file>
-<path>savant-code-export-file-name.md${closeXml('path')}
-<content>
-[Insert markdown content here]
-${closeXml('content')}
-${closeXml('write_file')}
-`.trim()
-
-const initPrompt = `
-User has typed "init". Help them set up project knowledge files for better results.
-
-1. Ensure there is a \`knowledge.md\` file in the project root. If it does not exist, create it.
-2. Fill \`knowledge.md\` with concise, high-signal information about this repo:
-   - What this project is and where key code lives
-   - Commands to run (install/dev/test/lint/build) based on package/tooling files
-   - Notable conventions, constraints, and "gotchas"
-3. Prefer reading existing docs (e.g. README, package.json, scripts) before writing.
-4. Use the \`write_file\` tool to create/update \`knowledge.md\`. Do not mention any deprecated configuration files.
-`.trim()
-
-export const additionalSystemPrompts = {
-  '/init': initPrompt,
-  init: initPrompt,
-  '/export': exportPrompt,
-  export: exportPrompt,
-  '/compact': compactPrompt,
-  compact: compactPrompt,
-} as const
-
-export const getProjectFileTreePrompt = (params: {
-  fileContext: ProjectFileContext
-  fileTreeTokenBudget: number
-  mode: 'search' | 'agent'
-  logger: Logger
-}) => {
-  const { fileContext, fileTreeTokenBudget, mode, logger } = params
-  const { projectRoot } = fileContext
-  const { printedTree, truncationLevel } = truncateFileTreeBasedOnTokenBudget({
-    fileContext,
-    tokenBudget: Math.max(0, fileTreeTokenBudget),
-    logger,
-  })
-
-  const truncationNote =
-    truncationLevel === 'none'
-      ? ''
-      : truncationLevel === 'unimportant-files'
-        ? '\nNote: Unimportant files (like build artifacts and cache files) have been removed from the file tree.'
-        : truncationLevel === 'tokens'
-          ? '\nNote: Selected function, class, and variable names in source files have been removed from the file tree to fit within token limits.'
-          : '\nNote: The file tree has been truncated to show a subset of files to fit within token limits.'
-
-  return `
-# Project file tree
-
-As Savant, you have access to all the files in the project.
-
-The following is the path to the project on the user's computer. It is also the current working directory for terminal commands:
-<project_path>
-${projectRoot}
-${closeXml('project_path')}
-
-Within this project directory, here is the file tree.
-Note that the file tree:
-- Is cached from the start of this conversation. Files created after the start of this conversation will not appear.
-- Excludes files that are .gitignored.
-${
-  mode === 'agent'
-    ? `\nThe project file tree below can be ignored unless you need to know what files are in the project.\n`
-    : ''
-}
-<project_file_tree>
-${printedTree}
-${closeXml('project_file_tree')}
-${truncationNote}
-`.trim()
-}
-
-const windowsNote = `
-Note: terminal commands run in bash on Windows (Git Bash / MSYS), so POSIX syntax works — \`mkdir -p\`, \`grep\`, \`ls\`, \`mv\`, \`rm\`, \`cp\` are all available. Write paths with forward slashes: bash treats \`\\\` as an escape, so \`C:\\Users\\me\` becomes \`C:Usersme\`. Only when the user's shell is PowerShell should you use PowerShell verbs (\`dir\`, \`move\`, \`del\`, \`copy\`) and backslash paths.
-`.trim()
-
-export const getSystemInfoPrompt = (fileContext: ProjectFileContext) => {
-  const { fileTree, shellConfigFiles, systemInfo } = fileContext
-  const flattenedNodes = flattenTree(fileTree)
-  const lastReadFilePaths = getLastReadFilePaths(flattenedNodes, 20)
-
-  return `
-# System Info
-
-Operating System: ${systemInfo.platform}
-${systemInfo.platform === 'win32' ? windowsNote + '\n' : ''}
-Shell: ${systemInfo.shell}
-Chrome: ${systemInfo.chromeAvailable ? 'installed' : 'not found'}
-
-<user_shell_config_files>
-${Object.entries(shellConfigFiles)
-  .map(([path, content]) => createMarkdownFileBlock(path, content))
-  .join('\n')}
-${closeXml('user_shell_config_files')}
-
-The following are the most recently read files according to the OS atime. This is cached from the start of this conversation:
-<recently_read_file_paths_most_recent_first>
-${lastReadFilePaths.join('\n')}
-${closeXml('recently_read_file_paths_most_recent_first')}
-`.trim()
-}
-
-export const getGitChangesPrompt = (fileContext: ProjectFileContext) => {
-  const { gitChanges } = fileContext
-  if (!gitChanges) {
-    return ''
-  }
-  const maxLength = 30_000
-  return `
-Git Changes:
-<git_status>
-${truncateString(gitChanges.status, maxLength / 10)}
-${closeXml('git_status')}
-
-<git_diff>
-${truncateString(gitChanges.diff, maxLength)}
-${closeXml('git_diff')}
-
-<git_diff_cached>
-${truncateString(gitChanges.diffCached, maxLength)}
-${closeXml('git_diff_cached')}
-
-<git_commit_messages_most_recent_first>
-${truncateString(gitChanges.lastCommitMessages, maxLength / 10)}
-${closeXml('git_commit_messages_most_recent_first')}
-`.trim()
-}

package/packages/agent-runtime/src/system-prompt/search-system-prompt.ts

@@ -1,89 +0,0 @@
-import { buildArray } from '@savant-code/common/util/array'
-
-import {
-  getGitChangesPrompt,
-  getProjectFileTreePrompt,
-  getSystemInfoPrompt,
-} from './prompts'
-import { countTokens, countTokensJson } from '../util/token-counter'
-
-import type { Logger } from '@savant-code/common/types/contracts/logger'
-import type { ProjectFileContext } from '@savant-code/common/util/file'
-
-export function getSearchSystemPrompt(params: {
-  fileContext: ProjectFileContext
-  messagesTokens: number
-  logger: Logger
-  options: {
-    agentStepId: string
-    clientSessionId: string
-    fingerprintId: string
-    userInputId: string
-    userId: string | undefined
-  }
-}): string {
-  const { fileContext, messagesTokens, logger, options: _options } = params
-  const _startTime = Date.now()
-
-  const maxTokens = 500_000
-  const maxFilesTokens = 100_000
-  const miscTokens = 10_000
-  const systemPromptTokenBudget = maxTokens - messagesTokens - miscTokens
-
-  const gitChangesPrompt = getGitChangesPrompt(fileContext)
-  const fileTreeTokenBudget =
-    // Give file tree as much token budget as possible,
-    // but stick to fixed increments so as not to break prompt caching too often.
-    Math.floor(
-      (systemPromptTokenBudget -
-        maxFilesTokens -
-        countTokens(gitChangesPrompt)) /
-        20_000,
-    ) * 20_000
-
-  const projectFileTreePrompt = getProjectFileTreePrompt({
-    fileContext,
-    fileTreeTokenBudget,
-    mode: 'search',
-    logger,
-  })
-
-  const _t = Date.now()
-  const truncationBudgets = [5_000, 20_000, 40_000, 100_000, 500_000]
-  const _truncatedTrees = truncationBudgets.reduce(
-    (acc, budget) => {
-      acc[budget] = getProjectFileTreePrompt({
-        fileContext,
-        fileTreeTokenBudget: budget,
-        mode: 'search',
-        logger,
-      })
-      return acc
-    },
-    {} as Record<number, string>,
-  )
-  const _fileTreeTokens = countTokensJson(projectFileTreePrompt)
-
-  const systemInfoPrompt = getSystemInfoPrompt(fileContext)
-  const _systemInfoTokens = countTokens(systemInfoPrompt)
-
-  const systemPrompt = buildArray([
-    projectFileTreePrompt,
-    systemInfoPrompt,
-    gitChangesPrompt,
-  ]).join('\n\n')
-
-  // logger.debug(
-  //   {
-  //     fileTreeTokens,
-  //     fileTreeTokenBudget,
-  //     systemInfoTokens,
-  //     systemPromptTokens: countTokensJson(systemPrompt),
-  //     messagesTokens,
-  //     duration: Date.now() - startTime,
-  //   },
-  //   'search system prompt tokens',
-  // )
-
-  return systemPrompt
-}