docs/guides/codebase-documentation-awareness.mdx
Agent mode works best when it understands the context of your project. This guide shows you how to give agent mode access to codebases and documentation, making it more helpful and accurate.
When agent mode understands your current codebase, it can provide more relevant suggestions and answers.
Agent mode can use built-in tools to navigate and understand your code:
Rules guide agent mode's behavior and understanding. Place markdown files in .continue/rules in your project to provide context:
# Project Architecture
This is a React application with:
- Components in `/src/components`
- API routes in `/src/api`
- State management using Redux in `/src/store`
## Coding Standards
- Use TypeScript for all new files
- Follow the existing naming conventions
- Write tests for all new features
Learn more about rules configuration.
Sometimes you need agent mode to understand code beyond your current project.
For open-source projects and public repositories, you have several options:
Create rules that point to external codebases:
# External Dependencies
Our authentication system is based on:
- [Auth.js documentation](https://authjs.dev/)
- [Example implementation](https://github.com/nextauthjs/next-auth-example)
When implementing auth features, reference these patterns.
Enable gh or glab CLI access for agent mode to interact with repositories.
Add rules to guide CLI usage:
# Repository Access
You can use the `gh` CLI to:
- Search for issues: `gh issue list --repo owner/repo`
- View pull requests: `gh pr list --repo owner/repo`
- Clone repositories: `gh repo clone owner/repo`
DeepWiki MCP lets agent mode explore any public GitHub repository.
Once configured, agent mode can explore repositories like:
For private and internal repositories, you need additional setup:
Create an MCP server that has access to your internal repositories.
For faster retrieval and lower costs with very large internal codebases, consider implementing a custom code RAG system. This is an advanced approach that requires more setup but can provide performance benefits at scale.
Documentation provides crucial context for agent mode to understand APIs, frameworks, and best practices.
Guide agent mode to relevant documentation:
# Documentation Resources
For framework-specific questions, refer to:
- React: https://react.dev/reference/react
- Next.js: https://nextjs.org/docs
- Tailwind CSS: https://tailwindcss.com/docs
Always cite documentation when explaining concepts.
Context7 MCP enables agent mode to search and retrieve information from public documentation:
Agent mode can then answer questions like:
For private documentation and wikis:
Create rules that reference internal resources:
# Internal Documentation
Our team documentation is available at:
- API Documentation: https://internal.docs/api
- Architecture Guide: https://internal.docs/architecture
- Deployment Process: https://internal.docs/deployment
Always follow our internal standards when suggesting code.
Create an MCP server that accesses your internal documentation.
If you were previously using the @Codebase or @Docs context providers, here's how to migrate to the new approach:
The @Codebase context provider has been deprecated. Instead:
.continue/rules files to provide context about your project structureThe @Docs context provider has been deprecated. Instead:
The new approach provides better integration with Continue's Agent mode features and more intelligent context selection.