In this categoryVS Code Setup ยท 25
- How to Set Up GitHub Copilot in VS CodeStart
- How to Use Copilot Chat and Inline Chat in VS Code
- How to Install and Manage Extensions in VS Code
- How to Install the Continue Extension in VS Code
- How to Install Cline, the Autonomous Coding Agent, in VS Code
- How to Configure Continue with an API Model
- How to Set Up an AI Assistant in VS Code
- How to Run Continue with a Local Model Using Ollama
- How to Run Copilot, Continue, and Cline Together Without Conflicts
- How to Add an MCP Server to Cline
- How to Fix AI Suggestions Not Appearing in VS Code
- How to Install and Trust an AI Extension in VS Code
- How to Install a VS Code Extension from the Command Line
- How to Create a launch.json to Debug a Node.js App in VS Code
- How to Initialize a Git Repository in VS Code
- How to Stage, Commit, and Push Changes from VS Code
- How to Debug a Browser App in VS Code with the Built-in Chrome Debugger
- How to Resolve Git Merge Conflicts in VS Code
- How to Run Build and Dev Commands with tasks.json in VS Code
- How to Add Environment Variables to a VS Code Debug Configuration
How to Run Copilot, Continue, and Cline Together Without Conflicts
Use multiple AI assistants in one VS Code window by stopping their autocomplete features from fighting each other.
It is common to want Copilot for fast inline completions, Continue for flexible chat with your own models, and Cline for agent tasks. The catch is that more than one tool offering inline suggestions at once produces flickering ghost text and confusing accept behavior. This guide assigns one job to each so they cooperate.
What you need
- Copilot, Continue, and Cline all installed
- Each one signed in or connected to a model
- About 6 minutes
Step 1: Decide who owns autocomplete
Only one extension should provide inline completions. Pick the one you prefer for that job; many people keep Copilot for completions because it is fast. Then disable autocomplete in the others so they stop competing for the same ghost text slot.
Step 2: Turn off Continue autocomplete
If Copilot owns completions, remove the autocomplete role from your Continue config, or remove the autocomplete model entirely. Continue still handles chat and edit, which do not conflict with Copilot.
models:
- name: Claude Sonnet
provider: anthropic
model: claude-sonnet-4-5
apiKey: sk-ant-your-key
roles:
- chat
- edit
# autocomplete removed so Copilot owns inline suggestionsStep 3: Keep Cline to the agent panel
Cline does not provide inline completions at all, so it never fights Copilot. Just keep using its panel for multi-step tasks. The one thing to watch is approving Cline edits while Copilot is suggesting in the same file, so finish one before the other.
Step 4: Verify there is no flicker
Open a code file and type. You should see one clean stream of grey suggestions, not flickering. Open the Continue and Cline panels and confirm they work without affecting the inline text. If you still see double suggestions, check that no second extension has autocomplete enabled.
Result
Copilot handles inline completions, Continue handles chat and edits with your chosen model, and Cline handles agent tasks. Each tool stays in its lane and the editor feels smooth instead of cluttered.
Watch related tutorials
12:47
18:33
15:21
14:27
15:22
1:02:14New guides in your inbox
Fresh step-by-step how-to guides as we publish them. One email a week, no more.