[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"pack-detail-cline-roo-vscode-setup-fr":3,"seo:pack:cline-roo-vscode-setup:fr":94},{"code":4,"message":5,"data":6},200,"操作成功",{"pack":7},{"slug":8,"icon":9,"tone":10,"status":11,"status_label":12,"title":13,"description":14,"items":15,"install_cmd":93},"cline-roo-vscode-setup","🧩","#3B82F6","new","Nouveau · cette semaine","Cline + Roo Code — Configuration Agentique pour VS Code","Choisir entre les deux extensions agentiques phares de VS Code et les configurer correctement. Cline vs Roo Code, règles projet, modes personnalisés et les MCP qui s'y greffent bien.",[16,28,37,47,54,62,72,79,86],{"id":17,"uuid":18,"slug":19,"title":20,"description":21,"author_name":22,"view_count":23,"vote_count":24,"lang_type":25,"type":26,"type_label":27},212,"fe3f1223-13da-42dc-8493-28b6c1a92ca0","cline-autonomous-ai-coding-agent-vs-code-fe3f1223","Cline — Autonomous AI Coding Agent for VS Code","Autonomous coding agent in VS Code. Creates\u002Fedits files, runs commands, browses the web, and uses MCP tools — with human approval at every step. 60K+ stars.","Cline",241,0,"en","script","Script",{"id":29,"uuid":30,"slug":31,"title":32,"description":33,"author_name":22,"view_count":34,"vote_count":24,"lang_type":25,"type":35,"type_label":36},2776,"3136dbec-c3dd-49db-acb4-f52bc7acda00","clinerules-project-behavior-file-for-cline-ai-agent",".clinerules — Project Behavior File for Cline AI Agent",".clinerules is Cline's per-project rules file, read every task. Steers code style, libraries, conventions without retyping context. Roo-compatible.",38,"prompt","Prompt",{"id":38,"uuid":39,"slug":40,"title":41,"description":42,"author_name":43,"view_count":44,"vote_count":24,"lang_type":25,"type":45,"type_label":46},716,"baddacd0-3bbf-4076-96d5-f6cb2d54d145","roo-code-ai-coding-agent-custom-modes-baddacd0","Roo Code — AI Coding Agent with Custom Modes","Fork of Cline with custom agent modes, boomerang orchestration, and multi-model routing. Create specialized AI agents for coding, review, and architecture tasks.","Roo Code",257,"skill","Skill",{"id":48,"uuid":49,"slug":50,"title":51,"description":52,"author_name":43,"view_count":53,"vote_count":24,"lang_type":25,"type":45,"type_label":46},2777,"209beeb5-45d7-49e2-af7f-8f7328d296d5","roo-code-modes-architect-code-ask-debug-agents","Roo Code Modes — Architect, Code, Ask & Debug Agents","Roo Code's Modes feature splits the agent into 4 specialists with their own prompts and tool whitelists. Boomerang task delegation between modes built in.",58,{"id":55,"uuid":56,"slug":57,"title":58,"description":59,"author_name":60,"view_count":61,"vote_count":24,"lang_type":25,"type":35,"type_label":36},841,"b3a901fe-8380-4bfc-a631-c57f8d5b51f0","ai-coding-agent-comparison-2026-complete-guide-b3a901fe","AI Coding Agent Comparison 2026 — Complete Guide","Comprehensive comparison of all AI coding agents in 2026. Covers Claude Code, Cursor, Codex, Gemini CLI, Cline, Roo Code, Windsurf, and Aider with feature matrices and recommendations.","Agent Toolkit",226,{"id":63,"uuid":64,"slug":65,"title":66,"description":67,"author_name":68,"view_count":69,"vote_count":24,"lang_type":25,"type":70,"type_label":71},3062,"cd5e75f3-8aa3-41fc-9a7e-be6394ad67af","awesome-mcp-servers-mcp-directory-index","awesome-mcp-servers — MCP Directory & Index","awesome-mcp-servers is a curated index of MCP servers, clients, and tutorials. Use it to pick a server, then add it to your MCP config and verify.","MCP Hub",70,"mcp","MCP",{"id":73,"uuid":74,"slug":75,"title":76,"description":77,"author_name":68,"view_count":78,"vote_count":24,"lang_type":25,"type":70,"type_label":71},3059,"7f3a756c-8ec2-4b20-8ad6-99bfc5155af3","playwright-mcp-browser-automation-server","Playwright MCP — Browser Automation Server","Playwright MCP is an MCP server for browser automation via Playwright snapshots. Add via npx in Claude Code\u002FCodex to run deterministic actions.",148,{"id":80,"uuid":81,"slug":82,"title":83,"description":84,"author_name":68,"view_count":85,"vote_count":24,"lang_type":25,"type":70,"type_label":71},42,"8a28360d-6eef-449d-9857-d8b388a05f34","mcp-reference-servers-official-collection-8a28360d","MCP Reference Servers — Official Collection","Official MCP reference server implementations by Anthropic: filesystem, git, memory, fetch, sequential thinking, and more. The starting point for MCP development.",127,{"id":87,"uuid":88,"slug":89,"title":90,"description":91,"author_name":68,"view_count":92,"vote_count":24,"lang_type":25,"type":70,"type_label":71},803,"85eacf96-3b2b-43f5-ad6f-fd4413ad0b69","git-mcp-version-control-server-ai-agents-85eacf96","Git MCP — Version Control Server for AI Agents","MCP server that gives AI agents full Git capabilities. Git MCP enables Claude Code and Cursor to manage repositories, branches, commits, diffs, and history via tool calls.",180,"tokrepo install pack\u002Fcline-roo-vscode-setup",{"pageType":95,"pageKey":8,"locale":25,"title":96,"metaDescription":97,"h1":98,"tldr":99,"bodyMarkdown":100,"faq":101,"schema":117,"internalLinks":122,"citations":135,"wordCount":148,"generatedAt":149},"pack","Cline + Roo Code — Agentic VS Code Setup (Without Switching IDEs)","You like VS Code and want an agentic coding assistant in it. Cline and Roo Code are the two real options. This pack picks between them, wires in .clinerules \u002F custom modes, and adds the MCP servers (Playwright, Git, awesome-mcp-servers, official reference) that actually pay rent.","Cline + Roo Code — Agentic VS Code Setup","Two extensions, one comparison guide, four MCP servers, and the rule files that steer both. Start with Cline if you want stability and the larger community; switch (or run both) when you need Roo's per-mode prompts and tool whitelists. Wire MCPs the same way for either — they share the protocol.","## What's in this pack\n\nYou already use VS Code. You don't want to switch to Cursor, Windsurf, or a terminal-only CLI. You just want the agentic coding loop — read the repo, edit files, run commands, browse docs — to happen inside VS Code with human-in-the-loop approval.\n\nThere are exactly two extensions that do this seriously in 2026: **Cline** (the original, 60K+ stars) and **Roo Code** (a Cline fork that added per-mode specialists and boomerang orchestration, 22K+ stars). Everything else is either an inline-completion tool (Copilot, Continue's chat) or an external CLI pretending to be an extension.\n\nThis pack covers: how to pick between them, the rule files that steer their behavior, and the four MCP servers that pair well with **either**. Same MCP wiring works for both, so you can switch (or run both) without re-plumbing.\n\nWho this is for: a VS Code user who wants real agentic coding (multi-step, tool-using, file-creating) without leaving the editor — and wants to make the choice once instead of trying every extension on the marketplace.\n\n## Install in this order\n\n1. **Cline — Autonomous AI Coding Agent for VS Code** — Install this first as your default. Search \"Cline\" in the VS Code marketplace, click Install, paste an Anthropic or OpenAI API key. 60K+ stars, the largest user base, the most stable. Every action requires your approval — Cline never edits or runs without you clicking \"Approve.\"\n2. **Cline — VS Code Autonomous AI Coding Extension** — The MCP-config variant of the same extension. Use this entry as your reference for connecting MCP servers to Cline's settings JSON (slightly different syntax from Roo's, which we'll cover below).\n3. **.clinerules — Project Behavior File for Cline AI Agent** — Drop a `.clinerules` file in your repo root before you start any real work. It's the project-memory equivalent of CLAUDE.md: tech stack, conventions, hard NOs. Cline reads it on every task. Crucially, **Roo Code reads the same file** — so when you try Roo later, your rules carry over for free.\n4. **Roo Code — AI Coding Team Inside VS Code** — Install Roo as your second extension (yes, both can live in VS Code at once — they don't conflict). Roo is a Cline fork with the same core capabilities plus per-mode specialists and boomerang task orchestration. You'll want it eventually; install now so you can A\u002FB test.\n5. **Roo Code — AI Coding Agent with Custom Modes** — Same extension, different reference entry — covers the custom-modes UX in detail. Modes are Roo's headline feature: you define agent specialists with their own system prompts and tool whitelists.\n6. **Roo Code Modes — Architect, Code, Ask & Debug Agents** — The four built-in Roo modes that ship out of the box. Architect plans, Code writes, Ask reads, Debug investigates. Use this entry to learn the boomerang pattern (Architect kicks off a multi-step task, hands subtasks to Code, gets results back). Cline has no equivalent — this is Roo's main differentiator.\n7. **AI Coding Agent Comparison 2026 — Complete Guide** — The decision document. Covers Claude Code, Cursor, Codex, Gemini CLI, Cline, Roo Code, Windsurf, and Aider with feature matrices. Read it once after step 1 to confirm Cline is the right starting point, then again after step 6 to decide whether Roo earns its second slot.\n8. **MCP Reference Servers — Official Collection** — The Anthropic-maintained baseline: filesystem, git, memory, fetch, sequential thinking. Wire these into Cline first; they're battle-tested and zero-config. Once these work, you trust the MCP pipe and can add more aggressive ones with confidence.\n9. **Playwright MCP — Browser Automation Server** — The single highest-leverage MCP for both extensions. Lets the agent take browser snapshots, click links, fill forms — so it can debug your frontend, scrape docs, or QA a deployed page without you screen-sharing. Add it second, after the official reference servers prove the pipe works.\n10. **Git MCP — Version Control Server for AI Agents** — Cline and Roo can already run `git` via the terminal, but Git MCP gives them **structured** access — branch lists, diff summaries, log queries as typed responses instead of shell output to parse. Worth it for any non-trivial repo.\n11. **awesome-mcp-servers — MCP Directory & Index** — Your monthly browse target. Once you have 3-4 MCPs wired and working, this curated index is where you discover the next one. Don't install from here on day one; come back when you've felt the limits of the four above.\n\n## How they fit together\n\n```\n         VS Code (your editor, unchanged)\n              │\n   ┌──────────┴──────────┐\n   │                     │\nCline (#1, #2)       Roo Code (#4, #5)\n  default            second opinion\n   │                     │\n   │   reads same file:  │\n   └──── .clinerules (#3) ────┘\n                │\n         (project memory)\n                │\n   ┌────────────┴────────────┐\n   │       Roo only:         │\n   │  Modes (#6) — Architect │\n   │  \u002F Code \u002F Ask \u002F Debug   │\n   │  + boomerang routing    │\n   └─────────────────────────┘\n                │\n         MCP protocol layer\n      (same wire for both extensions)\n                │\n   ┌────────┬───┴────┬──────────┐\n   │        │        │          │\nReference  Playwright Git MCP  awesome-mcp\nServers    MCP (#9)  (#10)    catalog (#11)\n(#8)\nfilesystem browser   structured monthly\ngit\u002Fmemory snapshots git ops    browse\nfetch\u002Fseq  click\u002F    diff\u002Flog\nthinking   fill\n\n   ↑                                ↑\n   start here                       come back monthly\n   (zero-config, official)          (after you've felt limits)\n\n   AI Coding Agent Comparison 2026 (#7)\n      └── decision document, read twice:\n            • after #1 to confirm Cline\n            • after #6 to decide on Roo\n```\n\nThe non-obvious win: **.clinerules is read by both extensions**, so you can switch between Cline and Roo without retyping conventions. Same with MCPs — wire them once at the system level, both extensions see the same servers.\n\n## Tradeoffs you'll hit (Cline vs Roo Code)\n\nThis is the section the pack exists for. Read it before you pick.\n\n- **Stability vs flexibility** — Cline is the upstream, more conservative, larger user base, fewer surprise breakages on extension updates. Roo ships features faster (custom modes, boomerang, cloud agents) but also breaks more often. **If you can't afford a Tuesday-morning \"my agent stopped working\" incident, default to Cline.** If you tinker for fun, default to Roo.\n- **One mode vs many** — Cline has one agent personality with one system prompt. Roo has Architect \u002F Code \u002F Ask \u002F Debug (and you can define unlimited custom modes), each with its own prompt and tool whitelist. **One-personality is enough for 80% of tasks.** Custom modes earn their complexity when you have a real multi-step workflow — e.g., \"Architect plans the migration, Code executes each step, Debug runs after every failure.\" Don't add modes preemptively; you'll just maintain more YAML.\n- **Boomerang vs linear** — Roo's boomerang orchestration lets one mode kick off a task in another mode, get the result back, and continue. Cline runs the whole task in one context. **Boomerang is genuinely useful for >30-minute tasks** (context stays clean, sub-agent failures don't poison the parent). For 5-minute edits, it's overhead.\n- **Cost per task** — Both burn the same API tokens for the model itself. Roo's modes can drive cost **up** (multi-mode tasks make more LLM calls) or **down** (cheaper model on the Ask\u002FDebug modes, expensive one only on Architect). Configure mode-level models early or you'll bleed money.\n- **Ecosystem maturity** — Cline has more third-party MCP guides, more YouTube tutorials, more Reddit threads. Roo's docs are sharper but the community is smaller. **Start with Cline if you Google your way out of problems; start with Roo if you prefer reading source.**\n- **MCP compatibility** — Identical. Both speak the protocol. Every MCP in this pack works with both. You wire the server once at the system level; both extensions see it. This is why running both extensions in parallel is cheap — there's no duplicate plumbing.\n- **Approval fatigue** — Both ask for approval on every action by default. Cline's approval UI is faster (fewer clicks). Roo's is more granular (you can pre-approve patterns per mode). After a week, you'll want pre-approvals for `git status`, `ls`, `cat`; do this carefully and only for read-only commands.\n- **The honest summary** — Cline is the iPhone (stable, mainstream, what you recommend to your boss). Roo is the Android (more customizable, faster-moving, what you recommend to the engineer who likes config files). Run Cline as your default; install Roo and try modes on a side project for two weeks; keep both if you can justify it, drop one if you can't.\n\n## Common pitfalls\n\n- **Installing Roo without trying Cline first** — You'll have no baseline for what \"normal\" feels like. The modes \u002F boomerang features are real, but you can't tell whether you need them until you've hit Cline's limits. Two weeks on Cline, then evaluate.\n- **Wiring MCPs into one extension and forgetting the other** — Cline's settings live in its extension config; Roo's live in its. Wire each MCP twice (or use the system-level config at `~\u002F.config\u002Fmcp\u002F` if your OS supports it). If a server seems to work in Cline but not Roo, you forgot to add it on the Roo side.\n- **`.clinerules` over-engineering** — Same trap as CLAUDE.md: people paste their architecture doc and burn 4K tokens every task. Keep it under 100 lines: stack, commands, conventions, hard NOs. Both extensions read it on every turn.\n- **Approve-all clicking** — Both extensions show \"Auto-approve\" toggles. Don't enable them globally on day one. Whitelist specific read-only commands (`git status`, `ls`, `pwd`) and stay manual on writes \u002F deletes \u002F network calls until you trust the model on your codebase.\n- **Skipping the comparison guide (#7)** — It's the boring document but it's the one that prevents the \"why did I install all four of these?\" moment. Read it once, decide which extensions earn permanent slots, uninstall the rest.\n- **Treating Playwright MCP as optional** — It's the MCP that makes the agent *useful* for frontend work. Without it, Cline \u002F Roo can edit your React component but can't tell whether the page renders. With it, the loop closes.",[102,105,108,111,114],{"q":103,"a":104},"Cline or Roo Code — which one should I install first?","Cline. It's the upstream, 60K+ stars, more stable, larger community to Google your way out of problems. Install Cline, use it for two weeks on real work, then install Roo Code as a second extension to evaluate modes and boomerang orchestration. They don't conflict in VS Code — both can be enabled at the same time. After a month, decide whether Roo earns its second slot or whether Cline alone is enough. For 80% of people, Cline alone is enough.",{"q":106,"a":107},"Do Cline and Roo Code share configuration, or do I configure everything twice?","Mixed. The good news: `.clinerules` is read by both — Roo deliberately stayed compatible. So your project conventions carry across for free. The bad news: MCP server wiring lives inside each extension's settings, so you connect each MCP to Cline once and Roo once. There's no system-level MCP registry yet that both extensions share. Budget 5 extra minutes per MCP if you want both extensions to see it.",{"q":109,"a":110},"I already use Cursor \u002F Windsurf \u002F Claude Code. Why would I switch back to VS Code?","You probably wouldn't *switch back* — but you might run VS Code + Cline alongside your other tool. VS Code's extension ecosystem (debuggers, language servers, dev containers, remote SSH) is still richer than any AI-native editor. If you do data engineering, you probably can't leave VS Code anyway — Jupyter \u002F dbt \u002F Databricks extensions live there. Cline + Roo let you keep that ecosystem and still get agentic coding.",{"q":112,"a":113},"What about Continue? Isn't it also an open-source VS Code AI extension?","Continue is great for inline completion and chat — that's its design center. Cline and Roo are designed for autonomous multi-step tasks: edit a file, run a test, fix the error, re-run. Different category. Use Continue for autocomplete-style help; use Cline \u002F Roo when you want the agent to actually drive a task to completion. Many people run all three (Continue for completion, Cline for tasks, Roo for experiments).",{"q":115,"a":116},"Do I need GPT-4 \u002F Claude Opus API access, or can I use local models?","Both extensions support local models via Ollama, LM Studio, or any OpenAI-compatible endpoint. Quality drops sharply below 70B-class models — agentic loops need strong instruction-following and self-correction. If you must run local, use Qwen3-Coder, DeepSeek-Coder, or Llama 3.1 70B at minimum. For real production use, Claude Sonnet \u002F GPT-4o \u002F Gemini 2.5 Pro are the floor — the tool-use accuracy gap is too large to ignore.",{"@context":118,"@type":119,"name":98,"description":120,"numberOfItems":121,"inLanguage":25},"https:\u002F\u002Fschema.org","ItemList","Nine assets that wire Cline and Roo Code into VS Code with shared project rules and MCP servers, including the comparison guide that picks between them.",9,[123,127,131],{"url":124,"anchor":125,"reason":126},"\u002Fen\u002Ftopics","Browse other topic packs","Adjacent packs cover AI Coding Agents Compared, MCP Server Stack, and Claude Code Onboarding",{"url":128,"anchor":129,"reason":130},"\u002Fen\u002Fai-tools-for\u002Fcoding","AI tools for coding","See how Cline and Roo Code compare with Cursor, Windsurf, Claude Code, and Codex",{"url":132,"anchor":133,"reason":134},"\u002Fen\u002Ffeatured","Featured assets on TokRepo","These extensions and MCPs live alongside the broader curated catalog",[136,140,144],{"claim":137,"source_name":138,"source_url":139},"Cline is an autonomous coding agent for VS Code with 60K+ GitHub stars","cline\u002Fcline on GitHub","https:\u002F\u002Fgithub.com\u002Fcline\u002Fcline",{"claim":141,"source_name":142,"source_url":143},"Roo Code is a Cline fork adding custom modes and boomerang orchestration","Roo-Code on GitHub","https:\u002F\u002Fgithub.com\u002FRooVetGit\u002FRoo-Code",{"claim":145,"source_name":146,"source_url":147},"Model Context Protocol is the open standard both extensions use for tool servers","Model Context Protocol specification","https:\u002F\u002Fmodelcontextprotocol.io",1650,"2026-05-22T00:00:00Z"]