chore: remove codebuff.json and repurpose /init

Author: brandonkachen

.agents/base/ask.ts

@@ -99,17 +99,7 @@ Messages from the system are surrounded by <system>${closeXml('system')} or <sys
 
 ## Verifying Your Changes at the End of Your Response
 
-### User has a \`codebuff.json\`
-
-If the user has a \`codebuff.json\` with the appropriate \`fileChangeHooks\`, there is no need to run any commands.
-
-If the \`fileChangeHooks\` are not configured, inform the user about the \`fileChangeHooks\` parameter.
-
-### User has no \`codebuff.json\`
-
-If this is the case, inform the user know about the \`/init\` command (within Codebuff, not a terminal command).
-
-Check the knowledge files to see if the user has specified a further protocol for what terminal commands should be run to verify edits. For example, a \`knowledge.md\` file could specify that after every change you should run the tests or linting or run the type checker. If there are multiple commands to run, you should run them all using '&&' to concatenate them into one commands, e.g. \`npm run lint && npm run test\`.
+Check the knowledge files to see if the user has specified a protocol for what commands should be run to verify edits. If so, follow it. Otherwise, suggest the most relevant checks for the change.
 
 ## Example Response (Simplified - Demonstrating Rules)
 
@@ -152,18 +142,6 @@ What is included in knowledge files:
 
 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.
 
-# Codebuff Configuration (codebuff.json)
-
-## Schema
-
-The following describes the structure of the \`./codebuff.json\` configuration file that users might have in their project root. You can use this to understand user settings if they mention them.
-
-${PLACEHOLDER.CONFIG_SCHEMA}
-
-## Background Processes
-
-The user does not have access to these outputs. Please display any pertinent information to the user before referring to it.
-
 ${PLACEHOLDER.FILE_TREE_PROMPT}
 
 ${PLACEHOLDER.SYSTEM_INFO_PROMPT}

.agents/base/base-prompts.ts

@@ -104,16 +104,6 @@ ${
 
 ## Verifying Your Changes at the End of Your Response
 
-### User has a \`codebuff.json\`
-
-If the user has a \`codebuff.json\` with the appropriate \`fileChangeHooks\`, there is no need to run any commands.
-
-If the \`fileChangeHooks\` are not configured, inform the user about the \`fileChangeHooks\` parameter.
-
-### User has no \`codebuff.json\`
-
-If this is the case, inform the user know about the \`/init\` command (within Codebuff, not a terminal command).
-
 Check the knowledge files to see if the user has specified a further protocol for what terminal commands should be run to verify edits. For example, a \`knowledge.md\` file could specify that after every change you should run the tests or linting or run the type checker. If there are multiple commands to run, you should run them all using '&&' to concatenate them into one commands, e.g. \`npm run lint && npm run test\`.
 
 ## Example Response (Simplified - Demonstrating Rules)
@@ -202,15 +192,7 @@ 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.
 
-# Codebuff Configuration (codebuff.json)
-
-## Schema
-
-The following describes the structure of the \`./codebuff.json\` configuration file that users might have in their project root. You can use this to understand user settings if they mention them.
-
-${PLACEHOLDER.CONFIG_SCHEMA}
-
-## Background Processes
+# Background Processes
 
 The user does not have access to these outputs. Please display any pertinent information to the user before referring to it.
 

.agents/types/secret-agent-definition.ts

@@ -23,7 +23,6 @@ export interface SecretAgentDefinition
 const placeholderNames = [
   'AGENT_NAME',
   'AGENTS_PROMPT',
-  'CONFIG_SCHEMA',
   'FILE_TREE_PROMPT_SMALL',
   'FILE_TREE_PROMPT',
   'FILE_TREE_PROMPT_LARGE',

cli/src/commands/__tests__/command-args.test.ts

@@ -161,7 +161,7 @@ describe('command factory pattern', () => {
     })
 
     test('expected commands ignore args', () => {
-      const expectedNoArgs = ['login', 'logout', 'exit', 'init', 'usage']
+      const expectedNoArgs = ['login', 'logout', 'exit', 'usage', 'init']
       for (const name of expectedNoArgs) {
         const cmd = COMMAND_REGISTRY.find((c) => c.name === name)
         expect(cmd, `Command ${name} should exist`).toBeDefined()

cli/src/commands/init.ts

@@ -1,38 +1,51 @@
 import { existsSync, writeFileSync } from 'fs'
 import path from 'path'
 
-import {
-  codebuffConfigFile,
-  INITIAL_CODEBUFF_CONFIG,
-} from '@codebuff/common/json-config/constants'
-
 import { getProjectRoot } from '../project-files'
 import { getSystemMessage } from '../utils/message-history'
 
 import type { PostUserMessageFn } from '../types/contracts/send-message'
 
+const KNOWLEDGE_FILE_NAME = 'knowledge.md'
+
+const INITIAL_KNOWLEDGE_FILE = `# Project knowledge
+
+This file gives Codebuff context about your project: goals, commands, conventions, and gotchas.
+
+## Quickstart
+- Setup:
+- Dev:
+- Test:
+
+## Architecture
+- Key directories:
+- Data flow:
+
+## Conventions
+- Formatting/linting:
+- Patterns to follow:
+- Things to avoid:
+`
+
 export function handleInitializationFlowLocally(): {
   postUserMessage: PostUserMessageFn
 } {
   const projectRoot = getProjectRoot()
-  const configPath = path.join(projectRoot, codebuffConfigFile)
+  const knowledgePath = path.join(projectRoot, KNOWLEDGE_FILE_NAME)
 
-  if (existsSync(configPath)) {
+  if (existsSync(knowledgePath)) {
     const postUserMessage: PostUserMessageFn = (prev) => [
       ...prev,
-      getSystemMessage(`📋 ${codebuffConfigFile} already exists.`),
+      getSystemMessage(`📋 \`${KNOWLEDGE_FILE_NAME}\` already exists.`),
     ]
-    return {
-      postUserMessage,
-    }
+    return { postUserMessage }
   }
 
-  // Create the config file
-  writeFileSync(configPath, JSON.stringify(INITIAL_CODEBUFF_CONFIG, null, 2))
+  writeFileSync(knowledgePath, INITIAL_KNOWLEDGE_FILE)
 
   const postUserMessage: PostUserMessageFn = (prev) => [
     ...prev,
-    getSystemMessage(`✅ Created \`${codebuffConfigFile}\``),
+    getSystemMessage(`✅ Created \`${KNOWLEDGE_FILE_NAME}\``),
   ]
   return { postUserMessage }
 }

cli/src/data/slash-commands.ts

@@ -24,7 +24,7 @@ export const SLASH_COMMANDS: SlashCommand[] = [
   {
     id: 'init',
     label: 'init',
-    description: 'Configure project for better results',
+    description: 'Create a starter knowledge.md file',
   },
   {
     id: 'logout',