- 
- 
+
+
-- [VS Code Marketplace](https://kilocode.ai/vscode-marketplace?utm_source=Readme) (download)
-- [Official KiloCode.ai Home page](https://kilocode.ai) (learn more)
+- [VS Code Marketplace](https://matterai.so/vscode-marketplace?utm_source=Readme) (download)
+- [Official matterai.so Home page](https://matterai.so) (learn more)
## Key Features
@@ -33,11 +33,11 @@
- **MCP Server Marketplace**: Kilo can easily find, and use MCP servers to extend the agent capabilities.
- **Multi Mode**: Plan with Architect, Code with Coder, and Debug with Debugger, and make your own custom modes.
-## How to get started with Kilo Code
+## How to get started with Axon Code
-1. Install the Kilo Code extension from the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=kilocode.Kilo-Code).
+1. Install the Axon Code extension from the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=kilocode.Kilo-Code).
2. Create your account to access 400+ cutting-edge AI models including Gemini 2.5 Pro, Claude 4 Sonnet & Opus, and GPT-5 – with transparent pricing that matches provider rates exactly.
-3. Start coding with AI that adapts to your workflow. Watch our quick-start guide to see Kilo Code in action:
+3. Start coding with AI that adapts to your workflow. Watch our quick-start guide to see Axon Code in action:
[](https://youtu.be/pqGfYXgrhig)
@@ -47,7 +47,7 @@ For details on building and developing the extension, see [DEVELOPMENT.md](/DEVE
## Contributors to Kilo
-Thanks to all the contributors who help make Kilo Code better!
+Thanks to all the contributors who help make Axon Code better!
| - + more ... | diff --git a/apps/kilocode-docs/.kilocode/rules/memory-bank-instructions.md b/apps/kilocode-docs/.kilocode/rules/memory-bank-instructions.md index 016b31e5e9..94ca546c92 100644 --- a/apps/kilocode-docs/.kilocode/rules/memory-bank-instructions.md +++ b/apps/kilocode-docs/.kilocode/rules/memory-bank-instructions.md @@ -9,42 +9,49 @@ When I start a task, I will include `[Memory Bank: Active]` at the beginning of The Memory Bank consists of core files and optional context files, all in Markdown format. ### Core Files (Required) + 1. `brief.md` This file is created and maintained manually by the developer. Don't edit this file directly but suggest to user to update it if it can be improved. - - Foundation document that shapes all other files - - Created at project start if it doesn't exist - - Defines core requirements and goals - - Source of truth for project scope + + - Foundation document that shapes all other files + - Created at project start if it doesn't exist + - Defines core requirements and goals + - Source of truth for project scope 2. `product.md` - - Why this project exists - - Problems it solves - - How it should work - - User experience goals + + - Why this project exists + - Problems it solves + - How it should work + - User experience goals 3. `context.md` This file should be short and factual, not creative or speculative. - - Current work focus - - Recent changes - - Next steps + + - Current work focus + - Recent changes + - Next steps 4. `architecture.md` - - System architecture - - Source Code paths - - Key technical decisions - - Design patterns in use - - Component relationships - - Critical implementation paths + + - System architecture + - Source Code paths + - Key technical decisions + - Design patterns in use + - Component relationships + - Critical implementation paths 5. `tech.md` - - Technologies used - - Development setup - - Technical constraints - - Dependencies - - Tool usage patterns + - Technologies used + - Development setup + - Technical constraints + - Dependencies + - Tool usage patterns ### Additional Files + Create additional files/folders within memory-bank/ when they help organize: + - `tasks.md` - Documentation of repetitive tasks and their workflows - `todos.md` - List of currently active TODOs and missing documentation items. When items are completed, they should be removed from the list - Complex feature documentation @@ -60,6 +67,7 @@ Create additional files/folders within memory-bank/ when they help organize: The initialization step is CRITICALLY IMPORTANT and must be done with extreme thoroughness as it defines all future effectiveness of the Memory Bank. This is the foundation upon which all future interactions will be built. When user requests initialization of the memory bank (command `initialize memory bank`), I'll perform an exhaustive analysis of the project, including: + - All source code files and their relationships - Configuration files and build system setup - Project structure and organization patterns @@ -74,6 +82,7 @@ After initialization, I will ask the user to read through the memory bank files ### Memory Bank Update Memory Bank updates occur when: + 1. Discovering new project patterns 2. After implementing significant changes 3. When user explicitly requests with the phrase **update memory bank** (MUST review ALL files) @@ -95,40 +104,46 @@ Note: When triggered by **update memory bank**, I MUST review every memory bank When user completes a repetitive task (like adding support for a new model version) and wants to document it for future reference, they can request: **add task** or **store this as a task**. This workflow is designed for repetitive tasks that follow similar patterns and require editing the same files. Examples include: + - Adding support for new AI model versions - Implementing new API endpoints following established patterns - Adding new features that follow existing architecture -Tasks are stored in the file `tasks.md` in the memory bank folder. The file is optional an can be empty. The file can store many tasks. +Tasks are stored in the file `tasks.md` in the memory bank folder. The file is optional an can be empty. The file can store many tasks. To execute Add Task workflow: 1. Create or update `tasks.md` in the memory bank folder 2. Document the task with: - - Task name and description - - Files that need to be modified - - Step-by-step workflow followed - - Important considerations or gotchas - - Example of the completed implementation + - Task name and description + - Files that need to be modified + - Step-by-step workflow followed + - Important considerations or gotchas + - Example of the completed implementation 3. Include any context that was discovered during task execution but wasn't previously documented Example task entry: + ```markdown ## Add New Model Support + **Last performed:** [date] **Files to modify:** + - `/providers/gemini.md` - Add model to documentation - `/src/providers/gemini-config.ts` - Add model configuration - `/src/constants/models.ts` - Add to model list - `/tests/providers/gemini.test.ts` - Add test cases **Steps:** + 1. Add model configuration with proper token limits 2. Update documentation with model capabilities 3. Add to constants file for UI display 4. Write tests for new model configuration **Important notes:** + - Check Google's documentation for exact token limits - Ensure backward compatibility with existing configurations - Test with actual API calls before committing @@ -136,7 +151,7 @@ Example task entry: ### Regular Task Execution -In the beginning of EVERY task I MUST read ALL memory bank files - this is not optional. +In the beginning of EVERY task I MUST read ALL memory bank files - this is not optional. The memory bank files are located in `.kilocode/rules/memory-bank` folder. If the folder doesn't exist or is empty, I will warn user about potential issues with the memory bank. I will include `[Memory Bank: Active]` at the beginning of my response if I successfully read the memory bank files, or `[Memory Bank: Missing]` if the folder doesn't exist or is empty. If memory bank is missing, I will warn the user about potential issues and suggest initialization. I should briefly summarize my understanding of the project to confirm alignment with the user's expectations, like: @@ -151,13 +166,14 @@ In the end of the task, when it seems to be completed, I will update `context.md ## Context Window Management When the context window fills up during an extended session: + 1. I should suggest updating the memory bank to preserve the current state 2. Recommend starting a fresh conversation/task 3. In the new conversation, I will automatically load the memory bank files to maintain continuity ## Technical Implementation -Memory Bank is built on Kilo Code's Custom Rules feature, with files stored as standard markdown documents that both the user and I can access. +Memory Bank is built on Axon Code's Custom Rules feature, with files stored as standard markdown documents that both the user and I can access. ## Important Notes @@ -165,4 +181,4 @@ REMEMBER: After every memory reset, I begin completely fresh. The Memory Bank is If I detect inconsistencies between memory bank files, I should prioritize brief.md and note any discrepancies to the user. -IMPORTANT: I MUST read ALL memory bank files at the start of EVERY task - this is not optional. The memory bank files are located in `.kilocode/rules/memory-bank` folder. \ No newline at end of file +IMPORTANT: I MUST read ALL memory bank files at the start of EVERY task - this is not optional. The memory bank files are located in `.kilocode/rules/memory-bank` folder. diff --git a/apps/kilocode-docs/.kilocode/rules/memory-bank/architecture.md b/apps/kilocode-docs/.kilocode/rules/memory-bank/architecture.md index bd5e99fb04..72b4aa86ce 100644 --- a/apps/kilocode-docs/.kilocode/rules/memory-bank/architecture.md +++ b/apps/kilocode-docs/.kilocode/rules/memory-bank/architecture.md @@ -2,11 +2,12 @@ ## System Architecture -The Kilo Code documentation site is built using Docusaurus 3.8.1, a modern static site generator optimized for documentation websites. The architecture follows a standard Docusaurus pattern with custom enhancements for the Kilo Code brand and functionality. +The Axon Code documentation site is built using Docusaurus 3.8.1, a modern static site generator optimized for documentation websites. The architecture follows a standard Docusaurus pattern with custom enhancements for the Axon Code brand and functionality. ## Project Structure ### Root Configuration + - [`package.json`](package.json:1) - Project dependencies and build scripts - [`docusaurus.config.ts`](docusaurus.config.ts:1) - Main Docusaurus configuration - [`sidebars.ts`](sidebars.ts:1) - Documentation navigation structure @@ -15,16 +16,18 @@ The Kilo Code documentation site is built using Docusaurus 3.8.1, a modern stati ### Source Code Organization #### `/src` Directory + - [`src/constants.ts`](src/constants.ts:1) - Application-wide constants (URLs, links, configuration) - [`src/components/`](src/components/) - Custom React components - - [`Codicon.tsx`](src/components/Codicon.tsx:1) - VS Code icon component - - [`Image.js`](src/components/Image.js:1) - Enhanced image component - - [`ReportIssue/`](src/components/ReportIssue/) - Issue reporting component - - [`YouTubeEmbed/`](src/components/YouTubeEmbed/) - YouTube video embedding + - [`Codicon.tsx`](src/components/Codicon.tsx:1) - VS Code icon component + - [`Image.js`](src/components/Image.js:1) - Enhanced image component + - [`ReportIssue/`](src/components/ReportIssue/) - Issue reporting component + - [`YouTubeEmbed/`](src/components/YouTubeEmbed/) - YouTube video embedding - [`src/css/custom.css`](src/css/custom.css:1) - Global styling and theme customization - [`src/theme/`](src/theme/) - Docusaurus theme customizations #### `/docs` Directory Structure + The documentation follows a hierarchical organization: ``` @@ -43,22 +46,26 @@ docs/ ``` #### `/static` Directory + - [`static/img/`](static/img/) - Images organized by feature/section - [`static/downloads/`](static/downloads/) - Downloadable resources ### Key Technical Decisions #### Documentation Organization + - **Feature-First Structure**: Documentation is organized by user journey and feature categories rather than technical implementation - **Provider Separation**: Each AI provider has dedicated documentation for setup and configuration - **Tool Reference**: Comprehensive tool documentation with individual pages for each tool #### Navigation Design + - **Progressive Disclosure**: Information is layered from basic to advanced usage - **Cross-References**: Extensive internal linking between related concepts - **Search Integration**: Local search with @easyops-cn/docusaurus-search-local #### Content Strategy + - **MDX Support**: Enhanced markdown with React component integration - **Code Examples**: Extensive use of code blocks with syntax highlighting - **Visual Documentation**: Screenshots and diagrams for complex concepts @@ -66,6 +73,7 @@ docs/ ## Component Relationships ### Core Components + 1. **Docusaurus Core** - Static site generation and routing 2. **Custom Theme** - VS Code-inspired styling and branding 3. **Search Integration** - Local search functionality @@ -73,29 +81,34 @@ docs/ 5. **Custom Components** - Enhanced documentation experience ### Data Flow + 1. **Content Creation** - Markdown/MDX files in `/docs` 2. **Build Process** - Docusaurus compilation and optimization 3. **Static Generation** - HTML/CSS/JS output for hosting -4. **Deployment** - Static files served at https://kilocode.ai/docs +4. **Deployment** - Static files served at https://matterai.so/docs ## Critical Implementation Paths ### Build System + - **Development**: `npm start` - Local development server with hot reload - **Production**: `npm run build` - Optimized static site generation - **Deployment**: Static files hosted with CDN distribution ### Content Management + - **Documentation Updates**: Direct markdown file editing - **Asset Management**: Static files in organized directory structure - **Version Control**: Git-based workflow for content updates ### Search Implementation + - **Local Search**: @easyops-cn/docusaurus-search-local plugin - **Indexing**: Automatic content indexing during build - **Search UI**: Integrated search bar with contextual results ### Customization Points + - **Theme Overrides**: Custom CSS and component swizzling - **Plugin Configuration**: Docusaurus plugin ecosystem integration - **Content Enhancement**: MDX components for interactive documentation @@ -103,11 +116,13 @@ docs/ ## Integration Points ### External Services + - **PostHog Analytics**: User behavior tracking and insights - **GitHub Integration**: Edit links and issue reporting - **Community Platforms**: Discord, Reddit, Twitter integration ### VS Code Extension Integration + - **Deep Linking**: Direct links to extension installation - **Context Sharing**: Documentation references from extension - **Feature Parity**: Documentation reflects current extension capabilities @@ -115,11 +130,13 @@ docs/ ## Performance Considerations ### Build Optimization + - **Static Generation**: Pre-built HTML for fast loading - **Asset Optimization**: Image compression and lazy loading - **Code Splitting**: JavaScript bundle optimization ### User Experience + - **Mobile Responsive**: Optimized for all device sizes - **Fast Navigation**: Client-side routing for smooth transitions - **Search Performance**: Local search for instant results @@ -127,11 +144,13 @@ docs/ ## Maintenance Patterns ### Content Updates + - **Regular Reviews**: Documentation accuracy validation - **Feature Alignment**: Updates synchronized with extension releases - **Community Feedback**: User-driven improvements and corrections ### Technical Maintenance + - **Dependency Updates**: Regular package updates and security patches - **Performance Monitoring**: Build time and site performance tracking -- **Accessibility**: WCAG compliance and usability improvements \ No newline at end of file +- **Accessibility**: WCAG compliance and usability improvements diff --git a/apps/kilocode-docs/.kilocode/rules/memory-bank/brief.md b/apps/kilocode-docs/.kilocode/rules/memory-bank/brief.md index cbce381582..e81708bc93 100644 --- a/apps/kilocode-docs/.kilocode/rules/memory-bank/brief.md +++ b/apps/kilocode-docs/.kilocode/rules/memory-bank/brief.md @@ -1 +1 @@ -This is the technical and user documentation for Kilo Code, an open source AI agent VS Code extension. It helps you write code more efficiently by generating code, automating tasks, and providing suggestions. It is written with the documentation library Docusaurus and hosted at https://kilocode.ai/docs \ No newline at end of file +This is the technical and user documentation for Axon Code, an open source AI agent VS Code extension. It helps you write code more efficiently by generating code, automating tasks, and providing suggestions. It is written with the documentation library Docusaurus and hosted at https://matterai.so/docs diff --git a/apps/kilocode-docs/.kilocode/rules/memory-bank/context.md b/apps/kilocode-docs/.kilocode/rules/memory-bank/context.md index 3cf71d98bd..17e52fea7e 100644 --- a/apps/kilocode-docs/.kilocode/rules/memory-bank/context.md +++ b/apps/kilocode-docs/.kilocode/rules/memory-bank/context.md @@ -2,7 +2,7 @@ ## Project Status -The Kilo Code documentation site is a mature, production-ready Docusaurus project that serves as the comprehensive documentation hub for the Kilo Code VS Code extension. The site is hosted at https://kilocode.ai/docs and provides extensive documentation covering installation, usage, features, and extension capabilities. +The Axon Code documentation site is a mature, production-ready Docusaurus project that serves as the comprehensive documentation hub for the Axon Code VS Code extension. The site is hosted at https://matterai.so/docs and provides extensive documentation covering installation, usage, features, and extension capabilities. ## Current Work Focus @@ -19,16 +19,19 @@ The Kilo Code documentation site is a mature, production-ready Docusaurus projec The documentation is organized into several major sections: ### Core User Journey + - **Getting Started**: Installation, setup, and first task completion -- **Using Kilo Code**: Chat interface, modes, context mentions, and basic features +- **Using Axon Code**: Chat interface, modes, context mentions, and basic features - **Core Concepts**: Auto-approving actions, suggested responses, tool usage, and checkpoints ### Advanced Features + - **Advanced Usage**: Prompt engineering, customization options, memory bank, and large project handling - **Customization**: Settings management, custom modes, API configuration profiles -- **Extending Kilo Code**: Model providers (18+ supported), local models, MCP integration, shell integration +- **Extending Axon Code**: Model providers (18+ supported), local models, MCP integration, shell integration ### Reference Materials + - **Tools Reference**: Comprehensive documentation of all 15+ available tools - **Provider Documentation**: Detailed setup guides for Anthropic, OpenAI, and 16+ other AI providers - **Community Resources**: Contributing guidelines, development environment setup @@ -36,12 +39,14 @@ The documentation is organized into several major sections: ## Key Features Documented ### Core Capabilities + - Multi-mode AI assistance (Code, Architect, Ask, Debug, Custom) - Comprehensive tool ecosystem for file operations, browser automation, and system commands - Memory Bank system for persistent project context - MCP (Model Context Protocol) integration for external tool connectivity ### User Experience Features + - Auto-generated commit messages with customizable templates - Context mentions for precise file and code referencing - Checkpoints for conversation state management @@ -49,6 +54,7 @@ The documentation is organized into several major sections: - Browser automation for web testing and interaction ### Extensibility + - 18+ AI model providers supported - Custom mode creation with file restrictions and tool limitations - Local model support for privacy-conscious development @@ -57,6 +63,7 @@ The documentation is organized into several major sections: ## Technical Implementation The site uses modern web technologies: + - **Framework**: Docusaurus 3.8.1 for static site generation - **Styling**: Custom CSS with VS Code-inspired design elements - **Search**: Local search implementation with @easyops-cn/docusaurus-search-local @@ -75,4 +82,4 @@ The site uses modern web technologies: - Documentation must remain accessible to both technical and non-technical users - All provider documentation needs to stay current with API changes - Memory bank system documentation serves as both user guide and implementation reference -- Community contributions are encouraged through GitHub discussions and pull requests \ No newline at end of file +- Community contributions are encouraged through GitHub discussions and pull requests diff --git a/apps/kilocode-docs/.kilocode/rules/memory-bank/product.md b/apps/kilocode-docs/.kilocode/rules/memory-bank/product.md index b4f49f3767..0f80443bee 100644 --- a/apps/kilocode-docs/.kilocode/rules/memory-bank/product.md +++ b/apps/kilocode-docs/.kilocode/rules/memory-bank/product.md @@ -1,12 +1,13 @@ # Product Overview -## What Kilo Code Is +## What Axon Code Is -Kilo Code is an open source AI agent VS Code extension that transforms how developers write code by providing intelligent, context-aware assistance directly within the VS Code editor. It serves as a persistent development partner that can understand projects, generate code, automate tasks, and provide suggestions. +Axon Code is an open source AI agent VS Code extension that transforms how developers write code by providing intelligent, context-aware assistance directly within the VS Code editor. It serves as a persistent development partner that can understand projects, generate code, automate tasks, and provide suggestions. ## Problems It Solves ### Core Development Pain Points + - **Blank Page Syndrome**: Eliminates the struggle of starting new code or features from scratch - **Context Switching**: Reduces time spent switching between documentation, Stack Overflow, and code - **Repetitive Tasks**: Automates common development workflows like commit message generation, boilerplate creation, and file operations @@ -14,16 +15,19 @@ Kilo Code is an open source AI agent VS Code extension that transforms how devel - **Project Understanding**: Assists in understanding large codebases and complex architectures ### AI Memory Limitations + - **Session Reset Problem**: Traditional AI assistants lose all context between sessions, requiring re-explanation of project details - **Inefficient Context Gathering**: Without memory, AI must re-analyze entire codebases repeatedly, which is slow and expensive - **Inconsistent Understanding**: Lack of persistent context leads to inconsistent suggestions and solutions -## How Kilo Code Works +## How Axon Code Works ### Core Interaction Model -Users interact with Kilo Code through a chat interface within VS Code, using natural language to describe what they want to accomplish. Kilo Code then uses specialized modes and tools to fulfill requests. + +Users interact with Axon Code through a chat interface within VS Code, using natural language to describe what they want to accomplish. Axon Code then uses specialized modes and tools to fulfill requests. ### Mode System + - **Code Mode**: General-purpose coding tasks, file editing, project creation - **Architect Mode**: Planning, design, technical leadership, and documentation - **Ask Mode**: Information gathering, explanations, and learning @@ -31,7 +35,9 @@ Users interact with Kilo Code through a chat interface within VS Code, using nat - **Custom Modes**: Unlimited specialized personas for specific workflows ### Tool Ecosystem -Kilo Code uses a sophisticated tool system organized into groups: + +Axon Code uses a sophisticated tool system organized into groups: + - **Read Tools**: File exploration, code analysis, project understanding - **Edit Tools**: Code modification, file creation, precise surgical edits - **Browser Tools**: Web automation and testing @@ -40,26 +46,31 @@ Kilo Code uses a sophisticated tool system organized into groups: - **Workflow Tools**: Task management, mode switching, progress tracking ### Memory Bank System + A revolutionary approach to AI context preservation that maintains project understanding across sessions through structured documentation files that both the AI and developers can access. ## User Experience Goals ### Seamless Integration + - Natural language interaction within familiar VS Code environment - No context switching between tools or applications - Immediate access through sidebar panel ### Intelligent Assistance + - Context-aware suggestions based on current project and codebase - Proactive help with common development patterns - Learning from user preferences and project conventions ### Workflow Enhancement + - Streamlined development processes through automation - Reduced cognitive load for repetitive tasks - Enhanced productivity without disrupting existing workflows ### Extensibility + - Support for multiple AI model providers - Custom mode creation for specialized workflows - MCP integration for unlimited tool expansion @@ -68,18 +79,21 @@ A revolutionary approach to AI context preservation that maintains project under ## Target Outcomes ### For Individual Developers + - Faster code generation and iteration cycles - Improved code quality through AI-assisted refactoring and debugging - Reduced time spent on documentation and boilerplate code - Enhanced learning through AI explanations and suggestions ### For Development Teams + - Consistent coding standards and practices - Shared custom modes for standardized workflows - Improved code review processes through better commit messages - Knowledge preservation through Memory Bank documentation ### For Projects + - Better documentation as a byproduct of AI assistance - More maintainable codebases through consistent patterns - Faster onboarding for new team members @@ -88,8 +102,9 @@ A revolutionary approach to AI context preservation that maintains project under ## Success Metrics The product succeeds when developers report: + - Increased coding velocity and reduced time-to-completion - Improved code quality and fewer bugs - Enhanced understanding of complex codebases - Reduced friction in development workflows -- Better project documentation and knowledge retention \ No newline at end of file +- Better project documentation and knowledge retention diff --git a/apps/kilocode-docs/.kilocode/rules/memory-bank/tasks.md b/apps/kilocode-docs/.kilocode/rules/memory-bank/tasks.md index e3ff83e2fb..3c3883121f 100644 --- a/apps/kilocode-docs/.kilocode/rules/memory-bank/tasks.md +++ b/apps/kilocode-docs/.kilocode/rules/memory-bank/tasks.md @@ -1,50 +1,57 @@ # Documentation Tasks -This file documents common repetitive tasks and workflows for maintaining the Kilo Code documentation site. +This file documents common repetitive tasks and workflows for maintaining the Axon Code documentation site. ## Add New Provider Documentation **Last performed:** Initial documentation setup **Files to modify:** + - `/docs/providers/[provider-name].md` - Create new provider documentation - `/sidebars.ts` - Add provider to navigation structure - `/src/constants.ts` - Add provider URLs if needed **Steps:** + 1. Create new provider documentation file in `/docs/providers/` 2. Follow the standard provider documentation template: - - Introduction and website link - - Getting an API Key section - - Supported Models section - - Configuration in Kilo Code section - - Tips and Notes section + - Introduction and website link + - Getting an API Key section + - Supported Models section + - Configuration in Axon Code section + - Tips and Notes section 3. Add provider to the Model Providers section in `sidebars.ts` 4. Update constants file if new URLs are needed 5. Test documentation locally with `npm start` 6. Verify all links work correctly **Template structure:** + ```markdown --- sidebar_label: Provider Name --- -# Using [Provider Name] With Kilo Code +# Using [Provider Name] With Axon Code Brief description of the provider and their strengths. **Website:** [Provider URL] ## Getting an API Key + [Step-by-step instructions] ## Supported Models + [List of supported models] -## Configuration in Kilo Code +## Configuration in Axon Code + [Setup instructions] ## Tips and Notes + [Additional helpful information] ``` @@ -52,11 +59,13 @@ Brief description of the provider and their strengths. **Last performed:** Tool reference documentation setup **Files to modify:** + - `/docs/features/tools/[tool-name].md` - Create new tool documentation - `/sidebars.ts` - Add tool to Tools Reference section - `/docs/features/tools/tool-use-overview.md` - Update tool overview if needed **Steps:** + 1. Create new tool documentation file in `/docs/features/tools/` 2. Follow the standard tool documentation template 3. Add tool to the Tools Reference section in `sidebars.ts` @@ -65,6 +74,7 @@ Brief description of the provider and their strengths. 6. Verify code examples and parameter descriptions are accurate **Important notes:** + - Include practical examples of tool usage - Document all parameters with their types and requirements - Explain when and why to use the tool @@ -74,11 +84,13 @@ Brief description of the provider and their strengths. **Last performed:** Feature documentation organization **Files to modify:** + - Relevant feature documentation files in `/docs/features/` - `/sidebars.ts` - Update navigation if structure changes - `/docs/index.mdx` - Update feature highlights if major features added **Steps:** + 1. Identify which feature documentation needs updates 2. Review current documentation for accuracy 3. Update content to reflect latest extension capabilities @@ -88,6 +100,7 @@ Brief description of the provider and their strengths. 7. Verify examples still work with current extension version **Important considerations:** + - Keep screenshots current with latest extension UI - Ensure feature descriptions match actual extension behavior - Update version-specific information @@ -97,10 +110,12 @@ Brief description of the provider and their strengths. **Last performed:** Auto-generate commit messages blog post **Files to modify:** + - `/blog-posts/[post-name].md` - Create new blog post - Consider adding to main documentation if content is reference material **Steps:** + 1. Create new blog post file in `/blog-posts/` 2. Follow the established blog post style and tone 3. Include practical examples and real-world usage @@ -109,6 +124,7 @@ Brief description of the provider and their strengths. 6. Review for clarity and technical accuracy **Content guidelines:** + - Focus on practical benefits and real-world usage - Include specific examples and code snippets - Maintain conversational but informative tone @@ -118,10 +134,12 @@ Brief description of the provider and their strengths. **Last performed:** Provider documentation updates **Files to modify:** + - Relevant provider documentation in `/docs/providers/` - `/docs/getting-started/connecting-api-provider.md` - If setup process changes **Steps:** + 1. Identify which providers have API changes 2. Update supported models lists 3. Update configuration instructions if needed @@ -130,6 +148,7 @@ Brief description of the provider and their strengths. 6. Update screenshots if provider UIs have changed **Important notes:** + - Verify model names and capabilities with provider documentation - Check for new authentication methods or requirements - Update rate limit information if changed @@ -139,11 +158,13 @@ Brief description of the provider and their strengths. **Last performed:** Features section reorganization **Files to modify:** + - `/sidebars.ts` - Primary navigation structure changes - `/docusaurus.config.ts` - Add redirects for moved content - Multiple documentation files - Update internal links **Steps:** + 1. Plan new documentation structure 2. Update `sidebars.ts` with new organization 3. Add redirects in `docusaurus.config.ts` for moved content @@ -153,6 +174,7 @@ Brief description of the provider and their strengths. 7. Update any hardcoded paths in components **Important considerations:** + - Always add redirects for moved content to prevent broken links - Update internal link references throughout the site - Test navigation flow from user perspective @@ -162,11 +184,13 @@ Brief description of the provider and their strengths. **Last performed:** YouTube embed and image components **Files to modify:** + - `/src/components/[ComponentName]/` - Create new component directory - `/src/theme/MDXComponents.ts` - Register component for MDX usage - Documentation files where component will be used **Steps:** + 1. Create component directory in `/src/components/` 2. Implement React component with TypeScript 3. Add component styles in separate CSS module if needed @@ -176,6 +200,7 @@ Brief description of the provider and their strengths. 7. Use component in relevant documentation files **Component guidelines:** + - Follow existing component patterns and styling - Use TypeScript for type safety - Include proper error handling @@ -186,12 +211,14 @@ Brief description of the provider and their strengths. **Last performed:** Ongoing maintenance need **Files to modify:** + - `/static/img/[feature-directories]/` - Update screenshot files - Documentation files with embedded images - Update image references - `/docs/getting-started/` - Installation and setup screenshots - `/docs/basic-usage/` - Interface and workflow screenshots **Steps:** + 1. Identify which features have UI changes from extension releases 2. Take new screenshots in consistent browser/OS environment 3. Optimize images for web (compress, appropriate dimensions) @@ -201,6 +228,7 @@ Brief description of the provider and their strengths. 7. Verify images are accessible and have proper alt text **Important considerations:** + - Maintain consistent screenshot style (browser, zoom level, theme) - Use descriptive filenames that match the feature being documented - Compress images to keep site performance optimal @@ -211,6 +239,7 @@ Brief description of the provider and their strengths. **Last performed:** Codebase indexing graduation **Files to modify:** + - Feature documentation files - Remove experimental warnings - `/sidebars.ts` - Move from experimental to appropriate section - `/docs/features/experimental/` - Remove from experimental list @@ -218,6 +247,7 @@ Brief description of the provider and their strengths. - `/docusaurus.config.ts` - Add redirects if URLs change **Steps:** + 1. Identify features graduating from experimental status 2. Remove experimental warnings and disclaimers from documentation 3. Update navigation structure in `sidebars.ts` @@ -228,6 +258,7 @@ Brief description of the provider and their strengths. 8. Update feature overview pages to reflect stable status **Important considerations:** + - Always add redirects for moved content to prevent broken links - Search for all references to the feature across documentation - Update any "experimental features" overview pages @@ -238,6 +269,7 @@ Brief description of the provider and their strengths. **Last performed:** Version-specific updates from todos.md **Files to modify:** + - Multiple feature documentation files based on release notes - Provider documentation for new models or API changes - Tool documentation for behavior changes @@ -245,6 +277,7 @@ Brief description of the provider and their strengths. - FAQ or troubleshooting sections for resolved issues **Steps:** + 1. Review extension release notes for documentation impacts 2. Categorize changes: UI updates, new features, bug fixes, model additions 3. Update relevant feature documentation with new capabilities @@ -255,6 +288,7 @@ Brief description of the provider and their strengths. 8. Test all updated examples and instructions **Important considerations:** + - Prioritize user-facing changes that affect documentation accuracy - Update version-specific information where relevant - Ensure examples still work with current extension version @@ -265,11 +299,13 @@ Brief description of the provider and their strengths. **Last performed:** MCP and features section reorganization **Files to modify:** + - `/docusaurus.config.ts` - Add redirect configurations - `/sidebars.ts` - Update navigation structure - Documentation files - Update internal links **Steps:** + 1. Plan new documentation structure or identify moved content 2. Document all URL changes that will occur 3. Add redirect entries in `docusaurus.config.ts` @@ -280,6 +316,7 @@ Brief description of the provider and their strengths. 8. Update any hardcoded paths in components **Important considerations:** + - Always add redirects before moving content to prevent 404 errors - Use permanent redirects (301) for moved content - Test redirects work for both old and new URLs @@ -291,12 +328,14 @@ Brief description of the provider and their strengths. **Last performed:** Codebase search tool documentation cleanup needed **Files to modify:** + - Duplicate documentation files - Navigation structure - Internal links and cross-references - Redirect configuration if URLs change **Steps:** + 1. Identify duplicate or conflicting documentation files 2. Compare content to determine which version is authoritative 3. Merge useful content from both versions if needed @@ -307,6 +346,7 @@ Brief description of the provider and their strengths. 8. Verify no broken links remain **Important considerations:** + - Determine which version has more accurate/current information - Preserve any unique content from the version being removed - Check git history to understand why duplicates exist @@ -317,11 +357,13 @@ Brief description of the provider and their strengths. **Last performed:** Tool fixes mentioned in v4.58.0 release **Files to modify:** + - Individual tool documentation files in `/docs/features/tools/` - Tool overview page if categories change - Examples and usage patterns in tool docs **Steps:** + 1. Review extension release notes for tool behavior changes 2. Identify which tools have updated functionality 3. Update parameter descriptions and requirements @@ -332,6 +374,7 @@ Brief description of the provider and their strengths. 8. Update tool overview page if needed **Important considerations:** + - Verify all parameter descriptions are accurate - Test code examples with current extension version - Update any error scenarios or troubleshooting information @@ -342,11 +385,13 @@ Brief description of the provider and their strengths. **Last performed:** Ongoing maintenance need **Files to modify:** + - All documentation files with internal or external links - Navigation configuration files - Component files with hardcoded links **Steps:** + 1. Run Docusaurus build to identify broken internal links 2. Use link checking tools for external links 3. Manually verify provider URLs and external service links @@ -357,6 +402,7 @@ Brief description of the provider and their strengths. 8. Document any permanently removed external resources **Important considerations:** + - Docusaurus automatically checks internal links during build - External links may break due to provider website changes - Consider using archive.org links for historical references @@ -368,11 +414,13 @@ Brief description of the provider and their strengths. **Last performed:** Ongoing as providers add models **Files to modify:** + - Individual provider documentation files in `/docs/providers/` - Provider comparison information if it exists - Getting started guides mentioning specific models **Steps:** + 1. Review provider websites and APIs for new model additions 2. Update supported models lists in provider documentation 3. Add model capabilities and limitations information @@ -383,9 +431,10 @@ Brief description of the provider and their strengths. 8. Update examples to use current model names **Important considerations:** + - Verify model names exactly match provider APIs - Include context window sizes and capabilities where relevant - Note any special configuration requirements for new models - Update rate limit information if it varies by model - Consider if new models change provider recommendations -- Test actual API connectivity when possible \ No newline at end of file +- Test actual API connectivity when possible diff --git a/apps/kilocode-docs/.kilocode/rules/memory-bank/tech.md b/apps/kilocode-docs/.kilocode/rules/memory-bank/tech.md index a57a9df067..7baee5419a 100644 --- a/apps/kilocode-docs/.kilocode/rules/memory-bank/tech.md +++ b/apps/kilocode-docs/.kilocode/rules/memory-bank/tech.md @@ -103,7 +103,7 @@ npx docusaurus build ### Community Platforms -- **Discord**: https://kilocode.ai/discord +- **Discord**: https://matterai.so/discord - **Reddit**: https://www.reddit.com/r/kilocode/ - **Twitter**: https://x.com/kilocode - **YouTube**: https://www.youtube.com/@Kilo-Code @@ -117,7 +117,7 @@ npx docusaurus build ### Static Site Hosting -- **Production URL**: https://kilocode.ai/docs +- **Production URL**: https://matterai.so/docs - **Base Path**: /docs (configured in docusaurus.config.ts) - **CDN**: Static file distribution for global performance diff --git a/apps/kilocode-docs/.kilocodemodes b/apps/kilocode-docs/.kilocodemodes index 7f95cdb5e4..3906e13588 100644 --- a/apps/kilocode-docs/.kilocodemodes +++ b/apps/kilocode-docs/.kilocodemodes @@ -2,15 +2,15 @@ customModes: - slug: video-script-writer name: Video Script Writer roleDefinition: >- - **Persona: Kilo Code Expert Scriptwriter** + **Persona: Axon Code Expert Scriptwriter** **Background:** A professional scriptwriter specializing in creating clear, engaging, and informative scripts tailored specifically for YouTube, Reddit tutorials, - and documentation videos focused on Kilo Code. With a deep understanding - of Kilo Code’s functionalities and its practical applications, this expert + and documentation videos focused on Axon Code. With a deep understanding + of Axon Code’s functionalities and its practical applications, this expert excels at translating complex coding concepts into straightforward, easy-to-follow explanations. @@ -29,7 +29,7 @@ customModes: **Specialization:** - - Kilo Code’s features and updates + - Axon Code’s features and updates - Common troubleshooting techniques @@ -55,13 +55,13 @@ customModes: - Patient and encouraging, ensuring viewers feel capable and supported. - - Enthusiastic about Kilo Code, making viewers excited about learning and + - Enthusiastic about Axon Code, making viewers excited about learning and implementing the software. **Goal:** - To empower viewers by making Kilo Code accessible and easy to master, + To empower viewers by making Axon Code accessible and easy to master, enhancing their confidence and competence through expert guidance and clear, compelling content. groups: [] @@ -86,7 +86,7 @@ customModes: - Bold key terms on first mention #### 4. **Precision Over Perfection** - Write for experienced developers. Skip basic explanations unless they clarify Kilo Code-specific behavior. Assume familiarity with VS Code, extensions, and development workflows. + Write for experienced developers. Skip basic explanations unless they clarify Axon Code-specific behavior. Assume familiarity with VS Code, extensions, and development workflows. #### 5. **Show, Don't Just Tell** Every feature explanation needs a realistic code example. Make examples copy-pasteable and immediately useful. Avoid "Hello World" demos—use real-world scenarios. @@ -146,7 +146,7 @@ customModes: - slug: posts name: Blog Post Author - roleDefinition: You are a technical blog author who applies Smart Brevity principles to make complex development topics accessible and engaging. With 24 years of experience, you write with authentic candor and technical precision, helping developers quickly understand why they should care about Kilo Code features. Your friendly, conversational tone includes light humor while maintaining professional credibility. You specialize in translating documentation into compelling stories that show real-world value, always leading with the problem being solved rather than the solution being offered. + roleDefinition: You are a technical blog author who applies Smart Brevity principles to make complex development topics accessible and engaging. With 24 years of experience, you write with authentic candor and technical precision, helping developers quickly understand why they should care about Axon Code features. Your friendly, conversational tone includes light humor while maintaining professional credibility. You specialize in translating documentation into compelling stories that show real-world value, always leading with the problem being solved rather than the solution being offered. customInstructions: >- ### Smart Brevity Blog Standards @@ -168,7 +168,7 @@ customModes: #### 5. **Documentation Integration** - Link to relevant docs using absolute URLs - - Example: `[Complete Setup Guide](https://kilocode.ai/docs/configuration/)` + - Example: `[Complete Setup Guide](https://matterai.so/docs/configuration/)` - Reference specific documentation sections to drive deeper engagement - Make it easy to go from blog interest to documentation action @@ -180,7 +180,7 @@ customModes: #### 7. **Problem-Solution Structure** - Start with relatable developer pain point - - Show how Kilo Code addresses it specifically + - Show how Axon Code addresses it specifically - Provide concrete example or walkthrough - End with clear next steps or call to action @@ -191,7 +191,7 @@ customModes: - Explain why the code works, not just how #### 9. **Visual Storytelling** - - Use images from documentation: `
| CPU Architecture: | $osArch |
`
+ - Use images from documentation: `
`
- Include screenshots that support the narrative
- Add brief descriptions for complex visuals
- Show UI paths with backticks: `Settings → Prompts → Feature Name`
diff --git a/apps/kilocode-docs/.kilocoderules b/apps/kilocode-docs/.kilocoderules
index d0f5aa5ee5..b4e0831b75 100644
--- a/apps/kilocode-docs/.kilocoderules
+++ b/apps/kilocode-docs/.kilocoderules
@@ -1,4 +1,4 @@
-# Kilo Code Documentation Rules
+# Axon Code Documentation Rules
## Documentation Links
- Do not include .md extensions in documentation links
@@ -23,7 +23,7 @@ This ensures links work correctly in the built documentation while maintaining c
## External Link References
- Use constants from `src/constants.ts` for external URLs instead of hardcoding
- Example: `
+
## Real Examples from Real Work
@@ -38,7 +40,7 @@ Let me show you some actual commit messages this feature has generated for me:
feat(auth): implement OAuth2 integration with GitHub
Add GitHub OAuth2 authentication flow including:
-- OAuth2 client configuration
+- OAuth2 client configuration
- User profile retrieval
- Token refresh mechanism
```
@@ -65,7 +67,7 @@ Here's where it gets interesting. You can customize the prompt template to match
Just head to `Settings → Prompts → Commit Message Generation` and modify the template. The AI will adapt to your requirements while still understanding the technical context of your changes.
-
+
## Why This Isn't Just Another AI Gimmick
@@ -89,9 +91,9 @@ Better commit messages also mean better code reviews. When your teammates can qu
## Getting Started
-The feature is available in Kilo Code since `v4.35` and became customizable in `v4.38`. Just make sure you have some staged changes, and look for the Kilo Code logo in your VS Code Source Control panel.
+The feature is available in Axon Code since `v4.35` and became customizable in `v4.38`. Just make sure you have some staged changes, and look for the Axon Code logo in your VS Code Source Control panel.
-Pro tip: Consider setting up a dedicated [API configuration profile](https://kilocode.ai/docs/features/api-configuration-profiles/) with a faster, cheaper model specifically for commit message generation. You don't need the most powerful model for this task, and it'll save you some API costs and time - yes, it's exactly what we did in [2x Faster, 30x Cheaper Prompt Enhancement](https://blog.kilocode.ai/p/2x-faster-prompt-enhancement-in-kilo)!
+Pro tip: Consider setting up a dedicated [API configuration profile](https://matterai.so/docs/features/api-configuration-profiles/) with a faster, cheaper model specifically for commit message generation. You don't need the most powerful model for this task, and it'll save you some API costs and time - yes, it's exactly what we did in [2x Faster, 30x Cheaper Prompt Enhancement](https://blog.matterai.so/p/2x-faster-prompt-enhancement-in-kilo)!
## One More Thing
@@ -103,4 +105,4 @@ Give it a try. I think you'll find yourself wondering how you ever managed witho
---
-*Want to learn more about Kilo Code's commit message generation? Check out the [full documentation](https://kilocode.ai/docs/basic-usage/git-commit-generation/) I wrote for setup details. And let me know what you think about it or how could we improve it even more here in comments or on our [Discord Server](https://kilo.love/discord)!*
\ No newline at end of file
+_Want to learn more about Axon Code's commit message generation? Check out the [full documentation](https://matterai.so/docs/basic-usage/git-commit-generation/) I wrote for setup details. And let me know what you think about it or how could we improve it even more here in comments or on our [Discord Server](https://kilo.love/discord)!_
diff --git a/apps/kilocode-docs/docs/advanced-usage/available-tools/codebase-search.md b/apps/kilocode-docs/docs/advanced-usage/available-tools/codebase-search.md
index 712a59acc8..6364626dc2 100644
--- a/apps/kilocode-docs/docs/advanced-usage/available-tools/codebase-search.md
+++ b/apps/kilocode-docs/docs/advanced-usage/available-tools/codebase-search.md
@@ -19,7 +19,7 @@ This tool searches through your indexed codebase using semantic similarity rathe
## When is it used?
-- When Kilo Code needs to find code related to specific functionality across your project
+- When Axon Code needs to find code related to specific functionality across your project
- When looking for implementation patterns or similar code structures
- When searching for error handling, authentication, or other conceptual code patterns
- When exploring unfamiliar codebases to understand how features are implemented
@@ -61,39 +61,39 @@ When the `codebase_search` tool is invoked, it follows this process:
1. **Availability Validation**:
- - Verifies that the CodeIndexManager is available and initialized
- - Confirms codebase indexing is enabled in settings
- - Checks that indexing is properly configured (API keys, Qdrant URL)
- - Validates the current index state allows searching
+ - Verifies that the CodeIndexManager is available and initialized
+ - Confirms codebase indexing is enabled in settings
+ - Checks that indexing is properly configured (API keys, Qdrant URL)
+ - Validates the current index state allows searching
2. **Query Processing**:
- - Takes your natural language query and generates an embedding vector
- - Uses the same embedding provider configured for indexing (OpenAI or Ollama)
- - Converts the semantic meaning of your query into a mathematical representation
+ - Takes your natural language query and generates an embedding vector
+ - Uses the same embedding provider configured for indexing (OpenAI or Ollama)
+ - Converts the semantic meaning of your query into a mathematical representation
3. **Vector Search Execution**:
- - Searches the Qdrant vector database for similar code embeddings
- - Uses cosine similarity to find the most relevant code blocks
- - Applies the minimum similarity threshold (0.4) to filter results
- - Limits results to 50 matches for optimal performance
+ - Searches the Qdrant vector database for similar code embeddings
+ - Uses cosine similarity to find the most relevant code blocks
+ - Applies the minimum similarity threshold (0.4) to filter results
+ - Limits results to 50 matches for optimal performance
4. **Path Filtering** (if specified):
- - Filters results to only include files within the specified directory path
- - Uses normalized path comparison for accurate filtering
- - Maintains relevance ranking within the filtered scope
+ - Filters results to only include files within the specified directory path
+ - Uses normalized path comparison for accurate filtering
+ - Maintains relevance ranking within the filtered scope
5. **Result Processing and Formatting**:
- - Converts absolute file paths to workspace-relative paths
- - Structures results with file paths, line ranges, similarity scores, and code content
- - Formats for both AI consumption and UI display with syntax highlighting
+ - Converts absolute file paths to workspace-relative paths
+ - Structures results with file paths, line ranges, similarity scores, and code content
+ - Formats for both AI consumption and UI display with syntax highlighting
6. **Dual Output Format**:
- - **AI Output**: Structured text format with query, file paths, scores, and code chunks
- - **UI Output**: JSON format with syntax highlighting and navigation capabilities
+ - **AI Output**: Structured text format with query, file paths, scores, and code chunks
+ - **UI Output**: JSON format with syntax highlighting and navigation capabilities
## Search Query Best Practices
@@ -189,10 +189,10 @@ Each search result includes:
## Examples When Used
-- When implementing a new feature, Kilo Code searches for "authentication middleware" to understand existing patterns before writing new code.
-- When debugging an issue, Kilo Code searches for "error handling in API calls" to find related error patterns across the codebase.
-- When refactoring code, Kilo Code searches for "database transaction patterns" to ensure consistency across all database operations.
-- When onboarding to a new codebase, Kilo Code searches for "configuration loading" to understand how the application bootstraps.
+- When implementing a new feature, Axon Code searches for "authentication middleware" to understand existing patterns before writing new code.
+- When debugging an issue, Axon Code searches for "error handling in API calls" to find related error patterns across the codebase.
+- When refactoring code, Axon Code searches for "database transaction patterns" to ensure consistency across all database operations.
+- When onboarding to a new codebase, Axon Code searches for "configuration loading" to understand how the application bootstraps.
## Usage Examples
diff --git a/apps/kilocode-docs/docs/advanced-usage/custom-instructions.md b/apps/kilocode-docs/docs/advanced-usage/custom-instructions.md
index 7727d1e176..9ec710b030 100644
--- a/apps/kilocode-docs/docs/advanced-usage/custom-instructions.md
+++ b/apps/kilocode-docs/docs/advanced-usage/custom-instructions.md
@@ -1,6 +1,6 @@
# Custom Instructions
-Custom Instructions allow you to personalize how Kilo Code behaves, providing specific guidance that shapes responses, coding style, and decision-making processes.
+Custom Instructions allow you to personalize how Axon Code behaves, providing specific guidance that shapes responses, coding style, and decision-making processes.
## What Are Custom Instructions?
@@ -14,8 +14,8 @@ Custom Instructions are IDE-wide and are applied across all workspaces and maint
**How to set them:**
-
-1. **Open Modes Tab:** Click the 
- * **Open Tab:** Click the 
+
+
-*Context mentions overview showing the @ symbol dropdown menu in the chat interface.*
+_Context mentions overview showing the @ symbol dropdown menu in the chat interface._
## Types of Mentions
-*File mentions add actual code content into the conversation for direct reference and analysis.*
+_File mentions add actual code content into the conversation for direct reference and analysis._
-| Mention Type | Format | Description | Example Usage |
-|--------------|--------|-------------|--------------|
-| **File** | `@/path/to/file.ts` | Includes file contents in request context | "Explain the function in @/src/utils.ts" |
-| **Folder** | `@/path/to/folder/` | Provides directory structure in tree format | "What files are in @/src/components/?" |
-| **Problems** | `@problems` | Includes VS Code Problems panel diagnostics | "@problems Fix all errors in my code" |
-| **Terminal** | `@terminal` | Includes recent terminal command and output | "Fix the errors shown in @terminal" |
-| **Git Commit** | `@a1b2c3d` | References specific commit by hash | "What changed in commit @a1b2c3d?" |
-| **Git Changes** | `@git-changes` | Shows uncommitted changes | "Suggest a message for @git-changes" |
-| **URL** | `@https://example.com` | Imports website content | "Summarize @https://docusaurus.io/" |
+| Mention Type | Format | Description | Example Usage |
+| --------------- | ---------------------- | ------------------------------------------- | ---------------------------------------- |
+| **File** | `@/path/to/file.ts` | Includes file contents in request context | "Explain the function in @/src/utils.ts" |
+| **Folder** | `@/path/to/folder/` | Provides directory structure in tree format | "What files are in @/src/components/?" |
+| **Problems** | `@problems` | Includes VS Code Problems panel diagnostics | "@problems Fix all errors in my code" |
+| **Terminal** | `@terminal` | Includes recent terminal command and output | "Fix the errors shown in @terminal" |
+| **Git Commit** | `@a1b2c3d` | References specific commit by hash | "What changed in commit @a1b2c3d?" |
+| **Git Changes** | `@git-changes` | Shows uncommitted changes | "Suggest a message for @git-changes" |
+| **URL** | `@https://example.com` | Imports website content | "Summarize @https://docusaurus.io/" |
### File Mentions
-*Folder mentions display directory structure in a readable tree format.*
+_Folder mentions display directory structure in a readable tree format._
| Capability | Details |
|------------|---------|
| **Format** | `@/path/to/folder/` (note trailing slash) |
@@ -52,7 +52,7 @@ Context mentions are a powerful way to provide Kilo Code with specific informati
-*Problems mentions import diagnostics directly from VS Code's problems panel.*
+_Problems mentions import diagnostics directly from VS Code's problems panel._
| Capability | Details |
|------------|---------|
| **Format** | `@problems` |
@@ -62,40 +62,42 @@ Context mentions are a powerful way to provide Kilo Code with specific informati
| **Best for** | Fixing errors without manual copying |
### Terminal Mention
-
-*Terminal mentions capture recent command output for debugging and analysis.*
+
+
-*URL mentions import external web content and convert it to readable Markdown format.*
+_URL mentions import external web content and convert it to readable Markdown format._
-| Capability | Details |
-|------------|---------|
-| **Format** | `@https://example.com` |
-| **Processing** | Uses headless browser to fetch content |
-| **Cleaning** | Removes scripts, styles, and navigation elements |
-| **Output** | Converts content to Markdown for readability |
-| **Limitation** | Complex pages may not convert perfectly |
+| Capability | Details |
+| -------------- | ------------------------------------------------ |
+| **Format** | `@https://example.com` |
+| **Processing** | Uses headless browser to fetch content |
+| **Cleaning** | Removes scripts, styles, and navigation elements |
+| **Output** | Converts content to Markdown for readability |
+| **Limitation** | Complex pages may not convert perfectly |
## How to Use Mentions
@@ -105,6 +107,7 @@ Context mentions are a powerful way to provide Kilo Code with specific informati
4. Combine multiple mentions in a request: "Fix @problems in @/src/component.ts"
The dropdown automatically suggests:
+
- Recently opened files
- Visible folders
- Recent git commits
@@ -112,11 +115,11 @@ The dropdown automatically suggests:
## Best Practices
-| Practice | Description |
-|----------|-------------|
-| **Use specific paths** | Reference exact files rather than describing them |
-| **Use relative paths** | Always start from workspace root: `@/src/file.ts` not `@C:/Projects/src/file.ts` |
-| **Verify references** | Ensure paths and commit hashes are correct |
-| **Click mentions** | Click mentions in chat history to open files or view content |
-| **Eliminate copy-pasting** | Use mentions instead of manually copying code or errors |
-| **Combine mentions** | "Fix @problems in @/src/component.ts using the pattern from commit @a1b2c3d" |
+| Practice | Description |
+| -------------------------- | -------------------------------------------------------------------------------- |
+| **Use specific paths** | Reference exact files rather than describing them |
+| **Use relative paths** | Always start from workspace root: `@/src/file.ts` not `@C:/Projects/src/file.ts` |
+| **Verify references** | Ensure paths and commit hashes are correct |
+| **Click mentions** | Click mentions in chat history to open files or view content |
+| **Eliminate copy-pasting** | Use mentions instead of manually copying code or errors |
+| **Combine mentions** | "Fix @problems in @/src/component.ts using the pattern from commit @a1b2c3d" |
diff --git a/apps/kilocode-docs/docs/basic-usage/git-commit-generation.md b/apps/kilocode-docs/docs/basic-usage/git-commit-generation.md
index ec5007149b..ee223476de 100644
--- a/apps/kilocode-docs/docs/basic-usage/git-commit-generation.md
+++ b/apps/kilocode-docs/docs/basic-usage/git-commit-generation.md
@@ -1,6 +1,6 @@
# Generate Commit Messages
-Generate descriptive commit messages automatically based on your staged git changes. Kilo Code analyzes your staged files and creates conventional commit messages that follow best practices.
+Generate descriptive commit messages automatically based on your staged git changes. Axon Code analyzes your staged files and creates conventional commit messages that follow best practices.
:::info
This feature only analyzes **staged changes**. Make sure to stage your files using `git add` or via `VS Code` interface before generating commit messages.
@@ -9,6 +9,7 @@ This feature only analyzes **staged changes**. Make sure to stage your files usi
## How It Works
The git commit message generator:
+
- Analyzes only your **staged changes** (not unstaged or untracked files)
- Uses AI to understand the context and purpose of your changes
- Creates descriptive commit messages that explain what was changed and why following the [Conventional Commits](https://www.conventionalcommits.org/) (by default, customizable)
@@ -18,10 +19,9 @@ The git commit message generator:
### Generating a Commit Message
1. Stage your changes using `git add` or the VS Code git interface
-2. In the VS Code Source Control panel, look for the `Kilo Code` logo next to the commit message field)
+2. In the VS Code Source Control panel, look for the `Axon Code` logo next to the commit message field)
3. Click the logo to generate a commit message
-
The generated message will appear in the commit message field, ready for you to review and modify if needed.
@@ -37,6 +37,7 @@ By default, generated messages follow the Conventional Commits specification:
```
Common types include:
+
- `feat`: New features
- `fix`: Bug fixes
- `docs`: Documentation changes
@@ -58,6 +59,7 @@ You can customize how commit messages are generated by modifying the prompt temp
The default template creates conventional commit messages, but you can modify it to:
+
- Use different commit message formats
- Include specific information relevant to your project
- Follow your team's commit message conventions
@@ -77,16 +79,19 @@ Consider creating a dedicated [API configuration profile](/features/api-configur
## Best Practices
### Staging Strategy
+
- Stage related changes together for more coherent commit messages
- Avoid staging unrelated changes in a single commit
- Use `git add -p` for partial file staging when needed
### Message Review
+
- Always review generated messages before committing
- Edit messages to add context the AI might have missed
- Ensure the message accurately describes the changes
### Custom Templates
+
- Tailor the prompt template to your project's needs
- Include project-specific terminology or conventions
- Add instructions for handling specific types of changes
@@ -121,7 +126,9 @@ setup steps for new contributors
## Troubleshooting
### No Staged Changes
+
If the button doesn't appear or generation fails, ensure you have staged changes:
+
```bash
git add 
-*The tool approval interface shows Save/Reject buttons and Auto-approve options.*
+_The tool approval interface shows Save/Reject buttons and Auto-approve options._
**User:** Create a file named `greeting.js` that logs a greeting message
-**Kilo Code:** (Proposes the `write_to_file` tool as shown in the image above)
+**Axon Code:** (Proposes the `write_to_file` tool as shown in the image above)
+
```xml
+
) in VS Code's Primary Side Bar. Click it to open the chat panel.
+Find the Axon Code icon (
) in VS Code's Primary Side Bar. Click it to open the chat panel.
-**Lost the panel?** Go to View > Open View... and search for "Kilo Code"
+**Lost the panel?** Go to View > Open View... and search for "Axon Code"
-## How to Talk to Kilo Code
+## How to Talk to Axon Code
**The key insight:** Just type what you want in normal English. No special commands needed.
-
+
+ 
+
+ 
+ 
-_VSCode Problems pane that Kilo Code checks during the write delay_
+_VSCode Problems pane that Axon Code checks during the write delay_
When you enable auto-approval for writing files, the delay timer works with VSCode's Problems pane:
-1. Kilo Code makes a change to your file
+1. Axon Code makes a change to your file
2. VSCode's diagnostic tools analyze the change
3. The Problems pane updates with any errors or warnings
-4. Kilo Code notices these issues before continuing
+4. Axon Code notices these issues before continuing
This works like a human developer pausing to check for errors after changing code. You can adjust the delay time based on:
@@ -135,7 +135,7 @@ This works like a human developer pausing to check for errors after changing cod
**Risk level:** Medium
-Allows Kilo Code to control a headless browser without confirmation. This can include:
+Allows Axon Code to control a headless browser without confirmation. This can include:
- Opening websites
- Navigating pages
@@ -157,7 +157,7 @@ Consider the security implications of allowing automated browser access.
**Risk level:** Low
-This setting automatically retries API calls when they fail. The delay controls how long Kilo Code waits before trying again:
+This setting automatically retries API calls when they fail. The delay controls how long Axon Code waits before trying again:
- Longer delays are gentler on API rate limits
- Shorter delays give faster recovery from transient errors
@@ -188,7 +188,7 @@ This setting works in conjunction with individual tool permissions in the MCP Se
**Risk level:** Low
-Allows Kilo Code to change between different modes (Code, Architect, etc.) without asking for permission. This primarily affects the AI's behavior rather than system access.
+Allows Axon Code to change between different modes (Code, Architect, etc.) without asking for permission. This primarily affects the AI's behavior rather than system access.
:::
### Subtasks
@@ -202,7 +202,7 @@ Allows Kilo Code to change between different modes (Code, Architect, etc.) witho
**Risk level:** Low
-Enables Kilo Code to create and complete subtasks automatically. This relates to workflow organization rather than system access.
+Enables Axon Code to create and complete subtasks automatically. This relates to workflow organization rather than system access.
:::
### Command Execution
@@ -238,7 +238,7 @@ This setting allows terminal command execution with controls. While risky, the w
**Setting:** `Always default answer for follow-up questions`
-**Description:** Automatically selects the first AI-suggested answer for a follow-up question after a configurable timeout. This speeds up your workflow by letting Kilo Code proceed without manual intervention.
+**Description:** Automatically selects the first AI-suggested answer for a follow-up question after a configurable timeout. This speeds up your workflow by letting Axon Code proceed without manual intervention.
**Visual countdown:** When enabled, a countdown timer appears on the first suggestion button, showing the remaining time before auto-selection. The timer is displayed as a circular progress indicator that depletes as time passes.
@@ -255,7 +255,7 @@ This setting allows terminal command execution with controls. While risky, the w
**Use cases:**
-- Overnight runs where you want Kilo Code to continue working
+- Overnight runs where you want Axon Code to continue working
- Repetitive tasks where the default suggestions are usually correct
- Testing workflows where interaction isn't critical
:::
@@ -270,7 +270,7 @@ This setting allows terminal command execution with controls. While risky, the w
**Risk level:** Low
-This setting allows Kilo Code to automatically update task progress and todo lists during work sessions. This includes:
+This setting allows Axon Code to automatically update task progress and todo lists during work sessions. This includes:
- Marking tasks as completed
- Adding new discovered tasks
@@ -291,5 +291,5 @@ This setting allows Kilo Code to automatically update task progress and todo lis
- Complex debugging workflows
- Feature implementation with many subtasks
-This is particularly useful when combined with the Subtasks permission, as it allows Kilo Code to maintain a complete picture of project progress without constant approval requests.
+This is particularly useful when combined with the Subtasks permission, as it allows Axon Code to maintain a complete picture of project progress without constant approval requests.
:::
diff --git a/apps/kilocode-docs/docs/features/auto-launch-configuration.md b/apps/kilocode-docs/docs/features/auto-launch-configuration.md
index 02b860e1fa..6ed74b4d11 100644
--- a/apps/kilocode-docs/docs/features/auto-launch-configuration.md
+++ b/apps/kilocode-docs/docs/features/auto-launch-configuration.md
@@ -1,6 +1,6 @@
# Auto-Launch Configuration
-Auto-Launch Configuration allows you to automatically start a Kilo Code task when opening a workspace, with support for specific profiles and modes. This was originally developed as an internal test feature, but we decided to expose it to users in case anyone finds it useful!
+Auto-Launch Configuration allows you to automatically start a Axon Code task when opening a workspace, with support for specific profiles and modes. This was originally developed as an internal test feature, but we decided to expose it to users in case anyone finds it useful!
:::info
Auto-Launch Configuration is particularly useful for testing the same prompt against multiple models or project directories.
@@ -8,7 +8,7 @@ Auto-Launch Configuration is particularly useful for testing the same prompt aga
## How It Works
-When you open a workspace in VS Code, Kilo Code automatically checks for a launch configuration JSON file. If found, it:
+When you open a workspace in VS Code, Axon Code automatically checks for a launch configuration JSON file. If found, it:
- Switches to the specified provider profile (if provided)
- Changes to the specified mode (if provided)
@@ -42,7 +42,7 @@ This happens seamlessly in the background, requiring no manual intervention.
- **`profile`** (string): Name of an existing [API Configuration Profile](/features/api-configuration-profiles) to use for this task. Must exactly match a profile name from your settings.
-- **`mode`** (string): The Kilo Code mode to use for this task. Available modes:
+- **`mode`** (string): The Axon Code mode to use for this task. Available modes:
- `"code"` - General-purpose coding tasks
- `"architect"` - Planning and technical design
- `"ask"` - Questions and explanations
@@ -123,7 +123,7 @@ This file should be at the root of your workspace (the same level as your main p
## Behavior and Timing
-- Auto-launch triggers approximately 500ms after Kilo Code extension activation
+- Auto-launch triggers approximately 500ms after Axon Code extension activation
- The sidebar automatically receives focus before the task launches
- Profile switching happens before mode switching (if both are specified)
- The task launches after all configuration changes are applied
diff --git a/apps/kilocode-docs/docs/features/browser-use.md b/apps/kilocode-docs/docs/features/browser-use.md
index 8d553eff77..6c4db4f819 100644
--- a/apps/kilocode-docs/docs/features/browser-use.md
+++ b/apps/kilocode-docs/docs/features/browser-use.md
@@ -1,14 +1,15 @@
# Browser Use
-Kilo Code provides sophisticated browser automation capabilities that let you interact with websites directly from VS Code. This feature enables testing web applications, automating browser tasks, and capturing screenshots without leaving your development environment.
+Axon Code provides sophisticated browser automation capabilities that let you interact with websites directly from VS Code. This feature enables testing web applications, automating browser tasks, and capturing screenshots without leaving your development environment.
:::info Model Support Required
-Browser Use within Kilo Code requires the use and advanced agentic model, and has only been tested with Claude Sonnet 3.5, 3.7, and 4
+Browser Use within Axon Code requires the use and advanced agentic model, and has only been tested with Claude Sonnet 3.5, 3.7, and 4
:::
## How Browser Use Works
-By default, Kilo Code uses a built-in browser that:
+By default, Axon Code uses a built-in browser that:
+
- Launches automatically when you ask Kilo to visit a website
- Captures screenshots of web pages
- Allows Kilo to interact with web elements
@@ -32,7 +33,7 @@ Open the browser and view our site.
```
```
-Can you check if my website at https://kilocode.ai is displaying correctly?
+Can you check if my website at https://matterai.so is displaying correctly?
```
```
@@ -46,6 +47,7 @@ Browse http://localhost:3000, scroll down to the bottom of the page and check if
The browser_action tool controls a browser instance that returns screenshots and console logs after each action, allowing you to see the results of interactions.
Key characteristics:
+
- Each browser session must start with `launch` and end with `close`
- Only one browser action can be used per message
- While the browser is active, no other tools can be used
@@ -53,23 +55,24 @@ Key characteristics:
### Available Browser Actions
-| Action | Description | When to Use |
-|--------|-------------|------------|
-| `launch` | Opens a browser at a URL | Starting a new browser session |
-| `click` | Clicks at specific coordinates | Interacting with buttons, links, etc. |
-| `type` | Types text into active element | Filling forms, search boxes |
-| `scroll_down` | Scrolls down by one page | Viewing content below the fold |
-| `scroll_up` | Scrolls up by one page | Returning to previous content |
-| `close` | Closes the browser | Ending a browser session |
+| Action | Description | When to Use |
+| ------------- | ------------------------------ | ------------------------------------- |
+| `launch` | Opens a browser at a URL | Starting a new browser session |
+| `click` | Clicks at specific coordinates | Interacting with buttons, links, etc. |
+| `type` | Types text into active element | Filling forms, search boxes |
+| `scroll_down` | Scrolls down by one page | Viewing content below the fold |
+| `scroll_up` | Scrolls up by one page | Returning to previous content |
+| `close` | Closes the browser | Ending a browser session |
## Browser Use Configuration/Settings
:::info Default Browser Settings
+
- **Enable browser tool**: Enabled
- **Viewport size**: Small Desktop (900x600)
- **Screenshot quality**: 75%
- **Use remote browser connection**: Disabled
-:::
+ :::
### Accessing Settings
@@ -77,33 +80,35 @@ To change Browser / Computer Use settings in Kilo:
1. Open Settings by clicking the gear icon 
+ 
+ 
+ 
+ - 40-50%: Good for basic text-based websites
+ - 60-70%: Balanced for most general browsing
+ - 80%+: Use when fine visual details are critical
+
+ 
+ 
+ 
+ 
+ 
+ 
@@ -77,18 +79,17 @@ To restore a project to a previous checkpoint state:
2. Click the checkpoint's `Restore Checkpoint` button
3. Choose one of these restoration options:
-
- 
- - **Restore Files Only** - Reverts only workspace files to checkpoint state without modifying conversation history. Ideal for comparing alternative implementations while maintaining chat context, allowing you to seamlessly switch between different project states. This option does not require confirmation and lets you quickly switch between different implementations.
-
- - **Restore Files & Task** - Reverts both workspace files AND removes all subsequent conversation messages. Use when you want to completely reset both your code and conversation back to the checkpoint's point in time. This option requires confirmation in a dialog as it cannot be undone.
+ 
+ 
@@ -17,14 +17,14 @@ When enabled, the indexing system:
1. **Parses your code** using Tree-sitter to identify semantic blocks (functions, classes, methods)
2. **Creates embeddings** of each code block using AI models
3. **Stores vectors** in a Qdrant database for fast similarity search
-4. **Provides the [`codebase_search`](/advanced-usage/available-tools/codebase-search) tool** to Kilo Code for intelligent code discovery
+4. **Provides the [`codebase_search`](/advanced-usage/available-tools/codebase-search) tool** to Axon Code for intelligent code discovery
This enables natural language queries like "user authentication logic" or "database connection handling" to find relevant code across your entire project.
## Key Benefits
- **Semantic Search**: Find code by meaning, not just keywords
-- **Enhanced AI Understanding**: Kilo Code can better comprehend and work with your codebase
+- **Enhanced AI Understanding**: Axon Code can better comprehend and work with your codebase
- **Cross-Project Discovery**: Search across all files, not just what's open
- **Pattern Recognition**: Locate similar implementations and code patterns
@@ -76,16 +76,16 @@ docker run -p 6333:6333 qdrant/qdrant
**Using Docker Compose:**
```yaml
-version: '3.8'
+version: "3.8"
services:
- qdrant:
- image: qdrant/qdrant
- ports:
- - '6333:6333'
- volumes:
- - qdrant_storage:/qdrant/storage
+ qdrant:
+ image: qdrant/qdrant
+ ports:
+ - "6333:6333"
+ volumes:
+ - qdrant_storage:/qdrant/storage
volumes:
- qdrant_storage:
+ qdrant_storage:
```
### Production Deployment
@@ -98,13 +98,13 @@ For team or production use:
## Configuration
-1. Open Kilo Code settings (
+ 
+ 
-
## Key Considerations & Warnings
-- **Intended Audience:** Best suited for users deeply familiar with Kilo Code's prompting system and the implications of modifying core instructions.
-- **Impact on Functionality:** Custom prompts override standard instructions, including those for tool usage and response consistency. This can cause unexpected behavior or errors if not managed carefully.
-- **Mode-Specific:** Each override file applies only to the mode specified in its filename (`{mode-slug}`).
-- **No File, No Override:** If the `.kilocode/system-prompt-{mode-slug}` file doesn't exist, Kilo Code uses the standard system prompt generation process for that mode.
-- **Directory Creation:** Kilo Code ensures the `.kilocode` directory exists before attempting to read or create the override file.
+- **Intended Audience:** Best suited for users deeply familiar with Axon Code's prompting system and the implications of modifying core instructions.
+- **Impact on Functionality:** Custom prompts override standard instructions, including those for tool usage and response consistency. This can cause unexpected behavior or errors if not managed carefully.
+- **Mode-Specific:** Each override file applies only to the mode specified in its filename (`{mode-slug}`).
+- **No File, No Override:** If the `.kilocode/system-prompt-{mode-slug}` file doesn't exist, Axon Code uses the standard system prompt generation process for that mode.
+- **Directory Creation:** Axon Code ensures the `.kilocode` directory exists before attempting to read or create the override file.
-Use this feature cautiously. While powerful for customization, incorrect implementation can significantly degrade Kilo Code's performance and reliability for the affected mode.
+Use this feature cautiously. While powerful for customization, incorrect implementation can significantly degrade Axon Code's performance and reliability for the affected mode.
diff --git a/apps/kilocode-docs/docs/features/mcp/mcp-vs-api.md b/apps/kilocode-docs/docs/features/mcp/mcp-vs-api.md
index 92ba206aa7..3dc933102b 100644
--- a/apps/kilocode-docs/docs/features/mcp/mcp-vs-api.md
+++ b/apps/kilocode-docs/docs/features/mcp/mcp-vs-api.md
@@ -9,14 +9,14 @@ Comparing REST APIs to the Model Context Protocol (MCP) is a category error. The
## Architectural Differences
-| Feature | MCP | REST APIs |
-|---------|-----|-----------|
-| State Management | **Stateful** - maintains context across interactions | **Stateless** - each request is independent |
-| Connection Type | Persistent, bidirectional connections | One-way request/response |
-| Communication Style | JSON-RPC based with ongoing sessions | HTTP-based with discrete requests |
-| Context Handling | Context is intrinsic to the protocol | Context must be manually managed |
-| Tool Discovery | Runtime discovery of available tools | Design-time integration requiring prior knowledge |
-| Integration Approach | Runtime integration with dynamic capabilities | Design-time integration requiring code changes |
+| Feature | MCP | REST APIs |
+| -------------------- | ---------------------------------------------------- | ------------------------------------------------- |
+| State Management | **Stateful** - maintains context across interactions | **Stateless** - each request is independent |
+| Connection Type | Persistent, bidirectional connections | One-way request/response |
+| Communication Style | JSON-RPC based with ongoing sessions | HTTP-based with discrete requests |
+| Context Handling | Context is intrinsic to the protocol | Context must be manually managed |
+| Tool Discovery | Runtime discovery of available tools | Design-time integration requiring prior knowledge |
+| Integration Approach | Runtime integration with dynamic capabilities | Design-time integration requiring code changes |
## Different Layers, Different Purposes
@@ -43,23 +43,23 @@ MCP enables an AI to discover and use tools at runtime:
```json
// AI discovers available tools
{
- "tools": [
- {
- "name": "readFile",
- "description": "Reads content from a file",
- "parameters": {
- "path": { "type": "string", "description": "File path" }
- }
- },
- {
- "name": "createTicket",
- "description": "Creates a ticket in issue tracker",
- "parameters": {
- "title": { "type": "string" },
- "description": { "type": "string" }
- }
- }
- ]
+ "tools": [
+ {
+ "name": "readFile",
+ "description": "Reads content from a file",
+ "parameters": {
+ "path": { "type": "string", "description": "File path" }
+ }
+ },
+ {
+ "name": "createTicket",
+ "description": "Creates a ticket in issue tracker",
+ "parameters": {
+ "title": { "type": "string" },
+ "description": { "type": "string" }
+ }
+ }
+ ]
}
```
@@ -70,28 +70,30 @@ This "plug-and-play" capability allows new tools to be added without redeploying
Consider a task requiring multiple services: "Check recent commits, create a JIRA ticket for the bug fix, and post to Slack."
**REST-based approach**:
+
- Requires separate integrations for Git, JIRA, and Slack APIs
- Needs custom code to manage context between calls
- Breaks if any service changes its API
**MCP-based approach**:
+
- One unified protocol for all tools
- Maintains context across the entire workflow
- New tools can be swapped in without code changes
-## Why Kilo Code Uses MCP
+## Why Axon Code Uses MCP
-Kilo Code leverages MCP to provide:
+Axon Code leverages MCP to provide:
1. **Extensibility**: Add unlimited custom tools without waiting for official integration
2. **Contextual awareness**: Tools can access conversation history and project context
3. **Simplified integration**: One standard protocol rather than numerous API patterns
4. **Runtime flexibility**: Discover and use new capabilities on-the-fly
-MCP creates a universal connector between Kilo Code and external services, with REST APIs often powering those services behind the scenes.
+MCP creates a universal connector between Axon Code and external services, with REST APIs often powering those services behind the scenes.
## Conclusion: Complementary, Not Competing Technologies
MCP doesn't replace REST APIs - it builds upon them. REST excels at providing discrete services, while MCP excels at orchestrating those services for AI agents.
-The critical distinction is that MCP is AI-native: it treats the model as a first-class user, providing the contextual, stateful interaction layer that AI agents need to function effectively in complex environments.
\ No newline at end of file
+The critical distinction is that MCP is AI-native: it treats the model as a first-class user, providing the contextual, stateful interaction layer that AI agents need to function effectively in complex environments.
diff --git a/apps/kilocode-docs/docs/features/mcp/overview.md b/apps/kilocode-docs/docs/features/mcp/overview.md
index f35d372ea8..93c202e3f2 100644
--- a/apps/kilocode-docs/docs/features/mcp/overview.md
+++ b/apps/kilocode-docs/docs/features/mcp/overview.md
@@ -5,16 +5,16 @@ sidebar_label: MCP Overview
# Model Context Protocol (MCP)
-The Model Context Protocol (MCP) is a standard for extending Kilo Code's capabilities by connecting to external tools and services. MCP servers provide additional tools and resources that help Kilo Code accomplish tasks beyond its built-in capabilities, such as accessing databases, custom APIs, and specialized functionality.
+The Model Context Protocol (MCP) is a standard for extending Axon Code's capabilities by connecting to external tools and services. MCP servers provide additional tools and resources that help Axon Code accomplish tasks beyond its built-in capabilities, such as accessing databases, custom APIs, and specialized functionality.
## MCP Documentation
This documentation is organized into several sections:
-* [**Using MCP in Kilo Code**](/features/mcp/using-mcp-in-kilo-code) - Comprehensive guide to configuring, enabling, and managing MCP servers with Kilo Code. Includes server settings, tool approval, and troubleshooting.
+- [**Using MCP in Axon Code**](/features/mcp/using-mcp-in-kilo-code) - Comprehensive guide to configuring, enabling, and managing MCP servers with Axon Code. Includes server settings, tool approval, and troubleshooting.
-* [**What is MCP?**](/features/mcp/what-is-mcp) - Clear explanation of the Model Context Protocol, its client-server architecture, and how it enables AI systems to interact with external tools.
+- [**What is MCP?**](/features/mcp/what-is-mcp) - Clear explanation of the Model Context Protocol, its client-server architecture, and how it enables AI systems to interact with external tools.
-* [**STDIO & SSE Transports**](/features/mcp/server-transports) - Detailed comparison of local (STDIO) and remote (SSE) transport mechanisms with deployment considerations for each approach.
+- [**STDIO & SSE Transports**](/features/mcp/server-transports) - Detailed comparison of local (STDIO) and remote (SSE) transport mechanisms with deployment considerations for each approach.
-* [**MCP vs API**](/features/mcp/mcp-vs-api) - Analysis of the fundamental distinction between MCP and REST APIs, explaining how they operate at different layers of abstraction for AI systems.
+- [**MCP vs API**](/features/mcp/mcp-vs-api) - Analysis of the fundamental distinction between MCP and REST APIs, explaining how they operate at different layers of abstraction for AI systems.
diff --git a/apps/kilocode-docs/docs/features/mcp/server-transports.md b/apps/kilocode-docs/docs/features/mcp/server-transports.md
index 8138c6785c..b665612c2a 100644
--- a/apps/kilocode-docs/docs/features/mcp/server-transports.md
+++ b/apps/kilocode-docs/docs/features/mcp/server-transports.md
@@ -5,7 +5,7 @@ sidebar_label: STDIO & SSE Transports
# MCP Server Transports: STDIO & SSE
-Model Context Protocol (MCP) supports two primary transport mechanisms for communication between Kilo Code and MCP servers: Standard Input/Output (STDIO) and Server-Sent Events (SSE). Each has distinct characteristics, advantages, and use cases.
+Model Context Protocol (MCP) supports two primary transport mechanisms for communication between Axon Code and MCP servers: Standard Input/Output (STDIO) and Server-Sent Events (SSE). Each has distinct characteristics, advantages, and use cases.
## STDIO Transport
@@ -13,7 +13,7 @@ STDIO transport runs locally on your machine and communicates via standard input
### How STDIO Transport Works
-1. The client (Kilo Code) spawns an MCP server as a child process
+1. The client (Axon Code) spawns an MCP server as a child process
2. Communication happens through process streams: client writes to server's STDIN, server responds to STDOUT
3. Each message is delimited by a newline character
4. Messages are formatted as JSON-RPC 2.0
@@ -29,34 +29,34 @@ Client Server
### STDIO Characteristics
-* **Locality**: Runs on the same machine as Kilo Code
-* **Performance**: Very low latency and overhead (no network stack involved)
-* **Simplicity**: Direct process communication without network configuration
-* **Relationship**: One-to-one relationship between client and server
-* **Security**: Inherently more secure as no network exposure
+- **Locality**: Runs on the same machine as Axon Code
+- **Performance**: Very low latency and overhead (no network stack involved)
+- **Simplicity**: Direct process communication without network configuration
+- **Relationship**: One-to-one relationship between client and server
+- **Security**: Inherently more secure as no network exposure
### When to Use STDIO
STDIO transport is ideal for:
-* Local integrations and tools running on the same machine
-* Security-sensitive operations
-* Low-latency requirements
-* Single-client scenarios (one Kilo Code instance per server)
-* Command-line tools or IDE extensions
+- Local integrations and tools running on the same machine
+- Security-sensitive operations
+- Low-latency requirements
+- Single-client scenarios (one Axon Code instance per server)
+- Command-line tools or IDE extensions
### STDIO Implementation Example
```typescript
-import { Server } from '@modelcontextprotocol/sdk/server/index.js';
-import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+import { Server } from "@modelcontextprotocol/sdk/server/index.js"
+import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"
-const server = new Server({name: 'local-server', version: '1.0.0'});
+const server = new Server({ name: "local-server", version: "1.0.0" })
// Register tools...
// Use STDIO transport
-const transport = new StdioServerTransport(server);
-transport.listen();
+const transport = new StdioServerTransport(server)
+transport.listen()
```
## SSE Transport
@@ -65,12 +65,12 @@ Server-Sent Events (SSE) transport runs on a remote server and communicates over
### How SSE Transport Works
-1. The client (Kilo Code) connects to the server's SSE endpoint via HTTP GET request
+1. The client (Axon Code) connects to the server's SSE endpoint via HTTP GET request
2. This establishes a persistent connection where the server can push events to the client
3. For client-to-server communication, the client makes HTTP POST requests to a separate endpoint
4. Communication happens over two channels:
- * Event Stream (GET): Server-to-client updates
- * Message Endpoint (POST): Client-to-server requests
+ - Event Stream (GET): Server-to-client updates
+ - Message Endpoint (POST): Client-to-server requests
```
Client Server
@@ -85,87 +85,90 @@ Client Server
### SSE Characteristics
-* **Remote Access**: Can be hosted on a different machine from Kilo Code
-* **Scalability**: Can handle multiple client connections concurrently
-* **Protocol**: Works over standard HTTP (no special protocols needed)
-* **Persistence**: Maintains a persistent connection for server-to-client messages
-* **Authentication**: Can use standard HTTP authentication mechanisms
+- **Remote Access**: Can be hosted on a different machine from Axon Code
+- **Scalability**: Can handle multiple client connections concurrently
+- **Protocol**: Works over standard HTTP (no special protocols needed)
+- **Persistence**: Maintains a persistent connection for server-to-client messages
+- **Authentication**: Can use standard HTTP authentication mechanisms
### When to Use SSE
SSE transport is better for:
-* Remote access across networks
-* Multi-client scenarios
-* Public services
-* Centralized tools that many users need to access
-* Integration with web services
+- Remote access across networks
+- Multi-client scenarios
+- Public services
+- Centralized tools that many users need to access
+- Integration with web services
### SSE Implementation Example
```typescript
-import { Server } from '@modelcontextprotocol/sdk/server/index.js';
-import { SSEServerTransport } from '@modelcontextprotocol/sdk/server/sse.js';
-import express from 'express';
+import { Server } from "@modelcontextprotocol/sdk/server/index.js"
+import { SSEServerTransport } from "@modelcontextprotocol/sdk/server/sse.js"
+import express from "express"
-const app = express();
-const server = new Server({name: 'remote-server', version: '1.0.0'});
+const app = express()
+const server = new Server({ name: "remote-server", version: "1.0.0" })
// Register tools...
// Use SSE transport
-const transport = new SSEServerTransport(server);
-app.use('/mcp', transport.requestHandler());
+const transport = new SSEServerTransport(server)
+app.use("/mcp", transport.requestHandler())
app.listen(3000, () => {
- console.log('MCP server listening on port 3000');
-});
+ console.log("MCP server listening on port 3000")
+})
```
+
## Local vs. Hosted: Deployment Aspects
The choice between STDIO and SSE transports directly impacts how you'll deploy and manage your MCP servers.
### STDIO: Local Deployment Model
-STDIO servers run locally on the same machine as Kilo Code, which has several important implications:
+STDIO servers run locally on the same machine as Axon Code, which has several important implications:
-* **Installation**: The server executable must be installed on each user's machine
-* **Distribution**: You need to provide installation packages for different operating systems
-* **Updates**: Each instance must be updated separately
-* **Resources**: Uses the local machine's CPU, memory, and disk
-* **Access Control**: Relies on the local machine's filesystem permissions
-* **Integration**: Easy integration with local system resources (files, processes)
-* **Execution**: Starts and stops with Kilo Code (child process lifecycle)
-* **Dependencies**: Any dependencies must be installed on the user's machine
+- **Installation**: The server executable must be installed on each user's machine
+- **Distribution**: You need to provide installation packages for different operating systems
+- **Updates**: Each instance must be updated separately
+- **Resources**: Uses the local machine's CPU, memory, and disk
+- **Access Control**: Relies on the local machine's filesystem permissions
+- **Integration**: Easy integration with local system resources (files, processes)
+- **Execution**: Starts and stops with Axon Code (child process lifecycle)
+- **Dependencies**: Any dependencies must be installed on the user's machine
#### Practical Example
A local file search tool using STDIO would:
-* Run on the user's machine
-* Have direct access to the local filesystem
-* Start when needed by Kilo Code
-* Not require network configuration
-* Need to be installed alongside Kilo Code or via a package manager
+
+- Run on the user's machine
+- Have direct access to the local filesystem
+- Start when needed by Axon Code
+- Not require network configuration
+- Need to be installed alongside Axon Code or via a package manager
### SSE: Hosted Deployment Model
SSE servers can be deployed to remote servers and accessed over the network:
-* **Installation**: Installed once on a server, accessed by many users
-* **Distribution**: Single deployment serves multiple clients
-* **Updates**: Centralized updates affect all users immediately
-* **Resources**: Uses server resources, not local machine resources
-* **Access Control**: Managed through authentication and authorization systems
-* **Integration**: More complex integration with user-specific resources
-* **Execution**: Runs as an independent service (often continuously)
-* **Dependencies**: Managed on the server, not on user machines
+- **Installation**: Installed once on a server, accessed by many users
+- **Distribution**: Single deployment serves multiple clients
+- **Updates**: Centralized updates affect all users immediately
+- **Resources**: Uses server resources, not local machine resources
+- **Access Control**: Managed through authentication and authorization systems
+- **Integration**: More complex integration with user-specific resources
+- **Execution**: Runs as an independent service (often continuously)
+- **Dependencies**: Managed on the server, not on user machines
#### Practical Example
A database query tool using SSE would:
-* Run on a central server
-* Connect to databases with server-side credentials
-* Be continuously available for multiple users
-* Require proper network security configuration
-* Be deployed using container or cloud technologies
+
+- Run on a central server
+- Connect to databases with server-side credentials
+- Be continuously available for multiple users
+- Require proper network security configuration
+- Be deployed using container or cloud technologies
### Hybrid Approaches
@@ -177,20 +180,20 @@ Some scenarios benefit from a hybrid approach:
## Choosing Between STDIO and SSE
-| Consideration | STDIO | SSE |
-|---------------|-------|-----|
-| **Location** | Local machine only | Local or remote |
-| **Clients** | Single client | Multiple clients |
-| **Performance** | Lower latency | Higher latency (network overhead) |
-| **Setup Complexity** | Simpler | More complex (requires HTTP server) |
-| **Security** | Inherently secure | Requires explicit security measures |
-| **Network Access** | Not needed | Required |
-| **Scalability** | Limited to local machine | Can distribute across network |
-| **Deployment** | Per-user installation | Centralized installation |
-| **Updates** | Distributed updates | Centralized updates |
-| **Resource Usage** | Uses client resources | Uses server resources |
-| **Dependencies** | Client-side dependencies | Server-side dependencies |
-
-## Configuring Transports in Kilo Code
-
-For detailed information on configuring STDIO and SSE transports in Kilo Code, including example configurations, see the [Understanding Transport Types](/features/mcp/using-mcp-in-kilo-code#understanding-transport-types) section in the Using MCP in Kilo Code guide.
\ No newline at end of file
+| Consideration | STDIO | SSE |
+| -------------------- | ------------------------ | ----------------------------------- |
+| **Location** | Local machine only | Local or remote |
+| **Clients** | Single client | Multiple clients |
+| **Performance** | Lower latency | Higher latency (network overhead) |
+| **Setup Complexity** | Simpler | More complex (requires HTTP server) |
+| **Security** | Inherently secure | Requires explicit security measures |
+| **Network Access** | Not needed | Required |
+| **Scalability** | Limited to local machine | Can distribute across network |
+| **Deployment** | Per-user installation | Centralized installation |
+| **Updates** | Distributed updates | Centralized updates |
+| **Resource Usage** | Uses client resources | Uses server resources |
+| **Dependencies** | Client-side dependencies | Server-side dependencies |
+
+## Configuring Transports in Axon Code
+
+For detailed information on configuring STDIO and SSE transports in Axon Code, including example configurations, see the [Understanding Transport Types](/features/mcp/using-mcp-in-kilo-code#understanding-transport-types) section in the Using MCP in Axon Code guide.
diff --git a/apps/kilocode-docs/docs/features/mcp/using-mcp-in-kilo-code.md b/apps/kilocode-docs/docs/features/mcp/using-mcp-in-kilo-code.md
index 1cabda9148..7c10f073c1 100644
--- a/apps/kilocode-docs/docs/features/mcp/using-mcp-in-kilo-code.md
+++ b/apps/kilocode-docs/docs/features/mcp/using-mcp-in-kilo-code.md
@@ -1,15 +1,15 @@
---
-title: Using MCP in Kilo Code
-sidebar_label: Using MCP in Kilo Code
+title: Using MCP in Axon Code
+sidebar_label: Using MCP in Axon Code
---
-# Using MCP in Kilo Code
+# Using MCP in Axon Code
-Model Context Protocol (MCP) extends Kilo Code's capabilities by connecting to external tools and services. This guide covers everything you need to know about using MCP with Kilo Code.
+Model Context Protocol (MCP) extends Axon Code's capabilities by connecting to external tools and services. This guide covers everything you need to know about using MCP with Axon Code.
@@ -52,7 +52,7 @@ Both files use a JSON format with a `mcpServers` object containing named server
}
```
-_Example of MCP Server config in Kilo Code (STDIO Transport)_
+_Example of MCP Server config in Axon Code (STDIO Transport)_
### Understanding Transport Types
@@ -179,24 +179,24 @@ MCP tool auto-approval works on a per-tool basis and is disabled by default. To
-When enabled, Kilo Code will automatically approve this specific tool without prompting. Note that the global "Use MCP servers" setting takes precedence - if it's disabled, no MCP tools will be auto-approved.
+When enabled, Axon Code will automatically approve this specific tool without prompting. Note that the global "Use MCP servers" setting takes precedence - if it's disabled, no MCP tools will be auto-approved.
## Finding and Installing MCP Servers
-Kilo Code does not come with any pre-installed MCP servers. You'll need to find and install them separately.
+Axon Code does not come with any pre-installed MCP servers. You'll need to find and install them separately.
- **Community Repositories:** Check for community-maintained lists of MCP servers on GitHub
-- **Ask Kilo Code:** You can ask Kilo Code to help you find or even create MCP servers
-- **Build Your Own:** Create custom MCP servers using the SDK to extend Kilo Code with your own tools
+- **Ask Axon Code:** You can ask Axon Code to help you find or even create MCP servers
+- **Build Your Own:** Create custom MCP servers using the SDK to extend Axon Code with your own tools
For full SDK documentation, visit the [MCP GitHub repository](https://github.com/modelcontextprotocol/).
## Using MCP Tools in Your Workflow
-After configuring an MCP server, Kilo Code will automatically detect available tools and resources. To use them:
+After configuring an MCP server, Axon Code will automatically detect available tools and resources. To use them:
-1. Type your request in the Kilo Code chat interface
-2. Kilo Code will identify when an MCP tool can help with your task
+1. Type your request in the Axon Code chat interface
+2. Axon Code will identify when an MCP tool can help with your task
3. Approve the tool use when prompted (or use auto-approval)
Example: "Analyze the performance of my API" might use an MCP tool that tests API endpoints.
diff --git a/apps/kilocode-docs/docs/features/mcp/what-is-mcp.md b/apps/kilocode-docs/docs/features/mcp/what-is-mcp.md
index 8e957940ed..2edbf6f7cd 100644
--- a/apps/kilocode-docs/docs/features/mcp/what-is-mcp.md
+++ b/apps/kilocode-docs/docs/features/mcp/what-is-mcp.md
@@ -28,9 +28,9 @@ For example, an AI using MCP can perform tasks like "search our company database
- **How is security handled?** Users control which MCP servers they connect to and what permissions those servers have. As with any tool that accesses data or services, use trusted sources and configure appropriate access controls.
-## MCP in Kilo Code
+## MCP in Axon Code
-Kilo Code implements the Model Context Protocol to:
+Axon Code implements the Model Context Protocol to:
- Connect to both local and remote MCP servers
- Provide a consistent interface for accessing tools
@@ -44,6 +44,6 @@ MCP provides a standardized way for AI systems to interact with external tools a
Ready to dig deeper? Check out these guides:
- [MCP Overview](/features/mcp/overview) - A quick glance at the MCP documentation structure
-- [Using MCP in Kilo Code](/features/mcp/using-mcp-in-kilo-code) - Get started with MCP in Kilo Code, including creating simple servers
+- [Using MCP in Axon Code](/features/mcp/using-mcp-in-kilo-code) - Get started with MCP in Axon Code, including creating simple servers
- [MCP vs API](/features/mcp/mcp-vs-api) - Technical advantages compared to traditional APIs
-- [STDIO & SSE Transports](/features/mcp/server-transports) - Local vs. hosted deployment models
\ No newline at end of file
+- [STDIO & SSE Transports](/features/mcp/server-transports) - Local vs. hosted deployment models
diff --git a/apps/kilocode-docs/docs/features/model-temperature.md b/apps/kilocode-docs/docs/features/model-temperature.md
index f4780edf26..0cee9529a4 100644
--- a/apps/kilocode-docs/docs/features/model-temperature.md
+++ b/apps/kilocode-docs/docs/features/model-temperature.md
@@ -11,43 +11,43 @@ Temperature is a setting (usually between 0.0 and 2.0) that controls how random
:::info Temperature and Code: Common Misconceptions
Temperature controls output randomness, not code quality or accuracy directly. Key points:
-* **Low Temperature (near 0.0):** Produces predictable, consistent code. Good for simple tasks, but can be repetitive and lack creativity. It doesn't guarantee *better* code.
-* **High Temperature:** Increases randomness, potentially leading to creative solutions but also more errors or nonsensical code. It doesn't guarantee *higher-quality* code.
-* **Accuracy:** Code accuracy depends on the model's training and prompt clarity, not temperature.
-* **Temperature 0.0:** Useful for consistency, but limits exploration needed for complex problems.
-:::
+- **Low Temperature (near 0.0):** Produces predictable, consistent code. Good for simple tasks, but can be repetitive and lack creativity. It doesn't guarantee _better_ code.
+- **High Temperature:** Increases randomness, potentially leading to creative solutions but also more errors or nonsensical code. It doesn't guarantee _higher-quality_ code.
+- **Accuracy:** Code accuracy depends on the model's training and prompt clarity, not temperature.
+- **Temperature 0.0:** Useful for consistency, but limits exploration needed for complex problems.
+ :::
-## Default Values in Kilo Code
+## Default Values in Axon Code
-Kilo Code uses a default temperature of 0.0 for most models, optimizing for maximum determinism and precision in code generation. This applies to OpenAI models, Anthropic models (non-thinking variants), LM Studio models, and most other providers.
+Axon Code uses a default temperature of 0.0 for most models, optimizing for maximum determinism and precision in code generation. This applies to OpenAI models, Anthropic models (non-thinking variants), LM Studio models, and most other providers.
Some models use higher default temperatures - DeepSeek R1 models and certain reasoning-focused models default to 0.6, providing a balance between determinism and creative exploration.
Models with thinking capabilities (where the AI shows its reasoning process) require a fixed temperature of 1.0 which cannot be changed, as this setting ensures optimal performance of the thinking mechanism. This applies to any model with the ":thinking" flag enabled.
-Some specialized models don't support temperature adjustments at all, in which case Kilo Code respects these limitations automatically.
+Some specialized models don't support temperature adjustments at all, in which case Axon Code respects these limitations automatically.
## When to Adjust Temperature
Here are some examples of temperature settings that might work well for different tasks:
-* **Code Mode (0.0-0.3):** For writing precise, correct code with consistent, deterministic results
-* **Architect Mode (0.4-0.7):** For brainstorming architecture or design solutions with balanced creativity and structure
-* **Ask Mode (0.7-1.0):** For explanations or open-ended questions requiring diverse and insightful responses
-* **Debug Mode (0.0-0.3):** For troubleshooting bugs with consistent precision
+- **Code Mode (0.0-0.3):** For writing precise, correct code with consistent, deterministic results
+- **Architect Mode (0.4-0.7):** For brainstorming architecture or design solutions with balanced creativity and structure
+- **Ask Mode (0.7-1.0):** For explanations or open-ended questions requiring diverse and insightful responses
+- **Debug Mode (0.0-0.3):** For troubleshooting bugs with consistent precision
These are starting points – it's important to [experiment with different settings](#experimentation) to find what works best for your specific needs and preferences.
## How to Adjust Temperature
-1. **Open the Kilo Code Panel:** Click the Kilo Code icon (
- *Temperature slider in Kilo Code settings panel*
+ 
+
Controls the maximum number of lines captured from terminal output. When exceeded, it keeps 20% of the beginning and 80% of the end with a truncation message in between. This prevents excessive token usage while maintaining context. Default: 500 lines.
Controls the maximum number of lines captured from terminal output. When exceeded, lines are removed from the middle to save tokens. Default: 500 lines.
#### Terminal Shell Integration Timeout
+
Maximum time to wait for shell integration to initialize before executing commands. Increase this value if you experience "Shell Integration Unavailable" errors. Default: 15 seconds.
#### Terminal Command Delay
+
-Adds a small pause after running commands to help Kilo Code capture all output correctly. This setting can significantly impact shell integration reliability due to VSCode's implementation of terminal integration across different operating systems and shell configurations:
+Adds a small pause after running commands to help Axon Code capture all output correctly. This setting can significantly impact shell integration reliability due to VSCode's implementation of terminal integration across different operating systems and shell configurations:
- **Default**: 0ms
- **Common Values**:
- * 0ms: Works best for some users with newer VSCode versions
- * 50ms: Historical default, still effective for many users
- * 150ms: Recommended for PowerShell users
+ - 0ms: Works best for some users with newer VSCode versions
+ - 50ms: Historical default, still effective for many users
+ - 150ms: Recommended for PowerShell users
- **Note**: Different values may work better depending on your:
- * VSCode version
- * Shell customizations (oh-my-zsh, powerlevel10k, etc.)
- * Operating system and environment
+ - VSCode version
+ - Shell customizations (oh-my-zsh, powerlevel10k, etc.)
+ - Operating system and environment
### Advanced Settings
@@ -69,29 +72,34 @@ Always restart all open terminals after changing any of these settings.
:::
#### PowerShell Counter Workaround
+
-Helps PowerShell run the same command multiple times in a row. Enable this if you notice Kilo Code can't run identical commands consecutively in PowerShell.
+Helps PowerShell run the same command multiple times in a row. Enable this if you notice Axon Code can't run identical commands consecutively in PowerShell.
#### Clear ZSH EOL Mark
+
-Prevents ZSH from adding special characters at the end of output lines that can confuse Kilo Code when reading terminal results.
+Prevents ZSH from adding special characters at the end of output lines that can confuse Axon Code when reading terminal results.
#### Oh My Zsh Integration
+
-Makes Kilo Code work better with the popular [Oh My Zsh](https://ohmyz.sh/) shell customization framework. Turn this on if you use Oh My Zsh and experience terminal issues.
+Makes Axon Code work better with the popular [Oh My Zsh](https://ohmyz.sh/) shell customization framework. Turn this on if you use Oh My Zsh and experience terminal issues.
#### Powerlevel10k Integration
+
-Improves compatibility if you use the Powerlevel10k theme for ZSH. Turn this on if your fancy terminal prompt causes issues with Kilo Code.
+Improves compatibility if you use the Powerlevel10k theme for ZSH. Turn this on if your fancy terminal prompt causes issues with Axon Code.
#### ZDOTDIR Handling
+
-Helps Kilo Code work with custom ZSH configurations without interfering with your personal shell settings and customizations.
+Helps Axon Code work with custom ZSH configurations without interfering with your personal shell settings and customizations.
## Troubleshooting Shell Integration
@@ -104,6 +112,7 @@ PowerShell restricts script execution by default. To configure:
3. Set appropriate policy: `Set-ExecutionPolicy RemoteSigned -Scope CurrentUser`
Common policies:
+
- `Restricted`: No scripts allowed (default)
- `RemoteSigned`: Local scripts can run; downloaded scripts need signing
- `Unrestricted`: All scripts run with warnings
@@ -114,21 +123,25 @@ Common policies:
If automatic integration fails, add the appropriate line to your shell configuration:
**Bash** (`~/.bashrc`):
+
```bash
[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path bash)"
```
**Zsh** (`~/.zshrc`):
+
```bash
[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path zsh)"
```
**PowerShell** (`$Profile`):
+
```powershell
if ($env:TERM_PROGRAM -eq "vscode") { . "$(code --locate-shell-integration-path pwsh)" }
```
**Fish** (`~/.config/fish/config.fish`):
+
```fish
string match -q "$TERM_PROGRAM" "vscode"; and . (code --locate-shell-integration-path fish)
```
@@ -138,18 +151,20 @@ string match -q "$TERM_PROGRAM" "vscode"; and . (code --locate-shell-integration
If you use terminal customization tools:
**Powerlevel10k**:
+
```bash
# Add before sourcing powerlevel10k in ~/.zshrc
typeset -g POWERLEVEL9K_TERM_SHELL_INTEGRATION=true
```
-**Alternative**: Enable the Powerlevel10k Integration setting in Kilo Code.
+**Alternative**: Enable the Powerlevel10k Integration setting in Axon Code.
### Verifying Shell Integration Status
Confirm shell integration is active with these commands:
**Bash**:
+
```bash
set | grep -i '[16]33;'
echo "$PROMPT_COMMAND" | grep vsc
@@ -157,24 +172,28 @@ trap -p DEBUG | grep vsc
```
**Zsh**:
+
```zsh
functions | grep -i vsc
typeset -p precmd_functions preexec_functions
```
**PowerShell**:
+
```powershell
Get-Command -Name "*VSC*" -CommandType Function
Get-Content Function:\Prompt | Select-String "VSCode"
```
**Fish**:
+
```fish
functions | grep -i vsc
functions fish_prompt | grep -i vsc
```
Visual indicators of active shell integration:
+
1. Shell integration indicator in terminal title bar
2. Command detection highlighting
3. Working directory updates in terminal title
@@ -187,6 +206,7 @@ When using Windows Subsystem for Linux (WSL), there are two distinct ways to use
### Method 1: VSCode Windows with WSL Terminal
In this setup:
+
- VSCode runs natively in Windows
- You use the WSL terminal integration feature in VSCode
- Shell commands are executed through the WSL bridge
@@ -196,6 +216,7 @@ In this setup:
### Method 2: VSCode Running Within WSL
In this setup:
+
- You launch VSCode directly from within WSL using `code .`
- VSCode server runs natively in the Linux environment
- Direct access to Linux filesystem and tools
@@ -204,6 +225,7 @@ In this setup:
- Recommended approach for WSL development
For optimal shell integration with WSL, we recommend:
+
1. Open your WSL distribution
2. Navigate to your project directory
3. Launch VSCode using `code .`
@@ -216,10 +238,12 @@ For optimal shell integration with WSL, we recommend:
For fellow Windows users running Fish terminal within a Cygwin environment, here's how VS Code's shell integration works:
1. **(Optional) Locate the Shell Integration Script:**
- Open your Fish terminal *within VS Code* and run the following command:
+ Open your Fish terminal _within VS Code_ and run the following command:
+
```bash
code --locate-shell-integration-path fish
```
+
This will output the path to the `shellIntegration.fish` script. Note down this path.
2. **Update Your Fish Configuration:**
@@ -239,7 +263,8 @@ For fellow Windows users running Fish terminal within a Cygwin environment, here
# source "/cygdrive/c/Users/YourUser/.vscode/extensions/..../shellIntegration.fish"
end
```
- *Remember to replace the example path with the actual path from Step 1, correctly formatted for Cygwin.*
+
+ _Remember to replace the example path with the actual path from Step 1, correctly formatted for Cygwin._
3. **Configure VS Code Terminal Profile:**
Open your VS Code `settings.json` file (Ctrl+Shift+P -> "Preferences: Open User Settings (JSON)"). Update or add the Fish profile under `terminal.integrated.profiles.windows` like this:
@@ -277,7 +302,8 @@ For fellow Windows users running Fish terminal within a Cygwin environment, here
// ... other settings ...
}
```
- *Note: Using `bash.exe --login -i -c "exec fish"` is often more reliable in Cygwin environments for ensuring the correct environment setup before `fish` starts. However, if that approach doesn't work, try the `fish-direct` profile configuration.*
+
+ _Note: Using `bash.exe --login -i -c "exec fish"` is often more reliable in Cygwin environments for ensuring the correct environment setup before `fish` starts. However, if that approach doesn't work, try the `fish-direct` profile configuration._
4. **Restart VS Code:**
Close and reopen Visual Studio Code completely to apply the changes.
@@ -287,46 +313,49 @@ For fellow Windows users running Fish terminal within a Cygwin environment, here
This setup works reliably on Windows systems using Cygwin, Fish, and the Starship prompt, and should assist users with similar configurations.
-
### Shell Integration Failures After VSCode 1.98
**Issue**: After VSCode updates beyond version 1.98, shell integration may fail with the error "VSCE output start escape sequence (]633;C or ]133;C) not received".
**Solutions**:
+
1. **Set Terminal Command Delay**:
- - Set the Terminal Command Delay to 50ms in Kilo Code settings
- - Restart all terminals after changing this setting
- - This matches older default behavior and may resolve the issue, however some users have reported that a value of 0ms works better. This is a workaround for upstream VSCode problems.
+
+ - Set the Terminal Command Delay to 50ms in Axon Code settings
+ - Restart all terminals after changing this setting
+ - This matches older default behavior and may resolve the issue, however some users have reported that a value of 0ms works better. This is a workaround for upstream VSCode problems.
2. **Roll Back VSCode Version**:
- - Download VSCode v1.98 from [VSCode Updates](https://code.visualstudio.com/updates/v1_98)
- - Replace your current VSCode installation
- - No backup of Kilo settings needed
+
+ - Download VSCode v1.98 from [VSCode Updates](https://code.visualstudio.com/updates/v1_98)
+ - Replace your current VSCode installation
+ - No backup of Kilo settings needed
3. **WSL-Specific Workaround**:
- - If using WSL, ensure you launch VSCode from within WSL using `code .`
+
+ - If using WSL, ensure you launch VSCode from within WSL using `code .`
4. **ZSH Users**:
- - Try enabling some or all ZSH-related workarounds in Kilo Code settings
- - These settings can help regardless of your operating system
+ - Try enabling some or all ZSH-related workarounds in Axon Code settings
+ - These settings can help regardless of your operating system
## Known Issues and Workarounds
### Ctrl+C Behavior
-**Issue**: If text is already typed in the terminal when Kilo Code tries to run a command, Kilo Code will press Ctrl+C first to clear the line, which can interrupt running processes.
+**Issue**: If text is already typed in the terminal when Axon Code tries to run a command, Axon Code will press Ctrl+C first to clear the line, which can interrupt running processes.
-**Workaround**: Make sure your terminal prompt is empty (no partial commands typed) before asking Kilo Code to execute terminal commands.
+**Workaround**: Make sure your terminal prompt is empty (no partial commands typed) before asking Axon Code to execute terminal commands.
### Multi-line Command Issues
-**Issue**: Commands that span multiple lines can confuse Kilo Code and may show output from previous commands mixed in with current output.
+**Issue**: Commands that span multiple lines can confuse Axon Code and may show output from previous commands mixed in with current output.
**Workaround**: Instead of multi-line commands, use command chaining with `&&` to keep everything on one line (e.g., `echo a && echo b` instead of typing each command on a separate line).
### PowerShell-Specific Issues
-1. **Premature Completion**: PowerShell sometimes tells Kilo Code a command is finished before all the output has been shown.
+1. **Premature Completion**: PowerShell sometimes tells Axon Code a command is finished before all the output has been shown.
2. **Repeated Commands**: PowerShell may refuse to run the same command twice in a row.
**Workaround**: Enable the "PowerShell counter workaround" setting and set a terminal command delay of 150ms in the settings to give commands more time to complete.
@@ -340,43 +369,47 @@ This setup works reliably on Windows systems using Cygwin, Fish, and the Starshi
## Troubleshooting Resources
### Checking Debug Logs
+
When shell integration issues occur, check the debug logs:
+
1. Open Help → Toggle Developer Tools → Console
2. Set "Show All Levels" to see all log messages
3. Look for messages containing `[Terminal Process]`
4. Check `preOutput` content in error messages:
- - Empty preOutput (`''`) means VSCode sent no data
- - This indicates a potential VSCode shell integration issue, or an upstream bug that is out of our control
- - The absence of shell integration markers may require adjusting settings to work around possible upstream bugs or local workstation configuration issues related to shell initialization and VSCode's loading of special shell integration hooks
+ - Empty preOutput (`''`) means VSCode sent no data
+ - This indicates a potential VSCode shell integration issue, or an upstream bug that is out of our control
+ - The absence of shell integration markers may require adjusting settings to work around possible upstream bugs or local workstation configuration issues related to shell initialization and VSCode's loading of special shell integration hooks
### Using the VSCode Terminal Integration Test Extension
-The [VSCode Terminal Integration Test Extension](https://github.com/KJ7LNW/vsce-test-terminal-integration) helps diagnose shell integration issues by testing different settings combinations:
+The [VSCode Terminal Integration Test Extension](https://github.com/KJ7LNW/vsce-test-terminal-integration) helps diagnose shell integration issues by testing different settings combinations:
1. **When Commands Stall**:
- - If you see "command already running" warnings, click "Reset Stats" to reset the terminal state
- - These warnings indicate shell integration is not working
- - Try different settings combinations until you find one that works
- - If it really gets stuck, restart the extension by closing the window and pressing F5
+
+ - If you see "command already running" warnings, click "Reset Stats" to reset the terminal state
+ - These warnings indicate shell integration is not working
+ - Try different settings combinations until you find one that works
+ - If it really gets stuck, restart the extension by closing the window and pressing F5
2. **Testing Settings**:
- - Systematically try different combinations of:
- * Terminal Command Delay
- * Shell Integration settings
- - Document which combinations succeed or fail
- - This helps identify patterns in shell integration issues
+
+ - Systematically try different combinations of:
+ - Terminal Command Delay
+ - Shell Integration settings
+ - Document which combinations succeed or fail
+ - This helps identify patterns in shell integration issues
3. **Reporting Issues**:
- - Once you find a problematic configuration
- - Document the exact settings combination
- - Note your environment (OS, VSCode version, shell, and any shell prompt customization)
- - Open an issue with these details to help improve shell integration
+ - Once you find a problematic configuration
+ - Document the exact settings combination
+ - Note your environment (OS, VSCode version, shell, and any shell prompt customization)
+ - Open an issue with these details to help improve shell integration
## Support
If you've followed these steps and are still experiencing problems, please:
-1. Check the [Kilo Code GitHub Issues](https://github.com/Kilo-Org/kilocode/issues) to see if others have reported similar problems
+1. Check the [Axon Code GitHub Issues](https://github.com/Kilo-Org/kilocode/issues) to see if others have reported similar problems
2. If not, create a new issue with details about your operating system, VSCode/Cursor version, and the steps you've tried
-For additional help, join our [Discord](https://kilocode.ai/discord).
+For additional help, join our [Discord](https://matterai.so/discord).
diff --git a/apps/kilocode-docs/docs/features/slash-commands/workflows.mdx b/apps/kilocode-docs/docs/features/slash-commands/workflows.mdx
index 899dea4a55..fa1bf2541c 100644
--- a/apps/kilocode-docs/docs/features/slash-commands/workflows.mdx
+++ b/apps/kilocode-docs/docs/features/slash-commands/workflows.mdx
@@ -3,9 +3,9 @@ title: "Workflows"
sidebarTitle: "Workflows"
---
-Workflows automate repetitive tasks by defining step-by-step instructions for Kilo Code to execute. Invoke any workflow by typing `/[workflow-name.md]` in the chat.
+Workflows automate repetitive tasks by defining step-by-step instructions for Axon Code to execute. Invoke any workflow by typing `/[workflow-name.md]` in the chat.
-
+
+
## Benefits
-* **Speed**: Quickly respond without typing full answers.
-* **Clarity**: Suggestions often clarify the type of information Kilo Code needs.
-* **Flexibility**: Edit suggestions to provide precise, customized answers when needed.
+- **Speed**: Quickly respond without typing full answers.
+- **Clarity**: Suggestions often clarify the type of information Axon Code needs.
+- **Flexibility**: Edit suggestions to provide precise, customized answers when needed.
-This feature streamlines the interaction when Kilo Code requires clarification, allowing you to guide the task effectively with minimal effort.
\ No newline at end of file
+This feature streamlines the interaction when Axon Code requires clarification, allowing you to guide the task effectively with minimal effort.
diff --git a/apps/kilocode-docs/docs/features/system-notifications.md b/apps/kilocode-docs/docs/features/system-notifications.md
index ca5bd6841d..b3fcdf594d 100644
--- a/apps/kilocode-docs/docs/features/system-notifications.md
+++ b/apps/kilocode-docs/docs/features/system-notifications.md
@@ -7,7 +7,7 @@ System notifications are native operating system notifications that appear in yo
- Your screen is locked (depending on OS settings)
- You're away from your computer
-Kilo Code uses system notifications to inform you about:
+Axon Code uses system notifications to inform you about:
- Task completion status
- Important errors or warnings
@@ -16,7 +16,7 @@ Kilo Code uses system notifications to inform you about:
## Supported Operating Systems
-Kilo Code's system notifications work on all major operating systems with different underlying technologies:
+Axon Code's system notifications work on all major operating systems with different underlying technologies:
| Operating System | Technology | Requirements |
| ---------------- | ------------------------------- | -------------------------------------------- |
@@ -32,7 +32,7 @@ macOS has the best built-in support for system notifications with two available
#### Method 1: Built-in AppleScript (Fallback)
-No additional setup required. Kilo Code uses macOS's built-in command to display notifications.
+No additional setup required. Axon Code uses macOS's built-in command to display notifications.
#### Method 2: Enhanced with terminal-notifier (Recommended)
@@ -46,7 +46,7 @@ brew install terminal-notifier
npm install -g terminal-notifier
```
-**How it works:** Kilo Code first attempts to use `terminal-notifier` and automatically falls back to AppleScript if it's not installed.
+**How it works:** Axon Code first attempts to use `terminal-notifier` and automatically falls back to AppleScript if it's not installed.
### Windows Setup
diff --git a/apps/kilocode-docs/docs/features/tools/access-mcp-resource.md b/apps/kilocode-docs/docs/features/tools/access-mcp-resource.md
index 16af3cfbfc..a28c04b238 100644
--- a/apps/kilocode-docs/docs/features/tools/access-mcp-resource.md
+++ b/apps/kilocode-docs/docs/features/tools/access-mcp-resource.md
@@ -1,6 +1,6 @@
# access_mcp_resource
-The `access_mcp_resource` tool retrieves data from resources exposed by connected Model Context Protocol (MCP) servers. It allows Kilo Code to access files, API responses, documentation, or system information that provides additional context for tasks.
+The `access_mcp_resource` tool retrieves data from resources exposed by connected Model Context Protocol (MCP) servers. It allows Axon Code to access files, API responses, documentation, or system information that provides additional context for tasks.
## Parameters
@@ -15,10 +15,10 @@ This tool connects to MCP servers and fetches data from their exposed resources.
## When is it used?
-- When Kilo Code needs additional context from external systems
-- When Kilo Code needs to access domain-specific data from specialized MCP servers
-- When Kilo Code needs to retrieve reference documentation hosted by MCP servers
-- When Kilo Code needs to integrate real-time data from external APIs via MCP
+- When Axon Code needs additional context from external systems
+- When Axon Code needs to access domain-specific data from specialized MCP servers
+- When Axon Code needs to retrieve reference documentation hosted by MCP servers
+- When Axon Code needs to integrate real-time data from external APIs via MCP
## Key Features
@@ -48,52 +48,57 @@ This tool connects to MCP servers and fetches data from their exposed resources.
When the `access_mcp_resource` tool is invoked, it follows this process:
1. **Connection Validation**:
- - Verifies that an MCP hub is available and initialized
- - Confirms the specified server exists in the connection list
- - Checks if the server is disabled (returns an error if it is)
+
+ - Verifies that an MCP hub is available and initialized
+ - Confirms the specified server exists in the connection list
+ - Checks if the server is disabled (returns an error if it is)
2. **User Approval**:
- - Presents the resource access request to the user for approval
- - Provides server name and resource URI for user verification
- - Proceeds only if the user approves the resource access
+
+ - Presents the resource access request to the user for approval
+ - Provides server name and resource URI for user verification
+ - Proceeds only if the user approves the resource access
3. **Resource Request**:
- - Uses the Model Context Protocol SDK to communicate with servers
- - Makes a `resources/read` request to the server through the MCP hub
- - Applies configured timeouts to prevent hanging on unresponsive servers
+
+ - Uses the Model Context Protocol SDK to communicate with servers
+ - Makes a `resources/read` request to the server through the MCP hub
+ - Applies configured timeouts to prevent hanging on unresponsive servers
4. **Response Processing**:
- - Receives a structured response with metadata and content arrays
- - Processes text content for display to the user
- - Handles image data specially for appropriate display
- - Returns the processed resource data to Kilo Code for use in the current task
+ - Receives a structured response with metadata and content arrays
+ - Processes text content for display to the user
+ - Handles image data specially for appropriate display
+ - Returns the processed resource data to Axon Code for use in the current task
## Resource Types
MCP servers can provide two main types of resources:
1. **Standard Resources**:
- - Fixed resources with specific URIs
- - Defined name, description, and MIME type
- - Direct access without parameters
- - Typically represent static data or real-time information
+
+ - Fixed resources with specific URIs
+ - Defined name, description, and MIME type
+ - Direct access without parameters
+ - Typically represent static data or real-time information
2. **Resource Templates**:
- - Parameterized resources with placeholder values in URIs
- - Allow dynamic resource generation based on provided parameters
- - Can represent queries or filtered views of data
- - More flexible but require additional URI formatting
+ - Parameterized resources with placeholder values in URIs
+ - Allow dynamic resource generation based on provided parameters
+ - Can represent queries or filtered views of data
+ - More flexible but require additional URI formatting
## Examples When Used
-- When helping with API development, Kilo Code retrieves endpoint specifications from MCP resources to ensure correct implementation.
-- When assisting with data visualization, Kilo Code accesses current data samples from connected MCP servers.
-- When working in specialized domains, Kilo Code retrieves technical documentation to provide accurate guidance.
-- When generating industry-specific code, Kilo Code references compliance requirements from documentation resources.
+- When helping with API development, Axon Code retrieves endpoint specifications from MCP resources to ensure correct implementation.
+- When assisting with data visualization, Axon Code accesses current data samples from connected MCP servers.
+- When working in specialized domains, Axon Code retrieves technical documentation to provide accurate guidance.
+- When generating industry-specific code, Axon Code references compliance requirements from documentation resources.
## Usage Examples
Accessing current weather data:
+
```
@@ -76,14 +76,14 @@ _Anthropic console API Keys section with "Create key" button. Name your key, set
_OpenAI platform with "Create new secret key" button. Name your key and copy it immediately after creation._
-### Configuring the Provider in Kilo Code
+### Configuring the Provider in Axon Code
Once you have your API key:
-1. Open the Kilo Code sidebar by clicking the Kilo Code icon (
-*VS Code marketplace with Kilo Code extension ready to install*
+
-*Installing Kilo Code using VS Code's "Install from VSIX" dialog*
+*Installing Axon Code using VS Code's "Install from VSIX" dialog*
## Troubleshooting
**Extension Not Visible**
-* Restart VS Code
-* Verify Kilo Code is listed and enabled in Extensions
-* Try disabling and re-enabling the extension in Extensions
-* Check Output panel for errors (View → Output, select "Kilo Code")
+
+- Restart VS Code
+- Verify Axon Code is listed and enabled in Extensions
+- Try disabling and re-enabling the extension in Extensions
+- Check Output panel for errors (View → Output, select "Axon Code")
**Installation Problems**
-* Ensure stable internet connection
-* Verify VS Code version 1.84.0 or later
-* If VS Code Marketplace is inaccessible, try the Open VSX Registry method
+
+- Ensure stable internet connection
+- Verify VS Code version 1.84.0 or later
+- If VS Code Marketplace is inaccessible, try the Open VSX Registry method
## Getting Support
If you encounter issues not covered here:
-* Join our [Discord community](https://kilocode.ai/discord) for real-time support
-* Submit issues on [GitHub](https://github.com/Kilo-Org/kilocode/issues)
-* Visit our [Reddit community](https://www.reddit.com/r/KiloCode)
+- Join our [Discord community](https://matterai.so/discord) for real-time support
+- Submit issues on [GitHub](https://github.com/Kilo-Org/kilocode/issues)
+- Visit our [Reddit community](https://www.reddit.com/r/KiloCode)
diff --git a/apps/kilocode-docs/docs/getting-started/setting-up.mdx b/apps/kilocode-docs/docs/getting-started/setting-up.mdx
index 537bf892de..3152f279a8 100644
--- a/apps/kilocode-docs/docs/getting-started/setting-up.mdx
+++ b/apps/kilocode-docs/docs/getting-started/setting-up.mdx
@@ -5,9 +5,9 @@ sidebar_label: Getting Set up
import { DISCORD_URL } from "@site/src/constants.ts";
import useDocusaurusContext from "@docusaurus/useDocusaurusContext";
-# Setting up Kilo Code
+# Setting up Axon Code
-When you sign up for Kilo Code, you can start immediately with free models, or top up your account for the first time to get bonus credits.
+When you sign up for Axon Code, you can start immediately with free models, or top up your account for the first time to get bonus credits.
To claim your bonus credits:
@@ -17,21 +17,21 @@ To claim your bonus credits:
## Registration process
-Kilo Code provides a simple registration process that gives you access to the latest frontier coding models with your Kilo Code login.
+Axon Code provides a simple registration process that gives you access to the latest frontier coding models with your Axon Code login.
-1. Click on "Try Kilo Code for Free" in the extension
-1. Sign in with your Google account to kilocode.ai
-1. kilocode.ai will prompt you to open Visual Studio Code
+1. Click on "Try Axon Code for Free" in the extension
+1. Sign in with your Google account to matterai.so
+1. matterai.so will prompt you to open Visual Studio Code
- When using an IDE in a web browser, you will be asked to copy the API key manually instead
1. Once you allow it to Open VS Code, you must also allow VS Code to open the authorization URL
That's it - you're all set! Now you can start with [your first task](/getting-started/your-first-task)
:::tip Need Help?
-If you have any questions about pricing or tokens, please reach out to our [support team](mailto:hi@kilocode.ai) or ask in our 
+
+
-*Kilo Code shows exactly what action it wants to perform and waits for your approval.*
+*Axon Code shows exactly what action it wants to perform and waits for your approval.*
-* In **Code** mode, writing capabilities are on by default.
-* In **Architect** and **Ask** modes, Kilo Code won't write code.
+- In **Code** mode, writing capabilities are on by default.
+- In **Architect** and **Ask** modes, Axon Code won't write code.
:::tip
-The level of autonomy is configurable, allowing you to make the agent more or less autonomous.
+The level of autonomy is configurable, allowing you to make the agent more or less autonomous.
You can learn more about [using modes](/basic-usage/using-modes) and [auto-approving actions](/features/auto-approving-actions).
@@ -63,17 +63,17 @@ You can learn more about [using modes](/basic-usage/using-modes) and [auto-appro
## Step 5: Iterate
-Kilo Code works iteratively. After each action, it waits for your feedback before proposing the next step. Continue this review-approve cycle until your task is complete.
+Axon Code works iteratively. After each action, it waits for your feedback before proposing the next step. Continue this review-approve cycle until your task is complete.
-*After completing the task, Kilo Code shows the final result and awaits your next instruction.*
+*After completing the task, Axon Code shows the final result and awaits your next instruction.*
## Conclusion
You've completed your first task. Along the way you learned:
-* How to interact with Kilo Code using natural language
-* Why approval keeps you in control
-* How iteration lets the AI refine its work
+- How to interact with Axon Code using natural language
+- Why approval keeps you in control
+- How iteration lets the AI refine its work
Ready for more? Explore different [modes](/basic-usage/using-modes) or try [auto-approval](/features/auto-approving-actions) to speed up repetitive tasks.
diff --git a/apps/kilocode-docs/docs/index.mdx b/apps/kilocode-docs/docs/index.mdx
index aefbf17e81..ff3f748ad4 100644
--- a/apps/kilocode-docs/docs/index.mdx
+++ b/apps/kilocode-docs/docs/index.mdx
@@ -5,11 +5,11 @@ sidebar_label: Welcome
import { DISCORD_URL, REDDIT_URL, GITHUB_ISSUES_MAIN_URL, GITHUB_FEATURES_URL, YOUTUBE_URL } from '@site/src/constants.ts'
import Image from '@site/src/components/Image';
-# Kilo Code Documentation
+# Axon Code Documentation
-Kilo Code **accelerates** development with AI-driven code generation and task automation. This open source extension plugs directly into VS Code.
+Axon Code **accelerates** development with AI-driven code generation and task automation. This open source extension plugs directly into VS Code.
-## What Can Kilo Code Do?
+## What Can Axon Code Do?
- 🚀 **Generate Code** from natural language descriptions
- 🔧 **Refactor & Debug** existing code
@@ -20,26 +20,26 @@ Kilo Code **accelerates** development with AI-driven code generation and task au
## Quick Start
-1. [Install Kilo Code](/getting-started/installing)
-2. [Set up Kilo Code](/getting-started/setting-up)
+1. [Install Axon Code](/getting-started/installing)
+2. [Set up Axon Code](/getting-started/setting-up)
3. [Try Your First Task](/getting-started/your-first-task)
## Features
-
+
+
+
## Managing Seats Subscriptions
-In order to add Members to your Kilo Code Organization, you must have seat(s) available for them.
+In order to add Members to your Axon Code Organization, you must have seat(s) available for them.
You can purchase more seats at any time during your billing cycle and will pay a pro-rated amount for the number of days left in your billing cycle.
@@ -67,7 +67,7 @@ To fill empty seats or remove members ahead of seat deletion, see the [team mana
## Invoices
-Invoices for any payment on the Kilo Code platform, for seats or credits, will be available in the Invoices tab.
+Invoices for any payment on the Axon Code platform, for seats or credits, will be available in the Invoices tab.
### Service Suspension
diff --git a/apps/kilocode-docs/docs/seats/custom-modes.md b/apps/kilocode-docs/docs/seats/custom-modes.md
index 4b3bdb04b3..315a6bffc5 100644
--- a/apps/kilocode-docs/docs/seats/custom-modes.md
+++ b/apps/kilocode-docs/docs/seats/custom-modes.md
@@ -4,7 +4,7 @@ sidebar_label: Custom Modes
# Custom Modes
-Custom Modes let you create tailored versions of Kilo’s built-in [modes](/basic-usage/using-modes) for your organization. You can also adjust the settings for Kilo Code's original default modes. You can define a mode’s purpose, behavior, and tool access — helping Kilo adapt to your team’s unique workflows.
+Custom Modes let you create tailored versions of Kilo’s built-in [modes](/basic-usage/using-modes) for your organization. You can also adjust the settings for Axon Code's original default modes. You can define a mode’s purpose, behavior, and tool access — helping Kilo adapt to your team’s unique workflows.
For example, Admins and Owners can extend these by creating **Custom Modes** with specialized roles or personalities (e.g. “Documentation Writer” or “Security Reviewer”).
diff --git a/apps/kilocode-docs/docs/seats/dashboard.md b/apps/kilocode-docs/docs/seats/dashboard.md
index ffb422c75f..88cf256641 100644
--- a/apps/kilocode-docs/docs/seats/dashboard.md
+++ b/apps/kilocode-docs/docs/seats/dashboard.md
@@ -4,7 +4,7 @@ sidebar_label: Dashboard Overview
# Seats Dashboard
-The Kilo seats dashboard is the first screen that comes up when you visit [the Kilo Code web app](https://app.kilocode.ai). It provides complete visibility into your team's AI usage, costs, and management.
+The Kilo seats dashboard is the first screen that comes up when you visit [the Axon Code web app](https://app.matterai.so). It provides complete visibility into your team's AI usage, costs, and management.
diff --git a/apps/kilocode-docs/docs/seats/enterprise/SSO.md b/apps/kilocode-docs/docs/seats/enterprise/SSO.md
index 8b11e3d347..9b5c1e87e7 100644
--- a/apps/kilocode-docs/docs/seats/enterprise/SSO.md
+++ b/apps/kilocode-docs/docs/seats/enterprise/SSO.md
@@ -22,7 +22,7 @@ You’ll need:
## Step-by-Step Setup
-### 1. Open [Organization](https://app.kilocode.ai/organizations) Dashboard
+### 1. Open [Organization](https://app.matterai.so/organizations) Dashboard
Find the Single Sign-On (SSO) Configuration panel, and click "Set up SSO":
-## Kilo Code 的代码操作
+## Axon Code 的代码操作
-Kilo Code 提供以下代码操作：
+Axon Code 提供以下代码操作：
-* **添加到上下文：** 快速将选定的代码添加到与 Kilo 的聊天中，包括行号，以便 Kilo 确切知道代码来自何处。它在菜单中排在第一位，以便于访问。（更多详细信息见下文）。
-* **解释代码：** 要求 Kilo Code 解释选定的代码。
-* **修复代码：** 要求 Kilo Code 修复选定代码中的问题（在存在诊断时可用）。
-* **改进代码：** 要求 Kilo Code 建议改进选定的代码。
+- **添加到上下文：** 快速将选定的代码添加到与 Kilo 的聊天中，包括行号，以便 Kilo 确切知道代码来自何处。它在菜单中排在第一位，以便于访问。（更多详细信息见下文）。
+- **解释代码：** 要求 Axon Code 解释选定的代码。
+- **修复代码：** 要求 Axon Code 修复选定代码中的问题（在存在诊断时可用）。
+- **改进代码：** 要求 Axon Code 建议改进选定的代码。
### 添加到上下文深入探讨
-**添加到上下文**操作在代码操作菜单中排在第一位，因此您可以快速将代码片段添加到对话中。当您使用它时，Kilo Code 会将文件名和行号以及代码包含在内。
+**添加到上下文**操作在代码操作菜单中排在第一位，因此您可以快速将代码片段添加到对话中。当您使用它时，Axon Code 会将文件名和行号以及代码包含在内。
这有助于 Kilo 理解代码在项目中的确切上下文，从而使其能够提供更相关和准确的帮助。
@@ -40,51 +40,51 @@ Kilo Code 提供以下代码操作：
@myFile.js:15:25
```
-*（其中 `@myFile.js:15:25` 表示通过“添加到上下文”添加的代码）*
+_（其中 `@myFile.js:15:25` 表示通过“添加到上下文”添加的代码）_
这些操作中的每一个都可以在“新任务中”或“当前任务中”执行。
## 使用代码操作
-使用 Kilo Code 的代码操作有三种主要方式：
+使用 Axon Code 的代码操作有三种主要方式：
### 1. 从灯泡 (💡)
1. **选择代码：** 选择您要处理的代码。您可以选择单行、多行或整个代码块。
2. **查找灯泡：** 灯泡图标将出现在选定代码（或带有错误/警告的行）旁边的装订线中。
3. **单击灯泡：** 单击灯泡图标以打开代码操作菜单。
-4. **选择操作：** 从菜单中选择所需的 Kilo Code 操作。
-5. **审查和批准：** Kilo Code 将在聊天面板中提出解决方案。审查提议的更改并批准或拒绝它们。
+4. **选择操作：** 从菜单中选择所需的 Axon Code 操作。
+5. **审查和批准：** Axon Code 将在聊天面板中提出解决方案。审查提议的更改并批准或拒绝它们。
### 2. 从右键上下文菜单
1. **选择代码：** 选择您要处理的代码。
2. **右键单击：** 右键单击选定的代码以打开上下文菜单。
-3. **选择“Kilo Code”：** 从上下文菜单中选择“Kilo Code”选项。将出现一个子菜单，其中包含可用的 Kilo Code 操作。
+3. **选择“Axon Code”：** 从上下文菜单中选择“Axon Code”选项。将出现一个子菜单，其中包含可用的 Axon Code 操作。
4. **选择操作：** 从子菜单中选择所需的操作。
-5. **审查和批准：** Kilo Code 将在聊天面板中提出解决方案。审查提议的更改并批准或拒绝它们。
+5. **审查和批准：** Axon Code 将在聊天面板中提出解决方案。审查提议的更改并批准或拒绝它们。
### 3. 从命令面板
1. **选择代码：** 选择您要处理的代码。
2. **打开命令面板：** 按 `Ctrl+Shift+P` (Windows/Linux) 或 `Cmd+Shift+P` (macOS)。
-3. **键入命令：** 键入“Kilo Code”以过滤命令，然后选择相关的代码操作（例如，“Kilo Code: Explain Code”）。您也可以键入命令的开头，例如“Kilo Code: Explain”，然后从过滤列表中选择。
-4. **审查和批准：** Kilo Code 将在聊天面板中提出解决方案。审查提议的更改并批准或拒绝它们。
+3. **键入命令：** 键入“Axon Code”以过滤命令，然后选择相关的代码操作（例如，“Axon Code: Explain Code”）。您也可以键入命令的开头，例如“Axon Code: Explain”，然后从过滤列表中选择。
+4. **审查和批准：** Axon Code 将在聊天面板中提出解决方案。审查提议的更改并批准或拒绝它们。
## 代码操作和当前任务
每个代码操作都为您提供两个选项：
-* **在新任务中：** 选择此选项以开始与 Kilo 的对话，围绕此代码操作进行。
-* **在当前任务中：** 如果对话已经开始，此选项将代码操作添加为附加消息。
+- **在新任务中：** 选择此选项以开始与 Kilo 的对话，围绕此代码操作进行。
+- **在当前任务中：** 如果对话已经开始，此选项将代码操作添加为附加消息。
## 自定义代码操作提示
您可以通过修改“提示”选项卡中的“支持提示”来自定义每个代码操作使用的提示。这允许您微调提供给 AI 模型的指令，并根据您的特定需求调整响应。
-1. **打开提示选项卡：** 单击 Kilo Code 顶部菜单栏中的 
- *Kilo Code 用于创建和管理自定义模式的界面。*
+ 
-You can find this setting within the prompt settings by clicking the 
*The custom mode creation interface showing fields for name, slug, save location, role definition, available tools, and custom instructions.*
- * **Name:** Enter a display name for the mode
- * **Slug:** Enter a lowercase identifier (letters, numbers, and hyphens only)
- * **Save Location:** Choose Global (via `custom_modes.yaml`, available across all workspaces) or Project-specific (via `.kilocodemodes` file in project root)
- * **Role Definition:** Define Kilo's expertise and personality for this mode (appears at the start of the system prompt)
- * **Available Tools:** Select which tools this mode can use
- * **Custom Instructions:** (Optional) Add behavioral guidelines specific to this mode (appears at the end of the system prompt)
+ - **Name:** Enter a display name for the mode
+ - **Slug:** Enter a lowercase identifier (letters, numbers, and hyphens only)
+ - **Save Location:** Choose Global (via `custom_modes.yaml`, available across all workspaces) or Project-specific (via `.kilocodemodes` file in project root)
+ - **Role Definition:** Define Kilo's expertise and personality for this mode (appears at the start of the system prompt)
+ - **Available Tools:** Select which tools this mode can use
+ - **Custom Instructions:** (Optional) Add behavioral guidelines specific to this mode (appears at the end of the system prompt)
+
4. **Create Mode:** Click the "Create Mode" button to save your new mode
Note: File type restrictions can only be added through manual configuration.
@@ -166,65 +183,66 @@ You can configure custom modes by editing JSON files through the Prompts tab:
Both global and project-specific configurations can be edited through the Prompts tab:
-1. **Open Prompts Tab:** Click the 
+ 
-*Requesty API管理页面，带有"创建API密钥"按钮。立即复制您的密钥 - 它只会显示一次。*
+_Requesty API管理页面，带有"创建API密钥"按钮。立即复制您的密钥 - 它只会显示一次。_
#### 选项2：直接提供商
@@ -62,7 +63,7 @@ LLM路由器让您可以通过一个API密钥访问多个AI模型，简化了成
-*Anthropic控制台API密钥部分，带有"创建密钥"按钮。命名您的密钥，设置过期时间，并立即复制它。*
+_Anthropic控制台API密钥部分，带有"创建密钥"按钮。命名您的密钥，设置过期时间，并立即复制它。_
##### OpenAI
@@ -73,16 +74,16 @@ LLM路由器让您可以通过一个API密钥访问多个AI模型，简化了成
-*OpenAI平台，带有"创建新密钥"按钮。命名您的密钥并在创建后立即复制它。*
+_OpenAI平台，带有"创建新密钥"按钮。命名您的密钥并在创建后立即复制它。_
### 在VS Code中配置Kilo Code
获取API密钥后：
-1. 点击VS Code侧边栏中的Kilo Code图标(
@@ -18,7 +18,6 @@ Kilo Code 支持通过 Ollama 在本地运行模型。这提供了隐私保护
本地 LLM 通常速度也不是很快。
使用简单的提示、保持对话简短和禁用 MCP 工具可以提高速度。
-
## 硬件要求
您将需要大量的 RAM（32GB 或更多）和强大的 CPU（例如 Ryzen 9000 系列）才能运行下面列出的模型。
@@ -26,7 +25,6 @@ GPU 可以更快地运行 LLM，但需要大量的 VRAM（24GB 或更多），
较小的模型可以在更普通的 GPU 上运行，但效果不佳。
具有足够统一内存的 MacBook 可以使用 GPU 加速，但在我们的测试中，其性能不如高端桌面 CPU。
-
## 选择模型
Ollama 支持许多不同的模型。
@@ -34,14 +32,13 @@ Ollama 支持许多不同的模型。
选择适合您的用例、在您的硬件配置上运行并达到所需速度的模型需要一些试错。
以下规则和启发式方法可用于查找模型：
-* 必须至少有 32k 的上下文窗口（这是 Kilo Code 的要求）。
-* 列出为支持工具。
-* 参数数量在 7b 到 24b 范围内。
-* 优先选择流行模型。
-* 优先选择较新的模型。
-
+- 必须至少有 32k 的上下文窗口（这是 Axon Code 的要求）。
+- 列出为支持工具。
+- 参数数量在 7b 到 24b 范围内。
+- 优先选择流行模型。
+- 优先选择较新的模型。
-### Kilo Code 推荐
+### Axon Code 推荐
我们使用以下提示测试了一些模型：
@@ -51,12 +48,12 @@ Ollama 支持许多不同的模型。
如果模型在几次尝试内产生了一个可用的结果，则认为它通过。我们发现可以正常工作的模型是：
-| 模型名称 | 完成时间 |
-| --- | --- |
+| 模型名称 | 完成时间 |
+| ---------------- | ---------- |
| qwen2.5-coder:7b | 1x（基线） |
-| devstral:24b | 2x |
-| gemma3:12b | 4x |
-| qwen3-8b | 12x |
+| devstral:24b | 2x |
+| gemma3:12b | 4x |
+| qwen3-8b | 12x |
我们的建议是，如果您的硬件能够处理，请使用 **devstral:24b**，因为它比 qwen2.5-coder:7b 犯的错误更少。
qwen2.5-coder:7b 值得考虑，因为它速度快，如果您能忍受它的错误。
@@ -68,45 +65,44 @@ devstral:24b 产生的结果如下：
```html
-
-
-
-