- Type
@in the chat input and select from the picker - Click the + button in the bottom-left corner to browse files, images, or mentions
Quick reference
| What you want | Syntax | Example |
|---|---|---|
| File contents | @/path/to/file | @/src/index.ts |
| Folder contents | @/path/to/folder/ | @/src/components/ |
| Workspace errors | @problems | @problems |
| Terminal output | @terminal | @terminal |
| Uncommitted changes | @git-changes | @git-changes |
| Specific commit | @<commit-hash> | @a1b2c3d |
| Web page | @<url> | @https://react.dev/learn |
File mentions
Reference any file with@/path/to/file. Cline sees the complete file contents, including imports, related functions, and surrounding context.
Folder mentions
Reference an entire directory with@/path/to/folder/ (note the trailing slash). Cline sees the folder structure and all file contents within it.
In multi-root workspaces, prefix paths with the workspace name:
@workspace-name:/path/to/fileProblem mentions
Use@problems to share all errors and warnings from your workspace’s Problems panel directly with Cline.
Terminal mentions
Use@terminal to share recent terminal output. Useful for debugging build errors, test failures, or unexpected command output.
Git mentions
Reference uncommitted changes with@git-changes:
@<commit-hash> (7–40 character hex string):
URL mentions
Reference web content with a full URL prefixed by@. Cline fetches the page and reads it as part of the conversation.
Combining mentions
You can combine multiple @ mentions in a single message for comprehensive context:Drag and drop
Drag files directly into the chat input to add them to your conversation.In VS Code, hold Shift while dragging files into the chat input.
Images require a multimodal model. Check the model selector to confirm your current model supports image inputs.
Reviewing file changes
When Cline edits a file, it presents a diff view showing exactly what changed. You can:- Accept the change to apply it
- Reject the change to discard it
- Edit the diff directly to adjust the proposed change before accepting
- Provide feedback in chat to ask Cline to try a different approach
Context menu commands
Right-click on selected code to access Cline without typing. This is the fastest way to get help with specific code because it automatically includes the selected text and file location as context.Code editor commands
Add to Cline
Ask questions about code, get suggestions, or start a conversation with specific code as context.
Fix with Cline
Quick fixes for errors, bugs, or issues in the selected code. Also appears in the lightbulb Quick Fix menu when your cursor is on an error.
Explain with Cline
Understand unfamiliar code, complex logic, or code you’re reviewing.
Improve with Cline
Get refactoring suggestions, performance improvements, or cleaner implementations.
Terminal commands
Right-click in the terminal and select Add to Cline to get help with:- Build errors and failed commands
- Test failures and stack traces
- Configuration issues
- Any terminal output you need help interpreting