Context Providers

Built-in Context Providers
@File Context Provider – Reference Files in Your Workspace
@Code Context Provider – Reference Functions and Classes
@Git Diff Context Provider – Reference Branch Changes
@Current File Context Provider – Reference the Active File
@Terminal Context Provider – Reference Last Terminal Command and Output
@Docs Context Provider – Reference Documentation Site Content
@Open Context Provider – Reference All Open Files or Pinned Files
@Web Context Provider – Reference Relevant Web Pages
@Codebase Context Provider – Reference Relevant Codebase Snippets
@Folder Context Provider – Reference Code from a Specific Folder
@Search Context Provider – Reference Code Search Results
@Url Context Provider – Reference Content from a URL
@Clipboard Context Provider – Reference Clipboard Items
@Tree Context Provider – Reference Workspace File Structure
@Problems Context Provider – Reference Problems in the Current File
@Debugger Context Provider – Reference Debugger Local Variables
@Repository Map Context Provider – Reference Codebase Outline and Signatures
@Operating System Context Provider – Reference System Architecture and Platform
Using the Model Context Protocol (MCP) in Continue
How to Request a New Context Provider in Continue

As an example, say you are working on solving a new GitHub Issue. You type ‘@Issue’ and select the one you are working on. Continue can now see the issue title and contents. You also know that the issue is related to the files ‘readme.md’ and ‘helloNested.py’, so you type ‘@readme’ and ‘@hello’ to find and select them. Now these 3 “Context Items” are displayed inline with the rest of your input.

Customize