Skip to main content
hc
Submit
toolsSource-backedReview first Safety · Privacy ·
Roo Code logo

Roo Code

Open-source AI coding agent for VS Code with modes for planning, editing, debugging, and workflow automation.

by Roo Code·added 2026-04-27·
CLI
HarnessCLI
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/tools/roo-code
Source URLs
https://docs.roocode.com, https://github.com/RooCodeInc/Roo-Code, https://roocode.com
Brand
Roo Code
Brand domain
roocode.com
Brand asset source
brandfetch
Author
Roo Code
Claim status
unclaimed
Last verified
2026-04-27

Schema details

Install type
copy
Troubleshooting
No
Source repository stats
Scope
Source repo
Tool listing metadata
Pricing
open-source
Disclosure
editorial
Application category
DeveloperApplication
Operating system
macOS, Windows, Linux
Full copyable content
## Editorial notes

Roo Code is a good fit when users want mode-specific agent behavior for planning, code edits, debugging, and routine project work.

## Disclosure

Editorial listing. No paid placement or affiliate link is used.

About this resource

Editorial notes

Roo Code is a good fit when users want mode-specific agent behavior for planning, code edits, debugging, and routine project work.

Disclosure

Editorial listing. No paid placement or affiliate link is used.

#vs-code#coding-agent

Source citations

Add this badge to your README

Show that Roo Code is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/tools/roo-code.svg)](https://heyclau.de/entry/tools/roo-code)

How it compares

Roo Code side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field
Roo Code logoRoo Code

Open-source AI coding agent for VS Code with modes for planning, editing, debugging, and workflow automation.

Open dossier
Cline logoCline

Open-source autonomous coding agent extension for planning, editing, running commands, and using tools from VS Code.

Open dossier
Open SWE

Open-source framework for building internal coding agents that accept tasks via Slack, Linear, or GitHub, execute code changes in isolated cloud sandboxes, and open draft pull requests automatically.

Open dossier
Browser Harness logoBrowser Harness

MIT-licensed CDP browser-control harness from Browser Use that lets Claude Code, Codex, and other coding agents connect to a real or cloud Chrome browser, use screenshots and coordinate clicks, edit task-specific helpers, and optionally learn reusable domain skills for web automation workflows.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety · Privacy · Safety · Privacy · Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandRoo Code logoRoo CodeCline logoCline—Browser Harness logoBrowser Harness
Categorytoolstoolstoolstools
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorRoo CodeClineLangChainBrowser Use
Added2026-04-272026-04-272026-06-052026-06-18
Platforms
CLI
CLI
CLI
CodexCLI
Source repo————
Safety notes— missing— missing✓Each task runs in an isolated cloud Linux sandbox (Modal, Daytona, Runloop, or LangSmith) to prevent production impact. The agent executes shell commands, file operations, web fetches, and HTTP requests inside the sandbox without confirmation prompts — review sandbox provider permissions before deployment. GitHub operations are performed through a GH_TOKEN proxy; scope token permissions to the minimum required repositories. Subagent orchestration can spawn parallel child agents — set appropriate step limits and monitor LangSmith traces to prevent runaway execution. AGENTS.md or CLAUDE.md at the repository root is injected into the system prompt; review this file to control agent behavior and conventions.✓Browser Harness can connect agents to a real logged-in Chrome profile. Remote debugging may expose active sessions, extensions, bookmarks, history, page content, downloads, uploads, and account actions to the agent. The documented Way 1 setup uses the user's everyday Chrome profile through `chrome://inspect/#remote-debugging`; require explicit user consent before attaching to sensitive accounts. The documented Way 2 setup launches Chrome with a non-default `--user-data-dir` and remote debugging port; keep that isolated profile separate from everyday browser data. Remote Browser Use Cloud sessions require `BROWSER_USE_API_KEY`, may use proxies, can persist profile state, and can continue billing until timeout or shutdown. Agents using Browser Harness can edit `agent-workspace/agent_helpers.py` and optional domain-skill files; review generated helper code and public skill contributions before reuse. Browser automation can submit forms, send messages, purchase items, scrape websites, change account settings, and upload files. Keep destructive or account-writing tasks behind confirmation.
Privacy notes— missing— missing✓Repository code, Linear issue history, and Slack thread history are sent to the configured model provider API. Sandbox providers (Modal, Daytona, Runloop, LangSmith) process task execution data according to their own privacy policies. LangSmith tracing, when enabled, logs full agent traces including tool inputs and outputs — configure retention and access controls in your LangSmith organization. GitHub OAuth tokens and model API keys should be stored as secrets and never committed to the repository.✓Browser Harness workflows can expose page screenshots, DOM text, URLs, cookies-backed login state, account data, downloads, uploads, form inputs, and extracted website data to the agent and configured model providers. Profile sync for Browser Use Cloud is documented as cookies-only, but it still moves browser authentication material into a remote browser environment. Cloud browser live URLs, proxy settings, profile identifiers, daemon logs, `/tmp` socket or pid files, and copied support artifacts may reveal browsing activity or account context. Public domain-skill PRs should not include secrets, private selectors tied to confidential apps, customer data, screenshots, credentials, tokens, or personal browsing history.
Prerequisites— none listed— none listed
  • GitHub account with OAuth access for repository operations.
  • A model API key (Anthropic, OpenAI, or compatible provider).
  • A LangSmith API key when using LangSmith as the sandbox provider.
  • Slack workspace, Linear workspace, or GitHub repository access for the desired trigger integrations.
  • Python 3.11 or newer, uv, git, and a durable local checkout for editable installation.
  • A Chrome or Chromium-based browser that can be attached through Chrome remote debugging, or a Browser Use Cloud API key for cloud browsers.
  • Codex, Claude Code, or another agent host that can read the Browser Harness `SKILL.md` instructions.
  • A clear boundary for which browser profile, logged-in sites, cloud browser sessions, downloads, uploads, and account actions the agent may access.
Install———
git clone https://github.com/browser-use/browser-harness && cd browser-harness && uv tool install -e .
Config————
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Related guides

Source-backed guides for putting this to work.

guides

Claude Code VS Code Extension Setup For Teams

Deploy Claude Code VS Code extension to teams with permission and sign-in checklists.

Review firstSource-backedReview firstAdded 19d ago
Safety ✓ Privacy ✓by kiannidev

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.