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.
Make agent mode aware of your open codebase
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:
- File exploration tools: The agent can read files, search for patterns, and understand project structure
- Code search: Use search to find relevant code snippets
- Git integration: Access commit history and understand code evolution
Create rules to help the agent understand your codebase
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
Place rules files at different levels of your project hierarchy to scope when
they trigger
Make agent mode aware of other codebases
Sometimes you need agent mode to understand code beyond your current project.
Public codebases
For open-source projects and public repositories, you have several options:
Rules with hyperlinks
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.
GitHub and GitLab CLIs
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
DeepWiki MCP lets agent mode explore any public GitHub repository.
Once configured, agent mode can explore repositories like:
- “Explore the React repository structure”
- “Find how authentication is implemented in NextAuth.js”
Internal codebases
For private and internal repositories, you need additional setup:
Custom MCP servers
Create an MCP server that has access to your internal repositories.
Custom code RAG
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.
Make agent mode aware of relevant documentation
Documentation provides crucial context for agent mode to understand APIs, frameworks, and best practices.
Public documentation
Rules with documentation links
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
Context7 MCP enables agent mode to search and retrieve information from public documentation:
Agent mode can then answer questions like:
- “How do I use React hooks?”
- “What’s the syntax for Tailwind CSS animations?”
Internal documentation
For private documentation and wikis:
Rules with internal links
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.
Custom MCP servers for docs
Create an MCP server that accesses your internal documentation.
Migrating from deprecated context providers
If you were previously using the @Codebase or @Docs context providers, here’s how to migrate to the new approach:
Migrating from @Codebase
The @Codebase context provider has been deprecated. Instead:
- Use built-in tools: Agent mode can now use file exploration and search tools to understand your codebase
- Add rules: Create
.continue/rules files to provide context about your project structure
- Use MCP servers: For external codebases, use DeepWiki MCP or custom MCP servers
Migrating from @Docs
The @Docs context provider has been deprecated. Instead:
- Use Context7 MCP: For public documentation, Context7 MCP provides similar functionality
- Add documentation links in rules: Create rules that reference documentation URLs
- Use custom MCP servers: For internal documentation, create an MCP server with access to your docs
The new approach provides better integration with Continue’s Agent mode features and more intelligent context selection.
Next steps
