Merge branch 'main' into xml-tools

Author: jahooma

.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',

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing to Codebuff
 
-Hey there! 👋 Thanks for wanting to contribute to Codebuff. Whether you're squashing bugs, building cool features, or making our docs better, we're excited to have you aboard!
+Hey there! 👋 Thanks for contributing to Codebuff. Bug fixes, features, and documentation improvements are welcome.
 
 ## Getting Started
 
@@ -147,15 +147,13 @@ Not sure where to start? Here are some great ways to jump in:
 
 ### Development Workflow
 
-Here's how we like to work together:
+1. **Fork and branch** - Create a fork and a new branch
+2. **Follow style guidelines** - See below
+3. **Test** - Write tests for new features, run `bun test`
+4. **Type check** - Run `bun run typecheck`
+5. **Submit a PR** - Clear description of changes
 
-1. **Fork and branch** - Create your own fork and a new branch for your changes
-2. **Code away** - Follow our style guidelines (more on that below)
-3. **Test it** - Write tests for new features and run `bun test` to make sure everything works
-4. **Type check** - Run `bun run typecheck` to catch any TypeScript issues
-5. **Submit a PR** - Open a pull request with a clear description of what you built and why
-
-_Pro tip: Small, focused PRs are easier to review and merge quickly!_
+Small PRs merge faster.
 
 ### Code Style Guidelines
 
@@ -218,27 +216,25 @@ test: add unit tests for file operations
 
 ## Areas Where We Need Help
 
-There are tons of ways to make Codebuff better! Here are some areas where your skills could really shine:
-
 ### 🤖 **Agent Development**
 
-Build specialized agents in `.agents/` for different languages, frameworks, or workflows. Think React experts, Python debuggers, or Git wizards!
+Build agents in `.agents/` for different languages, frameworks, or workflows.
 
 ### 🔧 **Tool System**
 
-Add new capabilities in `common/src/tools` and the SDK helpers - file operations, API integrations, development environment helpers. The sky's the limit!
+Add capabilities in `common/src/tools` and SDK helpers: file operations, API integrations, dev environment helpers.
 
 ### 📦 **SDK Improvements**
 
-Make the SDK in `sdk/` even more powerful with new methods, better TypeScript support, or killer integration examples.
+New methods, better TypeScript support, integration examples in `sdk/`.
 
-### 💻 **CLI Magic**
+### 💻 **CLI**
 
-Enhance the user experience in `cli/` with smoother commands, better error messages, or interactive features that make developers smile.
+Improve `cli/`: better commands, error messages, interactive features.
 
 ### 🌐 **Web Dashboard**
 
-Level up the web interface in `web/` with better agent management, project templates, analytics, or any UX improvements you can dream up.
+Improve `web/`: agent management, project templates, analytics.
 
 ## Getting Help
 

README.md

@@ -83,17 +83,17 @@ To get started building your own agents, run:
 codebuff init-agents
 ```
 
-> 💡 **Tip**: This command creates a comprehensive agent development guide at `.agents/README.md` (293 lines) with detailed documentation, complete examples, and full TypeScript type definitions. Start there for complete guidance.
+> 💡 **Tip**: This creates an agent development guide at `.agents/README.md` with examples and TypeScript types.
 
 This creates:
 ```
 .agents/
-├── README.md              # Comprehensive 293-line agent guide
-├── my-custom-agent.ts     # Working agent template to edit
-├── package.json           # NPM package configuration
-├── LICENSE                # Apache-2.0 license for publishing
-├── examples/              # 3 example agents (basic → advanced)
-└── types/                 # Complete TypeScript definitions
+├── README.md              # Agent development guide
+├── my-custom-agent.ts     # Working agent template
+├── package.json           # NPM package config
+├── LICENSE                # Apache-2.0 license
+├── examples/              # 3 example agents
+└── types/                 # TypeScript definitions
 ```
 
 You can write agent definition files that give you maximum control over agent behavior.
@@ -146,7 +146,7 @@ const client = new CodebuffClient({
 // 2. Do a coding task...
 const result = await client.run({
   agent: 'base', // Codebuff's base coding agent
-  prompt: 'Add comprehensive error handling to all API endpoints',
+  prompt: 'Add error handling to all API endpoints',
   handleEvent: (event) => {
     console.log('Progress', event)
   },
@@ -174,13 +174,13 @@ Learn more about the SDK [here](https://www.npmjs.com/package/@codebuff/sdk).
 
 ## Why choose Codebuff
 
-**Deep customizability**: Create sophisticated agent workflows with TypeScript generators that mix AI generation with programmatic control. Define custom agents that spawn subagents, implement conditional logic, and orchestrate complex multi-step processes that adapt to your specific use cases.
+**Custom workflows**: TypeScript generators let you mix AI generation with programmatic control. Agents can spawn subagents, branch on conditions, and run multi-step processes.
 
 **Any model on OpenRouter**: Unlike Claude Code which locks you into Anthropic's models, Codebuff supports any model available on [OpenRouter](https://openrouter.ai/models) - from Claude and GPT to specialized models like Qwen, DeepSeek, and others. Switch models for different tasks or use the latest releases without waiting for platform updates.
 
 **Reuse any published agent**: Compose existing [published agents](https://www.codebuff.com/store) to get a leg up. Codebuff agents are the new MCP!
 
-**Fully customizable SDK**: Build Codebuff's capabilities directly into your applications with a complete TypeScript SDK. Create custom tools, integrate with your CI/CD pipeline, build AI-powered development environments, or embed intelligent coding assistance into your products.
+**SDK**: Build Codebuff into your applications. Create custom tools, integrate with CI/CD, or embed coding assistance into your products.
 
 ## Contributing to Codebuff
 
@@ -232,7 +232,7 @@ Some ways you can help:
 
 **Documentation**: [codebuff.com/docs](https://codebuff.com/docs)
 
-**Community**: [Discord](https://codebuff.com/discord) - Join our friendly community
+**Community**: [Discord](https://codebuff.com/discord)
 
 **Issues & Ideas**: [GitHub Issues](https://github.com/CodebuffAI/codebuff/issues)