scriptoriumadmin/Roo-Code
1
0
Fork 0
mirror of https://github.com/RooVetGit/Roo-Code.git synced 2026-08-28 05:27:24 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Remove contributor and community references (#12347)
Some checks failed
Code QA Roo Code / check-translations (push) Has been cancelled
Details
Code QA Roo Code / knip (push) Has been cancelled
Details
Code QA Roo Code / compile (push) Has been cancelled
Details
Code QA Roo Code / platform-unit-test (ubuntu-latest) (push) Has been cancelled
Details
Code QA Roo Code / platform-unit-test (windows-latest) (push) Has been cancelled
Details
CodeQL Advanced / Analyze (javascript-typescript) (push) Has been cancelled
Details
Deploy docs to GitHub Pages / build (push) Has been cancelled
Details
Nightly Publish / publish-nightly (push) Has been cancelled
Details
Deploy roocode.com / check-secrets (push) Has been cancelled
Details
Deploy docs to GitHub Pages / deploy (push) Has been cancelled
Details
Deploy roocode.com / deploy (push) Has been cancelled
Details

Browse source 
* Remove contributor and community references

* shutdown notice

* Allow empty web app test suite
This commit is contained in:
Bruno Bergher 2026-05-12 16:33:09 +01:00 • committed by GitHub
parent 28acb6acf2
commit e921f9d21e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
146 changed files with 158 additions and 7937 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.github/ISSUE_TEMPLATE/feature_request.yml vendored
View file

@ -64,7 +64,7 @@ body:
attributes:
value: |
---
Optional (for contributors): You can stop here if you're just proposing the improvement.
Optional: You can stop here if you're just proposing the improvement.
- type: textarea
id: acceptance-criteria

75
.github/pull_request_template.md vendored
View file

@ -1,75 +0,0 @@
<!--
Thank you for contributing to Roo Code!
Before submitting your PR, please ensure:
- It's linked to an approved GitHub Issue.
- You've reviewed our [Contributing Guidelines](../CONTRIBUTING.md).
-->
### Related GitHub Issue
<!-- Every PR MUST be linked to an approved issue. -->
Closes: # <!-- Replace with the issue number, e.g., Closes: #123 -->
### Roo Code Task Context (Optional)
<!--
If you used Roo Code to help create this PR, you can share public task links here.
This helps reviewers understand your development process and provides additional context.
Example: https://app.roocode.com/share/task-id
-->
### Description
<!--
Briefly summarize the changes in this PR and how they address the linked issue.
The issue should cover the "what" and "why"; this section should focus on:
- The "how": key implementation details, design choices, or trade-offs made.
- Anything specific reviewers should pay attention to in this PR.
-->
### Test Procedure
<!--
Detail the steps to test your changes. This helps reviewers verify your work.
- How did you test this specific implementation? (e.g., unit tests, manual testing steps)
- How can reviewers reproduce your tests or verify the fix/feature?
- Include relevant testing environment details if applicable.
-->
### Pre-Submission Checklist
<!-- Go through this checklist before marking your PR as ready for review. -->
- [ ] **Issue Linked**: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
- [ ] **Scope**: My changes are focused on the linked issue (one major feature/fix per PR).
- [ ] **Self-Review**: I have performed a thorough self-review of my code.
- [ ] **Testing**: New and/or updated tests have been added to cover my changes (if applicable).
- [ ] **Documentation Impact**: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
- [ ] **Contribution Guidelines**: I have read and agree to the [Contributor Guidelines](/CONTRIBUTING.md).
### Screenshots / Videos
<!--
For UI changes, please provide before-and-after screenshots or a short video of the *actual results*.
This greatly helps in understanding the visual impact of your changes.
-->
### Documentation Updates
<!--
Does this PR necessitate updates to user-facing documentation?
- [ ] No documentation updates are required.
- [ ] Yes, documentation updates are required. (Please describe what needs to be updated or link to a PR in the docs repository).
-->
### Additional Notes
<!-- Add any other context, questions, or information for reviewers here. -->
### Get in Touch
<!--
Please provide your Discord username for reviewers or maintainers to reach you if they have questions about your PR
-->

67
.github/workflows/update-contributors.yml vendored
View file

@ -1,67 +0,0 @@
name: Update Contributors # Refresh contrib.rocks image cache
on:
workflow_dispatch:
permissions:
contents: write
pull-requests: write
jobs:
refresh-contrib-cache:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Bump cacheBust in all README files
run: |
set -euo pipefail
TS="$(date +%s)"
# Target only the root README.md and localized READMEs under locales/*/README.md
mapfile -t FILES < <(git ls-files README.md 'locales/*/README.md' || true)
if [ "${#FILES[@]}" -eq 0 ]; then
echo "No target README files found." >&2
exit 1
fi
UPDATED=0
for f in "${FILES[@]}"; do
if grep -q 'cacheBust=' "$f"; then
# Use portable sed in GNU environment of ubuntu-latest
sed -i -E "s/cacheBust=[0-9]+/cacheBust=${TS}/g" "$f"
echo "Updated cacheBust in $f"
UPDATED=1
else
echo "Warning: cacheBust parameter not found in $f" >&2
fi
done
if [ "$UPDATED" -eq 0 ]; then
echo "No files were updated. Ensure READMEs embed contrib.rocks with cacheBust param." >&2
exit 1
fi
- name: Detect changes
id: changes
run: |
if git diff --quiet; then
echo "changed=false" >> $GITHUB_OUTPUT
else
echo "changed=true" >> $GITHUB_OUTPUT
fi
- name: Create Pull Request
if: steps.changes.outputs.changed == 'true'
uses: peter-evans/create-pull-request@v7
with:
token: ${{ secrets.GITHUB_TOKEN }}
commit-message: "docs: update contributors list [skip ci]"
committer: "github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>"
branch: refresh-contrib-cache
delete-branch: true
title: "Refresh contrib.rocks image cache (all READMEs)"
body: |
Automated refresh of the contrib.rocks image cache by bumping the cacheBust parameter in README.md and locales/*/README.md.
base: main

10
CHANGELOG.md
View file

@ -1274,7 +1274,6 @@
- Reposition Add Image button inside ChatTextArea (thanks @roomote!)
- Bring back a way to temporarily and globally pause auto-approve without losing your toggle state (thanks @brunobergher!)
- Makes text area buttons appear only when there's text (thanks @brunobergher!)
- CONTRIBUTING.md tweaks and issue template rewrite (thanks @hannesrudolph!)
- Bump axios from 1.9.0 to 1.12.0 (thanks @dependabot!)
## [3.28.2] - 2025-09-14
@ -1734,7 +1733,6 @@
- Fix Claude model detection by name for API protocol selection (thanks @daniel-lxs!)
- Move marketplace icon from overflow menu to top navigation
- Optional setting to prevent completion with open todos
- Added YouTube to website footer (thanks @thill2323!)
## [3.23.14] - 2025-07-17
@ -2128,7 +2126,6 @@
- Fix bug with context condensing in Amazon Bedrock
- Fix UTF-8 encoding in ExecaTerminalProcess (thanks @mr-ryan-james!)
- Set sidebar name bugfix (thanks @chrarnoldus!)
- Fix link to CONTRIBUTING.md in feature request template (thanks @cannuri!)
- Add task metadata to Unbound and improve caching logic (thanks @pugazhendhi-m!)
## [3.19.0] - 2025-05-29
@ -3096,7 +3093,6 @@
- Ask and Architect modes can now edit markdown files
- Custom modes can now be restricted to specific file patterns (for example, a technical writer who can only edit markdown files 👋)
- Support for configuring the Bedrock provider with AWS Profiles
- New Roo Code community Discord at https://roocode.com/discord!
## [3.2.8]
@ -3136,8 +3132,6 @@
- Create specialized assistants for any workflow
- Just type "Create a new mode for <X>" or visit the Prompts tab in the top menu to get started
Join us at https://www.reddit.com/r/RooCode to share your custom modes and be part of our next chapter!
## [3.1.7]
- DeepSeek-R1 support (thanks @philipnext!)
@ -3185,12 +3179,8 @@ Join us at https://www.reddit.com/r/RooCode to share your custom modes and be pa
## [3.0.1]
- Fix the reddit link and a small visual glitch in the chat input
## [3.0.0]
- This release adds chat modes! Now you can ask Roo Code questions about system architecture or the codebase without immediately jumping into writing code. You can even assign different API configuration profiles to each mode if you prefer to use different models for thinking vs coding. Would love feedback in the new Roo Code Reddit! https://www.reddit.com/r/RooCode
## [2.2.46]
- Only parse @-mentions in user input (not in files)

90
CODE_OF_CONDUCT.md
View file

@ -1,90 +0,0 @@
<div align="center">
<sub>
<b>English</b> • [Català](locales/ca/CODE_OF_CONDUCT.md) • [Deutsch](locales/de/CODE_OF_CONDUCT.md) • [Español](locales/es/CODE_OF_CONDUCT.md) • [Français](locales/fr/CODE_OF_CONDUCT.md) • [हिंदी](locales/hi/CODE_OF_CONDUCT.md) • [Bahasa Indonesia](locales/id/CODE_OF_CONDUCT.md) • [Italiano](locales/it/CODE_OF_CONDUCT.md) • [日本語](locales/ja/CODE_OF_CONDUCT.md)
</sub>
<sub>
[한국어](locales/ko/CODE_OF_CONDUCT.md) • [Nederlands](locales/nl/CODE_OF_CONDUCT.md) • [Polski](locales/pl/CODE_OF_CONDUCT.md) • [Português (BR)](locales/pt-BR/CODE_OF_CONDUCT.md) • [Русский](locales/ru/CODE_OF_CONDUCT.md) • [Türkçe](locales/tr/CODE_OF_CONDUCT.md) • [Tiếng Việt](locales/vi/CODE_OF_CONDUCT.md) • [简体中文](locales/zh-CN/CODE_OF_CONDUCT.md) • [繁體中文](locales/zh-TW/CODE_OF_CONDUCT.md)
</sub>
</div>
# Contributor Covenant Code of Conduct
## Our Pledge
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to make participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and expression,
level of experience, education, socio-economic status, nationality, personal
appearance, race, religion, or sexual identity and orientation.
## Our Standards
Examples of behavior that contributes to creating a positive environment
include:
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
- The use of sexualized language or imagery and unwelcome sexual attention or
advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or electronic
address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a
professional setting
## Our Responsibilities
Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.
## Scope
This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at support@roocode.com. All complaints
will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.
## Attribution
This Code of Conduct is adapted from [Cline's version][cline_coc] of the [Contributor Covenant][homepage], version 1.4,
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[cline_coc]: https://github.com/cline/cline/blob/main/CODE_OF_CONDUCT.md
[homepage]: https://www.contributor-covenant.org
For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq

141
CONTRIBUTING.md
View file

@ -1,141 +0,0 @@
<div align="center">
<sub>
<b>English</b> • [Català](locales/ca/CONTRIBUTING.md) • [Deutsch](locales/de/CONTRIBUTING.md) • [Español](locales/es/CONTRIBUTING.md) • [Français](locales/fr/CONTRIBUTING.md) • [हिंदी](locales/hi/CONTRIBUTING.md) • [Bahasa Indonesia](locales/id/CONTRIBUTING.md) • [Italiano](locales/it/CONTRIBUTING.md) • [日本語](locales/ja/CONTRIBUTING.md)
</sub>
<sub>
[한국어](locales/ko/CONTRIBUTING.md) • [Nederlands](locales/nl/CONTRIBUTING.md) • [Polski](locales/pl/CONTRIBUTING.md) • [Português (BR)](locales/pt-BR/CONTRIBUTING.md) • [Русский](locales/ru/CONTRIBUTING.md) • [Türkçe](locales/tr/CONTRIBUTING.md) • [Tiếng Việt](locales/vi/CONTRIBUTING.md) • [简体中文](locales/zh-CN/CONTRIBUTING.md) • [繁體中文](locales/zh-TW/CONTRIBUTING.md)
</sub>
</div>
# Contributing to Roo Code
Roo Code is a community-driven project, and we deeply value every contribution. To streamline collaboration, we operate on an [Issue-First](#issue-first-approach) basis, meaning all [Pull Requests (PRs)](#submitting-a-pull-request) must first be linked to a GitHub Issue. Please review this guide carefully.
## Table of Contents
- [Before You Contribute](#before-you-contribute)
- [Finding & Planning Your Contribution](#finding--planning-your-contribution)
- [Development & Submission Process](#development--submission-process)
- [Legal](#legal)
## Before You Contribute
### 1. Code of Conduct
All contributors must adhere to our [Code of Conduct](./CODE_OF_CONDUCT.md).
### 2. Project Roadmap
Our roadmap guides the project's direction. Align your contributions with these key goals:
### Reliability First
- Ensure diff editing and command execution are consistently reliable.
- Reduce friction points that deter regular usage.
- Guarantee smooth operation across all locales and platforms.
- Expand robust support for a wide variety of AI providers and models.
### Enhanced User Experience
- Streamline the UI/UX for clarity and intuitiveness.
- Continuously improve the workflow to meet the high expectations developers have for daily-use tools.
### Leading on Agent Performance
- Establish comprehensive evaluation benchmarks (evals) to measure real-world productivity.
- Make it easy for everyone to easily run and interpret these evals.
- Ship improvements that demonstrate clear increases in eval scores.
Mention alignment with these areas in your PRs.
### 3. Join the Roo Code Community
- **Primary:** Join our [Discord](https://discord.gg/roocode) and DM **Hannes Rudolph (`hrudolph`)**.
- **Alternative:** Experienced contributors can engage directly via [GitHub Projects](https://github.com/orgs/RooCodeInc/projects/1).
## Finding & Planning Your Contribution
### Types of Contributions
- **Bug Fixes:** Addressing code issues.
- **New Features:** Adding functionality.
- **Documentation:** Improving guides and clarity.
### Issue-First Approach
All contributions start with a GitHub Issue using our skinny templates.
- **Check existing issues**: Search [GitHub Issues](https://github.com/RooCodeInc/Roo-Code/issues).
- **Create an issue** using:
- **Enhancements:** "Enhancement Request" template (plain language focused on user benefit).
- **Bugs:** "Bug Report" template (minimal repro + expected vs actual + version).
- **Want to work on it?** Comment "Claiming" on the issue and DM **Hannes Rudolph (`hrudolph`)** on [Discord](https://discord.gg/roocode) to get assigned. Assignment will be confirmed in the thread.
- **PRs must link to the issue.** Unlinked PRs may be closed.
### Deciding What to Work On
- Check the [GitHub Project](https://github.com/orgs/RooCodeInc/projects/1) for "Issue [Unassigned]" issues.
- For docs, visit [Roo Code Docs](https://github.com/RooCodeInc/Roo-Code-Docs).
### Reporting Bugs
- Check for existing reports first.
- Create a new bug using the ["Bug Report" template](https://github.com/RooCodeInc/Roo-Code/issues/new/choose) with:
- Clear, numbered reproduction steps
- Expected vs actual result
- Roo Code version (required); API provider/model if relevant
- **Security issues**: Report privately via [security advisories](https://github.com/RooCodeInc/Roo-Code/security/advisories/new).
## Development & Submission Process
### Development Setup
1. **Fork & Clone:**
```
git clone https://github.com/YOUR_USERNAME/Roo-Code.git
```
2. **Install Dependencies:**
```
pnpm install
```
3. **Debugging:** Open with VS Code (`F5`).
### Writing Code Guidelines
- One focused PR per feature or fix.
- Follow ESLint and TypeScript best practices.
- Write clear, descriptive commits referencing issues (e.g., `Fixes #123`).
- Provide thorough testing (`npm test`).
- Rebase onto the latest `main` branch before submission.
### Submitting a Pull Request
- Begin as a **Draft PR** if seeking early feedback.
- Clearly describe your changes following the Pull Request Template.
- Link the issue in the PR description/title (e.g., "Fixes #123").
- Provide screenshots/videos for UI changes.
- Indicate if documentation updates are necessary.
### Pull Request Policy
- Must reference an assigned GitHub Issue. To get assigned: comment "Claiming" on the issue and DM **Hannes Rudolph (`hrudolph`)** on [Discord](https://discord.gg/roocode). Assignment will be confirmed in the thread.
- Unlinked PRs may be closed.
- PRs should pass CI tests, align with the roadmap, and have clear documentation.
### Review Process
- **Daily Triage:** Quick checks by maintainers.
- **Weekly In-depth Review:** Comprehensive assessment.
- **Iterate promptly** based on feedback.
## Legal
By contributing, you agree your contributions will be licensed under the Apache 2.0 License, consistent with Roo Code's licensing.

124
README.md
View file

@ -1,32 +1,11 @@
<p align="center">
<a href="https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline"><img src="https://img.shields.io/badge/VS_Code_Marketplace-007ACC?style=flat&logo=visualstudiocode&logoColor=white" alt="VS Code Marketplace"></a>
<a href="https://x.com/roocode"><img src="https://img.shields.io/badge/roocode-000000?style=flat&logo=x&logoColor=white" alt="X"></a>
<a href="https://youtube.com/@roocodeyt?feature=shared"><img src="https://img.shields.io/badge/YouTube-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube"></a>
<a href="https://discord.gg/roocode"><img src="https://img.shields.io/badge/Join%20Discord-5865F2?style=flat&logo=discord&logoColor=white" alt="Join Discord"></a>
<a href="https://www.reddit.com/r/RooCode/"><img src="https://img.shields.io/badge/Join%20r%2FRooCode-FF4500?style=flat&logo=reddit&logoColor=white" alt="Join r/RooCode"></a>
</p>
<p align="center">
<em>Get help fast → <a href="https://discord.gg/roocode">Join Discord</a> • Prefer async? → <a href="https://www.reddit.com/r/RooCode/">Join r/RooCode</a></em>
</p>
# Roo Code
> Your AI-Powered Dev Team, Right in Your Editor
## What's New in v3.53.0
> ### The Roo Code plugin is not going away.
>
> You may have seen the [recent announcement](https://x.com/mattrubens/status/2046636598859559114) that Roo Code hit 3 million installs and the original team is going all-in on Roomote. We know that news was hard for a lot of you. This plugin means a lot to us and to you, and we hear you.
>
> The good news: **a community team has stepped up to carry Roo Code forward**, and we're working with them on an official handoff so the plugin you rely on keeps getting maintained and improved.
**What's new in this release:**
- Add GPT-5.5 support via the OpenAI Codex provider.
- Add Claude Opus 4.7 support on Vertex AI.
- Add previous checkpoint navigation controls in chat so you can step back through prior checkpoints more easily.
<details>
<summary>🌐 Available languages</summary>
@ -49,7 +28,7 @@
- [简体中文](locales/zh-CN/README.md)
- [繁體中文](locales/zh-TW/README.md)
- ...
</details>
</details>
---
@ -75,115 +54,24 @@ Roo Code adapts to how you work:
Learn more: [Using Modes](https://docs.roocode.com/basic-usage/using-modes) • [Custom Modes](https://docs.roocode.com/advanced-usage/custom-modes)
## Tutorial & Feature Videos
<div align="center">
| | | |
| :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <a href="https://www.youtube.com/watch?v=Mcq3r1EPZ-4"><img src="https://img.youtube.com/vi/Mcq3r1EPZ-4/maxresdefault.jpg" width="100%"></a><br><b>Installing Roo Code</b> | <a href="https://www.youtube.com/watch?v=ZBML8h5cCgo"><img src="https://img.youtube.com/vi/ZBML8h5cCgo/maxresdefault.jpg" width="100%"></a><br><b>Configuring Profiles</b> | <a href="https://www.youtube.com/watch?v=r1bpod1VWhg"><img src="https://img.youtube.com/vi/r1bpod1VWhg/maxresdefault.jpg" width="100%"></a><br><b>Codebase Indexing</b> |
| <a href="https://www.youtube.com/watch?v=iiAv1eKOaxk"><img src="https://img.youtube.com/vi/iiAv1eKOaxk/maxresdefault.jpg" width="100%"></a><br><b>Custom Modes</b> | <a href="https://www.youtube.com/watch?v=Ho30nyY332E"><img src="https://img.youtube.com/vi/Ho30nyY332E/maxresdefault.jpg" width="100%"></a><br><b>Checkpoints</b> | <a href="https://www.youtube.com/watch?v=HmnNSasv7T8"><img src="https://img.youtube.com/vi/HmnNSasv7T8/maxresdefault.jpg" width="100%"></a><br><b>Context Management</b> |
</div>
<p align="center">
<a href="https://docs.roocode.com/tutorial-videos">More quick tutorial and feature videos...</a>
</p>
## Resources
- **[Documentation](https://docs.roocode.com):** The official guide to installing, configuring, and mastering Roo Code.
- **[YouTube Channel](https://youtube.com/@roocodeyt?feature=shared):** Watch tutorials and see features in action.
- **[Discord Server](https://discord.gg/roocode):** Join the community for real-time help and discussion.
- **[Reddit Community](https://www.reddit.com/r/RooCode):** Share your experiences and see what others are building.
- **[GitHub Issues](https://github.com/RooCodeInc/Roo-Code/issues):** Report bugs and track development.
- **[Feature Requests](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop):** Have an idea? Share it with the developers.
---
## Local Setup & Development
1. **Clone** the repo:
```sh
git clone https://github.com/RooCodeInc/Roo-Code.git
```
2. **Install dependencies**:
```sh
pnpm install
```
3. **Run the extension**:
There are several ways to run the Roo Code extension:
### Development Mode (F5)
For active development, use VSCode's built-in debugging:
Press `F5` (or go to **Run** → **Start Debugging**) in VSCode. This will open a new VSCode window with the Roo Code extension running.
- Changes to the webview will appear immediately.
- Changes to the core extension will also hot reload automatically.
### Automated VSIX Installation
To build and install the extension as a VSIX package directly into VSCode:
```sh
pnpm install:vsix [-y] [--editor=<command>]
```
This command will:
- Ask which editor command to use (code/cursor/code-insiders) - defaults to 'code'
- Uninstall any existing version of the extension.
- Build the latest VSIX package.
- Install the newly built VSIX.
- Prompt you to restart VS Code for changes to take effect.
Options:
- `-y`: Skip all confirmation prompts and use defaults
- `--editor=<command>`: Specify the editor command (e.g., `--editor=cursor` or `--editor=code-insiders`)
### Manual VSIX Installation
If you prefer to install the VSIX package manually:
1. First, build the VSIX package:
```sh
pnpm vsix
```
2. A `.vsix` file will be generated in the `bin/` directory (e.g., `bin/roo-cline-<version>.vsix`).
3. Install it manually using the VSCode CLI:
```sh
code --install-extension bin/roo-cline-<version>.vsix
```
---
We use [changesets](https://github.com/changesets/changesets) for versioning and publishing. Check our `CHANGELOG.md` for release notes.
---
## Disclaimer
The Roo Code Extension was shut down on May 15th.
- If you're looking for an alternative, check out [ZooCode](https://github.com/Zoo-Code-Org/Zoo-Code/) (a fork started by the Roo Code community) and [Cline](https://cline.bot/) (from where Roo Code originated).
- If you were a paying user and have billing questions, please write [billing@roocode.com](mailto:billing@roocode.com).
**Please note** that Roo Code, Inc does **not** make any representations or warranties regarding any code, models, or other tools provided or made available in connection with Roo Code, any associated third-party tools, or any resulting outputs. You assume **all risks** associated with the use of any such tools or outputs; such tools are provided on an **"AS IS"** and **"AS AVAILABLE"** basis. Such risks may include, without limitation, intellectual property infringement, cyber vulnerabilities or attacks, bias, inaccuracies, errors, defects, viruses, downtime, property loss or damage, and/or personal injury. You are solely responsible for your use of any such tools or outputs (including, without limitation, the legality, appropriateness, and results thereof).
---
## Contributing
We love community contributions! Get started by reading our [CONTRIBUTING.md](CONTRIBUTING.md).
---
## License
[Apache 2.0 © 2025 Roo Code, Inc.](./LICENSE)
---
**Enjoy Roo Code!** Whether you keep it on a short leash or let it roam autonomously, we can’t wait to see what you build. If you have questions or feature ideas, drop by our [Reddit community](https://www.reddit.com/r/RooCode/) or [Discord](https://discord.gg/roocode). Happy coding!

15
apps/cli/README.md
View file

@ -53,21 +53,6 @@ roo upgrade
rm -rf ~/.roo/cli ~/.local/bin/roo
```
### Development Installation
For contributing or development:
```bash
# From the monorepo root.
pnpm install
# Build the main extension first.
pnpm --filter roo-cline bundle
# Build the CLI.
pnpm --filter @roo-code/cli build
```
## Usage
### Interactive Mode (Default)

62
apps/docs/docs/advanced-usage/local-development-setup.mdx
View file

@ -1,62 +0,0 @@
---
description: Learn how to set up Roo Code for local development, build from source, and contribute to the project. Complete developer setup guide.
keywords:
- local development
- build from source
- Roo Code development
- contribute
- developer setup
sidebar_label: Local Development Setup
---
## Local Setup & Development
:::note Developer Information Only
This section is for developers contributing to Roo Code or those who wish to build and run the extension from source.
:::
To set up Roo Code for local development:
1. **Clone the repository:**
```bash
git clone https://github.com/RooCodeInc/Roo-Code.git
cd Roo-Code
```
2. **Install dependencies:**
Roo Code uses `pnpm` for package management.
```bash
pnpm install
```
3. **Run the extension for development:**
You have two primary methods:
* **Directly in VS Code (Recommended for active development):**
* Open the cloned `Roo-Code` folder in VS Code.
* Press `F5` (or select **Run** → **Start Debugging** from the menu). This opens a new VS Code window (Extension Development Host) with Roo Code running.
* Changes to the webview code (under `webview-ui/`) will often update live.
* Changes to the core extension code (under `src/`) typically require restarting the Extension Development Host window.
* **Building and Installing a VSIX package:**
This method is useful for testing the packaged extension or distributing development builds.
1. Build the VSIX file:
```bash
pnpm vsix
```
A `.vsix` file (e.g., `roo-cline-<version>.vsix`) will be created in the `bin/` directory.
2. Install the VSIX in VS Code:
* **Using the command line:**
```bash
code --install-extension bin/roo-cline-<version>.vsix
```
(Replace `<version>` with the actual version number in the filename).
* **Using the VS Code interface:**
* Open the Extensions view (`Ctrl+Shift+X` or `Cmd+Shift+X`).
* Click the "..." (More Actions) menu in the Extensions view sidebar.
* Select "Install from VSIX..."
* Browse to and select the generated `.vsix` file from the `bin/` directory.
<img src="/img/installing/installing-2.png" alt="VS Code's Install from VSIX dialog" width="600" />
*Installing a development VSIX using VS Code's "Install from VSIX..." dialog.*

4
apps/docs/docs/advanced-usage/roo-code-nightly.mdx
View file

@ -11,8 +11,6 @@ sidebar_label: Roo Code Nightly
# Roo Code Nightly
For users who want the latest features and updates, Roo Code offers a prerelease build called **Roo Code Nightly**, which is automatically published whenever changes are merged into our main development branch. This means it always reflects the latest code. It's designed for users who want to access the newest features and contribute to early testing.
---
## Understanding Nightly vs. Other Prereleases
@ -50,4 +48,4 @@ To install Roo Code Nightly:
<img src="/img/installing/installing-5.png" alt="Roo Code Nightly extension in VS Code Marketplace" width="400" />
*Roo Code Nightly in the VS Code Marketplace.*
You can have both the stable version of Roo Code and Roo Code Nightly installed simultaneously.
You can have both the stable version of Roo Code and Roo Code Nightly installed simultaneously.

5
apps/docs/docs/faq.md
View file

@ -172,12 +172,9 @@ Codebase Indexing requires an OpenAI API key for generating embeddings and a Qdr
- Check your internet connection.
- Check the status of your chosen API provider.
- Try restarting VS Code.
- If the problem persists, report the issue on [GitHub](https://github.com/RooCodeInc/Roo-Code/issues) or [Discord](https://discord.gg/roocode).
### I'm seeing an error message. What does it mean?
The error message should provide some information about the problem. If you're unsure how to resolve it, seek help in [Discord](https://discord.gg/roocode).
### Roo Code made changes I didn't want. How do I undo them?
Roo Code uses VS Code's built-in file editing capabilities. You can use the standard "Undo" command (Ctrl/Cmd + Z) to revert changes. Also, if experimental checkpoints are enabled, Roo can revert changes made to a file.
@ -206,5 +203,3 @@ If Roo Code fails to write to `.md` files with errors like "Failed to open diff
- Restart VS Code after making these changes
### How do I report a bug or suggest a feature?
Please report bugs or suggest features on the Roo Code [Issues page](https://github.com/RooCodeInc/Roo-Code/issues) and [Feature Requests page](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop).

18
apps/docs/docs/features/api-configuration-profiles.mdx
View file

@ -16,23 +16,6 @@ API Configuration Profiles allow you to create and switch between different sets
Having multiple configuration profiles lets you quickly switch between different AI providers, models, and settings without reconfiguring everything each time you want to change your setup.
:::
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/eEJErgZBqLE?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
></iframe>
</div>
<br />
---
## How It Works
@ -103,7 +86,6 @@ The API configuration dropdown now supports pinning your favorite profiles for q
This feature makes it easier to navigate between commonly used profiles, especially when you have many configurations.
### Editing and Deleting Profiles
<img src="/img/api-configuration-profiles/api-configuration-profiles-10.png" alt="Profile editing interface" width="550" />

18
apps/docs/docs/features/auto-approving-actions.mdx
View file

@ -14,23 +14,6 @@ keywords:
Auto-approve settings speed up your workflow by eliminating repetitive confirmation prompts, but they significantly increase security risks.
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/bWtIxGsl2cQ?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
></iframe>
</div>
<br />
---
## Quick Start Guide
@ -76,7 +59,6 @@ The dropdown shows a grid of permission tiles. Controls:
- All / None (bottom-left): bulk select or clear permissions without changing Enabled
- Permission tiles: choose which actions can run without prompts; tiles disable only when Enabled is off. Some permissions take effect only if your model supports the capability.
### Available Permissions
| Permission | What it does | Risk level |

21
apps/docs/docs/features/boomerang-tasks.mdx
View file

@ -13,24 +13,6 @@ sidebar_label: 'Boomerang Tasks'
Boomerang Tasks (also known as subtasks or task orchestration) allow you to break down complex projects into smaller, manageable pieces using the built-in **`🪃 Orchestrator` Mode (aka Boomerang Mode)**. Think of it like delegating parts of your work to specialized assistants. Each subtask runs in its own context, often using a different Roo Code mode tailored for that specific job (like [`💻 Code`](/basic-usage/using-modes#code-mode-default), [`🏗️ Architect`](/basic-usage/using-modes#architect-mode), or [`🪲 Debug`](/basic-usage/using-modes#debug-mode)). The Orchestrator mode manages this process.
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/RX862U09fnE?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
></iframe>
</div>
<br />
:::info Orchestrator Mode is Built-In
The `🪃 Orchestrator` mode (previously achieved via a custom "Boomerang Mode") is now a built-in mode specifically designed to orchestrate workflows by breaking down tasks and delegating them to other modes. You no longer need to create a custom mode for this functionality.
@ -112,7 +94,6 @@ You can [customize the Orchestrator mode](/features/custom-modes) to add capabil
Adding capabilities to the Orchestrator mode should be done thoughtfully. The limited default capabilities help maintain focus on orchestration rather than implementation details.
:::
[^1]: This context is passed via the `message` parameter of the [`new_task`](/advanced-usage/available-tools/new-task) tool when the Orchestrator mode delegates the task.
[^2]: The mode for the subtask is specified via the `mode` parameter of the [`new_task`](/advanced-usage/available-tools/new-task) tool during initiation by the Orchestrator mode.
[^3]: This summary is passed via the `result` parameter of the [`attempt_completion`](/advanced-usage/available-tools/attempt-completion) tool when the subtask finishes.
[^3]: This summary is passed via the `result` parameter of the [`attempt_completion`](/advanced-usage/available-tools/attempt-completion) tool when the subtask finishes.

16
apps/docs/docs/features/checkpoints.mdx
View file

@ -19,22 +19,6 @@ Checkpoints let you:
- Compare different implementation approaches
- Revert to previous project states without losing work
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe title="Checkpoints Tutorial Video"
src="https://www.youtube.com/embed/Ho30nyY332E?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
></iframe>
</div>
<div style={{ marginTop: '20px' }}></div>
:::info Important Notes

16
apps/docs/docs/features/code-actions.mdx
View file

@ -14,22 +14,6 @@ keywords:
Code Actions provide instant access to Roo Code's AI assistance directly within your code editor through VSCode's lightbulb (quick fix) system. This context-aware feature automatically detects relevant code situations and offers appropriate AI-powered actions without requiring you to switch to the chat interface.
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/_Op3VfLPEu8?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
></iframe>
</div>
<div style={{ marginTop: '20px' }}></div>
---

22
apps/docs/docs/features/codebase-indexing.mdx
View file

@ -16,25 +16,6 @@ import Codicon from '@site/src/components/Codicon';
Codebase Indexing transforms how Roo Code understands your project by creating a semantic search index using AI embeddings. Instead of searching for exact text matches, it understands the *meaning* of your queries, helping Roo find relevant code even when you don't know specific function names or file locations.
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/r1bpod1VWhg?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
title="Codebase Indexing Setup Tutorial"
></iframe>
</div>
<br />
---
## What It Does
@ -48,7 +29,6 @@ When enabled, the indexing system:
This enables natural language queries like "user authentication logic" or "database connection handling" to find relevant code across your entire project.
---
## Quick Start Guide
@ -364,4 +344,4 @@ Planned improvements:
- Enhanced filtering options
- Team collaboration features
- VS Code native search integration
- Incremental re-indexing optimizations
- Incremental re-indexing optimizations

25
apps/docs/docs/features/custom-modes.mdx
View file

@ -13,31 +13,12 @@ keywords:
Roo Code allows you to create **custom modes** to tailor Roo's behavior to specific tasks or workflows. Custom modes can be either **global** (available across all projects) or **project-specific** (defined within a single project).
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/iiAv1eKOaxk?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
title="Custom Modes Overview Video"
></iframe>
</div>
<br />
:::tip Sticky Models for Efficient Workflow
Each mode—including custom ones—features **Sticky Models**. This means Roo Code automatically remembers and selects the last model you used with a particular mode. This lets you assign different preferred models to different tasks without constant reconfiguration, as Roo switches between models when you change modes.
:::
:::info Discover Community Modes
Looking for ready-to-use custom modes? Visit the [Roo Code Marketplace](/features/marketplace) to browse and install community-contributed modes with a single click. The marketplace offers specialized modes for various tasks like React development, documentation writing, testing, and more—all created and shared by the Roo Code community.
:::info Discover Modes
Looking for ready-to-use custom modes? Visit the [Roo Code Marketplace](/features/marketplace) to browse and install modes with a single click. The marketplace offers specialized modes for various tasks like React development, documentation writing, testing, and more.
:::
---
@ -616,7 +597,6 @@ In the table below, the 'Pattern (Conceptual / YAML-like)' column shows patterns
| `docs/.*\.md$` | `"docs/.*\\.md$"` | `docs/guide.md`, `docs/api/reference.md` | `guide.md`, `src/docs/notes.md` |
| `^(?!.*(test\|spec))\.(js\|ts)$` | `"^(?!.*(test\|spec))\\.(js\|ts)$"` | `app.js`, `utils.ts` | `app.test.js`, `utils.spec.js`, `app.jsx` |
**Key Regex Building Blocks:**
* `\.`: Matches a literal dot. (YAML: `\.`, JSON: `\\.`)
* `$`: Matches the end of the string.
@ -660,4 +640,3 @@ In addition to mode-specific rules directories, there's also a generic `.roo/rul
- **Mode not appearing:** After creating or importing a mode, you may need to reload the VS Code window for it to appear in the mode selector.
- **Invalid regex patterns:** If your `fileRegex` pattern is invalid, you'll receive an error message. Test your patterns using online regex testers before applying them.
- **Precedence confusion:** Remember that project modes completely override global modes with the same slug - no properties are merged.

17
apps/docs/docs/features/intelligent-context-condensing.mdx
View file

@ -14,23 +14,6 @@ import Codicon from '@site/src/components/Codicon';
The Intelligent Context Condensing feature helps manage long conversations by summarizing earlier parts of the dialogue. This prevents important information from being lost when the context window nears its limit. This feature is **enabled by default**.
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/9k8OAXlszak?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
></iframe>
</div>
<br />
---
## How It Works

28
apps/docs/docs/features/marketplace.mdx
View file

@ -1,45 +1,29 @@
---
description: Discover and install community-contributed MCP servers and custom modes from the Roo Code Marketplace to extend your AI coding assistant's capabilities.
description: Discover and install MCP servers and custom modes from the Roo Code Marketplace to extend your AI coding assistant's capabilities.
keywords:
- Roo Code Marketplace
- MCP servers
- custom modes
- extensions
- community tools
- tools
- AI integrations
---
import Codicon from '@site/src/components/Codicon';
# Roo Code Marketplace
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/WatooxMlW0U?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
></iframe>
</div>
<div style={{ marginTop: '20px' }}></div>
---
## Overview
The Roo Code Marketplace is a central hub for discovering and installing community-contributed extensions, known as MCPs (Model Context Protocol) and Modes. It allows you to easily extend the functionality of Roo Code to fit your specific needs and workflows.
The Roo Code Marketplace is a central hub for discovering and installing extensions, known as MCPs (Model Context Protocol) and Modes. It allows you to easily extend the functionality of Roo Code to fit your specific needs and workflows.
### Key Features
- **Discoverability**: Browse a curated list of MCPs and Modes.
- **Simple Installation**: Install and remove items with a single click.
- **Community-Driven**: Access a growing collection of extensions from the Roo Code community.
- **Curated Extensions**: Access a growing collection of ready-to-use extensions.
- **Project & Global Scopes**: Install items for a specific project or for all your projects.
---
@ -50,8 +34,6 @@ The Roo Code Marketplace is available directly within the Roo Code extension in
---
## Marketplace Items
The marketplace offers two types of items:
@ -172,4 +154,4 @@ If an installed item isn't working:
### For Modes
- [Using Modes](/basic-usage/using-modes) - Learn about built-in modes and how to switch between them
- [Custom Modes](/features/custom-modes) - Create and configure your own specialized modes
- [Custom Modes](/features/custom-modes) - Create and configure your own specialized modes

4
apps/docs/docs/features/mcp/recommended-mcp-servers.md
View file

@ -12,9 +12,9 @@ sidebar_label: Recommended MCP Servers
# Recommended MCP Servers
While Roo Code can connect to any Model Context Protocol (MCP) server that follows the specification, the community has already built several high-quality servers that work out-of-the-box. This page curates the servers we **actively recommend** and provides step-by-step setup instructions so you can get productive in minutes.
While Roo Code can connect to any Model Context Protocol (MCP) server that follows the specification, several high-quality servers work out-of-the-box. This page curates the servers we **actively recommend** and provides step-by-step setup instructions so you can get productive in minutes.
> We'll keep this list up-to-date. If you maintain a server you'd like us to consider, please open a pull-request.
> We'll keep this list up-to-date.
---

18
apps/docs/docs/features/mcp/using-mcp-in-roo.mdx
View file

@ -21,23 +21,6 @@ For a deeper dive, check out [What is MCP?](/features/mcp/what-is-mcp).
Model Context Protocol (MCP) extends Roo Code's capabilities by connecting to external tools and services. This guide covers everything you need to know about using MCP with Roo Code.
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/VAbadUDhH5c?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
></iframe>
</div>
<br />
---
## Configuring MCP Servers
@ -339,7 +322,6 @@ When enabled, Roo Code will automatically approve this specific tool without pro
Roo Code does not come with any pre-installed MCP servers. You'll need to find and install them separately.
* **Community Repositories:** Check for community-maintained lists of MCP servers on GitHub
* **Ask Roo:** You can ask Roo Code to help you find or even create MCP servers (when "[Enable MCP Server Creation](#enabling-or-disabling-mcp-server-creation)" is enabled)
* **Build Your Own:** Create custom MCP servers using the SDK to extend Roo Code with your own tools

25
apps/docs/docs/features/shell-integration.mdx
View file

@ -13,25 +13,6 @@ import Codicon from '@site/src/components/Codicon';
Terminal Shell Integration is a key feature that enables Roo Code to execute commands in your terminal and intelligently process their output. This bidirectional communication between the AI and your development environment unlocks powerful automation capabilities.
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/rkWBHeG9A-4?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
title="Terminal Integration Tutorial"
></iframe>
</div>
<br />
---
## What is Shell Integration?
@ -331,7 +312,6 @@ For optimal shell integration with WSL, we recommend:
---
#### Cygwin (bash, zsh)
Cygwin provides a Unix-like environment on Windows systems. To configure Cygwin as your terminal in VS Code:
@ -447,9 +427,6 @@ For fellow Windows users running Fish terminal within a Cygwin environment, here
This setup works reliably on Windows systems using Cygwin, Fish, and the Starship prompt, and should assist users with similar configurations.
#### Ctrl+C Behavior
**Issue**: If text is already typed in the terminal when Roo tries to run a command, Roo will press Ctrl+C first to clear the line, which can interrupt running processes.
@ -540,5 +517,3 @@ The [VS Code Terminal Integration Test Extension](https://github.com/KJ7LNW/vsce
- What you’ll see: a chat notice that real-time streaming and exit‑code detection may be limited.
- Fix: turn ON [Use Inline Terminal (recommended)](#use-inline-terminal-recommended) or follow the Troubleshooting steps above to restore VS Code shell integration.
<img src="/img/v3.15.0/v3.15.0.png" alt="Command execution fallback notification example" width="600" />

20
apps/docs/docs/features/skills.mdx
View file

@ -13,25 +13,6 @@ keywords:
Skills package task-specific instructions that Roo loads on-demand when your request matches the skill's purpose. Unlike custom instructions that apply to everything, skills activate only when needed—making Roo more effective at specialized tasks without cluttering the base prompt.
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/1992Rpfc800?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
title="Skills Tutorial Video"
></iframe>
</div>
<br />
---
## Why It Matters
@ -234,7 +215,6 @@ Roo automatically discovers skills:
You don't need to register or configure skills—just create the directory structure.
#### Symlink support
Skills support symbolic links for sharing skill libraries across projects:

24
apps/docs/docs/features/slash-commands.mdx
View file

@ -14,25 +14,6 @@ keywords:
Create custom slash commands to automate repetitive tasks and extend Roo Code's functionality with simple markdown files.
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/IOpmeUGLpg0?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
title="Slash Commands Tutorial Video"
></iframe>
</div>
<br />
:::tip Quick Start
Type `/` in chat to select a command. To create or manage commands, open Settings > Slash Commands. You can still store commands in `.roo/commands/` (project) or `~/.roo/commands/` (global).
:::
@ -293,8 +274,7 @@ Generate a README.md file that includes:
3. Usage examples
4. API documentation
5. Configuration options
6. Contributing guidelines
7. License information
6. License information
Base it on the current project structure and existing code.
```
@ -443,4 +423,4 @@ The slash menu includes mode-switching commands (like `/code`, `/ask`) that fund
- [Using Modes](/basic-usage/using-modes) - Learn about Roo Code's different operational modes
- [Custom Instructions](/features/custom-instructions) - Set persistent instructions for Roo Code
- [Keyboard Shortcuts](/features/keyboard-shortcuts) - Quick access to commands
- [Task Management](/features/task-todo-list) - Manage complex workflows
- [Task Management](/features/task-todo-list) - Manage complex workflows

20
apps/docs/docs/features/task-todo-list.mdx
View file

@ -20,24 +20,6 @@ Todo lists are automatically created for complex tasks, multi-step workflows, or
See [When Roo Creates Todo Lists](#when-roo-creates-todo-lists) for detailed information about automatic and manual triggers.
:::
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/6h5vB9PpoPk?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
></iframe>
</div>
<br />
---
## Use Case
@ -177,4 +159,4 @@ When enabled, this setting prevents task completion when there are uncompleted t
You can disable todo lists entirely through the `todoListEnabled` setting. When disabled:
- Roo will not create todo lists for any tasks
- The REMINDERS section will not appear in environment details
- Existing todo lists will remain visible but won't be updated
- Existing todo lists will remain visible but won't be updated

17
apps/docs/docs/features/worktrees.mdx
View file

@ -20,22 +20,6 @@ This is particularly powerful for agentic coding workflows where you might want
- Run multiple tasks on different branches simultaneously
- Maintain separate environments for development and debugging
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe title="Worktrees Tutorial Video"
src="https://www.youtube.com/embed/BRrhcYYSh9M?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
></iframe>
</div>
<div style={{ marginTop: '20px' }}></div>
:::note Requirements
@ -115,7 +99,6 @@ The worktrees list shows:
1. Navigate to Settings → Worktrees
2. Click the trash icon <Codicon name="trash" /> next to the worktree you want to delete
### Copying Files with .worktreeinclude
By default, Git worktrees only include files tracked by Git. Untracked files like `node_modules`, `.env`, or build artifacts aren't copied. The `.worktreeinclude` feature solves this problem.

22
apps/docs/docs/getting-started/installing.mdx
View file

@ -13,22 +13,6 @@ import KangarooIcon from '@site/src/components/KangarooIcon';
# Installing Roo Code
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/Mcq3r1EPZ-4?rel=0&modestbranding=1"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="autoplay; encrypted-media"
allowFullScreen
></iframe>
</div>
Roo Code is a VS Code extension that brings AI-powered coding assistance directly to your editor. Install using one of these methods:
1. **VS Code Marketplace (Recommended)** - fastest method for standard VS Code and Cursor users
2. **Open VSX Registry** - for VS Code-compatible editors like VSCodium
@ -62,12 +46,10 @@ For VS Code-compatible editors without Marketplace access (like VSCodium and Win
<img src="/img/installing/installing-3.png" alt="Open VSX Registry with Roo Code extension ready to install" width="400" />
## Roo Code Nightly
For information on installing Roo Code Nightly (our prerelease build published on each merge to main), please see the [Roo Code Nightly](/advanced-usage/roo-code-nightly) guide in the Advanced Usage section.
## Manual Installation from VSIX
If you prefer to download and install the VSIX file directly:
@ -90,8 +72,6 @@ If you prefer to download and install the VSIX file directly:
## Local Setup & Development
For instructions on setting up Roo Code for local development, building from source, or contributing, please see the [Local Development Setup](/advanced-usage/local-development-setup) guide in the Advanced Usage section.
---
## Troubleshooting
@ -116,6 +96,4 @@ For instructions on setting up Roo Code for local development, building from sou
If you encounter issues not covered here:
* Join our [Discord community](https://discord.gg/roocode) for real-time support
* Submit issues on [GitHub](https://github.com/RooCodeInc/Roo-Code/issues)
* Visit our [Reddit community](https://www.reddit.com/r/RooCode)

44
apps/docs/docs/index.mdx
View file

@ -13,6 +13,12 @@ keywords:
# Roo Code Docs
:::warning Extension Shutdown
The Roo Code Extension was shut down on May 15th.
- If you're looking for an alternative, check out [ZooCode](https://github.com/Zoo-Code-Org/Zoo-Code/) (a fork started by the Roo Code community) and [Cline](https://cline.bot/) (from where Roo Code originated).
- If you were a paying user and have billing questions, please write [billing@roocode.com](mailto:billing@roocode.com).
:::
Roo Code is an open-source AI coding agent for VS Code designed to take full advantage of advanced large-language models and change how you create software at a fundamental level. It's powerful, customizable, and model-agnostic, with actual file system access, terminal control, and multi-step workflows.
Roo's approach is to trade tokens for quality. If you want the best and most effective AI coding experience available, this is it.
@ -42,44 +48,6 @@ The most successful Roo users tend to embrace the following ideas:
- [Install the Extension](/getting-started/installing)
- [Connect an LLM Provider](/getting-started/connecting-api-provider)
## Tutorial & Feature Videos
<div style={{ display: 'grid', gridTemplateColumns: 'repeat(3, 1fr)', gap: '.5rem', margin: '0rem' }}>
<a href="https://www.youtube.com/watch?v=Mcq3r1EPZ-4" target="_blank" rel="noopener noreferrer" style={{ textDecoration: 'none', color: 'inherit' }}>
<img src="https://img.youtube.com/vi/Mcq3r1EPZ-4/maxresdefault.jpg" alt="Installing Roo Code" style={{ width: '100%', height: 'auto', borderRadius: '8px', display: 'block' }} />
<div style={{ marginTop: '0.0rem', textAlign: 'center', fontWeight: 600, fontSize: '1rem' }}>Installing Roo Code</div>
</a>
<a href="https://www.youtube.com/watch?v=ZBML8h5cCgo" target="_blank" rel="noopener noreferrer" style={{ textDecoration: 'none', color: 'inherit' }}>
<img src="https://img.youtube.com/vi/ZBML8h5cCgo/maxresdefault.jpg" alt="Configuring Profiles" style={{ width: '100%', height: 'auto', borderRadius: '8px', display: 'block' }} />
<div style={{ marginTop: '0.0rem', textAlign: 'center', fontWeight: 600, fontSize: '1rem' }}>Configuring Profiles</div>
</a>
<a href="https://www.youtube.com/watch?v=r1bpod1VWhg" target="_blank" rel="noopener noreferrer" style={{ textDecoration: 'none', color: 'inherit' }}>
<img src="https://img.youtube.com/vi/r1bpod1VWhg/maxresdefault.jpg" alt="Codebase Indexing" style={{ width: '100%', height: 'auto', borderRadius: '8px', display: 'block' }} />
<div style={{ marginTop: '0.0rem', textAlign: 'center', fontWeight: 600, fontSize: '1rem' }}>Codebase Indexing</div>
</a>
<a href="https://www.youtube.com/watch?v=iiAv1eKOaxk" target="_blank" rel="noopener noreferrer" style={{ textDecoration: 'none', color: 'inherit' }}>
<img src="https://img.youtube.com/vi/iiAv1eKOaxk/maxresdefault.jpg" alt="Custom Modes" style={{ width: '100%', height: 'auto', borderRadius: '8px', display: 'block' }} />
<div style={{ marginTop: '0.0rem', textAlign: 'center', fontWeight: 600, fontSize: '1rem' }}>Custom Modes</div>
</a>
<a href="https://www.youtube.com/watch?v=Ho30nyY332E" target="_blank" rel="noopener noreferrer" style={{ textDecoration: 'none', color: 'inherit' }}>
<img src="https://img.youtube.com/vi/Ho30nyY332E/maxresdefault.jpg" alt="Checkpoints" style={{ width: '100%', height: 'auto', borderRadius: '8px', display: 'block' }} />
<div style={{ marginTop: '0.0rem', textAlign: 'center', fontWeight: 600, fontSize: '1rem' }}>Checkpoints</div>
</a>
<a href="https://www.youtube.com/watch?v=6h5vB9PpoPk" target="_blank" rel="noopener noreferrer" style={{ textDecoration: 'none', color: 'inherit' }}>
<img src="https://img.youtube.com/vi/6h5vB9PpoPk/maxresdefault.jpg" alt="Todo Lists" style={{ width: '100%', height: 'auto', borderRadius: '8px', display: 'block' }} />
<div style={{ marginTop: '0.0rem', textAlign: 'center', fontWeight: 600, fontSize: '1rem' }}>Todo Lists</div>
</a>
</div>
<p style={{ textAlign: 'center', marginTop: '1rem' }}>
<a href="/tutorial-videos">More quick tutorial and feature videos...</a>
</p>
## Additional Resources
- [Discord Server](https://discord.gg/roocode): Join the community for real-time help and discussion.
- [Reddit Community](https://www.reddit.com/r/RooCode): Share your experiences and see what others are building.
- [YouTube Channel](https://youtube.com/@roocodeyt?feature=shared): Watch tutorials and see features in action.
- [GitHub Issues](https://github.com/RooCodeInc/Roo-Code/issues): Report bugs and track development.
- [Feature Requests](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop): Have an idea? Share it with the team.

17
apps/docs/docs/providers/openai-chatgpt-plus-pro.md
View file

@ -12,23 +12,6 @@ keywords:
- subscription
---
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0, overflow: 'hidden' }}>
<iframe
src="https://www.youtube.com/embed/c1IXRMl5i0g?rel=0&modestbranding=1"
title="OpenAI – ChatGPT Plus/Pro provider setup"
style={{
position: 'absolute',
top: 0,
left: 0,
width: '100%',
height: '100%',
}}
frameBorder="0"
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
allowFullScreen
></iframe>
</div>
---
## Quickstart: Connect your subscription to Roo Code

5
apps/docs/docs/providers/requesty.md
View file

@ -55,8 +55,3 @@ For the complete, up-to-date model list with pricing, see [Requesty's model list
* **Prompt Caching:** Some providers support prompt caching. [Search models with caching](https://app.requesty.ai/router/list).
---
## Relevant resources
- [Requesty Youtube channel](https://www.youtube.com/@requestyAI):
- [Requesty Discord](https://requesty.ai/discord)

3
apps/docs/docs/reporting-errors.md
View file

@ -35,7 +35,7 @@ The Error Details modal offers two buttons, each serving different needs:
- Provider and model being used
- The specific error message
**Use when:** You want to quickly share the error in Discord or a brief support email.
**Use when:** You want to quickly share the error in a brief support email.
2. **Get detailed error info** - Opens a full diagnostic report with:
@ -55,7 +55,6 @@ The Error Details modal offers two buttons, each serving different needs:
After copying error information:
- **Email**: Send to [support@roocode.com](mailto:support@roocode.com)
- **Discord**: Share in the [#support channel](https://discord.gg/roocode)
- **GitHub Issues**: File at [github.com/RooCodeInc/Roo-Code/issues](https://github.com/RooCodeInc/Roo-Code/issues)
Include a brief description of what you were trying to do when the error occurred. The exported diagnostics handle the technical details.

72
apps/docs/docs/tutorial-videos.json
View file

@ -1,72 +0,0 @@
{
"videos": [
{
"id": "Mcq3r1EPZ-4",
"title": "Installing Roo Code"
},
{
"id": "ZBML8h5cCgo",
"title": "Configuring Profiles"
},
{
"id": "VAbadUDhH5c",
"title": "Setting up MCP Servers"
},
{
"id": "bWtIxGsl2cQ",
"title": "Auto Approve Feature"
},
{
"id": "iiAv1eKOaxk",
"title": "Custom Modes"
},
{
"id": "Ho30nyY332E",
"title": "Checkpoints"
},
{
"id": "r1bpod1VWhg",
"title": "Codebase Indexing"
},
{
"id": "9k8OAXlszak",
"title": "Context Condensing"
},
{
"id": "WatooxMlW0U",
"title": "Roo Marketplace"
},
{
"id": "6h5vB9PpoPk",
"title": "Todo Lists"
},
{
"id": "IOpmeUGLpg0",
"title": "Slash Commands"
},
{
"id": "cAjzTs0194c",
"title": "Browser Use"
},
{
"id": "_Op3VfLPEu8",
"title": "Code Actions"
},
{
"id": "rkWBHeG9A-4",
"title": "Terminal Integration"
},
{
"id": "HmnNSasv7T8",
"title": "Context Management"
},
{
"id": "BRrhcYYSh9M",
"title": "Worktrees"
},
{
"id": "1992Rpfc800",
"title": "Skills"
}
]
}

17
apps/docs/docs/tutorial-videos.mdx
View file

@ -1,17 +0,0 @@
---
description: Watch comprehensive video tutorials to learn how to use Roo Code effectively. From basics to advanced features, master AI-assisted development.
keywords:
- Roo Code tutorials
- video tutorials
- AI coding tutorials
- learn Roo Code
- video guides
---
import VideoGrid from '@site/src/components/VideoGrid';
# Tutorial Videos
Learn how to build powerful applications and enhance your development workflow with these hands-on Roo Code tutorials. Big thanks to all of the creators!
<VideoGrid />

3
apps/docs/docs/update-notes/v3.0.1.md
View file

@ -1,9 +1,7 @@
---
description: Roo Code 3.0.1 fixes the community Reddit link and resolves a minor visual glitch in the chat input area for improved user experience.
keywords:
- roo code
- v3.0.1
- reddit link fix
- visual glitch
- chat input
- patch release
@ -19,5 +17,4 @@ This patch release fixes a link and a minor visual glitch.
## Fixes
- Fixed the community Reddit link.
- Fixed a small visual glitch in the chat input area.

4
apps/docs/docs/update-notes/v3.0.md
View file

@ -1,5 +1,4 @@
---
description: Roo Code 3.0 introduces Chat Modes for specialized interactions, launches Reddit community, and includes various UI fixes and compatibility updates.
keywords:
- roo code
- v3.0
@ -7,7 +6,6 @@ keywords:
- ask mode
- architect mode
- code mode
- reddit community
- ui fixes
- release cycle
- release notes
@ -25,13 +23,11 @@ This release cycle marked the introduction of Chat Modes in Roo Code, allowing u
- Ask questions about system architecture or the codebase.
- Engage in higher-level discussions before code implementation.
- Assign different API configuration profiles to each mode, enabling the use of different models for thinking versus coding.
- **Roo Code Reddit Community:** Launched the [Roo Code Reddit](https://www.reddit.com/r/RooCode) for feedback and community interaction.
---
## Bug Fixes & Minor Updates
- **Reddit Link Fix (v3.0.1):** Corrected the Reddit link in the application.
- **Chat Input Visual Glitch (v3.0.1):** Fixed a small visual glitch in the chat input.
- **Button Alignment Tweaks (v3.0.2):** Made minor adjustments to button alignment in the chat input.
- **VSCode Engine Requirement (v3.0.3):** Updated the required VSCode engine to `^1.84.0` to align with Cline.

3
apps/docs/docs/update-notes/v3.18.0.mdx
View file

@ -15,8 +15,6 @@ Watch a quick overview:
<div style={{width: '50%', margin: 'auto'}}>
<div style={{position: 'relative', paddingBottom: '177.77%', height: 0, overflow: 'hidden'}}>
<iframe
src="https://www.youtube.com/embed/o5xgO9N8vVU?rel=0&modestbranding=1"
title="YouTube Short"
frameBorder="0"
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
allowFullScreen
@ -31,7 +29,6 @@ Key updates:
For full details, see the main [Intelligent Context Condensing documentation](/features/intelligent-context-condensing).
---
## Custom Modes: YAML Support

5
apps/docs/docs/update-notes/v3.18.mdx
View file

@ -41,8 +41,6 @@ Watch a quick overview:
<div style={{width: '50%', margin: 'auto'}}>
<div style={{position: 'relative', paddingBottom: '177.77%', height: 0, overflow: 'hidden'}}>
<iframe
src="https://www.youtube.com/embed/o5xgO9N8vVU?rel=0&modestbranding=1"
title="YouTube Short"
frameBorder="0"
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
allowFullScreen
@ -59,7 +57,6 @@ Key updates:
For full details, see the main [Intelligent Context Condensing documentation](/features/intelligent-context-condensing).
---
## Custom Modes: YAML Support
@ -162,4 +159,4 @@ Access the latest `gemini-2.5-flash-preview-05-20` model, including its thinking
* **Simplified Loop Syntax**: Refactored loop structures in multiple components to use `for...of` loops for improved readability. (thanks noritaka1166!)
* **Telemetry**: Re-enable telemetry
These improvements work behind the scenes to provide a more reliable and stable extension experience with faster updates and higher quality releases.
These improvements work behind the scenes to provide a more reliable and stable extension experience with faster updates and higher quality releases.

3
apps/docs/docs/update-notes/v3.19.1.mdx
View file

@ -38,11 +38,10 @@ Enterprise customers can now use Roo Code with AWS Bedrock while maintaining com
* **AWS Bedrock Conversations**: Resolved context condensing error that required conversations to start with user messages
* **Terminal UTF-8 Encoding**: Fixed encoding errors when running Ruby/CocoaPods commands (thanks mr-ryan-james!)
* **Sidebar Context Menus**: Resolved empty menu items by properly setting sidebar name (thanks chrarnoldus!)
* **Documentation Links**: Fixed broken CONTRIBUTING.md link in feature request template (thanks cannuri!)
---
## Misc Improvements
* **Backend Task Tracking**: Added metadata to Unbound API requests for improved service reliability (thanks pugazhendhi-m!)
* **Model-Specific Caching**: Optimized cache strategies for Gemini and Anthropic models for better performance
* **Model-Specific Caching**: Optimized cache strategies for Gemini and Anthropic models for better performance

3
apps/docs/docs/update-notes/v3.20.0.mdx
View file

@ -8,7 +8,6 @@ This release introduces the experimental Marketplace for extensions and modes, c
## MCP & Mode Marketplace (experimental)
We've introduced an experimental [Marketplace](/features/marketplace) for discovering and installing community-contributed extensions and modes. This feature allows you to:
- Browse and search for new modes and MCP servers
- Install items at project or global scope
- Manage installations directly from the Marketplace view
@ -73,4 +72,4 @@ Navigate your prompt history with a terminal-like experience using the arrow key
## Internal
* **Integration Tests**: Added core tools integration tests for comprehensive coverage ([#4433](https://github.com/RooCodeInc/Roo-Code/pull/4433)).
* **Integration Tests**: Added core tools integration tests for comprehensive coverage ([#4433](https://github.com/RooCodeInc/Roo-Code/pull/4433)).

3
apps/docs/docs/update-notes/v3.20.mdx
View file

@ -14,7 +14,6 @@ This release introduces the experimental Marketplace for extensions and modes, c
## MCP & Mode Marketplace (experimental)
We've introduced an experimental [Marketplace](/features/marketplace) for discovering and installing community-contributed extensions and modes. This feature allows you to:
- Browse and search for new modes and MCP servers
- Install items at project or global scope
- Manage installations directly from the Marketplace view
@ -111,4 +110,4 @@ Navigate your prompt history with a terminal-like experience using the arrow key
## Internal
* **Integration Tests**: Added core tools integration tests for comprehensive coverage ([#4433](https://github.com/RooCodeInc/Roo-Code/pull/4433)).
* **Integration Tests**: Added core tools integration tests for comprehensive coverage ([#4433](https://github.com/RooCodeInc/Roo-Code/pull/4433)).

3
apps/docs/docs/update-notes/v3.23.15.mdx
View file

@ -17,7 +17,6 @@ This release improves diagnostics handling, UI accessibility, and includes vario
* **Go Diagnostics**: Configurable delay prevents false error reports about unused imports (thanks mmhobi7!) ([#5863](https://github.com/RooCodeInc/Roo-Code/pull/5863))
* **Marketplace Access**: Marketplace icon moved to top navigation for easier access ([#5864](https://github.com/RooCodeInc/Roo-Code/pull/5864))
* **Custom Modes**: Added helpful descriptions and usage guidance to custom modes (thanks RandalSchwartz!) ([#5862](https://github.com/RooCodeInc/Roo-Code/pull/5862))
* **YouTube Footer**: Quick access to Roo Code's YouTube channel from the website (thanks thill2323!) ([#5929](https://github.com/RooCodeInc/Roo-Code/pull/5929))
* **PR Templates**: Issue-fixer mode now uses the official Roo Code PR template (thanks MuriloFP!) ([#5839](https://github.com/RooCodeInc/Roo-Code/pull/5839))
## Bug Fixes
@ -27,4 +26,4 @@ This release improves diagnostics handling, UI accessibility, and includes vario
## Misc Improvements
* **Command Timeout Configuration**: Added command timeout allowlist for long-running commands ([#5910](https://github.com/RooCodeInc/Roo-Code/pull/5910))
* **Internal Modes**: Added Issue Investigator mode and enhanced Issue Writer mode for internal GitHub workflows ([#5913](https://github.com/RooCodeInc/Roo-Code/pull/5913))
* **Internal Modes**: Added Issue Investigator mode and enhanced Issue Writer mode for internal GitHub workflows ([#5913](https://github.com/RooCodeInc/Roo-Code/pull/5913))

1
apps/docs/docs/update-notes/v3.23.mdx
View file

@ -106,7 +106,6 @@ We've added native Windows support for the Claude Code provider (thanks Sannidhy
- **Go Diagnostics**: Configurable delay prevents false error reports about unused imports (thanks mmhobi7!)
- **Marketplace Access**: Marketplace icon moved to top navigation for easier access
- **Custom Modes**: Added helpful descriptions and usage guidance to custom modes (thanks RandalSchwartz!)
- **YouTube Footer**: Quick access to Roo Code's YouTube channel from the website (thanks thill2323!)
- **PR Templates**: Issue-fixer mode now uses the official Roo Code PR template (thanks MuriloFP!)
- **Jump to New Files**: Added jump icon for newly created files, matching the experience of edited files (thanks mkdir700!)
- **Apply Diff Error Messages**: Added case sensitivity reminder when apply_diff fails, helping users understand matching requirements (thanks maskelihileci!)

1
apps/docs/docs/update-notes/v3.3.md
View file

@ -110,4 +110,3 @@ This extensive release cycle brings a wealth of features including native VS Cod
- Improved DeepSeek R1 support. (thanks @Szpadel!)
- Sped up diff editing. (thanks @hannesrudolph, @KyleHerndon!)
- Thrown errors sooner for restricted file writes.
- New Roo Code community Discord.

1
apps/docs/docs/update-notes/v3.48.0.mdx
View file

@ -32,7 +32,6 @@ The History view now renders the complete nested subtask hierarchy as an expanda
* **`disabledTools` Setting**: Administrators can globally disable specific native tools via the new `disabledTools` extension or organization setting. Disabled tools are stripped from API requests and blocked at execution time, targeting enterprise deployments that require restricted tool access. ([#11277](https://github.com/RooCodeInc/Roo-Code/pull/11277))
* **Nine Providers Retired**: Cerebras, Chutes, DeepInfra, Doubao, Featherless, Groq, Hugging Face, IO Intelligence, and Unbound have been removed. Existing saved configurations will display a retirement message in Settings rather than a broken config form; your credentials are preserved until you explicitly delete them. ([#11297](https://github.com/RooCodeInc/Roo-Code/pull/11297))
* **Browser Tool Removed**: The built-in Puppeteer-based `browser_action` tool has been removed along with all related settings, the browser session panel, and the `puppeteer-core` dependencies. Migrate to [Playwright MCP](https://github.com/microsoft/playwright-mcp) or another MCP-based browser tool. ([#11392](https://github.com/RooCodeInc/Roo-Code/pull/11392))
* **Built-in Skills Removed**: The bundled `create-mcp-server` and `create-mode` skills and all built-in skills infrastructure have been removed. Skills now come exclusively from your global (`~/.roo/skills/`) and workspace (`.roo/skills/`) directories. All skills now have edit and delete buttons. Find community-contributed skills at [skills.sh](https://skills.sh). ([#11414](https://github.com/RooCodeInc/Roo-Code/pull/11414))
* **File-Based System Prompt Override Removed**: The `.roo/system-prompt-{mode}` file override mechanism has been removed along with the in-chat warning banner and the "Advanced: Override System Prompt" disclosure in Mode settings. Migrate to custom instructions or mode-level prompt customization. ([#11387](https://github.com/RooCodeInc/Roo-Code/pull/11387))
* **Linear Integration in Cloud UI**: The Roomote Control tile in the Cloud features grid has been replaced with a Linear Integration tile. ([#11280](https://github.com/RooCodeInc/Roo-Code/pull/11280))

17
apps/docs/docusaurus.config.ts
View file

@ -2,13 +2,10 @@ import { themes as prismThemes } from "prism-react-renderer"
import type { Config } from "@docusaurus/types"
import type * as Preset from "@docusaurus/preset-classic"
import {
DISCORD_URL,
REDDIT_URL,
TWITTER_URL,
BLUESKY_URL,
GITHUB_MAIN_REPO_URL,
GITHUB_ISSUES_MAIN_URL,
GITHUB_FEATURES_URL,
VSCODE_MARKETPLACE_URL,
OPEN_VSX_URL,
EXTENSION_PRIVACY_URL,
@ -395,16 +392,8 @@ const config: Config = {
},
links: [
{
title: "Community",
title: "Social",
items: [
{
label: "Discord",
href: DISCORD_URL,
},
{
label: "Reddit",
href: REDDIT_URL,
},
{
label: "Twitter",
href: TWITTER_URL,
@ -426,10 +415,6 @@ const config: Config = {
label: "Issues",
href: GITHUB_ISSUES_MAIN_URL,
},
{
label: "Feature Requests",
href: GITHUB_FEATURES_URL,
},
],
},
{

11
apps/docs/sidebars.ts
View file

@ -113,7 +113,6 @@ const sidebars: SidebarsConfig = {
"advanced-usage/context-poisoning",
"advanced-usage/large-projects",
"advanced-usage/local-models",
"advanced-usage/local-development-setup",
"advanced-usage/prompt-engineering",
"advanced-usage/prompt-structure",
"advanced-usage/rate-limits-costs",
@ -122,11 +121,6 @@ const sidebars: SidebarsConfig = {
},
],
},
{
type: "doc",
label: "Tutorial Videos",
id: "tutorial-videos",
},
{
type: "category",
label: "Model Providers",
@ -833,11 +827,6 @@ const sidebars: SidebarsConfig = {
label: "FAQ",
id: "faq",
},
{
type: "link",
label: "Contributing (GitHub)",
href: "https://github.com/RooCodeInc/Roo-Code/blob/main/CONTRIBUTING.md",
},
{
type: "link",
label: "Roocabulary (GitHub)",

33
apps/docs/src/components/NavbarSocialIcons/index.tsx
View file

@ -1,36 +1,5 @@
import React from "react"
import { FaReddit, FaDiscord } from "react-icons/fa6"
import { REDDIT_URL, DISCORD_URL } from "@site/src/constants"
import styles from "./styles.module.css"
export default function NavbarSocialIcons(): React.JSX.Element {
const socialLinks = [
{
href: REDDIT_URL,
icon: FaReddit,
label: "Reddit",
},
{
href: DISCORD_URL,
icon: FaDiscord,
label: "Discord",
},
]
return (
<div className={styles.socialIcons}>
{socialLinks.map(({ href, icon: Icon, label }) => (
<a
key={label}
href={href}
target="_blank"
rel="noopener noreferrer"
className={styles.socialLink}
title={label}
aria-label={label}>
<Icon />
</a>
))}
</div>
)
return <></>
}

14
apps/docs/src/components/SocialIcons/index.tsx
View file

@ -1,6 +1,6 @@
import React from "react"
import { FaBluesky, FaDiscord, FaGithub, FaReddit, FaXTwitter } from "react-icons/fa6"
import { DISCORD_URL, REDDIT_URL, TWITTER_URL, BLUESKY_URL, GITHUB_MAIN_REPO_URL } from "../../constants"
import { FaBluesky, FaGithub, FaXTwitter } from "react-icons/fa6"
import { TWITTER_URL, BLUESKY_URL, GITHUB_MAIN_REPO_URL } from "../../constants"
const SocialIcons: React.FC = () => {
const socialLinks = [
@ -9,16 +9,6 @@ const SocialIcons: React.FC = () => {
icon: FaGithub,
label: "GitHub",
},
{
href: DISCORD_URL,
icon: FaDiscord,
label: "Discord",
},
{
href: REDDIT_URL,
icon: FaReddit,
label: "Reddit",
},
{
href: TWITTER_URL,
icon: FaXTwitter,

127
apps/docs/src/components/VideoGrid.tsx
View file

@ -1,127 +0,0 @@
import React, { useRef } from "react"
import videos from "@site/docs/tutorial-videos.json"
interface Video {
id: string
title: string
}
export default function VideoGrid(): React.JSX.Element {
const videoRefs = useRef<{ [key: string]: HTMLDivElement | null }>({})
const scrollToVideo = (videoId: string) => {
const element = videoRefs.current[videoId]
if (element) {
element.scrollIntoView({ behavior: "smooth", block: "center" })
}
}
return (
<div>
{/* Table of Contents */}
<div
className="video-toc"
style={{
marginBottom: "2rem",
padding: "1.5rem",
backgroundColor: "var(--ifm-background-surface-color)",
borderRadius: "8px",
border: "1px solid var(--ifm-color-emphasis-200)",
}}>
<h3 style={{ marginTop: 0, marginBottom: "1rem" }}>Videos</h3>
<ol
style={{
listStylePosition: "inside",
paddingLeft: 0,
marginBottom: 0,
}}>
{videos.videos.map((video: Video) => (
<li
key={`toc-${video.id}`}
style={{
marginBottom: "0.5rem",
cursor: "pointer",
color: "var(--ifm-color-primary)",
}}>
<a
onClick={(e) => {
e.preventDefault()
scrollToVideo(video.id)
}}
style={{
cursor: "pointer",
textDecoration: "none",
color: "inherit",
}}
onMouseEnter={(e) => {
e.currentTarget.style.textDecoration = "underline"
}}
onMouseLeave={(e) => {
e.currentTarget.style.textDecoration = "none"
}}>
{video.title}
</a>
</li>
))}
</ol>
</div>
{/* Video Grid */}
<div className="video-grid">
{videos.videos.map((video: Video) => (
<div
key={video.id}
className="video-item"
ref={(el) => {
videoRefs.current[video.id] = el
}}>
<div
className="video-container"
onClick={(e) => {
const target = e.currentTarget
target.innerHTML = `<iframe src='https://www.youtube.com/embed/${video.id}?autoplay=1&rel=0&modestbranding=1' title='${video.title}' allow='accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture' allowFullScreen></iframe>`
}}>
<img
src={`https://img.youtube.com/vi/${video.id}/maxresdefault.jpg`}
alt={video.title}
style={{
width: "100%",
height: "100%",
position: "absolute",
top: 0,
left: 0,
cursor: "pointer",
}}
/>
<div
style={{
position: "absolute",
top: "50%",
left: "50%",
transform: "translate(-50%,-50%)",
width: "68px",
height: "48px",
background: "rgba(0,0,0,0.7)",
borderRadius: "12px",
}}>
<div
style={{
borderStyle: "solid",
borderWidth: "12px 0 12px 20px",
borderColor: "transparent transparent transparent white",
position: "absolute",
top: "12px",
left: "26px",
}}
/>
</div>
</div>
<div className="video-info">
<span className="video-title">{video.title}</span>
</div>
</div>
))}
</div>
</div>
)
}

4
apps/docs/src/constants.ts
View file

@ -7,16 +7,12 @@ export const GITHUB_REPO_URL = "https://github.com/RooCodeInc/Roo-Code"
export const GITHUB_ISSUES_URL = `${GITHUB_REPO_URL}/issues`
export const GITHUB_NEW_ISSUE_URL = `${GITHUB_ISSUES_URL}/new`
// Community links
export const DISCORD_URL = "https://discord.gg/roocode"
export const REDDIT_URL = "https://www.reddit.com/r/RooCode/"
export const TWITTER_URL = "https://x.com/roocode"
export const BLUESKY_URL = "https://bsky.app/profile/roocode.bsky.social"
// GitHub links
export const GITHUB_MAIN_REPO_URL = "https://github.com/RooCodeInc/Roo-Code"
export const GITHUB_ISSUES_MAIN_URL = `${GITHUB_MAIN_REPO_URL}/issues`
export const GITHUB_FEATURES_URL = `${GITHUB_MAIN_REPO_URL}/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop`
// Download links
export const VSCODE_MARKETPLACE_URL = "https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline"

48
apps/docs/src/css/custom.css
View file

@ -2400,54 +2400,6 @@ a.breadcrumbs__link:hover {
}
}
/* ============================================
CUSTOM TUTORIAL VIDEOS SIDEBAR STYLES
============================================ */
/* Move external link icons to the right for Tutorial Videos */
.menu__list-item a[href^="https://www.youtube.com/watch"]
{
display: flex !important;
justify-content: space-between !important;
align-items: center !important;
padding-right: 0.5rem !important;
width: 100% !important;
}
/* Ensure the link text takes up available space */
.menu__list-item a[href^="https://www.youtube.com/watch"] .menu__link-text
{
flex: 1 !important;
overflow: hidden !important;
text-overflow: ellipsis !important;
white-space: nowrap !important;
margin-right: 0.5rem !important;
}
/* Move the external link icon (svg) to the right */
.menu__list-item a[href^="https://www.youtube.com/watch"] svg
{
order: 2 !important;
margin-left: auto !important;
margin-right: 0 !important;
flex-shrink: 0 !important;
width: 13px !important;
height: 13px !important;
opacity: 0.6 !important;
}
/* Show icon more prominently on hover */
.menu__list-item a[href^="https://www.youtube.com/watch"]:hover svg
{
opacity: 1 !important;
}
/* Ensure consistent spacing for all tutorial video links */
.menu__list-item:has(> a[href^="https://www.youtube.com/watch"])
{
margin-bottom: 0 !important;
}
/* ============================================
FIX: SEARCH INPUT TINY BUBBLE ON MOBILE
============================================ */

5
apps/docs/src/theme/Footer/Links/MultiColumn/index.tsx
View file

@ -23,11 +23,6 @@ function ColumnLinkItem({ item }: { item: ColumnItemType }) {
}
function Column({ column }: { column: ColumnType }) {
// Skip Community section since social icons are now in the brand area
if (column.title === "Community") {
return null
}
return (
<div className={clsx(ThemeClassNames.layout.footer.column, "col footer__col", column.className)}>
<div className="footer__title">{column.title}</div>

2
apps/web-roo-code/package.json
View file

@ -10,7 +10,7 @@
"postbuild": "next-sitemap --config next-sitemap.config.cjs",
"start": "next start",
"clean": "rimraf .next .turbo",
"test": "vitest run",
"test": "vitest run --passWithNoTests",
"test:watch": "vitest"
},
"dependencies": {

282
apps/web-roo-code/src/components/blog/BlogContent.tsx
View file

@ -3,68 +3,16 @@
import * as React from "react"
import ReactMarkdown from "react-markdown"
import remarkGfm from "remark-gfm"
import { Play } from "lucide-react"
import { YouTubeModal, isYouTubeUrl, extractYouTubeVideoId, extractYouTubeTimestamp } from "./YouTubeModal"
type HastLikeNode = {
type?: unknown
tagName?: unknown
url?: unknown
properties?: unknown
children?: unknown
}
function getNodeUrl(node: HastLikeNode): string | null {
// mdast link node (remark)
if (node.type === "link" && typeof node.url === "string") return node.url
// hast anchor element (rehype)
if (node.type === "element" && node.tagName === "a") {
const props = node.properties as { href?: unknown } | undefined
if (typeof props?.href === "string") return props.href
}
return null
}
function nodeHasYouTubeLink(node: unknown): boolean {
if (!node || typeof node !== "object") return false
const anyNode = node as HastLikeNode
const url = getNodeUrl(anyNode)
if (url && isYouTubeUrl(url)) {
return true
}
const children = (anyNode as { children?: unknown }).children
if (Array.isArray(children)) {
return children.some(nodeHasYouTubeLink)
}
return false
}
interface BlogContentProps {
/** The markdown content to render */
content: string
}
/**
* State for the currently active YouTube video modal
*/
interface YouTubeModalState {
isOpen: boolean
videoId: string
startTime: number
title: string
}
/**
* BlogContent component
*
* Renders markdown content with special handling for YouTube links.
* YouTube links open in a modal with embedded video player instead of
* navigating away from the page.
* Renders markdown content with site-specific typography and link behavior.
*
* @example
* ```tsx
@ -72,169 +20,81 @@ interface YouTubeModalState {
* ```
*/
export function BlogContent({ content }: BlogContentProps) {
const [youtubeModal, setYoutubeModal] = React.useState<YouTubeModalState>({
isOpen: false,
videoId: "",
startTime: 0,
title: "",
})
/**
* Opens the YouTube modal with the specified video
*/
const openYouTubeModal = React.useCallback((url: string, linkText: string) => {
const videoId = extractYouTubeVideoId(url)
if (!videoId) return
const startTime = extractYouTubeTimestamp(url)
setYoutubeModal({
isOpen: true,
videoId,
startTime,
title: linkText,
})
}, [])
/**
* Closes the YouTube modal
*/
const closeYouTubeModal = React.useCallback(() => {
setYoutubeModal((prev) => ({ ...prev, isOpen: false }))
}, [])
return (
<>
<ReactMarkdown
remarkPlugins={[remarkGfm]}
components={{
// Custom heading styles - note: h1 in content becomes h2 to preserve single H1
h1: ({ node: _node, ...props }) => <h2 className="mt-12 text-2xl font-bold" {...props} />,
h2: ({ node: _node, ...props }) => <h2 className="mt-12 text-2xl font-bold" {...props} />,
h3: ({ node: _node, ...props }) => <h3 className="mt-8 text-xl font-semibold" {...props} />,
// Custom link component with YouTube modal support
a: ({ href, children, node: _node }) => {
const url = href ?? ""
const linkText =
typeof children === "string"
? children
: Array.isArray(children)
? children.join("")
: "YouTube Video"
// Check if this is a YouTube link
if (isYouTubeUrl(url)) {
return (
<button
type="button"
onClick={(e) => {
e.preventDefault()
openYouTubeModal(url, linkText)
}}
className="inline-flex items-baseline gap-1 text-primary hover:underline">
<Play className="relative top-px h-4 w-4" />
{children}
</button>
)
}
// Regular external link - opens in new tab
<ReactMarkdown
remarkPlugins={[remarkGfm]}
components={{
// Custom heading styles - note: h1 in content becomes h2 to preserve single H1
h1: ({ node: _node, ...props }) => <h2 className="mt-12 text-2xl font-bold" {...props} />,
h2: ({ node: _node, ...props }) => <h2 className="mt-12 text-2xl font-bold" {...props} />,
h3: ({ node: _node, ...props }) => <h3 className="mt-8 text-xl font-semibold" {...props} />,
// Regular external links open in a new tab.
a: ({ href, children }) => {
return (
<a className="text-primary hover:underline" target="_blank" rel="noopener noreferrer" href={href}>
{children}
</a>
)
},
// Styled blockquotes
blockquote: ({ ...props }) => {
return (
<blockquote
className={[
// Opt out of Tailwind Typography's automatic quote marks for blockquotes.
"not-prose my-6 border-l-4 border-primary pl-4 text-muted-foreground",
// Normalize paragraph spacing inside blockquotes regardless of our global <p> renderer.
"[&>p]:m-0 [&>p+ p]:mt-4",
"italic",
].join(" ")}
{...props}
/>
)
},
// Code blocks
code: ({ className, children, node: _node, ...props }) => {
const isInline = !className
if (isInline) {
return (
<a
className="text-primary hover:underline"
target="_blank"
rel="noopener noreferrer"
href={href}>
{children}
</a>
)
},
// Styled blockquotes
blockquote: ({ node, ...props }) => {
const children = (node as { children?: unknown[] } | undefined)?.children
const lastNonTextChild = Array.isArray(children)
? [...children].reverse().find((c) => {
if (!c || typeof c !== "object") return false
const anyChild = c as { type?: unknown }
// mdast uses "paragraph"; hast uses "element"
return anyChild.type === "paragraph" || anyChild.type === "element"
})
: null
const isAttributedQuote = nodeHasYouTubeLink(lastNonTextChild)
return (
<blockquote
className={[
// Opt out of Tailwind Typography's automatic quote marks for blockquotes.
"not-prose my-6 border-l-4 border-primary pl-4 text-muted-foreground",
// Normalize paragraph spacing inside blockquotes regardless of our global <p> renderer.
"[&>p]:m-0 [&>p+ p]:mt-4",
isAttributedQuote
? [
// Quote text reads well in italics, but the attribution line shouldn't.
"[&>p:not(:last-child)]:italic",
"[&>p:last-child]:not-italic",
].join(" ")
: "italic",
].join(" ")}
{...props}
/>
)
},
// Code blocks
code: ({ className, children, node: _node, ...props }) => {
const isInline = !className
if (isInline) {
return (
<code className="rounded bg-muted px-1.5 py-0.5 text-sm" {...props}>
{children}
</code>
)
}
return (
<code className={className} {...props}>
<code className="rounded bg-muted px-1.5 py-0.5 text-sm" {...props}>
{children}
</code>
)
},
// Strong text
strong: ({ node: _node, ...props }) => <strong className="font-semibold" {...props} />,
// Paragraphs
p: ({ node: _node, ...props }) => <p className="leading-7 [&:not(:first-child)]:mt-6" {...props} />,
// Lists
ul: ({ node: _node, ...props }) => <ul className="my-6 ml-6 list-disc [&>li]:mt-2" {...props} />,
ol: ({ node: _node, ...props }) => <ol className="my-6 ml-6 list-decimal [&>li]:mt-2" {...props} />,
// Tables with zebra striping (visible in both light and dark mode)
table: ({ node: _node, ...props }) => (
<div className="not-prose my-6 w-full overflow-x-auto rounded-lg border border-border">
<table className="w-full border-collapse text-sm" {...props} />
</div>
),
thead: ({ node: _node, ...props }) => <thead className="bg-muted" {...props} />,
tbody: ({ node: _node, ...props }) => <tbody {...props} />,
tr: ({ node: _node, ...props }) => (
<tr
className="border-b border-border last:border-b-0 transition-colors even:bg-muted/70 hover:bg-muted"
{...props}
/>
),
th: ({ node: _node, ...props }) => (
<th className="px-4 py-3 text-left font-semibold text-foreground" {...props} />
),
td: ({ node: _node, ...props }) => <td className="px-4 py-3" {...props} />,
}}>
{content}
</ReactMarkdown>
{/* YouTube Video Modal */}
<YouTubeModal
open={youtubeModal.isOpen}
onOpenChange={closeYouTubeModal}
videoId={youtubeModal.videoId}
startTime={youtubeModal.startTime}
title={youtubeModal.title}
/>
</>
}
return (
<code className={className} {...props}>
{children}
</code>
)
},
// Strong text
strong: ({ node: _node, ...props }) => <strong className="font-semibold" {...props} />,
// Paragraphs
p: ({ node: _node, ...props }) => <p className="leading-7 [&:not(:first-child)]:mt-6" {...props} />,
// Lists
ul: ({ node: _node, ...props }) => <ul className="my-6 ml-6 list-disc [&>li]:mt-2" {...props} />,
ol: ({ node: _node, ...props }) => <ol className="my-6 ml-6 list-decimal [&>li]:mt-2" {...props} />,
// Tables with zebra striping (visible in both light and dark mode)
table: ({ node: _node, ...props }) => (
<div className="not-prose my-6 w-full overflow-x-auto rounded-lg border border-border">
<table className="w-full border-collapse text-sm" {...props} />
</div>
),
thead: ({ node: _node, ...props }) => <thead className="bg-muted" {...props} />,
tbody: ({ node: _node, ...props }) => <tbody {...props} />,
tr: ({ node: _node, ...props }) => (
<tr
className="border-b border-border last:border-b-0 transition-colors even:bg-muted/70 hover:bg-muted"
{...props}
/>
),
th: ({ node: _node, ...props }) => (
<th className="px-4 py-3 text-left font-semibold text-foreground" {...props} />
),
td: ({ node: _node, ...props }) => <td className="px-4 py-3" {...props} />,
}}>
{content}
</ReactMarkdown>
)
}

140
apps/web-roo-code/src/components/blog/YouTubeModal.test.ts
View file

@ -1,140 +0,0 @@
import { describe, it, expect } from "vitest"
import { extractYouTubeVideoId, extractYouTubeTimestamp, isYouTubeUrl } from "./YouTubeModal"
describe("isYouTubeUrl", () => {
it("should return true for youtube.com/watch URLs", () => {
expect(isYouTubeUrl("https://www.youtube.com/watch?v=dQw4w9WgXcQ")).toBe(true)
expect(isYouTubeUrl("http://youtube.com/watch?v=dQw4w9WgXcQ")).toBe(true)
expect(isYouTubeUrl("https://youtube.com/watch?v=abc123_-XYZ")).toBe(true)
})
it("should return true for youtu.be URLs", () => {
expect(isYouTubeUrl("https://youtu.be/dQw4w9WgXcQ")).toBe(true)
expect(isYouTubeUrl("http://youtu.be/abc123_-XYZ")).toBe(true)
})
it("should return true for youtube.com/embed URLs", () => {
expect(isYouTubeUrl("https://www.youtube.com/embed/dQw4w9WgXcQ")).toBe(true)
})
it("should return true for youtube.com/v URLs", () => {
expect(isYouTubeUrl("https://www.youtube.com/v/dQw4w9WgXcQ")).toBe(true)
})
it("should return false for non-YouTube URLs", () => {
expect(isYouTubeUrl("https://www.google.com")).toBe(false)
expect(isYouTubeUrl("https://vimeo.com/123456")).toBe(false)
expect(isYouTubeUrl("https://example.com/youtube.com")).toBe(false)
})
it("should return false for invalid URLs", () => {
expect(isYouTubeUrl("not a url")).toBe(false)
expect(isYouTubeUrl("")).toBe(false)
})
})
describe("extractYouTubeVideoId", () => {
it("should extract video ID from youtube.com/watch URLs", () => {
expect(extractYouTubeVideoId("https://www.youtube.com/watch?v=dQw4w9WgXcQ")).toBe("dQw4w9WgXcQ")
expect(extractYouTubeVideoId("https://www.youtube.com/watch?v=abc123_-XYZ&list=PLxyz")).toBe("abc123_-XYZ")
expect(extractYouTubeVideoId("https://www.youtube.com/watch?feature=share&v=dQw4w9WgXcQ")).toBe("dQw4w9WgXcQ")
})
it("should extract video ID from youtu.be URLs", () => {
expect(extractYouTubeVideoId("https://youtu.be/dQw4w9WgXcQ")).toBe("dQw4w9WgXcQ")
expect(extractYouTubeVideoId("https://youtu.be/abc123_-XYZ?t=42")).toBe("abc123_-XYZ")
})
it("should extract video ID from youtube.com/embed URLs", () => {
expect(extractYouTubeVideoId("https://www.youtube.com/embed/dQw4w9WgXcQ")).toBe("dQw4w9WgXcQ")
})
it("should extract video ID from youtube.com/v URLs", () => {
expect(extractYouTubeVideoId("https://www.youtube.com/v/dQw4w9WgXcQ")).toBe("dQw4w9WgXcQ")
})
it("should return null for non-YouTube URLs", () => {
expect(extractYouTubeVideoId("https://www.google.com")).toBeNull()
expect(extractYouTubeVideoId("https://vimeo.com/123456")).toBeNull()
})
it("should return null for invalid URLs", () => {
expect(extractYouTubeVideoId("not a url")).toBeNull()
expect(extractYouTubeVideoId("")).toBeNull()
})
})
describe("extractYouTubeTimestamp", () => {
describe("numeric timestamps (seconds)", () => {
it("should extract timestamp in seconds from youtube.com URLs", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=42")).toBe(42)
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?t=120&v=dQw4w9WgXcQ")).toBe(120)
})
it("should extract timestamp from youtu.be URLs", () => {
expect(extractYouTubeTimestamp("https://youtu.be/dQw4w9WgXcQ?t=42")).toBe(42)
expect(extractYouTubeTimestamp("https://youtu.be/dQw4w9WgXcQ?t=3600")).toBe(3600)
})
it("should extract timestamp from start= URLs", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ&start=42")).toBe(42)
expect(extractYouTubeTimestamp("https://www.youtube.com/embed/dQw4w9WgXcQ?start=120")).toBe(120)
})
it("should extract timestamp from fragment (#t=) URLs", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ#t=42")).toBe(42)
})
})
describe("h/m/s format timestamps", () => {
it("should parse hours, minutes, and seconds", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=1h2m3s")).toBe(3723) // 1*3600 + 2*60 + 3
})
it("should parse minutes and seconds", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=2m30s")).toBe(150) // 2*60 + 30
})
it("should parse seconds only", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=45s")).toBe(45)
})
it("should parse hours and minutes", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=1h30m")).toBe(5400) // 1*3600 + 30*60
})
it("should parse hours only", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=2h")).toBe(7200) // 2*3600
})
it("should be case-insensitive", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=1H2M3S")).toBe(3723)
})
})
describe("colon-separated timestamps", () => {
it("should parse mm:ss format", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=1:23")).toBe(83)
})
it("should parse hh:mm:ss format", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=1:02:03")).toBe(3723)
})
})
describe("edge cases", () => {
it("should return 0 when no timestamp is present", () => {
expect(extractYouTubeTimestamp("https://www.youtube.com/watch?v=dQw4w9WgXcQ")).toBe(0)
expect(extractYouTubeTimestamp("https://youtu.be/dQw4w9WgXcQ")).toBe(0)
})
it("should return 0 for non-YouTube URLs", () => {
expect(extractYouTubeTimestamp("https://www.google.com")).toBe(0)
})
it("should return 0 for invalid URLs", () => {
expect(extractYouTubeTimestamp("not a url")).toBe(0)
expect(extractYouTubeTimestamp("")).toBe(0)
})
})
})

171
apps/web-roo-code/src/components/blog/YouTubeModal.tsx
View file

@ -1,171 +0,0 @@
"use client"
import * as React from "react"
import { Dialog, DialogContent, DialogTitle } from "@/components/ui/modal"
/**
* YouTube URL patterns and utilities
*/
/** Regular expression to match YouTube URLs and extract video ID */
const YOUTUBE_URL_REGEX = /(?:youtube\.com\/(?:[^/]+\/.+\/|(?:v|e(?:mbed)?)\/|.*[?&]v=)|youtu\.be\/)([^"&?/\s]{11})/i
/**
* Regular expression to extract timestamp from YouTube URLs.
*
* Supports:
* - query params: `t=123`, `t=1h2m3s`, `start=123`, `t=1:23`, `t=1:02:03`
* - fragment params: `#t=123` (less common but seen in some links)
*/
const TIMESTAMP_REGEX = /(?:[?&#](?:t|start)=)([0-9hms:]+)/i
/**
* Extracts the video ID from a YouTube URL
* Supports various YouTube URL formats:
* - https://www.youtube.com/watch?v=VIDEO_ID
* - https://youtu.be/VIDEO_ID
* - https://www.youtube.com/embed/VIDEO_ID
* - https://www.youtube.com/v/VIDEO_ID
*
* @param url - The YouTube URL to parse
* @returns The video ID or null if not found
*/
export function extractYouTubeVideoId(url: string): string | null {
const match = url.match(YOUTUBE_URL_REGEX)
return match?.[1] ?? null
}
/**
* Parses a YouTube timestamp string to seconds
* Supports formats like:
* - "123" (seconds)
* - "1h2m3s" (hours, minutes, seconds)
* - "2m30s" (minutes and seconds)
* - "45s" (seconds only)
*
* @param timestamp - The timestamp string
* @returns The timestamp in seconds
*/
function parseTimestampToSeconds(timestamp: string): number {
// If it's just a number, it's already in seconds
if (/^\d+$/.test(timestamp)) {
return parseInt(timestamp, 10)
}
// Parse colon-separated formats:
// - "mm:ss"
// - "hh:mm:ss"
const colonMatch = timestamp.match(/^(\d{1,2}):(\d{2})(?::(\d{2}))?$/)
if (colonMatch) {
const a = parseInt(colonMatch[1] ?? "0", 10)
const b = parseInt(colonMatch[2] ?? "0", 10)
const c = colonMatch[3] ? parseInt(colonMatch[3], 10) : null
if (c === null) return a * 60 + b
return a * 3600 + b * 60 + c
}
// Parse h/m/s format
let totalSeconds = 0
const hours = timestamp.match(/(\d+)h/i)
const minutes = timestamp.match(/(\d+)m/i)
const seconds = timestamp.match(/(\d+)s/i)
if (hours?.[1]) totalSeconds += parseInt(hours[1], 10) * 3600
if (minutes?.[1]) totalSeconds += parseInt(minutes[1], 10) * 60
if (seconds?.[1]) totalSeconds += parseInt(seconds[1], 10)
return totalSeconds
}
/**
* Extracts the start time (in seconds) from a YouTube URL
*
* @param url - The YouTube URL to parse
* @returns The start time in seconds or 0 if not found
*/
export function extractYouTubeTimestamp(url: string): number {
const match = url.match(TIMESTAMP_REGEX)
if (!match?.[1]) return 0
return parseTimestampToSeconds(match[1])
}
/**
* Checks if a URL is a YouTube URL
*
* @param url - The URL to check
* @returns True if the URL is a YouTube URL
*/
export function isYouTubeUrl(url: string): boolean {
return YOUTUBE_URL_REGEX.test(url)
}
interface YouTubeModalProps {
/** Whether the modal is open */
open: boolean
/** Callback when the modal open state changes */
onOpenChange: (open: boolean) => void
/** The YouTube video ID */
videoId: string
/** The start time in seconds (optional) */
startTime?: number
/** The video title for accessibility (optional) */
title?: string
}
/**
* YouTubeModal component
*
* A modal dialog that embeds a YouTube video player.
* Supports starting playback at a specific timestamp.
*
* @example
* ```tsx
* <YouTubeModal
* open={isOpen}
* onOpenChange={setIsOpen}
* videoId="dQw4w9WgXcQ"
* startTime={42}
* title="Never Gonna Give You Up"
* />
* ```
*/
export function YouTubeModal({ open, onOpenChange, videoId, startTime = 0, title }: YouTubeModalProps) {
// Build the YouTube embed URL with parameters
const embedUrl = React.useMemo(() => {
const params = new URLSearchParams({
autoplay: "1",
rel: "0", // Don't show related videos from other channels
modestbranding: "1", // Minimal YouTube branding
})
if (startTime > 0) {
params.set("start", startTime.toString())
}
return `https://www.youtube.com/embed/${videoId}?${params.toString()}`
}, [videoId, startTime])
return (
<Dialog open={open} onOpenChange={onOpenChange}>
<DialogContent className="max-w-4xl w-[90vw] p-0 overflow-hidden bg-black" aria-describedby={undefined}>
{/* Visually hidden title for accessibility */}
<DialogTitle className="sr-only">{title ?? "YouTube Video"}</DialogTitle>
<div className="relative w-full pt-[56.25%]">
{/* 16:9 aspect ratio container */}
{open && (
<iframe
className="absolute inset-0 w-full h-full"
src={embedUrl}
title={title ?? "YouTube Video"}
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
allowFullScreen
/>
)}
</div>
</DialogContent>
</Dialog>
)
}
export default YouTubeModal

45
apps/web-roo-code/src/components/chromes/footer.tsx
View file

@ -101,24 +101,6 @@ export function Footer() {
Issues
</a>
</li>
<li>
<a
href={EXTERNAL_LINKS.FEATURE_REQUESTS}
target="_blank"
rel="noopener noreferrer"
className="text-sm leading-6 text-muted-foreground transition-colors hover:text-foreground">
Feature Requests
</a>
</li>
<li>
<a
href={EXTERNAL_LINKS.OFFICE_HOURS_PODCAST}
target="_blank"
rel="noopener noreferrer"
className="text-sm leading-6 text-muted-foreground transition-colors hover:text-foreground">
Office Hours Podcast
</a>
</li>
</ul>
</div>
</div>
@ -205,24 +187,6 @@ export function Footer() {
GitHub
</a>
</li>
<li>
<a
href={EXTERNAL_LINKS.DISCORD}
target="_blank"
rel="noopener noreferrer"
className="text-sm leading-6 text-muted-foreground transition-colors hover:text-foreground">
Discord
</a>
</li>
<li>
<a
href={EXTERNAL_LINKS.REDDIT}
target="_blank"
rel="noopener noreferrer"
className="text-sm leading-6 text-muted-foreground transition-colors hover:text-foreground">
Reddit
</a>
</li>
<li>
<a
href={EXTERNAL_LINKS.X}
@ -232,15 +196,6 @@ export function Footer() {
X / Twitter
</a>
</li>
<li>
<a
href={EXTERNAL_LINKS.YOUTUBE}
target="_blank"
rel="noopener noreferrer"
className="text-sm leading-6 text-muted-foreground transition-colors hover:text-foreground">
YouTube
</a>
</li>
</ul>
</div>
</div>

18
apps/web-roo-code/src/components/chromes/nav-bar.tsx
View file

@ -61,16 +61,6 @@ export function NavBar({ stars, downloads }: NavBarProps) {
<Link href="/blog">Blog</Link>
</NavigationMenuLink>
</NavigationMenuItem>
<NavigationMenuItem>
<NavigationMenuLink
asChild
className={cn(navigationMenuTriggerStyle(), "bg-transparent font-light")}>
<a href={EXTERNAL_LINKS.DISCORD} target="_blank" rel="noopener noreferrer">
Discord
</a>
</NavigationMenuLink>
</NavigationMenuItem>
</NavigationMenuList>
</NavigationMenu>
@ -141,14 +131,6 @@ export function NavBar({ stars, downloads }: NavBarProps) {
onClick={() => setIsMenuOpen(false)}>
FAQ
</ScrollButton>
<a
href={EXTERNAL_LINKS.DISCORD}
target="_blank"
rel="noopener noreferrer"
className="block w-full p-5 py-3 text-left text-foreground active:opacity-50"
onClick={() => setIsMenuOpen(false)}>
Discord
</a>
</div>
{/* Bottom section with Cloud Login and stats */}

58
apps/web-roo-code/src/components/homepage/faq-section.tsx
View file

@ -155,38 +155,6 @@ const faqs: FAQItem[] = [
</>
),
},
{
question: "Can I contribute to Roo Code?",
answer: (
<>
Yes, please do! Roo Code is open-source on{" "}
<a
href="https://github.com/RooCodeInc/Roo-Code"
target="_blank"
rel="noopener noreferrer"
className="text-primary underline-offset-4 hover:underline">
GitHub
</a>
. Submit issues, suggest features, or open a pull request. There&apos;s also an active community on{" "}
<a
href="https://discord.gg/roocode"
target="_blank"
rel="noopener noreferrer"
className="text-primary underline-offset-4 hover:underline">
Discord
</a>{" "}
and{" "}
<a
href="https://reddit.com/r/RooCode"
target="_blank"
rel="noopener noreferrer"
className="text-primary underline-offset-4 hover:underline">
Reddit
</a>{" "}
if you want to share feedback or help others.
</>
),
},
{
question: "Where can I learn more or get help?",
answer: (
@ -199,31 +167,7 @@ const faqs: FAQItem[] = [
className="text-primary underline-offset-4 hover:underline">
official documentation
</a>{" "}
for both a quick-start set up and advanced guides. You can also get community support on{" "}
<a
href="https://discord.gg/roocode"
target="_blank"
rel="noopener noreferrer"
className="text-primary underline-offset-4 hover:underline">
Discord
</a>{" "}
and{" "}
<a
href="https://reddit.com/r/RooCode"
target="_blank"
rel="noopener noreferrer"
className="text-primary underline-offset-4 hover:underline">
Reddit
</a>
. You can also check out our{" "}
<a
href="https://www.youtube.com/@RooCodeYT"
target="_blank"
rel="noopener noreferrer"
className="text-primary underline-offset-4 hover:underline">
YouTube
</a>{" "}
tutorials and{" "}
for both a quick-start set up and advanced guides. You can also check out our{" "}
<a
href="https://blog.roocode.com"
target="_blank"

2
apps/web-roo-code/src/components/homepage/features.tsx
View file

@ -62,7 +62,7 @@ export const features: Feature[] = [
icon: GitPullRequest,
title: "Proudly open source",
description:
"Community-driven and fully auditable: no throttling or surprises about what's happening behind the scenes.",
"Fully auditable: no throttling or surprises about what's happening behind the scenes.",
},
{
icon: Shield,

4
apps/web-roo-code/src/components/homepage/testimonials.tsx
View file

@ -47,7 +47,7 @@ export const testimonials: Testimonial[] = [
name: "Darien Hardin",
role: "Reviewer",
origin: "VS Code Marketplace",
quote: "By far the best coding tool I have used. Looking forward to where this goes in the future. Also, their Discord is an excellent resource with many knowledgeable users sharing their discoveries.",
quote: "By far the best coding tool I have used. Looking forward to where this goes in the future.",
stars: 5,
},
{
@ -89,7 +89,7 @@ export const testimonials: Testimonial[] = [
name: "Edwin Jacques",
role: "Reviewer",
origin: "VS Code Marketplace",
quote: "The BEST. Super fast, no-nonsense, UI that makes sense, many API provider choices, responsive, helpful developer community.",
quote: "The BEST. Super fast, no-nonsense, UI that makes sense, many API provider choices, responsive, and helpful.",
stars: 5,
},
{

6
apps/web-roo-code/src/content/blog/ai-best-practices-spread-through-internal-influencers-not-topdown-mandates.md
View file

@ -35,13 +35,13 @@ What works instead is something Netflix discovered through practice, not theory.
> "I think that's probably the model that has happened organically at Netflix is look at the people who are the most effective and try to do what they're doing."
>
> David Leen, [Office Hours S01E04](https://www.youtube.com/watch?v=ZnKkwWuQ9QQ&t=1628)
> David Leen, Office Hours S01E04
The insight: every engineering org already has internal influencers. Developers that others watch and emulate. When one of these engineers shares a prompt or recommends a tool, people try it. Not because of a mandate. Because trust already exists.
> "A term that I like to use is almost like influencers. Developers that other people see, wow, this is a 10x developer or look how productive she is. And when that person speaks everyone listens and when they say try this as your prompt or I found this tool to be amazing, people around them try to emulate them."
>
> David Leen, [Office Hours S01E04](https://www.youtube.com/watch?v=ZnKkwWuQ9QQ&t=1584)
> David Leen, Office Hours S01E04
This isn't about creating evangelists from scratch. It's about identifying who already has influence and giving them time and space to experiment.
@ -51,7 +51,7 @@ Identifying influencers is step one. Step two is creating forums where they can
> "We have monthly get-togethers at the company where people can demo what they've built, shared lessons learned and that usually has like a two to three hundred engineer audience every month and that's been super valuable for sharing what's new."
>
> David Leen, [Office Hours S01E04](https://www.youtube.com/watch?v=ZnKkwWuQ9QQ&t=2465)
> David Leen, Office Hours S01E04
The format matters. A demo with a live audience is different from a doc in a wiki. Demos show what actually works. They invite questions. They create social proof in real time.

6
apps/web-roo-code/src/content/blog/manage-ai-spend-by-measuring-return-not-cost.md
View file

@ -35,7 +35,7 @@ The technical capability to track individual spend exists. You authenticate to u
> "I could actually get down to it because you have to authenticate to use tokens and so then there's a tracking to amount of tokens per person but I don't. I'm kind of staying away from that. I think it will lead to bad mindset and bad behavior."
>
> JB Brown, [Roo Cast S01E17](https://www.youtube.com/watch?v=R4U89z9eGPg&t=824)
> JB Brown, Roo Cast S01E17
The tracking is possible. The question is whether you should. Per-person dashboards create the exact cost anxiety that undermines the productivity gain you're paying for.
@ -45,7 +45,7 @@ Smartsheet took the opposite path. They moved all AI tool spend into a single ac
> "Here we're trying to drive return, not trying to reduce cost. And so to get that mindset shift and behavior and practice shift, I'm sort of precluding people from thinking about the cost too much."
>
> JB Brown, [Roo Cast S01E17](https://www.youtube.com/watch?v=R4U89z9eGPg&t=748)
> JB Brown, Roo Cast S01E17
The goal is explicit: shift the mental model from "how do I spend less?" to "how do I ship more?"
@ -57,7 +57,7 @@ Their answer: MR throughput. Merge requests completed. Commits merged. Work ship
> "We would measure it by MR throughput. And that's what we're trying to drive towards as that outcome."
>
> JB Brown, [Roo Cast S01E17](https://www.youtube.com/watch?v=R4U89z9eGPg&t=668)
> JB Brown, Roo Cast S01E17
This is the difference between treating AI as an expense line and treating it as a productivity lever. Expenses get minimized. Levers get pulled. A frontier model costs a fraction of an intern's hourly rate but can iterate on code continuously. The return-on-cost math favors spending more, not less.

6
apps/web-roo-code/src/content/blog/non-engineers-stopped-waiting-for-engineers-to-unblock-them.md
View file

@ -31,7 +31,7 @@ At Roo Vet, the behavior changed. Product managers, support reps, and operations
> "One nonobvious behavior change that came out of that I think is people don't wait around to be unblocked anymore. Non-engineers especially just ask our @roomote agent first."
>
> John Sterns, [Roo Cast S01E11](https://www.youtube.com/watch?v=bqLEMZ1c9Uk&t=290)
> John Sterns, Roo Cast S01E11
## The shift: ask the agent first
@ -43,7 +43,7 @@ The answers come from the codebase itself. Not tribal knowledge. Not someone's m
> "I use @roomote every day to ask questions about the codebase. I think that is the most effective thing as a PM."
>
> Theo, [Roo Cast S01E11](https://www.youtube.com/watch?v=bqLEMZ1c9Uk&t=2288)
> Theo, Roo Cast S01E11
## What the queries look like
@ -59,7 +59,7 @@ With a codebase-connected agent, the answer comes back fast.
> "You can ask it questions to better understand the logic that's been built into the product... it took me like 30 seconds to find that answer."
>
> Audrey, [Roo Cast S01E11](https://www.youtube.com/watch?v=bqLEMZ1c9Uk)
> Audrey, Roo Cast S01E11
## The tradeoff

2
apps/web-roo-code/src/content/blog/over-half-of-googles-production-code-is-now-aigenerated.md
View file

@ -29,7 +29,7 @@ At Google, more than half of the code checked into production each week is gener
> "Each week, over 50% of the code that gets checked in, and through code review, is accepted, isn't rolled back, is generated by AI."
>
> Paige Bailey, [Office Hours S01E15](https://www.youtube.com/watch?v=sAFQIqmDFL4&t=2328)
> Paige Bailey, Office Hours S01E15
This is not a demo. This is not a projection. This is the current state of one of the world's largest engineering organizations.

6
apps/web-roo-code/src/content/blog/prds-are-becoming-artifacts-of-the-past.md
View file

@ -33,7 +33,7 @@ This is what Paige Bailey observed at Google: teams are abandoning the rigorous
> "Now things are moving so fast that even if you had a PRD that was perfect as of January, it would not be perfect as of February."
>
> Paige Bailey, [Office Hours S01E15](https://www.youtube.com/watch?v=sAFQIqmDFL4&t=2760)
> Paige Bailey, Office Hours S01E15
## The shift: prototypes as specification
@ -43,7 +43,7 @@ Instead of writing a spec and then building, teams build something small and ite
> "For software, it's much more effective to get something out and keep iterating on it really really quickly."
>
> Paige Bailey, [Office Hours S01E15](https://www.youtube.com/watch?v=sAFQIqmDFL4&t=3003)
> Paige Bailey, Office Hours S01E15
This works because AI tooling has compressed the cost of producing working code. When you can generate a functional prototype in an afternoon, the economics of "plan first, build second" flip. The sunk cost of writing a detailed PRD becomes harder to justify when you could have shipped the first version instead.
@ -89,7 +89,7 @@ The compounding effect: teams that treat prototypes as the specification ship mo
> "I also feel like we don't have nearly as rigorous of a process around PRDs. PRDs kind of feel like an artifact of the past."
>
> Paige Bailey, [Office Hours S01E15](https://www.youtube.com/watch?v=sAFQIqmDFL4&t=2739)
> Paige Bailey, Office Hours S01E15
## The decision

2
apps/web-roo-code/src/content/blog/score-agents-like-employees-not-like-models.md
View file

@ -37,7 +37,7 @@ Some of the teams building these agents grade them differently. They treat the a
> "If you design your coding evals like you would a software engineer performance review, then you can measure their ability in the same ways as you can measure somebody who's coding."
>
> Brian Fioca, [Roo Cast S01E16](https://www.youtube.com/watch?v=Nu5TeVQbOOE&t=1225)
> Brian Fioca, Roo Cast S01E16
The rubric he described:

2
apps/web-roo-code/src/content/blog/sunsetting-roo-code-extension-cloud-and-router.md
View file

@ -14,7 +14,7 @@ featured: true
As you may have heard, we're sunsetting the Roo Code suite of tools on May 15th. This includes the Roo Code VS Code Extension, Roo Code Cloud, and Roo Code Router.
To our community: thank you. Your trust, contributions, and feedback helped us drive innovation in this space and pushed us past 3m extension downloads. We don't take that lightly.
Thank you to everyone who used Roo Code and shared feedback. Your trust helped us drive innovation in this space and pushed us past 3m extension downloads. We don't take that lightly.
That said, we don't believe IDEs are the future of coding. To keep pushing the future forward, we needed to make this difficult decision. You can read more about the reasoning behind it [here](https://x.com/mattrubens/status/2046636598859559114).

7
apps/web-roo-code/src/lib/constants.ts
View file

@ -1,27 +1,20 @@
export const EXTERNAL_LINKS = {
GITHUB: "https://github.com/RooCodeInc/Roo-Code",
GITHUB_DISCUSSIONS: "https://github.com/RooCodeInc/Roo-Code/discussions",
DISCORD: "https://discord.gg/roocode",
REDDIT: "https://reddit.com/r/RooCode",
X: "https://x.com/roocode",
LINKEDIN: "https://www.linkedin.com/company/roo-code",
TIKTOK: "https://www.tiktok.com/@roo.code",
BLUESKY: "https://bsky.app/profile/roocode.bsky.social",
YOUTUBE: "https://www.youtube.com/@RooCodeYT",
DOCUMENTATION: "https://docs.roocode.com",
SLACK_DOCS: "https://docs.roocode.com/roo-code-cloud/slack-integration",
CAREERS: "https://careers.roocode.com",
ISSUES: "https://github.com/RooCodeInc/Roo-Code/issues",
FEATURE_REQUESTS: "https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests",
COMMUNITY: "https://github.com/RooCodeInc/Roo-Code/discussions",
CHANGELOG: "https://github.com/RooCodeInc/Roo-Code/blob/main/CHANGELOG.md",
PRIVACY_POLICY_EXTENSION: "https://github.com/RooCodeInc/Roo-Code/blob/main/PRIVACY.md",
INTEGRATIONS: "https://docs.roocode.com/community",
TUTORIALS: "https://docs.roocode.com/tutorial-videos",
MARKETPLACE: "https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline",
SECURITY: "https://trust.roocode.com",
BLOG_SUBSTACK: "https://blog.roocode.com",
OFFICE_HOURS_PODCAST: "https://www.youtube.com/@RooCodeYT/podcasts",
FAQ: "https://roocode.com/#faq",
TESTIMONIALS: "https://roocode.com/#testimonials",
CLOUD_APP_LOGIN: "https://app.roocode.com/sign-in",

3
apps/web-roo-code/src/lib/structured-data.ts
View file

@ -83,9 +83,6 @@ export function getStructuredData(): StructuredDataGraph {
EXTERNAL_LINKS.MARKETPLACE,
EXTERNAL_LINKS.X,
EXTERNAL_LINKS.LINKEDIN,
EXTERNAL_LINKS.REDDIT,
EXTERNAL_LINKS.DISCORD,
EXTERNAL_LINKS.YOUTUBE,
],
}

90
locales/ca/CODE_OF_CONDUCT.md generated
View file

@ -1,90 +0,0 @@
<div align="center">
<sub>
[English](../../CODE_OF_CONDUCT.md) • <b>Català</b> • [Deutsch](../de/CODE_OF_CONDUCT.md) • [Español](../es/CODE_OF_CONDUCT.md) • [Français](../fr/CODE_OF_CONDUCT.md) • [हिंदी](../hi/CODE_OF_CONDUCT.md) • [Bahasa Indonesia](../id/CODE_OF_CONDUCT.md) • [Italiano](../it/CODE_OF_CONDUCT.md) • [日本語](../ja/CODE_OF_CONDUCT.md)
</sub>
<sub>
[한국어](../ko/CODE_OF_CONDUCT.md) • [Nederlands](../nl/CODE_OF_CONDUCT.md) • [Polski](../pl/CODE_OF_CONDUCT.md) • [Português (BR)](../pt-BR/CODE_OF_CONDUCT.md) • [Русский](../ru/CODE_OF_CONDUCT.md) • [Türkçe](../tr/CODE_OF_CONDUCT.md) • [Tiếng Việt](../vi/CODE_OF_CONDUCT.md) • [简体中文](../zh-CN/CODE_OF_CONDUCT.md) • [繁體中文](../zh-TW/CODE_OF_CONDUCT.md)
</sub>
</div>
# Codi de Conducta del Pacte de Col·laboradors
## El nostre Compromís
En interès de fomentar un entorn obert i acollidor, nosaltres, com a
col·laboradors i mantenidors, ens comprometem a fer de la participació en el nostre projecte i
la nostra comunitat una experiència lliure d'assetjament per a tothom, independentment de l'edat, mida
corporal, discapacitat, ètnia, característiques sexuals, identitat i expressió de gènere,
nivell d'experiència, educació, estatus socioeconòmic, nacionalitat, aparença
personal, raça, religió, o identitat i orientació sexual.
## Els nostres Estàndards
Exemples de comportament que contribueix a crear un entorn positiu
inclouen:
- Utilitzar llenguatge acollidor i inclusiu
- Respectar els diferents punts de vista i experiències
- Acceptar amb gràcia les crítiques constructives
- Centrar-se en el que és millor per a la comunitat
- Mostrar empatia envers altres membres de la comunitat
Exemples de comportament inacceptable per part dels participants inclouen:
- L'ús de llenguatge o imatges sexualitzades i atencions o
avenços sexuals no desitjats
- Trolling, comentaris insultants/despectius, i atacs personals o polítics
- Assetjament públic o privat
- Publicar informació privada d'altres persones, com ara informació física o electrònica
adreça, sense permís explícit
- Altres conductes que raonablement podrien considerar-se inadequades en un
entorn professional
## Les nostres Responsabilitats
Els mantenidors del projecte són responsables de clarificar els estàndards de comportament
acceptable i s'espera que prenguin mesures correctives apropiades i justes en
resposta a qualsevol cas de comportament inacceptable.
Els mantenidors del projecte tenen el dret i la responsabilitat d'eliminar, editar o
rebutjar comentaris, commits, codi, edicions wiki, incidències i altres contribucions
que no estiguin alineades amb aquest Codi de Conducta, o de prohibir temporalment o
permanentment qualsevol col·laborador per altres comportaments que considerin inapropiats,
amenaçadors, ofensius o perjudicials.
## Àmbit
Aquest Codi de Conducta s'aplica tant als espais del projecte com als espais públics
quan un individu representa el projecte o la seva comunitat. Exemples de
representació d'un projecte o comunitat inclouen l'ús d'un correu electrònic oficial del projecte,
publicar mitjançant un compte oficial de xarxes socials, o actuar com a representant designat
en un esdeveniment en línia o fora de línia. La representació d'un projecte pot ser
definida i clarificada addicionalment pels mantenidors del projecte.
## Aplicació
Els casos de comportament abusiu, assetjador o altrament inacceptable poden ser
reportats contactant amb l'equip del projecte a support@roocode.com. Totes les queixes
seran revisades i investigades i resultaran en una resposta que
es consideri necessària i adequada a les circumstàncies. L'equip del projecte està
obligat a mantenir la confidencialitat respecte al reportador d'un incident.
Es poden publicar separadament més detalls de polítiques d'aplicació específiques.
Els mantenidors del projecte que no segueixin o apliquin el Codi de Conducta de bona
fe poden enfrontar-se a repercussions temporals o permanents determinades per altres
membres del lideratge del projecte.
## Atribució
Aquest Codi de Conducta està adaptat de la [versió de Cline][cline_coc] del [Pacte de Col·laboradors][homepage], versió 1.4,
disponible a https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[cline_coc]: https://github.com/cline/cline/blob/main/CODE_OF_CONDUCT.md
[homepage]: https://www.contributor-covenant.org
Per a respostes a preguntes freqüents sobre aquest codi de conducta, vegeu
https://www.contributor-covenant.org/faq

141
locales/ca/CONTRIBUTING.md generated
View file

@ -1,141 +0,0 @@
<div align="center">
<sub>
[English](../../CONTRIBUTING.md) • <b>Català</b> • [Deutsch](../de/CONTRIBUTING.md) • [Español](../es/CONTRIBUTING.md) • [Français](../fr/CONTRIBUTING.md) • [हिंदी](../hi/CONTRIBUTING.md) • [Bahasa Indonesia](../id/CONTRIBUTING.md) • [Italiano](../it/CONTRIBUTING.md) • [日本語](../ja/CONTRIBUTING.md)
</sub>
<sub>
[한국어](../ko/CONTRIBUTING.md) • [Nederlands](../nl/CONTRIBUTING.md) • [Polski](../pl/CONTRIBUTING.md) • [Português (BR)](../pt-BR/CONTRIBUTING.md) • [Русский](../ru/CONTRIBUTING.md) • [Türkçe](../tr/CONTRIBUTING.md) • [Tiếng Việt](../vi/CONTRIBUTING.md) • [简体中文](../zh-CN/CONTRIBUTING.md) • [繁體中文](../zh-TW/CONTRIBUTING.md)
</sub>
</div>
# Contribuir a Roo Code
Roo Code és un projecte impulsat per la comunitat i valorem profundament cada contribució. Per agilitzar la col·laboració, operem sobre una base de [primer la incidència](#enfocament-de-primera-incidència), la qual cosa significa que totes les [sol·licituds d'extracció (PR)](#enviament-duna-sollicitud-dextracció) primer han d'estar enllaçades a una incidència de GitHub. Si us plau, reviseu aquesta guia amb atenció.
## Taula de continguts
- [Abans de contribuir](#abans-de-contribuir)
- [Trobar i planificar la vostra contribució](#trobar-i-planificar-la-vostra-contribució)
- [Procés de desenvolupament i submissió](#procés-de-desenvolupament-i-submissió)
- [Legal](#legal)
## Abans de contribuir
### 1. Codi de Conducta
Tots els col·laboradors han de complir el nostre [Codi de Conducta](./CODE_OF_CONDUCT.md).
### 2. Full de ruta del projecte
El nostre full de ruta guia la direcció del projecte. Alineeu les vostres contribucions amb aquests objectius clau:
### La fiabilitat primer
- Assegureu-vos que l'edició de diferències i l'execució d'ordres siguin fiables de manera consistent.
- Reduïu els punts de fricció que desincentiven l'ús habitual.
- Garantiu un funcionament fluid en tots els llocs i plataformes.
- Amplieu el suport robust per a una àmplia varietat de proveïdors i models d'IA.
### Experiència d'usuari millorada
- Agilitzeu la interfície d'usuari/experiència d'usuari per a més claredat i intuïtivitat.
- Milloreu contínuament el flux de treball per satisfer les altes expectatives que els desenvolupadors tenen de les eines d'ús diari.
### Liderant en rendiment d'agents
- Establir punts de referència d'avaluació complets (evals) per mesurar la productivitat del món real.
- Feu que sigui fàcil per a tothom executar i interpretar aquestes avaluacions.
- Envieu millores que demostrin augments clars en les puntuacions d'avaluació.
Mencioneu l'alineació amb aquestes àrees a les vostres sol·licituds d'extracció.
### 3. Uniu-vos a la comunitat de Roo Code
- **Principal:** Uniu-vos al nostre [Discord](https://discord.gg/roocode) i envieu un missatge directe a **Hannes Rudolph (`hrudolph`)**.
- **Alternativa:** Els col·laboradors experimentats poden participar directament a través de [Projectes de GitHub](https://github.com/orgs/RooCodeInc/projects/1).
## Trobar i planificar la vostra contribució
### Tipus de contribucions
- **Correccions d'errors:** abordar problemes de codi.
- **Noves característiques:** afegir funcionalitats.
- **Documentació:** millorar les guies i la claredat.
### Enfocament de primera incidència
Totes les contribucions comencen amb una incidència de GitHub utilitzant les nostres plantilles bàsiques.
- **Comproveu les incidències existents**: cerqueu a [Incidències de GitHub](https://github.com/RooCodeInc/Roo-Code/issues).
- **Creeu una incidència** utilitzant:
- **Millores:** plantilla "Sol·licitud de millora" (llenguatge senzill centrat en el benefici per a l'usuari).
- **Errors:** plantilla "Informe d'error" (reproducció mínima + esperat vs real + versió).
- **Voleu treballar-hi?** Comenteu "Reclamant" a la incidència i envieu un missatge directe a **Hannes Rudolph (`hrudolph`)** a [Discord](https://discord.gg/roocode) per ser assignat. L'assignació es confirmarà al fil.
- **Les sol·licituds d'extracció han d'enllaçar a la incidència.** Les sol·licituds d'extracció no enllaçades es poden tancar.
### Decidir en què treballar
- Consulteu el [Projecte de GitHub](https://github.com/orgs/RooCodeInc/projects/1) per a incidències "Incidència [No assignada]".
- Per a documents, visiteu [Documents de Roo Code](https://github.com/RooCodeInc/Roo-Code-Docs).
### Informar d'errors
- Comproveu primer si hi ha informes existents.
- Creeu un error nou utilitzant la [plantilla "Informe d'error"](https://github.com/RooCodeInc/Roo-Code/issues/new/choose) amb:
- Passos de reproducció clars i numerats
- Resultat esperat vs real
- Versió de Roo Code (obligatori); proveïdor/model d'API si és rellevant
- **Problemes de seguretat**: informeu de manera privada a través d' [avisos de seguretat](https://github.com/RooCodeInc/Roo-Code/security/advisories/new).
## Procés de desenvolupament i submissió
### Configuració del desenvolupament
1. **Bifurcació i clonació:**
```
git clone https://github.com/EL_TEU_NOM_USUARI/Roo-Code.git
```
2. **Instal·leu les dependències:**
```
pnpm install
```
3. **Depuració:** Obriu amb VS Code (`F5`).
### Directrius per escriure codi
- Una sol·licitud d'extracció centrada per característica o correcció.
- Seguiu les millors pràctiques d'ESLint i TypeScript.
- Escriviu confirmacions clares i descriptives que facin referència a incidències (p. ex., `Soluciona #123`).
- Proporcioneu proves exhaustives (`npm test`).
- Rebaseu a la branca `main` més recent abans de la submissió.
### Enviament d'una sol·licitud d'extracció
- Comenceu com a **PR d'esborrany** si busqueu comentaris primerencs.
- Descriviu clarament els vostres canvis seguint la plantilla de sol·licitud d'extracció.
- Enllaceu la incidència a la descripció/títol de la PR (p. ex., "Soluciona #123").
- Proporcioneu captures de pantalla/vídeos per a canvis a la interfície d'usuari.
- Indiqueu si calen actualitzacions de la documentació.
### Política de sol·licitud d'extracció
- Ha de fer referència a una incidència de GitHub assignada. Per ser assignat: comenteu "Reclamant" a la incidència i envieu un missatge directe a **Hannes Rudolph (`hrudolph`)** a [Discord](https://discord.gg/roocode). L'assignació es confirmarà al fil.
- Les sol·licituds d'extracció no enllaçades es poden tancar.
- Les sol·licituds d'extracció han de passar les proves de CI, alinear-se amb el full de ruta i tenir una documentació clara.
### Procés de revisió
- **Triatge diari:** revisions ràpides per part dels mantenidors.
- **Revisió setmanal en profunditat:** avaluació completa.
- **Itereu ràpidament** en funció dels comentaris.
## Legal
En contribuir, accepteu que les vostres contribucions es llicenciaran sota la llicència Apache 2.0, d'acord amb la llicència de Roo Code.

117
locales/ca/README.md generated
View file

@ -1,32 +1,11 @@
<p align="center">
<a href="https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline"><img src="https://img.shields.io/badge/VS_Code_Marketplace-007ACC?style=flat&logo=visualstudiocode&logoColor=white" alt="VS Code Marketplace"></a>
<a href="https://x.com/roocode"><img src="https://img.shields.io/badge/roocode-000000?style=flat&logo=x&logoColor=white" alt="X"></a>
<a href="https://youtube.com/@roocodeyt?feature=shared"><img src="https://img.shields.io/badge/YouTube-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube"></a>
<a href="https://discord.gg/roocode"><img src="https://img.shields.io/badge/Join%20Discord-5865F2?style=flat&logo=discord&logoColor=white" alt="Join Discord"></a>
<a href="https://www.reddit.com/r/RooCode/"><img src="https://img.shields.io/badge/Join%20r%2FRooCode-FF4500?style=flat&logo=reddit&logoColor=white" alt="Join r/RooCode"></a>
</p>
<p align="center">
<em>Obté ajuda ràpidament → <a href="https://discord.gg/roocode">Uneix-te a Discord</a> • Prefereixes l'asíncron? → <a href="https://www.reddit.com/r/RooCode/">Uneix-te a r/RooCode</a></em>
</p>
# Roo Code
> El teu equip de desenvolupament impulsat per IA, directament al teu editor
## Novetats de la v3.53.0
> ### El plugin Roo Code no desapareix.
>
> Potser has vist l'[anunci recent](https://x.com/mattrubens/status/2046636598859559114) que Roo Code ha arribat a 3 milions d'instal·lacions i que l'equip original es bolca completament amb Roomote. Sabem que aquesta notícia ha estat dura per a molts de vosaltres. Aquest plugin ens importa molt, tant a nosaltres com a tu, i t'escoltem.
>
> La bona notícia: **un equip de la comunitat ha donat un pas endavant per portar Roo Code cap endavant**, i estem treballant amb ells en un relleu oficial perquè el plugin en què confies continuï rebent manteniment i millores.
**Novetats d'aquesta versió:**
- S'ha afegit suport per a GPT-5.5 mitjançant el proveïdor OpenAI Codex.
- S'ha afegit suport per a Claude Opus 4.7 a Vertex AI.
- S'han afegit controls de navegació per checkpoints anteriors al xat, perquè puguis tornar enrere pels checkpoints previs més fàcilment.
<details>
<summary>🌐 Idiomes disponibles</summary>
@ -75,96 +54,10 @@ Roo Code s'adapta a la teva manera de treballar, no a l'inrevés:
Més informació: [Ús de Modes](https://docs.roocode.com/basic-usage/using-modes) • [Modes personalitzats](https://docs.roocode.com/advanced-usage/custom-modes)
## Tutorials i vídeos de funcionalitats
<div align="center">
| | | |
| :------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <a href="https://www.youtube.com/watch?v=Mcq3r1EPZ-4"><img src="https://img.youtube.com/vi/Mcq3r1EPZ-4/maxresdefault.jpg" width="100%"></a><br><b>Instal·lant Roo Code</b> | <a href="https://www.youtube.com/watch?v=ZBML8h5cCgo"><img src="https://img.youtube.com/vi/ZBML8h5cCgo/maxresdefault.jpg" width="100%"></a><br><b>Configurant perfils</b> | <a href="https://www.youtube.com/watch?v=r1bpod1VWhg"><img src="https://img.youtube.com/vi/r1bpod1VWhg/maxresdefault.jpg" width="100%"></a><br><b>Indexació de la base de codi</b> |
| <a href="https://www.youtube.com/watch?v=iiAv1eKOaxk"><img src="https://img.youtube.com/vi/iiAv1eKOaxk/maxresdefault.jpg" width="100%"></a><br><b>Modes personalitzats</b> | <a href="https://www.youtube.com/watch?v=Ho30nyY332E"><img src="https://img.youtube.com/vi/Ho30nyY332E/maxresdefault.jpg" width="100%"></a><br><b>Punts de control</b> | <a href="https://www.youtube.com/watch?v=HmnNSasv7T8"><img src="https://img.youtube.com/vi/HmnNSasv7T8/maxresdefault.jpg" width="100%"></a><br><b>Gestió de Context</b> |
</div>
<p align="center">
<a href="https://docs.roocode.com/tutorial-videos">Més tutorials ràpids i vídeos de funcionalitats...</a>
</p>
## Recursos
- **[Documentació](https://docs.roocode.com):** La guia oficial per instal·lar, configurar i dominar Roo Code.
- **[Canal de YouTube](https://youtube.com/@roocodeyt?feature=shared):** Mira tutorials i veu les funcionalitats en acció.
- **[Servidor de Discord](https://discord.gg/roocode):** Uneix-te a la comunitat per obtenir ajuda i discutir en temps real.
- **[Comunitat de Reddit](https://www.reddit.com/r/RooCode):** Comparteix les teves experiències i veu què estan construint altres.
- **[Incidències de GitHub](https://github.com/RooCodeInc/Roo-Code/issues):** Informa d'errors i segueix el desenvolupament.
- **[Sol·licituds de funcionalitats](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop):** Tens una idea? Comparteix-la amb els desenvolupadors.
---
## Configuració i desenvolupament local
1. **Clona** el repositori:
```sh
git clone https://github.com/RooCodeInc/Roo-Code.git
```
2. **Instal·la les dependències**:
```sh
pnpm install
```
3. **Executa l'extensió**:
Hi ha diverses maneres d'executar l'extensió Roo Code:
### Mode de desenvolupament (F5)
Per al desenvolupament actiu, utilitza la depuració integrada de VSCode:
Prem `F5` (o ves a **Executa** → **Inicia la depuració**) a VSCode. Això obrirà una nova finestra de VSCode amb l'extensió Roo Code en funcionament.
- Els canvis a la vista web apareixeran immediatament.
- Els canvis a l'extensió principal també es recarregaran automàticament.
### Instal·lació automatitzada de VSIX
Per construir i instal·lar l'extensió com un paquet VSIX directament a VSCode:
```sh
pnpm install:vsix [-y] [--editor=<command>]
```
Aquesta comanda farà el següent:
- Preguntarà quina comanda d'editor utilitzar (code/cursor/code-insiders) - per defecte és 'code'
- Desinstal·larà qualsevol versió existent de l'extensió.
- Construirà l'últim paquet VSIX.
- Instal·larà el VSIX acabat de construir.
- Et demanarà que reiniciïs VS Code perquè els canvis tinguin efecte.
Opcions:
- `-y`: Omet totes les confirmacions i utilitza els valors per defecte
- `--editor=<command>`: Especifica la comanda de l'editor (p. ex., `--editor=cursor` o `--editor=code-insiders`)
### Instal·lació manual de VSIX
Si prefereixes instal·lar el paquet VSIX manualment:
1. Primer, construeix el paquet VSIX:
```sh
pnpm vsix
```
2. Es generarà un fitxer `.vsix` al directori `bin/` (p. ej., `bin/roo-cline-<versió>.vsix`).
3. Instal·la'l manualment utilitzant la CLI de VSCode:
```sh
code --install-extension bin/roo-cline-<versió>.vsix
```
---
Utilitzem [changesets](https://github.com/changesets/changesets) per al versionat i la publicació. Consulta el nostre `CHANGELOG.md` per a les notes de la versió.
---
@ -174,16 +67,6 @@ Utilitzem [changesets](https://github.com/changesets/changesets) per al versiona
---
## Contribucions
Ens encanten les contribucions de la comunitat! Comença llegint el nostre [CONTRIBUTING.md](CONTRIBUTING.md).
---
## Llicència
[Apache 2.0 © 2025 Roo Code, Inc.](../../LICENSE)
---
**Gaudeix de Roo Code!** Tant si el mantens amb una corretja curta com si el deixes moure's de forma autònoma, estem impacients per veure què construeixes. Si tens preguntes o idees sobre funcionalitats, passa't per la nostra [comunitat de Reddit](https://www.reddit.com/r/RooCode/) o [Discord](https://discord.gg/roocode). Feliç programació!

89
locales/de/CODE_OF_CONDUCT.md generated
View file

@ -1,89 +0,0 @@
<div align="center">
<sub>
[English](../../CODE_OF_CONDUCT.md) • [Català](../ca/CODE_OF_CONDUCT.md) • <b>Deutsch</b> • [Español](../es/CODE_OF_CONDUCT.md) • [Français](../fr/CODE_OF_CONDUCT.md) • [हिंदी](../hi/CODE_OF_CONDUCT.md) • [Bahasa Indonesia](../id/CODE_OF_CONDUCT.md) • [Italiano](../it/CODE_OF_CONDUCT.md) • [日本語](../ja/CODE_OF_CONDUCT.md)
</sub>
<sub>
[한국어](../ko/CODE_OF_CONDUCT.md) • [Nederlands](../nl/CODE_OF_CONDUCT.md) • [Polski](../pl/CODE_OF_CONDUCT.md) • [Português (BR)](../pt-BR/CODE_OF_CONDUCT.md) • [Русский](../ru/CODE_OF_CONDUCT.md) • [Türkçe](../tr/CODE_OF_CONDUCT.md) • [Tiếng Việt](../vi/CODE_OF_CONDUCT.md) • [简体中文](../zh-CN/CODE_OF_CONDUCT.md) • [繁體中文](../zh-TW/CODE_OF_CONDUCT.md)
</sub>
</div>
# Verhaltenskodex für Mitwirkende
## Unser Versprechen
Im Interesse der Förderung eines offenen und einladenden Umfelds verpflichten wir uns als
Mitwirkende und Betreuer, die Teilnahme an unserem Projekt und
unserer Community zu einer belästigungsfreien Erfahrung für alle zu machen, unabhängig von Alter, Körpergröße,
Behinderung, ethnischer Zugehörigkeit, Geschlechtsmerkmalen, Geschlechtsidentität und -ausdruck,
Erfahrungsniveau, Bildung, sozioökonomischem Status, Nationalität, persönlichem
Aussehen, Rasse, Religion oder sexueller Identität und Orientierung.
## Unsere Standards
Beispiele für Verhaltensweisen, die zur Schaffung eines positiven Umfelds beitragen,
beinhalten:
- Verwendung von einladender und inklusiver Sprache
- Respektierung unterschiedlicher Standpunkte und Erfahrungen
- Konstruktive Kritik würdevoll annehmen
- Fokussierung auf das, was für die Community am besten ist
- Empathie gegenüber anderen Community-Mitgliedern zeigen
Beispiele für inakzeptables Verhalten von Teilnehmenden beinhalten:
- Verwendung sexualisierter Sprache oder Bilder und unerwünschte sexuelle Aufmerksamkeit oder
Annäherungsversuche
- Trolling, beleidigende/herabsetzende Kommentare und persönliche oder politische Angriffe
- Öffentliche oder private Belästigung
- Veröffentlichung privater Informationen anderer, wie z.B. einer physischen oder elektronischen
Adresse, ohne ausdrückliche Erlaubnis
- Anderes Verhalten, das in einem professionellen Umfeld vernünftigerweise als unangemessen angesehen werden könnte
## Unsere Verantwortlichkeiten
Projektbetreuer sind dafür verantwortlich, die Standards für akzeptables
Verhalten zu verdeutlichen und es wird von ihnen erwartet, angemessene und faire Korrekturmaßnahmen zu ergreifen als
Reaktion auf jegliche Fälle von inakzeptablem Verhalten.
Projektbetreuer haben das Recht und die Verantwortung, Kommentare, Commits, Code, Wiki-Bearbeitungen,
Issues und andere Beiträge zu entfernen, zu bearbeiten oder abzulehnen,
die nicht mit diesem Verhaltenskodex übereinstimmen, oder einen Mitwirkenden vorübergehend oder
dauerhaft für andere Verhaltensweisen zu sperren, die sie als unangemessen,
bedrohlich, beleidigend oder schädlich erachten.
## Geltungsbereich
Dieser Verhaltenskodex gilt sowohl innerhalb der Projekträume als auch in öffentlichen Räumen,
wenn eine Person das Projekt oder seine Community repräsentiert. Beispiele für
die Repräsentation eines Projekts oder einer Community beinhalten die Verwendung einer offiziellen Projekt-E-Mail-
Adresse, das Posten über ein offizielles Social-Media-Konto oder das Handeln als ernannter
Repräsentant bei einer Online- oder Offline-Veranstaltung. Die Repräsentation eines Projekts kann
von den Projektbetreuern weiter definiert und geklärt werden.
## Durchsetzung
Fälle von missbräuchlichem, belästigendem oder anderweitig inakzeptablem Verhalten können
dem Projektteam unter support@roocode.com gemeldet werden. Alle
Beschwerden werden überprüft und untersucht und führen zu einer Reaktion, die
als notwendig und angemessen für die Umstände erachtet wird. Das Projektteam ist
verpflichtet, die Vertraulichkeit in Bezug auf den Melder eines Vorfalls zu wahren.
Weitere Details zu spezifischen Durchsetzungsrichtlinien können separat veröffentlicht werden.
Projektbetreuer, die den Verhaltenskodex nicht in gutem Glauben befolgen oder durchsetzen,
können vorübergehende oder dauerhafte Konsequenzen erleben, die von anderen
Mitgliedern der Projektleitung bestimmt werden.
## Zuordnung
Dieser Verhaltenskodex ist adaptiert von [Clines Version][cline_coc] des [Contributor Covenant][homepage], Version 1.4,
verfügbar unter https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[cline_coc]: https://github.com/cline/cline/blob/main/CODE_OF_CONDUCT.md
[homepage]: https://www.contributor-covenant.org
Für Antworten auf häufig gestellte Fragen zu diesem Verhaltenskodex siehe
https://www.contributor-covenant.org/faq

141
locales/de/CONTRIBUTING.md generated
View file

@ -1,141 +0,0 @@
<div align="center">
<sub>
[English](../../CONTRIBUTING.md) • [Català](../ca/CONTRIBUTING.md) • <b>Deutsch</b> • [Español](../es/CONTRIBUTING.md) • [Français](../fr/CONTRIBUTING.md) • [हिंदी](../hi/CONTRIBUTING.md) • [Bahasa Indonesia](../id/CONTRIBUTING.md) • [Italiano](../it/CONTRIBUTING.md) • [日本語](../ja/CONTRIBUTING.md)
</sub>
<sub>
[한국어](../ko/CONTRIBUTING.md) • [Nederlands](../nl/CONTRIBUTING.md) • [Polski](../pl/CONTRIBUTING.md) • [Português (BR)](../pt-BR/CONTRIBUTING.md) • [Русский](../ru/CONTRIBUTING.md) • [Türkçe](../tr/CONTRIBUTING.md) • [Tiếng Việt](../vi/CONTRIBUTING.md) • [简体中文](../zh-CN/CONTRIBUTING.md) • [繁體中文](../zh-TW/CONTRIBUTING.md)
</sub>
</div>
# Beitrag zu Roo Code
Roo Code ist ein von der Community getragenes Projekt, und wir schätzen jeden Beitrag sehr. Um die Zusammenarbeit zu optimieren, arbeiten wir nach dem [Issue-First-Ansatz](#issue-first-ansatz), was bedeutet, dass alle [Pull Requests (PRs)](#einen-pull-request-einreichen) zuerst mit einem GitHub-Issue verknüpft sein müssen. Bitte lies diesen Leitfaden sorgfältig durch.
## Inhaltsverzeichnis
- [Bevor du beiträgst](#bevor-du-beiträgst)
- [Deinen Beitrag finden und planen](#deinen-beitrag-finden-und-planen)
- [Entwicklungs- und Einreichungsprozess](#entwicklungs-und-einreichungsprozess)
- [Rechtliches](#rechtliches)
## Bevor du beiträgst
### 1. Verhaltenskodex
Alle Mitwirkenden müssen sich an unseren [Verhaltenskodex](./CODE_OF_CONDUCT.md) halten.
### 2. Projekt-Roadmap
Unsere Roadmap gibt die Richtung des Projekts vor. Richte deine Beiträge an diesen Hauptzielen aus:
### Zuverlässigkeit an erster Stelle
- Stelle sicher, dass die Diff-Bearbeitung und die Befehlsausführung durchweg zuverlässig sind.
- Reduziere Reibungspunkte, die von der regelmäßigen Nutzung abhalten.
- Gewährleiste einen reibungslosen Betrieb in allen Gebietsschemata und auf allen Plattformen.
- Erweitere die robuste Unterstützung für eine Vielzahl von KI-Anbietern und -Modellen.
### Verbesserte Benutzererfahrung
- Optimiere die UI/UX für Klarheit und Intuitivität.
- Verbessere kontinuierlich den Arbeitsablauf, um den hohen Erwartungen gerecht zu werden, die Entwickler an täglich genutzte Werkzeuge haben.
### Führend in der Agentenleistung
- Etabliere umfassende Bewertungsmaßstäbe (evals), um die Produktivität in der Praxis zu messen.
- Mache es für jeden einfach, diese Bewertungen auszuführen und zu interpretieren.
- Liefere Verbesserungen, die klare Steigerungen der Bewertungsergebnisse zeigen.
Erwähne die Ausrichtung auf diese Bereiche in deinen PRs.
### 3. Tritt der Roo Code Community bei
- **Primär:** Tritt unserem [Discord](https://discord.gg/roocode) bei und schreibe eine DM an **Hannes Rudolph (`hrudolph`)**.
- **Alternative:** Erfahrene Mitwirkende können sich direkt über [GitHub-Projekte](https://github.com/orgs/RooCodeInc/projects/1) beteiligen.
## Deinen Beitrag finden und planen
### Arten von Beiträgen
- **Fehlerbehebungen:** Behebung von Code-Problemen.
- **Neue Funktionen:** Hinzufügen von Funktionalität.
- **Dokumentation:** Verbesserung von Anleitungen und Klarheit.
### Issue-First-Ansatz
Alle Beiträge beginnen mit einem GitHub-Issue unter Verwendung unserer schlanken Vorlagen.
- **Überprüfe bestehende Issues**: Suche in den [GitHub Issues](https://github.com/RooCodeInc/Roo-Code/issues).
- **Erstelle ein Issue** mit:
- **Verbesserungen:** Vorlage „Verbesserungsvorschlag“ (einfache Sprache mit Fokus auf den Nutzen für den Benutzer).
- **Fehler:** Vorlage „Fehlerbericht“ (minimale Reproduktion + erwartet vs. tatsächlich + Version).
- **Möchtest du daran arbeiten?** Kommentiere „Claiming“ im Issue und schreibe eine DM an **Hannes Rudolph (`hrudolph`)** auf [Discord](https://discord.gg/roocode), um zugewiesen zu werden. Die Zuweisung wird im Thread bestätigt.
- **PRs müssen auf das Issue verweisen.** Nicht verknüpfte PRs können geschlossen werden.
### Entscheiden, woran du arbeiten möchtest
- Überprüfe das [GitHub-Projekt](https://github.com/orgs/RooCodeInc/projects/1) auf „Issue [Unassigned]“-Issues.
- Für Dokumentation besuche [Roo Code Docs](https://github.com/RooCodeInc/Roo-Code-Docs).
### Fehler melden
- Überprüfe zuerst, ob bereits Berichte vorhanden sind.
- Erstelle einen neuen Fehler mit der [Vorlage „Fehlerbericht“](https://github.com/RooCodeInc/Roo-Code/issues/new/choose) mit:
- Klaren, nummerierten Reproduktionsschritten
- Erwartetes vs. tatsächliches Ergebnis
- Roo Code-Version (erforderlich); API-Anbieter/Modell, falls relevant
- **Sicherheitsprobleme**: Melde sie privat über [Sicherheitshinweise](https://github.com/RooCodeInc/Roo-Code/security/advisories/new).
## Entwicklungs- und Einreichungsprozess
### Entwicklungseinrichtung
1. **Fork & Klonen:**
```
git clone https://github.com/DEIN_BENUTZERNAME/Roo-Code.git
```
2. **Abhängigkeiten installieren:**
```
pnpm install
```
3. **Debugging:** Mit VS Code öffnen (`F5`).
### Richtlinien zum Schreiben von Code
- Ein fokussierter PR pro Funktion oder Fehlerbehebung.
- Befolge die Best Practices von ESLint und TypeScript.
- Schreibe klare, beschreibende Commits mit Verweis auf Issues (z. B. `Fixes #123`).
- Stelle gründliche Tests bereit (`npm test`).
- Rebase auf den neuesten `main`-Zweig vor der Einreichung.
### Einen Pull Request einreichen
- Beginne als **Entwurfs-PR**, wenn du frühzeitig Feedback einholen möchtest.
- Beschreibe deine Änderungen klar und deutlich gemäß der Pull-Request-Vorlage.
- Verknüpfe das Issue in der PR-Beschreibung/Titel (z. B. „Fixes #123“).
- Stelle Screenshots/Videos für UI-Änderungen bereit.
- Gib an, ob Dokumentationsaktualisierungen erforderlich sind.
### Pull-Request-Richtlinie
- Muss auf ein zugewiesenes GitHub-Issue verweisen. Um zugewiesen zu werden: Kommentiere „Claiming“ im Issue und schreibe eine DM an **Hannes Rudolph (`hrudolph`)** auf [Discord](https://discord.gg/roocode). Die Zuweisung wird im Thread bestätigt.
- Nicht verknüpfte PRs können geschlossen werden.
- PRs müssen die CI-Tests bestehen, mit der Roadmap übereinstimmen und eine klare Dokumentation haben.
### Überprüfungsprozess
- **Tägliche Triage:** Schnelle Überprüfungen durch die Betreuer.
- **Wöchentliche ausführliche Überprüfung:** Umfassende Bewertung.
- **Iteriere umgehend** basierend auf dem Feedback.
## Rechtliches
Indem du einen Beitrag leistest, stimmst du zu, dass deine Beiträge unter der Apache-2.0-Lizenz lizenziert werden, die mit der Lizenzierung von Roo Code übereinstimmt.

117
locales/de/README.md generated
View file

@ -1,32 +1,11 @@
<p align="center">
<a href="https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline"><img src="https://img.shields.io/badge/VS_Code_Marketplace-007ACC?style=flat&logo=visualstudiocode&logoColor=white" alt="VS Code Marketplace"></a>
<a href="https://x.com/roocode"><img src="https://img.shields.io/badge/roocode-000000?style=flat&logo=x&logoColor=white" alt="X"></a>
<a href="https://youtube.com/@roocodeyt?feature=shared"><img src="https://img.shields.io/badge/YouTube-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube"></a>
<a href="https://discord.gg/roocode"><img src="https://img.shields.io/badge/Join%20Discord-5865F2?style=flat&logo=discord&logoColor=white" alt="Join Discord"></a>
<a href="https://www.reddit.com/r/RooCode/"><img src="https://img.shields.io/badge/Join%20r%2FRooCode-FF4500?style=flat&logo=reddit&logoColor=white" alt="Join r/RooCode"></a>
</p>
<p align="center">
<em>Schnelle Hilfe → <a href="https://discord.gg/roocode">Discord beitreten</a> • Lieber asynchron? → <a href="https://www.reddit.com/r/RooCode/">r/RooCode beitreten</a></em>
</p>
# Roo Code
> Dein KI-gestütztes Dev-Team – direkt in deinem Editor
## Neu in v3.53.0
> ### Das Roo Code-Plugin verschwindet nicht.
>
> Du hast vielleicht die [neuliche Ankündigung](https://x.com/mattrubens/status/2046636598859559114) gesehen, dass Roo Code 3 Millionen Installationen erreicht hat und das ursprüngliche Team sich voll auf Roomote konzentriert. Wir wissen, dass diese Nachricht für viele von euch schwer war. Dieses Plugin bedeutet uns und dir sehr viel, und wir hören dich.
>
> Die gute Nachricht: **ein Community-Team hat sich bereit erklärt, Roo Code weiterzuführen**, und wir arbeiten mit ihnen an einer offiziellen Übergabe, damit das Plugin, auf das du dich verlässt, weiterhin gepflegt und verbessert wird.
**Neu in dieser Version:**
- GPT-5.5-Unterstützung über den OpenAI Codex-Provider hinzugefügt.
- Claude Opus 4.7-Unterstützung auf Vertex AI hinzugefügt.
- Steuerelemente zur Navigation zu vorherigen Checkpoints im Chat hinzugefügt, damit du leichter durch frühere Checkpoints zurückspringen kannst.
<details>
<summary>🌐 Verfügbare Sprachen</summary>
@ -75,96 +54,10 @@ Roo Code passt sich an deine Arbeitsweise an, nicht umgekehrt:
Mehr erfahren: [Modi verwenden](https://docs.roocode.com/basic-usage/using-modes) • [Benutzerdefinierte Modi](https://docs.roocode.com/advanced-usage/custom-modes)
## Tutorial- & Feature-Videos
<div align="center">
| | | |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <a href="https://www.youtube.com/watch?v=Mcq3r1EPZ-4"><img src="https://img.youtube.com/vi/Mcq3r1EPZ-4/maxresdefault.jpg" width="100%"></a><br><b>Roo Code installieren</b> | <a href="https://www.youtube.com/watch?v=ZBML8h5cCgo"><img src="https://img.youtube.com/vi/ZBML8h5cCgo/maxresdefault.jpg" width="100%"></a><br><b>Profile konfigurieren</b> | <a href="https://www.youtube.com/watch?v=r1bpod1VWhg"><img src="https://img.youtube.com/vi/r1bpod1VWhg/maxresdefault.jpg" width="100%"></a><br><b>Codebasis-Indizierung</b> |
| <a href="https://www.youtube.com/watch?v=iiAv1eKOaxk"><img src="https://img.youtube.com/vi/iiAv1eKOaxk/maxresdefault.jpg" width="100%"></a><br><b>Benutzerdefinierte Modi</b> | <a href="https://www.youtube.com/watch?v=Ho30nyY332E"><img src="https://img.youtube.com/vi/Ho30nyY332E/maxresdefault.jpg" width="100%"></a><br><b>Checkpoints</b> | <a href="https://www.youtube.com/watch?v=HmnNSasv7T8"><img src="https://img.youtube.com/vi/HmnNSasv7T8/maxresdefault.jpg" width="100%"></a><br><b>Kontextverwaltung</b> |
</div>
<p align="center">
<a href="https://docs.roocode.com/tutorial-videos">Weitere schnelle Tutorial- und Feature-Videos...</a>
</p>
## Ressourcen
- **[Dokumentation](https://docs.roocode.com):** Die offizielle Anleitung zur Installation, Konfiguration und Beherrschung von Roo Code.
- **[YouTube-Kanal](https://youtube.com/@roocodeyt?feature=shared):** Schau dir Tutorials an und sieh Features in Aktion.
- **[Discord-Server](https://discord.gg/roocode):** Tritt der Community bei für Echtzeit-Hilfe und Diskussionen.
- **[Reddit-Community](https://www.reddit.com/r/RooCode):** Teile deine Erfahrungen und sieh, was andere bauen.
- **[GitHub Issues](https://github.com/RooCodeInc/Roo-Code/issues):** Melde Fehler und verfolge die Entwicklung.
- **[Feature-Anfragen](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop):** Hast du eine Idee? Teile sie mit den Entwicklern.
---
## Lokales Setup & Entwicklung
1. **Klone** das Repo:
```sh
git clone https://github.com/RooCodeInc/Roo-Code.git
```
2. **Installiere die Abhängigkeiten**:
```sh
pnpm install
```
3. **Führe die Erweiterung aus**:
Es gibt mehrere Möglichkeiten, die Roo Code-Erweiterung auszuführen:
### Entwicklungsmodus (F5)
Für die aktive Entwicklung verwende das integrierte Debugging von VSCode:
Drücke `F5` (oder gehe zu **Ausführen** → **Debuggen starten**) in VSCode. Dies öffnet ein neues VSCode-Fenster mit der laufenden Roo Code-Erweiterung.
- Änderungen an der Webview werden sofort angezeigt.
- Änderungen an der Kern-Erweiterung werden ebenfalls automatisch per Hot-Reload neu geladen.
### Automatisierte VSIX-Installation
Um die Erweiterung als VSIX-Paket zu erstellen und direkt in VSCode zu installieren:
```sh
pnpm install:vsix [-y] [--editor=<command>]
```
Dieser Befehl wird:
- Fragen, welcher Editor-Befehl verwendet werden soll (code/cursor/code-insiders) - standardmäßig 'code'
- Jede vorhandene Version der Erweiterung deinstallieren.
- Das neueste VSIX-Paket erstellen.
- Das neu erstellte VSIX installieren.
- Dich auffordern, VS Code neu zu starten, damit die Änderungen wirksam werden.
Optionen:
- `-y`: Alle Bestätigungsaufforderungen überspringen und Standardwerte verwenden
- `--editor=<command>`: Gib den Editor-Befehl an (z. B. `--editor=cursor` oder `--editor=code-insiders`)
### Manuelle VSIX-Installation
Wenn du das VSIX-Paket lieber manuell installieren möchtest:
1. Erstelle zuerst das VSIX-Paket:
```sh
pnpm vsix
```
2. Eine `.vsix`-Datei wird im `bin/`-Verzeichnis generiert (z. B. `bin/roo-cline-<version>.vsix`).
3. Installiere sie manuell mit der VSCode-Befehlszeilenschnittstelle:
```sh
code --install-extension bin/roo-cline-<version>.vsix
```
---
Wir verwenden [changesets](https://github.com/changesets/changesets) für die Versionierung und Veröffentlichung. Schau in unsere `CHANGELOG.md` für Versionshinweise.
---
@ -174,16 +67,6 @@ Wir verwenden [changesets](https://github.com/changesets/changesets) für die Ve
---
## Mitwirken
Wir lieben Community-Beiträge! Lies unsere [CONTRIBUTING.md](CONTRIBUTING.md), um loszulegen.
---
## Lizenz
[Apache 2.0 © 2025 Roo Code, Inc.](../../LICENSE)
---
**Viel Spaß mit Roo Code!** Egal, ob du ihn an der kurzen Leine führst oder autonom agieren lässt, wir können es kaum erwarten zu sehen, was du baust. Wenn du Fragen oder Ideen für neue Funktionen hast, schau in unserer [Reddit-Community](https://www.reddit.com/r/RooCode/) oder auf [Discord](https://discord.gg/roocode) vorbei. Viel Spaß beim Codieren!

89
locales/es/CODE_OF_CONDUCT.md generated
View file

@ -1,89 +0,0 @@
<div align="center">
<sub>
[English](../../CODE_OF_CONDUCT.md) • [Català](../ca/CODE_OF_CONDUCT.md) • [Deutsch](../de/CODE_OF_CONDUCT.md) • <b>Español</b> • [Français](../fr/CODE_OF_CONDUCT.md) • [हिंदी](../hi/CODE_OF_CONDUCT.md) • [Bahasa Indonesia](../id/CODE_OF_CONDUCT.md) • [Italiano](../it/CODE_OF_CONDUCT.md) • [日本語](../ja/CODE_OF_CONDUCT.md)
</sub>
<sub>
[한국어](../ko/CODE_OF_CONDUCT.md) • [Nederlands](../nl/CODE_OF_CONDUCT.md) • [Polski](../pl/CODE_OF_CONDUCT.md) • [Português (BR)](../pt-BR/CODE_OF_CONDUCT.md) • [Русский](../ru/CODE_OF_CONDUCT.md) • [Türkçe](../tr/CODE_OF_CONDUCT.md) • [Tiếng Việt](../vi/CODE_OF_CONDUCT.md) • [简体中文](../zh-CN/CODE_OF_CONDUCT.md) • [繁體中文](../zh-TW/CODE_OF_CONDUCT.md)
</sub>
</div>
# Código de Conducta del Pacto de Colaboradores
## Nuestro Compromiso
En el interés de fomentar un ambiente abierto y acogedor, nosotros como
colaboradores y mantenedores nos comprometemos a hacer que la participación en nuestro proyecto y
nuestra comunidad sea una experiencia libre de acoso para todos, independientemente de la edad, tamaño
corporal, discapacidad, etnia, características sexuales, identidad y expresión de género,
nivel de experiencia, educación, nivel socioeconómico, nacionalidad, apariencia
personal, raza, religión, o identidad y orientación sexual.
## Nuestros Estándares
Ejemplos de comportamiento que contribuye a crear un ambiente positivo
incluyen:
- Usar lenguaje acogedor e inclusivo
- Ser respetuoso con los diferentes puntos de vista y experiencias
- Aceptar con gracia la crítica constructiva
- Centrarse en lo que es mejor para la comunidad
- Mostrar empatía hacia otros miembros de la comunidad
Ejemplos de comportamiento inaceptable por parte de los participantes incluyen:
- El uso de lenguaje o imágenes sexualizadas y atención o avances sexuales no deseados
- Troleo, comentarios insultantes/despectivos, y ataques personales o políticos
- Acoso público o privado
- Publicar información privada de otros, como una dirección física o electrónica,
sin permiso explícito
- Otra conducta que razonablemente podría considerarse inapropiada en un
entorno profesional
## Nuestras Responsabilidades
Los mantenedores del proyecto son responsables de aclarar los estándares de comportamiento aceptable
y se espera que tomen medidas correctivas apropiadas y justas en
respuesta a cualquier caso de comportamiento inaceptable.
Los mantenedores del proyecto tienen el derecho y la responsabilidad de eliminar, editar o
rechazar comentarios, commits, código, ediciones de wiki, issues y otras contribuciones
que no estén alineadas con este Código de Conducta, o de prohibir temporal o
permanentemente a cualquier colaborador por otros comportamientos que consideren inapropiados,
amenazantes, ofensivos o dañinos.
## Alcance
Este Código de Conducta se aplica tanto dentro de los espacios del proyecto como en espacios públicos
cuando un individuo está representando al proyecto o su comunidad. Ejemplos de
representación de un proyecto o comunidad incluyen usar una dirección de correo electrónico oficial del proyecto,
publicar a través de una cuenta oficial de redes sociales, o actuar como representante designado
en un evento en línea o fuera de línea. La representación de un proyecto puede ser
definida y aclarada aún más por los mantenedores del proyecto.
## Aplicación
Los casos de comportamiento abusivo, acosador o de otro modo inaceptable pueden ser
reportados contactando al equipo del proyecto en support@roocode.com. Todas las quejas
serán revisadas e investigadas y resultarán en una respuesta que
se considera necesaria y apropiada a las circunstancias. El equipo del proyecto está
obligado a mantener la confidencialidad con respecto al informante de un incidente.
Más detalles de políticas específicas de aplicación pueden ser publicados por separado.
Los mantenedores del proyecto que no sigan o hagan cumplir el Código de Conducta de buena
fe pueden enfrentar repercusiones temporales o permanentes según lo determinen otros
miembros del liderazgo del proyecto.
## Atribución
Este Código de Conducta está adaptado de la [versión de Cline][cline_coc] del [Pacto de Colaboradores][homepage], versión 1.4,
disponible en https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[cline_coc]: https://github.com/cline/cline/blob/main/CODE_OF_CONDUCT.md
[homepage]: https://www.contributor-covenant.org
Para respuestas a preguntas comunes sobre este código de conducta, véase
https://www.contributor-covenant.org/faq

141
locales/es/CONTRIBUTING.md generated
View file

@ -1,141 +0,0 @@
<div align="center">
<sub>
[English](../../CONTRIBUTING.md) • [Català](../ca/CONTRIBUTING.md) • [Deutsch](../de/CONTRIBUTING.md) • <b>Español</b> • [Français](../fr/CONTRIBUTING.md) • [हिंदी](../hi/CONTRIBUTING.md) • [Bahasa Indonesia](../id/CONTRIBUTING.md) • [Italiano](../it/CONTRIBUTING.md) • [日本語](../ja/CONTRIBUTING.md)
</sub>
<sub>
[한국어](../ko/CONTRIBUTING.md) • [Nederlands](../nl/CONTRIBUTING.md) • [Polski](../pl/CONTRIBUTING.md) • [Português (BR)](../pt-BR/CONTRIBUTING.md) • [Русский](../ru/CONTRIBUTING.md) • [Türkçe](../tr/CONTRIBUTING.md) • [Tiếng Việt](../vi/CONTRIBUTING.md) • [简体中文](../zh-CN/CONTRIBUTING.md) • [繁體中文](../zh-TW/CONTRIBUTING.md)
</sub>
</div>
# Contribuir a Roo Code
Roo Code es un proyecto impulsado por la comunidad y valoramos profundamente cada contribución. Para agilizar la colaboración, operamos con un [enfoque de "primero la incidencia"](#enfoque-de-primero-la-incidencia), lo que significa que todas las [solicitudes de extracción (PR)](#envío-de-una-solicitud-de-extracción) deben estar primero vinculadas a una incidencia de GitHub. Por favor, revise esta guía detenidamente.
## Tabla de contenidos
- [Antes de contribuir](#antes-de-contribuir)
- [Encontrar y planificar su contribución](#encontrar-y-planificar-su-contribución)
- [Proceso de desarrollo y envío](#proceso-de-desarrollo-y-envío)
- [Legal](#legal)
## Antes de contribuir
### 1. Código de conducta
Todos los colaboradores deben adherirse a nuestro [Código de conducta](./CODE_OF_CONDUCT.md).
### 2. Hoja de ruta del proyecto
Nuestra hoja de ruta guía la dirección del proyecto. Alinee sus contribuciones con estos objetivos clave:
### La fiabilidad es lo primero
- Asegúrese de que la edición de diferencias y la ejecución de comandos sean consistentemente fiables.
- Reduzca los puntos de fricción que desalientan el uso regular.
- Garantice un funcionamiento fluido en todas las localidades y plataformas.
- Amplíe el soporte robusto para una amplia variedad de proveedores y modelos de IA.
### Experiencia de usuario mejorada
- Agilice la interfaz de usuario/experiencia de usuario para mayor claridad e intuición.
- Mejore continuamente el flujo de trabajo para cumplir con las altas expectativas que los desarrolladores tienen de las herramientas de uso diario.
### Liderando el rendimiento de los agentes
- Establezca puntos de referencia de evaluación (evals) exhaustivos para medir la productividad en el mundo real.
- Facilite que todos puedan ejecutar e interpretar fácilmente estas evaluaciones.
- Envíe mejoras que demuestren un claro aumento en las puntuaciones de las evaluaciones.
Mencione la alineación con estas áreas en sus solicitudes de extracción.
### 3. Únase a la comunidad de Roo Code
- **Principal:** Únase a nuestro [Discord](https://discord.gg/roocode) y envíe un mensaje directo a **Hannes Rudolph (`hrudolph`)**.
- **Alternativa:** Los colaboradores experimentados pueden participar directamente a través de [Proyectos de GitHub](https://github.com/orgs/RooCodeInc/projects/1).
## Encontrar y planificar su contribución
### Tipos de contribuciones
- **Correcciones de errores:** abordar problemas de código.
- **Nuevas características:** agregar funcionalidad.
- **Documentación:** mejorar las guías y la claridad.
### Enfoque de primero la incidencia
Todas las contribuciones comienzan con una incidencia de GitHub utilizando nuestras plantillas simplificadas.
- **Compruebe las incidencias existentes**: busque en [Incidencias de GitHub](https://github.com/RooCodeInc/Roo-Code/issues).
- **Cree una incidencia** utilizando:
- **Mejoras:** plantilla "Solicitud de mejora" (lenguaje sencillo centrado en el beneficio del usuario).
- **Errores:** plantilla "Informe de error" (reproducción mínima + esperado vs. real + versión).
- **¿Quiere trabajar en ello?** Comente "Reclamando" en la incidencia y envíe un mensaje directo a **Hannes Rudolph (`hrudolph`)** en [Discord](https://discord.gg/roocode) para que se le asigne. La asignación se confirmará en el hilo.
- **Las solicitudes de extracción deben enlazar a la incidencia.** Las solicitudes de extracción no enlazadas pueden cerrarse.
### Decidir en qué trabajar
- Consulte el [Proyecto de GitHub](https://github.com/orgs/RooCodeInc/projects/1) para ver las incidencias "Incidencia [Sin asignar]".
- Para la documentación, visite [Documentos de Roo Code](https://github.com/RooCodeInc/Roo-Code-Docs).
### Informar de errores
- Compruebe primero si existen informes.
- Cree un nuevo error utilizando la [plantilla "Informe de error"](https://github.com/RooCodeInc/Roo-Code/issues/new/choose) con:
- Pasos de reproducción claros y numerados
- Resultado esperado vs. real
- Versión de Roo Code (obligatorio); proveedor/modelo de API si es relevante
- **Problemas de seguridad**: informe de forma privada a través de [avisos de seguridad](https://github.com/RooCodeInc/Roo-Code/security/advisories/new).
## Proceso de desarrollo y envío
### Configuración de desarrollo
1. **Bifurcar y clonar:**
```
git clone https://github.com/SU_NOMBRE_DE_USUARIO/Roo-Code.git
```
2. **Instalar dependencias:**
```
pnpm install
```
3. **Depuración:** Abra con VS Code (`F5`).
### Directrices para escribir código
- Una solicitud de extracción centrada por característica o corrección.
- Siga las mejores prácticas de ESLint y TypeScript.
- Escriba confirmaciones claras y descriptivas que hagan referencia a las incidencias (p. ej., `Corrige #123`).
- Proporcione pruebas exhaustivas (`npm test`).
- Rebase a la rama `main` más reciente antes del envío.
### Envío de una solicitud de extracción
- Comience como una **PR en borrador** si busca comentarios tempranos.
- Describa claramente sus cambios siguiendo la plantilla de solicitud de extracción.
- Enlace la incidencia en la descripción/título de la PR (p. ej., "Corrige #123").
- Proporcione capturas de pantalla/vídeos para los cambios en la interfaz de usuario.
- Indique si es necesario actualizar la documentación.
### Política de solicitud de extracción
- Debe hacer referencia a una incidencia de GitHub asignada. Para que se le asigne: comente "Reclamando" en la incidencia y envíe un mensaje directo a **Hannes Rudolph (`hrudolph`)** en [Discord](https://discord.gg/roocode). La asignación se confirmará en el hilo.
- Las solicitudes de extracción no enlazadas pueden cerrarse.
- Las solicitudes de extracción deben pasar las pruebas de CI, estar alineadas con la hoja de ruta y tener una documentación clara.
### Proceso de revisión
- **Clasificación diaria:** comprobaciones rápidas por parte de los mantenedores.
- **Revisión semanal en profundidad:** evaluación exhaustiva.
- **Itere rápidamente** en función de los comentarios.
## Legal
Al contribuir, acepta que sus contribuciones se licenciarán bajo la Licencia Apache 2.0, de acuerdo con la licencia de Roo Code.

117
locales/es/README.md generated
View file

@ -1,32 +1,11 @@
<p align="center">
<a href="https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline"><img src="https://img.shields.io/badge/VS_Code_Marketplace-007ACC?style=flat&logo=visualstudiocode&logoColor=white" alt="VS Code Marketplace"></a>
<a href="https://x.com/roocode"><img src="https://img.shields.io/badge/roocode-000000?style=flat&logo=x&logoColor=white" alt="X"></a>
<a href="https://youtube.com/@roocodeyt?feature=shared"><img src="https://img.shields.io/badge/YouTube-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube"></a>
<a href="https://discord.gg/roocode"><img src="https://img.shields.io/badge/Join%20Discord-5865F2?style=flat&logo=discord&logoColor=white" alt="Join Discord"></a>
<a href="https://www.reddit.com/r/RooCode/"><img src="https://img.shields.io/badge/Join%20r%2FRooCode-FF4500?style=flat&logo=reddit&logoColor=white" alt="Join r/RooCode"></a>
</p>
<p align="center">
<em>Obtén ayuda rápido → <a href="https://discord.gg/roocode">Únete a Discord</a> • ¿Prefieres asíncrono? → <a href="https://www.reddit.com/r/RooCode/">Únete a r/RooCode</a></em>
</p>
# Roo Code
> Tu equipo de desarrollo con IA, directamente en tu editor
## Novedades de la v3.53.0
> ### El plugin de Roo Code no va a desaparecer.
>
> Puede que hayas visto el [anuncio reciente](https://x.com/mattrubens/status/2046636598859559114) de que Roo Code ha llegado a 3 millones de instalaciones y que el equipo original se está volcando por completo en Roomote. Sabemos que esa noticia fue dura para muchos de vosotros. Este plugin significa mucho para nosotros y para ti, y te escuchamos.
>
> La buena noticia: **un equipo de la comunidad ha dado un paso adelante para seguir adelante con Roo Code**, y estamos trabajando con ellos en un relevo oficial para que el plugin del que dependes siga recibiendo mantenimiento y mejoras.
**Novedades de esta versión:**
- Se añadió soporte para GPT-5.5 a través del proveedor OpenAI Codex.
- Se añadió soporte para Claude Opus 4.7 en Vertex AI.
- Se añadieron controles de navegación por checkpoints anteriores en el chat para que puedas retroceder por los checkpoints previos más fácilmente.
<details>
<summary>🌐 Idiomas disponibles</summary>
@ -75,96 +54,10 @@ Roo Code se adapta a tu forma de trabajar, no al revés:
Más info: [Usar Modos](https://docs.roocode.com/basic-usage/using-modes) • [Modos Personalizados](https://docs.roocode.com/advanced-usage/custom-modes)
## Tutoriales y vídeos de funcionalidades
<div align="center">
| | | |
| :------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <a href="https://www.youtube.com/watch?v=Mcq3r1EPZ-4"><img src="https://img.youtube.com/vi/Mcq3r1EPZ-4/maxresdefault.jpg" width="100%"></a><br><b>Instalando Roo Code</b> | <a href="https://www.youtube.com/watch?v=ZBML8h5cCgo"><img src="https://img.youtube.com/vi/ZBML8h5cCgo/maxresdefault.jpg" width="100%"></a><br><b>Configurando perfiles</b> | <a href="https://www.youtube.com/watch?v=r1bpod1VWhg"><img src="https://img.youtube.com/vi/r1bpod1VWhg/maxresdefault.jpg" width="100%"></a><br><b>Indexación de la base de código</b> |
| <a href="https://www.youtube.com/watch?v=iiAv1eKOaxk"><img src="https://img.youtube.com/vi/iiAv1eKOaxk/maxresdefault.jpg" width="100%"></a><br><b>Modos personalizados</b> | <a href="https://www.youtube.com/watch?v=Ho30nyY332E"><img src="https://img.youtube.com/vi/Ho30nyY332E/maxresdefault.jpg" width="100%"></a><br><b>Checkpoints</b> | <a href="https://www.youtube.com/watch?v=HmnNSasv7T8"><img src="https://img.youtube.com/vi/HmnNSasv7T8/maxresdefault.jpg" width="100%"></a><br><b>Gestión de Contexto</b> |
</div>
<p align="center">
<a href="https://docs.roocode.com/tutorial-videos">Más tutoriales rápidos y vídeos de funcionalidades...</a>
</p>
## Recursos
- **[Documentación](https://docs.roocode.com):** La guía oficial para instalar, configurar y dominar Roo Code.
- **[Canal de YouTube](https://youtube.com/@roocodeyt?feature=shared):** Mira tutoriales y ve las funcionalidades en acción.
- **[Servidor de Discord](https://discord.gg/roocode):** Únete a la comunidad para obtener ayuda y discutir en tiempo real.
- **[Comunidad de Reddit](https://www.reddit.com/r/RooCode):** Comparte tus experiencias y ve lo que otros están construyendo.
- **[Incidencias de GitHub](https://github.com/RooCodeInc/Roo-Code/issues):** Reporta errores y sigue el desarrollo.
- **[Solicitudes de funcionalidades](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop):** ¿Tienes una idea? Compártela con los desarrolladores.
---
## Configuración y desarrollo local
1. **Clona** el repositorio:
```sh
git clone https://github.com/RooCodeInc/Roo-Code.git
```
2. **Instala las dependencias**:
```sh
pnpm install
```
3. **Ejecuta la extensión**:
Hay varias formas de ejecutar la extensión Roo Code:
### Modo de desarrollo (F5)
Para el desarrollo activo, utiliza la depuración integrada de VSCode:
Presiona `F5` (o ve a **Ejecutar** → **Iniciar depuración**) en VSCode. Esto abrirá una nueva ventana de VSCode con la extensión Roo Code en ejecución.
- Los cambios en la vista web aparecerán inmediatamente.
- Los cambios en la extensión principal también se recargarán automáticamente.
### Instalación automatizada de VSIX
Para construir e instalar la extensión como un paquete VSIX directamente en VSCode:
```sh
pnpm install:vsix [-y] [--editor=<command>]
```
Este comando hará lo siguiente:
- Preguntará qué comando de editor usar (code/cursor/code-insiders) - por defecto es 'code'
- Desinstalará cualquier versión existente de la extensión.
- Construirá el último paquete VSIX.
- Instalará el VSIX recién construido.
- Te pedirá que reinicies VS Code para que los cambios surtan efecto.
Opciones:
- `-y`: Omitir todas las confirmaciones y usar los valores predeterminados
- `--editor=<command>`: Especifica el comando del editor (p. ej., `--editor=cursor` o `--editor=code-insiders`)
### Instalación manual de VSIX
Si prefieres instalar el paquete VSIX manualmente:
1. Primero, construye el paquete VSIX:
```sh
pnpm vsix
```
2. Se generará un archivo `.vsix` en el directorio `bin/` (p. ej., `bin/roo-cline-<version>.vsix`).
3. Instálalo manualmente usando la CLI de VSCode:
```sh
code --install-extension bin/roo-cline-<version>.vsix
```
---
Usamos [changesets](https://github.com/changesets/changesets) para el versionado y la publicación. Consulta nuestro `CHANGELOG.md` para ver las notas de la versión.
---
@ -174,16 +67,6 @@ Usamos [changesets](https://github.com/changesets/changesets) para el versionado
---
## Contribuciones
¡Amamos las contribuciones de la comunidad! Comienza leyendo nuestro [CONTRIBUTING.md](CONTRIBUTING.md).
---
## Licencia
[Apache 2.0 © 2025 Roo Code, Inc.](../../LICENSE)
---
**¡Disfruta de Roo Code!** Ya sea que lo mantengas con una correa corta o lo dejes deambular de forma autónoma, no podemos esperar a ver qué construyes. Si tienes preguntas o ideas sobre funcionalidades, pásate por nuestra [comunidad de Reddit](https://www.reddit.com/r/RooCode/) o [Discord](https://discord.gg/roocode). ¡Feliz codificación!

90
locales/fr/CODE_OF_CONDUCT.md generated
View file

@ -1,90 +0,0 @@
<div align="center">
<sub>
[English](../../CODE_OF_CONDUCT.md) • [Català](../ca/CODE_OF_CONDUCT.md) • [Deutsch](../de/CODE_OF_CONDUCT.md) • [Español](../es/CODE_OF_CONDUCT.md) • <b>Français</b> • [हिंदी](../hi/CODE_OF_CONDUCT.md) • [Bahasa Indonesia](../id/CODE_OF_CONDUCT.md) • [Italiano](../it/CODE_OF_CONDUCT.md) • [日本語](../ja/CODE_OF_CONDUCT.md)
</sub>
<sub>
[한국어](../ko/CODE_OF_CONDUCT.md) • [Nederlands](../nl/CODE_OF_CONDUCT.md) • [Polski](../pl/CODE_OF_CONDUCT.md) • [Português (BR)](../pt-BR/CODE_OF_CONDUCT.md) • [Русский](../ru/CODE_OF_CONDUCT.md) • [Türkçe](../tr/CODE_OF_CONDUCT.md) • [Tiếng Việt](../vi/CODE_OF_CONDUCT.md) • [简体中文](../zh-CN/CODE_OF_CONDUCT.md) • [繁體中文](../zh-TW/CODE_OF_CONDUCT.md)
</sub>
</div>
# Code de Conduite des Contributeurs
## Notre Engagement
Dans l'intérêt de favoriser un environnement ouvert et accueillant, nous nous
engageons, en tant que contributeurs et responsables, à faire de la participation
à notre projet et à notre communauté une expérience sans harcèlement pour tous,
indépendamment de l'âge, de la taille corporelle, du handicap, de l'origine ethnique,
des caractéristiques sexuelles, de l'identité et de l'expression de genre,
du niveau d'expérience, de l'éducation, du statut socio-économique, de la nationalité,
de l'apparence personnelle, de la race, de la religion, ou de l'orientation sexuelle.
## Nos Standards
Exemples de comportements qui contribuent à créer un environnement positif :
- Utiliser un langage accueillant et inclusif
- Respecter les différents points de vue et expériences
- Accepter gracieusement les critiques constructives
- Se concentrer sur ce qui est le mieux pour la communauté
- Faire preuve d'empathie envers les autres membres de la communauté
Exemples de comportements inacceptables de la part des participants :
- L'utilisation de langage ou d'images à caractère sexuel et l'attention ou les avances
sexuelles importunes
- Le trolling, les commentaires insultants/désobligeants, et les attaques personnelles ou politiques
- Le harcèlement public ou privé
- La publication d'informations privées d'autrui, telles que des informations physiques ou
électroniques, sans autorisation explicite
- Tout autre comportement qui pourrait raisonnablement être considéré comme inapproprié
dans un cadre professionnel
## Nos Responsabilités
Les mainteneurs de projet sont responsables de clarifier les standards de comportement
acceptable et sont censés prendre des mesures correctives appropriées et équitables en
réponse à tout cas de comportement inacceptable.
Les mainteneurs de projet ont le droit et la responsabilité de supprimer, modifier ou
rejeter les commentaires, commits, code, modifications du wiki, questions et autres contributions
qui ne sont pas alignés sur ce Code de Conduite, ou de bannir temporairement ou
définitivement tout contributeur pour d'autres comportements qu'ils jugent inappropriés,
menaçants, offensants ou nuisibles.
## Portée
Ce Code de Conduite s'applique à la fois dans les espaces du projet et dans les espaces
publics lorsqu'un individu représente le projet ou sa communauté. Les exemples de
représentation d'un projet ou d'une communauté incluent l'utilisation d'une adresse e-mail
officielle du projet, la publication via un compte officiel sur les réseaux sociaux,
ou le fait d'agir en tant que représentant désigné lors d'un événement en ligne ou hors ligne.
La représentation d'un projet peut être définie et clarifiée davantage par les mainteneurs du projet.
## Application
Les cas de comportement abusif, harcelant ou autrement inacceptable peuvent être
signalés en contactant l'équipe du projet à support@roocode.com. Toutes les plaintes
seront examinées et étudiées et donneront lieu à une réponse qui
est jugée nécessaire et appropriée aux circonstances. L'équipe du projet est
obligée de maintenir la confidentialité concernant la personne qui signale un incident.
Des détails supplémentaires sur des politiques d'application spécifiques peuvent être publiés séparément.
Les mainteneurs de projet qui ne suivent ou n'appliquent pas le Code de Conduite de bonne
foi peuvent faire face à des répercussions temporaires ou permanentes déterminées par d'autres
membres de la direction du projet.
## Attribution
Ce Code de Conduite est adapté de la [version de Cline][cline_coc] du [Contributor Covenant][homepage], version 1.4,
disponible à https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[cline_coc]: https://github.com/cline/cline/blob/main/CODE_OF_CONDUCT.md
[homepage]: https://www.contributor-covenant.org
Pour obtenir des réponses aux questions courantes sur ce code de conduite, voir
https://www.contributor-covenant.org/faq

141
locales/fr/CONTRIBUTING.md generated
View file

@ -1,141 +0,0 @@
<div align="center">
<sub>
[English](../../CONTRIBUTING.md) • [Català](../ca/CONTRIBUTING.md) • [Deutsch](../de/CONTRIBUTING.md) • [Español](../es/CONTRIBUTING.md) • <b>Français</b> • [हिंदी](../hi/CONTRIBUTING.md) • [Bahasa Indonesia](../id/CONTRIBUTING.md) • [Italiano](../it/CONTRIBUTING.md) • [日本語](../ja/CONTRIBUTING.md)
</sub>
<sub>
[한국어](../ko/CONTRIBUTING.md) • [Nederlands](../nl/CONTRIBUTING.md) • [Polski](../pl/CONTRIBUTING.md) • [Português (BR)](../pt-BR/CONTRIBUTING.md) • [Русский](../ru/CONTRIBUTING.md) • [Türkçe](../tr/CONTRIBUTING.md) • [Tiếng Việt](../vi/CONTRIBUTING.md) • [简体中文](../zh-CN/CONTRIBUTING.md) • [繁體中文](../zh-TW/CONTRIBUTING.md)
</sub>
</div>
# Contribuer à Roo Code
Roo Code est un projet communautaire, et nous apprécions profondément chaque contribution. Pour simplifier la collaboration, nous fonctionnons sur une base [d'abord l'issue](#approche-issue-first), ce qui signifie que toutes les [Pull Requests (PRs)](#soumettre-une-pull-request) doivent d'abord être liées à une Issue GitHub. Veuillez lire attentivement ce guide.
## Table des matières
- [Avant de contribuer](#avant-de-contribuer)
- [Trouver et planifier votre contribution](#trouver-et-planifier-votre-contribution)
- [Processus de développement et de soumission](#processus-de-développement-et-de-soumission)
- [Légal](#légal)
## Avant de contribuer
### 1. Code de conduite
Tous les contributeurs doivent adhérer à notre [Code de conduite](./CODE_OF_CONDUCT.md).
### 2. Feuille de route du projet
Notre feuille de route guide la direction du projet. Alignez vos contributions sur ces objectifs clés :
### La fiabilité d'abord
- Assurez-vous que l'édition de diff et l'exécution de commandes sont fiables de manière constante.
- Réduisez les points de friction qui découragent une utilisation régulière.
- Garantissez un fonctionnement fluide dans toutes les langues et sur toutes les plateformes.
- Étendez le support robuste à une grande variété de fournisseurs et de modèles d'IA.
### Expérience utilisateur améliorée
- Simplifiez l'UI/UX pour plus de clarté et d'intuitivité.
- Améliorez continuellement le flux de travail pour répondre aux attentes élevées des développeurs pour les outils à usage quotidien.
### Leader en performance d'agent
- Établissez des benchmarks d'évaluation complets (evals) pour mesurer la productivité en conditions réelles.
- Facilitez l'exécution et l'interprétation de ces évaluations par tout le monde.
- Livrez des améliorations qui démontrent des augmentations claires des scores d'évaluation.
Mentionnez l'alignement avec ces domaines dans vos PRs.
### 3. Rejoignez la communauté Roo Code
- **Principal :** Rejoignez notre [Discord](https://discord.gg/roocode) et envoyez un DM à **Hannes Rudolph (`hrudolph`)**.
- **Alternative :** Les contributeurs expérimentés peuvent s'engager directement via les [Projets GitHub](https://github.com/orgs/RooCodeInc/projects/1).
## Trouver et planifier votre contribution
### Types de contributions
- **Corrections de bugs :** Résoudre les problèmes de code.
- **Nouvelles fonctionnalités :** Ajouter des fonctionnalités.
- **Documentation :** Améliorer les guides et la clarté.
### Approche Issue-First
Toutes les contributions commencent par une Issue GitHub en utilisant nos modèles simples.
- **Vérifiez les issues existantes** : Recherchez dans les [Issues GitHub](https://github.com/RooCodeInc/Roo-Code/issues).
- **Créez une issue** en utilisant :
- **Améliorations :** Modèle "Demande d'amélioration" (langage simple axé sur l'avantage pour l'utilisateur).
- **Bugs :** Modèle "Rapport de bug" (reproduction minimale + attendu vs réel + version).
- **Vous voulez y travailler ?** Commentez "Claiming" sur l'issue et envoyez un DM à **Hannes Rudolph (`hrudolph`)** sur [Discord](https://discord.gg/roocode) pour être assigné. L'assignation sera confirmée dans le fil de discussion.
- **Les PRs doivent être liées à l'issue.** Les PRs non liées peuvent être fermées.
### Décider sur quoi travailler
- Consultez le [Projet GitHub](https://github.com/orgs/RooCodeInc/projects/1) pour les issues "Issue [Non assignée]".
- Pour la documentation, visitez [Roo Code Docs](https://github.com/RooCodeInc/Roo-Code-Docs).
### Signaler des bugs
- Vérifiez d'abord les rapports existants.
- Créez un nouveau bug en utilisant le [modèle "Rapport de bug"](https://github.com/RooCodeInc/Roo-Code/issues/new/choose) avec :
- Des étapes de reproduction claires et numérotées
- Résultat attendu vs réel
- Version de Roo Code (requise) ; fournisseur/modèle d'API si pertinent
- **Problèmes de sécurité** : Signalez-les en privé via les [avis de sécurité](https://github.com/RooCodeInc/Roo-Code/security/advisories/new).
## Processus de développement et de soumission
### Configuration du développement
1. **Fork & Cloner :**
```
git clone https://github.com/VOTRE_NOM_UTILISATEUR/Roo-Code.git
```
2. **Installer les dépendances :**
```
pnpm install
```
3. **Débogage :** Ouvrir avec VS Code (`F5`).
### Lignes directrices pour l'écriture de code
- Une PR ciblée par fonctionnalité ou correction.
- Suivez les meilleures pratiques d'ESLint et de TypeScript.
- Rédigez des commits clairs et descriptifs faisant référence aux issues (par exemple, `Fixes #123`).
- Fournissez des tests approfondis (`npm test`).
- Rebasez sur la dernière branche `main` avant la soumission.
### Soumettre une Pull Request
- Commencez par une **PR en brouillon** si vous recherchez des commentaires précoces.
- Décrivez clairement vos changements en suivant le modèle de Pull Request.
- Liez l'issue dans la description/le titre de la PR (par exemple, "Fixes #123").
- Fournissez des captures d'écran/vidéos pour les changements d'interface utilisateur.
- Indiquez si des mises à jour de la documentation sont nécessaires.
### Politique de Pull Request
- Doit faire référence à une Issue GitHub assignée. Pour être assigné : commentez "Claiming" sur l'issue et envoyez un DM à **Hannes Rudolph (`hrudolph`)** sur [Discord](https://discord.gg/roocode). L'assignation sera confirmée dans le fil de discussion.
- Les PRs non liées peuvent être fermées.
- Les PRs doivent passer les tests d'intégration continue, s'aligner sur la feuille de route et avoir une documentation claire.
### Processus de révision
- **Triage quotidien :** Vérifications rapides par les mainteneurs.
- **Révision hebdomadaire approfondie :** Évaluation complète.
- **Itérez rapidement** en fonction des commentaires.
## Légal
En contribuant, vous acceptez que vos contributions soient sous licence Apache 2.0, conformément à la licence de Roo Code.

117
locales/fr/README.md generated
View file

@ -1,32 +1,11 @@
<p align="center">
<a href="https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline"><img src="https://img.shields.io/badge/VS_Code_Marketplace-007ACC?style=flat&logo=visualstudiocode&logoColor=white" alt="VS Code Marketplace"></a>
<a href="https://x.com/roocode"><img src="https://img.shields.io/badge/roocode-000000?style=flat&logo=x&logoColor=white" alt="X"></a>
<a href="https://youtube.com/@roocodeyt?feature=shared"><img src="https://img.shields.io/badge/YouTube-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube"></a>
<a href="https://discord.gg/roocode"><img src="https://img.shields.io/badge/Join%20Discord-5865F2?style=flat&logo=discord&logoColor=white" alt="Join Discord"></a>
<a href="https://www.reddit.com/r/RooCode/"><img src="https://img.shields.io/badge/Join%20r%2FRooCode-FF4500?style=flat&logo=reddit&logoColor=white" alt="Join r/RooCode"></a>
</p>
<p align="center">
<em>Obtenez de l'aide rapidement → <a href="https://discord.gg/roocode">Rejoignez Discord</a> • Vous préférez l'asynchrone ? → <a href="https://www.reddit.com/r/RooCode/">Rejoignez r/RooCode</a></em>
</p>
# Roo Code
> Ton équipe de dev propulsée par l'IA, directement dans ton éditeur
## Nouveautés de la v3.53.0
> ### L'extension Roo Code ne va pas disparaître.
>
> Tu as peut-être vu l'[annonce récente](https://x.com/mattrubens/status/2046636598859559114) : Roo Code a franchi les 3 millions d'installations et l'équipe d'origine se consacre désormais entièrement à Roomote. On sait que cette nouvelle a été difficile pour beaucoup d'entre vous. Cette extension compte énormément pour nous comme pour toi, et on t'entend.
>
> La bonne nouvelle : **une équipe de la communauté a décidé de prendre le relais pour faire avancer Roo Code**, et on travaille avec eux sur une transmission officielle pour que l'extension sur laquelle tu comptes continue d'être maintenue et améliorée.
**Nouveautés de cette version :**
- Ajout du support de GPT-5.5 via le fournisseur OpenAI Codex.
- Ajout du support de Claude Opus 4.7 sur Vertex AI.
- Ajout de contrôles de navigation vers les checkpoints précédents dans le chat pour que tu puisses revenir en arrière plus facilement à travers les checkpoints antérieurs.
<details>
<summary>🌐 Langues disponibles</summary>
@ -75,96 +54,10 @@ Roo Code s'adapte à votre façon de travailler, pas l'inverse :
En savoir plus : [Utiliser les Modes](https://docs.roocode.com/basic-usage/using-modes) • [Modes personnalisés](https://docs.roocode.com/advanced-usage/custom-modes)
## Tutoriels & Vidéos de fonctionnalités
<div align="center">
| | | |
| :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <a href="https://www.youtube.com/watch?v=Mcq3r1EPZ-4"><img src="https://img.youtube.com/vi/Mcq3r1EPZ-4/maxresdefault.jpg" width="100%"></a><br><b>Installer Roo Code</b> | <a href="https://www.youtube.com/watch?v=ZBML8h5cCgo"><img src="https://img.youtube.com/vi/ZBML8h5cCgo/maxresdefault.jpg" width="100%"></a><br><b>Configurer les profils</b> | <a href="https://www.youtube.com/watch?v=r1bpod1VWhg"><img src="https://img.youtube.com/vi/r1bpod1VWhg/maxresdefault.jpg" width="100%"></a><br><b>Indexation de la base de code</b> |
| <a href="https://www.youtube.com/watch?v=iiAv1eKOaxk"><img src="https://img.youtube.com/vi/iiAv1eKOaxk/maxresdefault.jpg" width="100%"></a><br><b>Modes personnalisés</b> | <a href="https://www.youtube.com/watch?v=Ho30nyY332E"><img src="https://img.youtube.com/vi/Ho30nyY332E/maxresdefault.jpg" width="100%"></a><br><b>Checkpoints</b> | <a href="https://www.youtube.com/watch?v=HmnNSasv7T8"><img src="https://img.youtube.com/vi/HmnNSasv7T8/maxresdefault.jpg" width="100%"></a><br><b>Gestion du Contexte</b> |
</div>
<p align="center">
<a href="https://docs.roocode.com/tutorial-videos">Plus de tutoriels rapides et de vidéos de fonctionnalités...</a>
</p>
## Ressources
- **[Documentation](https://docs.roocode.com):** Le guide officiel pour installer, configurer et maîtriser Roo Code.
- **[Chaîne YouTube](https://youtube.com/@roocodeyt?feature=shared):** Regardez des tutoriels et découvrez les fonctionnalités en action.
- **[Serveur Discord](https://discord.gg/roocode):** Rejoignez la communauté pour obtenir de l'aide en temps réel et discuter.
- **[Communauté Reddit](https://www.reddit.com/r/RooCode):** Partagez vos expériences et découvrez ce que les autres construisent.
- **[Problèmes GitHub](https://github.com/RooCodeInc/Roo-Code/issues):** Signalez des bugs et suivez le développement.
- **[Demandes de fonctionnalités](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop):** Vous avez une idée ? Partagez-la avec les développeurs.
---
## Configuration et développement local
1. **Clonez** le dépôt :
```sh
git clone https://github.com/RooCodeInc/Roo-Code.git
```
2. **Installez les dépendances** :
```sh
pnpm install
```
3. **Exécutez l'extension** :
Il existe plusieurs façons d'exécuter l'extension Roo Code :
### Mode développement (F5)
Pour un développement actif, utilisez le débogage intégré de VSCode :
Appuyez sur `F5` (ou allez dans **Exécuter** → **Démarrer le débogage**) dans VSCode. Cela ouvrira une nouvelle fenêtre VSCode avec l'extension Roo Code en cours d'exécution.
- Les modifications apportées à la vue Web apparaîtront immédiatement.
- Les modifications apportées à l'extension principale se rechargeront également à chaud automatiquement.
### Installation automatisée de VSIX
Pour compiler et installer l'extension en tant que package VSIX directement dans VSCode :
```sh
pnpm install:vsix [-y] [--editor=<command>]
```
Cette commande va :
- Demander quelle commande d'éditeur utiliser (code/cursor/code-insiders) - par défaut, 'code'
- Désinstaller toute version existante de l'extension.
- Compiler le dernier package VSIX.
- Installer le VSIX nouvellement compilé.
- Vous inviter à redémarrer VS Code pour que les modifications prennent effet.
Options :
- `-y` : Ignorer toutes les invites de confirmation et utiliser les valeurs par défaut
- `--editor=<command>` : Spécifier la commande de l'éditeur (par exemple, `--editor=cursor` ou `--editor=code-insiders`)
### Installation manuelle de VSIX
Si vous préférez installer le package VSIX manuellement :
1. D'abord, compilez le package VSIX :
```sh
pnpm vsix
```
2. Un fichier `.vsix` sera généré dans le répertoire `bin/` (par exemple, `bin/roo-cline-<version>.vsix`).
3. Installez-le manuellement à l'aide de la CLI de VSCode :
```sh
code --install-extension bin/roo-cline-<version>.vsix
```
---
Nous utilisons [changesets](https://github.com/changesets/changesets) pour la gestion des versions et la publication. Consultez notre `CHANGELOG.md` pour les notes de version.
---
@ -174,16 +67,6 @@ Nous utilisons [changesets](https://github.com/changesets/changesets) pour la ge
---
## Contribuer
Nous adorons les contributions de la communauté ! Commencez par lire notre [CONTRIBUTING.md](CONTRIBUTING.md).
---
## Licence
[Apache 2.0 © 2025 Roo Code, Inc.](../../LICENSE)
---
**Profitez de Roo Code !** Que vous le teniez en laisse courte ou que vous le laissiez errer de manière autonome, nous sommes impatients de voir ce que vous allez construire. Si vous avez des questions ou des idées de fonctionnalités, n'hésitez pas à passer sur notre [communauté Reddit](https://www.reddit.com/r/RooCode/) ou sur [Discord](https://discord.gg/roocode). Bon codage !

88
locales/hi/CODE_OF_CONDUCT.md generated
View file

@ -1,88 +0,0 @@
<div align="center">
<sub>
[English](../../CODE_OF_CONDUCT.md) • [Català](../ca/CODE_OF_CONDUCT.md) • [Deutsch](../de/CODE_OF_CONDUCT.md) • [Español](../es/CODE_OF_CONDUCT.md) • [Français](../fr/CODE_OF_CONDUCT.md) • <b>हिंदी</b> • [Bahasa Indonesia](../id/CODE_OF_CONDUCT.md) • [Italiano](../it/CODE_OF_CONDUCT.md) • [日本語](../ja/CODE_OF_CONDUCT.md)
</sub>
<sub>
[한국어](../ko/CODE_OF_CONDUCT.md) • [Nederlands](../nl/CODE_OF_CONDUCT.md) • [Polski](../pl/CODE_OF_CONDUCT.md) • [Português (BR)](../pt-BR/CODE_OF_CONDUCT.md) • [Русский](../ru/CODE_OF_CONDUCT.md) • [Türkçe](../tr/CODE_OF_CONDUCT.md) • [Tiếng Việt](../vi/CODE_OF_CONDUCT.md) • [简体中文](../zh-CN/CODE_OF_CONDUCT.md) • [繁體中文](../zh-TW/CODE_OF_CONDUCT.md)
</sub>
</div>
# योगदानकर्ता संधि आचार संहिता
## हमारी प्रतिज्ञा
एक खुले और स्वागतयोग्य वातावरण को बढ़ावा देने के हित में, हम
योगदानकर्ता और अनुरक्षक प्रतिज्ञा करते हैं कि हमारे प्रोजेक्ट और
हमारे समुदाय में भागीदारी को हर किसी के लिए उत्पीड़न-मुक्त अनुभव बनाएंगे, चाहे उम्र, शरीर
आकार, विकलांगता, जातीयता, यौन विशेषताएं, लिंग पहचान और अभिव्यक्ति,
अनुभव का स्तर, शिक्षा, सामाजिक-आर्थिक स्थिति, राष्ट्रीयता, व्यक्तिगत
उपस्थिति, नस्ल, धर्म, या यौन पहचान और अभिविन्यास कुछ भी हो।
## हमारे मानक
सकारात्मक वातावरण बनाने में योगदान देने वाले व्यवहार के उदाहरणों
में शामिल हैं:
- स्वागतयोग्य और समावेशी भाषा का उपयोग
- भिन्न दृष्टिकोणों और अनुभवों का सम्मान करना
- रचनात्मक आलोचना को सौम्यता से स्वीकार करना
- समुदाय के लिए जो सबसे अच्छा है उस पर ध्यान केंद्रित करना
- अन्य समुदाय सदस्यों के प्रति सहानुभूति दिखाना
प्रतिभागियों द्वारा अस्वीकार्य व्यवहार के उदाहरणों में शामिल हैं:
- यौन भाषा या छवियों का उपयोग और अवांछित यौन ध्यान या
अग्रिम कदम
- ट्रोलिंग, अपमानजनक/अपमानकारी टिप्पणियां, और व्यक्तिगत या राजनीतिक हमले
- सार्वजनिक या निजी उत्पीड़न
- दूसरों की निजी जानकारी, जैसे भौतिक या इलेक्ट्रॉनिक
पता, बिना स्पष्ट अनुमति के प्रकाशित करना
- अन्य आचरण जिसे एक
पेशेवर सेटिंग में अनुचित माना जा सकता है
## हमारी जिम्मेदारियां
प्रोजेक्ट अनुरक्षक स्वीकार्य व्यवहार के मानकों को स्पष्ट करने के लिए जिम्मेदार हैं
और उनसे अस्वीकार्य व्यवहार के किसी भी उदाहरण के जवाब में उचित और निष्पक्ष सुधारात्मक कार्रवाई करने की उम्मीद की जाती है।
प्रोजेक्ट अनुरक्षकों के पास टिप्पणियों, कमिट्स, कोड, विकी संपादनों, मुद्दों और अन्य योगदानों को हटाने, संपादित करने या
अस्वीकार करने का अधिकार और जिम्मेदारी है जो इस आचार संहिता के अनुरूप नहीं हैं, या किसी भी योगदानकर्ता को अस्थायी रूप से या
स्थायी रूप से प्रतिबंधित करने का अधिकार है जिन्हें वे अनुचित,
धमकी देने वाला, आक्रामक, या हानिकारक व्यवहार मानते हैं।
## दायरा
यह आचार संहिता प्रोजेक्ट स्थानों के भीतर और सार्वजनिक स्थानों दोनों में लागू होती है
जब कोई व्यक्ति प्रोजेक्ट या उसके समुदाय का प्रतिनिधित्व कर रहा हो। परियोजना का
प्रतिनिधित्व करने के उदाहरणों में आधिकारिक प्रोजेक्ट ई-मेल का उपयोग शामिल है,
आधिकारिक सोशल मीडिया अकाउंट के माध्यम से पोस्टिंग, या नियुक्त किए गए प्रतिनिधि के रूप में कार्य करना
ऑनलाइन या ऑफलाइन इवेंट में। प्रोजेक्ट का प्रतिनिधित्व आगे
प्रोजेक्ट अनुरक्षकों द्वारा परिभाषित और स्पष्ट किया जा सकता है।
## प्रवर्तन
दुर्व्यवहार, उत्पीड़न, या अन्यथा अस्वीकार्य व्यवहार के उदाहरणों की
रिपोर्ट support@roocode.com पर प्रोजेक्ट टीम से संपर्क करके की जा सकती है। सभी शिकायतें
समीक्षा की जाएंगी और जांच की जाएगी और इसके परिणामस्वरूप एक प्रतिक्रिया होगी जो
परिस्थितियों के अनुसार आवश्यक और उचित मानी जाती है। प्रोजेक्ट टीम
एक घटना के रिपोर्टर के संबंध में गोपनीयता बनाए रखने के लिए बाध्य है।
विशिष्ट प्रवर्तन नीतियों के अतिरिक्त विवरण अलग से पोस्ट किए जा सकते हैं।
प्रोजेक्ट अनुरक्षक जो आचार संहिता का पालन या लागू नहीं करते हैं
सद्भाव से, प्रोजेक्ट के अन्य नेतृत्व सदस्यों द्वारा निर्धारित अस्थायी या
स्थायी प्रतिक्रियाओं का सामना कर सकते हैं।
## श्रेय
यह आचार संहिता [Cline के संस्करण][cline_coc] से अनुकूलित है [योगदानकर्ता संधि][homepage], संस्करण 1.4,
जो यहां उपलब्ध है https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[cline_coc]: https://github.com/cline/cline/blob/main/CODE_OF_CONDUCT.md
[homepage]: https://www.contributor-covenant.org
इस आचार संहिता के बारे में आम सवालों के जवाब के लिए, देखें
https://www.contributor-covenant.org/faq

141
locales/hi/CONTRIBUTING.md generated
View file

@ -1,141 +0,0 @@
<div align="center">
<sub>
[English](../../CONTRIBUTING.md) • [Català](../ca/CONTRIBUTING.md) • [Deutsch](../de/CONTRIBUTING.md) • [Español](../es/CONTRIBUTING.md) • [Français](../fr/CONTRIBUTING.md) • <b>हिंदी</b> • [Bahasa Indonesia](../id/CONTRIBUTING.md) • [Italiano](../it/CONTRIBUTING.md) • [日本語](../ja/CONTRIBUTING.md)
</sub>
<sub>
[한국어](../ko/CONTRIBUTING.md) • [Nederlands](../nl/CONTRIBUTING.md) • [Polski](../pl/CONTRIBUTING.md) • [Português (BR)](../pt-BR/CONTRIBUTING.md) • [Русский](../ru/CONTRIBUTING.md) • [Türkçe](../tr/CONTRIBUTING.md) • [Tiếng Việt](../vi/CONTRIBUTING.md) • [简体中文](../zh-CN/CONTRIBUTING.md) • [繁體中文](../zh-TW/CONTRIBUTING.md)
</sub>
</div>
# Roo Code में योगदान
Roo Code एक समुदाय-संचालित परियोजना है, और हम हर योगदान को बहुत महत्व देते हैं। सहयोग को सुव्यवस्थित करने के لیے, हम [पहले-समस्या दृष्टिकोण](#समस्या-पहले-दृष्टिकोण) पर काम करते हैं, जिसका अर्थ है कि सभी [पुल अनुरोध (पीआर)](#एक-पुल-अनुरोध-सबमिट-करना) पहले एक गिटहब समस्या से जुड़े होने चाहिए। कृपया इस गाइड की सावधानीपूर्वक समीक्षा करें।
## विषय-सूची
- [योगदान करने से पहले](#योगदान-करने-से-पहले)
- [अपना योगदान ढूँढना और योजना बनाना](#अपना-योगदान-ढूँढना-और-योजना-बनाना)
- [विकास और प्रस्तुत करने की प्रक्रिया](#विकास-और-प्रस्तुत-करने-की-प्रक्रिया)
- [कानूनी](#कानूनी)
## योगदान करने से पहले
### 1. आचार संहिता
सभी योगदानकर्ताओं को हमारी [आचार संहिता](./CODE_OF_CONDUCT.md) का पालन करना होगा।
### 2. परियोजना का रोडमैप
हमारा रोडमैप परियोजना की दिशा का मार्गदर्शन करता है। अपने योगदानों को इन प्रमुख लक्ष्यों के साथ संरेखित करें:
### विश्वसनीयता पहले
- सुनिश्चित करें कि डिफ़ संपादन और कमांड निष्पादन लगातार विश्वसनीय हैं।
- नियमित उपयोग को रोकने वाले घर्षण बिंदुओं को कम करें।
- सभी लोकेल और प्लेटफार्मों पर सुचारू संचालन की गारंटी दें।
- विभिन्न प्रकार के एआई प्रदाताओं और मॉडलों के लिए मजबूत समर्थन का विस्तार करें।
### उन्नत उपयोगकर्ता अनुभव
- स्पष्टता और सहजता के लिए यूआई/यूएक्स को सुव्यवस्थित करें।
- दैनिक उपयोग के उपकरणों के लिए डेवलपर्स की उच्च अपेक्षाओं को पूरा करने के लिए वर्कफ़्लो में लगातार सुधार करें।
### एजेंट प्रदर्शन में अग्रणी
- वास्तविक दुनिया की उत्पादकता को मापने के लिए व्यापक मूल्यांकन बेंचमार्क (evals) स्थापित करें।
- सभी के लिए इन मूल्यांकनों को आसानी से चलाना और व्याख्या करना आसान बनाएं।
- ऐसे सुधार भेजें जो मूल्यांकन स्कोर में स्पष्ट वृद्धि प्रदर्शित करते हैं।
अपने पीआर में इन क्षेत्रों के साथ संरेखण का उल्लेख करें।
### 3. Roo Code समुदाय में शामिल हों
- **प्राथमिक:** हमारे [डिस्कॉर्ड](https://discord.gg/roocode) में शामिल हों और **Hannes Rudolph (`hrudolph`)** को डीएम करें।
- **वैकल्पिक:** अनुभवी योगदानकर्ता [गिटहब प्रोजेक्ट्स](https://github.com/orgs/RooCodeInc/projects/1) के माध्यम से सीधे जुड़ सकते हैं।
## अपना योगदान ढूँढना और योजना बनाना
### योगदान के प्रकार
- **बग फिक्स:** कोड समस्याओं का समाधान करना।
- **नई सुविधाएँ:** कार्यक्षमता जोड़ना।
- **दस्तावेज़ीकरण:** गाइड और स्पष्टता में सुधार।
### समस्या-पहले दृष्टिकोण
सभी योगदान हमारे पतले टेम्पलेट्स का उपयोग करके एक गिटहब समस्या से शुरू होते हैं।
- **मौजूदा समस्याओं की जाँच करें**: [गिटहब समस्याएँ](https://github.com/RooCodeInc/Roo-Code/issues) में खोजें।
- **एक समस्या बनाएँ** का उपयोग करके:
- **सुधार:** "सुधार अनुरोध" टेम्पलेट (उपयोगकर्ता लाभ पर केंद्रित सरल भाषा)।
- **बग:** "बग रिपोर्ट" टेम्पलेट (न्यूनतम प्रतिकृति + अपेक्षित बनाम वास्तविक + संस्करण)।
- **इस पर काम करना चाहते हैं?** समस्या पर "दावा करना" टिप्पणी करें और असाइन होने के लिए [डिस्कॉर्ड](https://discord.gg/roocode) पर **Hannes Rudolph (`hrudolph`)** को डीएम करें। असाइनमेंट की पुष्टि थ्रेड में की जाएगी।
- **पीआर को समस्या से लिंक करना होगा।** अनलिंक किए गए पीआर बंद किए जा सकते हैं।
### क्या काम करना है यह तय करना
- "समस्या [असाइन नहीं की गई]" समस्याओं के लिए [गिटहब प्रोजेक्ट](https://github.com/orgs/RooCodeInc/projects/1) की जाँच करें।
- दस्तावेज़ों के लिए, [Roo Code दस्तावेज़](https://github.com/RooCodeInc/Roo-Code-Docs) पर जाएँ।
### बग की रिपोर्ट करना
- पहले मौजूदा रिपोर्ट की जाँच करें।
- ["बग रिपोर्ट" टेम्पलेट](https://github.com/RooCodeInc/Roo-Code/issues/new/choose) का उपयोग करके एक नया बग बनाएँ:
- स्पष्ट, क्रमांकित पुनरुत्पादन चरण
- अपेक्षित बनाम वास्तविक परिणाम
- Roo Code संस्करण (आवश्यक); यदि प्रासंगिक हो तो एपीआई प्रदाता/मॉडल
- **सुरक्षा समस्याएँ**: [सुरक्षा सलाहकारों](https://github.com/RooCodeInc/Roo-Code/security/advisories/new) के माध्यम से निजी तौर पर रिपोर्ट करें।
## विकास और प्रस्तुत करने की प्रक्रिया
### विकास सेटअप
1. **फोर्क और क्लोन:**
```
git clone https://github.com/आपका_उपयोगकर्ता_नाम/Roo-Code.git
```
2. **निर्भरताएँ स्थापित करें:**
```
pnpm install
```
3. **डीबगिंग:** वीएस कोड (`F5`) के साथ खोलें।
### कोड लिखने के दिशानिर्देश
- प्रति सुविधा या फिक्स एक केंद्रित पीआर।
- ESLint और TypeScript की सर्वोत्तम प्रथाओं का पालन करें।
- समस्याओं का संदर्भ देने वाले स्पष्ट, वर्णनात्मक कमिट लिखें (उदाहरण के लिए, `फिक्स #123`)।
- पूरी तरह से परीक्षण प्रदान करें (`npm test`)।
- प्रस्तुत करने से पहले नवीनतम `main` शाखा पर रीबेस करें।
### एक पुल अनुरोध सबमिट करना
- यदि आप जल्दी प्रतिक्रिया चाहते हैं तो **ड्राफ्ट पीआर** के रूप में शुरू करें।
- पुल अनुरोध टेम्पलेट का पालन करते हुए अपने परिवर्तनों का स्पष्ट रूप से वर्णन करें।
- पीआर विवरण/शीर्षक में समस्या को लिंक करें (उदाहरण के लिए, "फिक्स #123")।
- यूआई परिवर्तनों के लिए स्क्रीनशॉट/वीडियो प्रदान करें।
- इंगित करें कि क्या दस्तावेज़ीकरण अद्यतन आवश्यक हैं।
### पुल अनुरोध नीति
- एक असाइन की गई गिटहब समस्या का संदर्भ देना होगा। असाइन होने के लिए: समस्या पर "दावा करना" टिप्पणी करें और [डिस्कॉर्ड](https://discord.gg/roocode) पर **Hannes Rudolph (`hrudolph`)** को डीएम करें। असाइनमेंट की पुष्टि थ्रेड में की जाएगी।
- अनलिंक किए गए पीआर बंद किए जा सकते हैं।
- पीआर को सीआई परीक्षण पास करना होगा, रोडमैप के साथ संरेखित होना होगा, और स्पष्ट दस्तावेज़ीकरण होना होगा।
### समीक्षा प्रक्रिया
- **दैनिक ट्राइएज:** अनुरक्षकों द्वारा त्वरित जाँच।
- **साप्ताहिक गहन समीक्षा:** व्यापक मूल्यांकन।
- **प्रतिक्रिया के आधार पर तुरंत पुनरावृति करें**।
## कानूनी
योगदान करके, आप सहमत हैं कि आपके योगदान अपाचे 2.0 लाइसेंस के तहत लाइसेंस प्राप्त होंगे, जो Roo Code के लाइसेंस के अनुरूप है।

117
locales/hi/README.md generated
View file

@ -1,32 +1,11 @@
<p align="center">
<a href="https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline"><img src="https://img.shields.io/badge/VS_Code_Marketplace-007ACC?style=flat&logo=visualstudiocode&logoColor=white" alt="VS Code Marketplace"></a>
<a href="https://x.com/roocode"><img src="https://img.shields.io/badge/roocode-000000?style=flat&logo=x&logoColor=white" alt="X"></a>
<a href="https://youtube.com/@roocodeyt?feature=shared"><img src="https://img.shields.io/badge/YouTube-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube"></a>
<a href="https://discord.gg/roocode"><img src="https://img.shields.io/badge/Join%20Discord-5865F2?style=flat&logo=discord&logoColor=white" alt="Join Discord"></a>
<a href="https://www.reddit.com/r/RooCode/"><img src="https://img.shields.io/badge/Join%20r%2FRooCode-FF4500?style=flat&logo=reddit&logoColor=white" alt="Join r/RooCode"></a>
</p>
<p align="center">
<em>जल्दी मदद पाएं → <a href="https://discord.gg/roocode">डिस्कॉर्ड से जुड़ें</a> • एसिंक पसंद है? → <a href="https://www.reddit.com/r/RooCode/">r/RooCode से जुड़ें</a></em>
</p>
# Roo Code
> तुम्हारी AI-संचालित डेवलपमेंट टीम, सीधे तुम्हारे एडिटर में
## v3.53.0 में नया क्या है
> ### Roo Code plugin कहीं नहीं जा रहा है।
>
> आपने शायद [हाल ही की घोषणा](https://x.com/mattrubens/status/2046636598859559114) देखी होगी कि Roo Code ने 30 लाख installs पार कर लिए हैं और मूल टीम पूरी तरह Roomote पर focus कर रही है। हम जानते हैं कि यह खबर आप में से कई के लिए कठिन थी। यह plugin हमारे और आपके लिए बहुत मायने रखता है, और हम आपकी बात सुन रहे हैं।
>
> अच्छी खबर: **एक community team ने Roo Code को आगे ले जाने की ज़िम्मेदारी ली है**, और हम उनके साथ एक आधिकारिक handoff पर काम कर रहे हैं ताकि जिस plugin पर आप भरोसा करते हैं, उसका maintenance और improvement जारी रहे।
**इस रिलीज़ में नया क्या है:**
- OpenAI Codex provider के माध्यम से GPT-5.5 support जोड़ा गया।
- Vertex AI पर Claude Opus 4.7 support जोड़ा गया।
- चैट में पिछले checkpoint navigation controls जोड़े गए ताकि आप पिछले checkpoints पर आसानी से वापस जा सकें।
<details>
<summary>🌐 उपलब्ध भाषाएँ</summary>
@ -75,96 +54,10 @@
और जानो: [मोड्स का इस्तेमाल](https://docs.roocode.com/basic-usage/using-modes) • [कस्टम मोड्स](https://docs.roocode.com/advanced-usage/custom-modes)
## ट्यूटोरियल और फ़ीचर वीडियो
<div align="center">
| | | |
| :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <a href="https://www.youtube.com/watch?v=Mcq3r1EPZ-4"><img src="https://img.youtube.com/vi/Mcq3r1EPZ-4/maxresdefault.jpg" width="100%"></a><br><b>रू कोड इंस्टॉल करना</b> | <a href="https://www.youtube.com/watch?v=ZBML8h5cCgo"><img src="https://img.youtube.com/vi/ZBML8h5cCgo/maxresdefault.jpg" width="100%"></a><br><b>प्रोफाइल कॉन्फ़िगर करना</b> | <a href="https://www.youtube.com/watch?v=r1bpod1VWhg"><img src="https://img.youtube.com/vi/r1bpod1VWhg/maxresdefault.jpg" width="100%"></a><br><b>कोडबेस इंडेक्सिंग</b> |
| <a href="https://www.youtube.com/watch?v=iiAv1eKOaxk"><img src="https://img.youtube.com/vi/iiAv1eKOaxk/maxresdefault.jpg" width="100%"></a><br><b>कस्टम मोड</b> | <a href="https://www.youtube.com/watch?v=Ho30nyY332E"><img src="https://img.youtube.com/vi/Ho30nyY332E/maxresdefault.jpg" width="100%"></a><br><b>चेकपॉइंट्स</b> | <a href="https://www.youtube.com/watch?v=HmnNSasv7T8"><img src="https://img.youtube.com/vi/HmnNSasv7T8/maxresdefault.jpg" width="100%"></a><br><b>संदर्भ प्रबंधन</b> |
</div>
<p align="center">
<a href="https://docs.roocode.com/tutorial-videos">अधिक त्वरित ट्यूटोरियल और फ़ीचर वीडियो...</a>
</p>
## संसाधन
- **[दस्तावेज़ीकरण](https://docs.roocode.com):** Roo Code को स्थापित करने, कॉन्फ़िगर करने और उसमें महारत हासिल करने के लिए आधिकारिक गाइड।
- **[यूट्यूब चैनल](https://youtube.com/@roocodeyt?feature=shared):** ट्यूटोरियल देखें और सुविधाओं को एक्शन में देखें।
- **[डिस्कॉर्ड सर्वर](https://discord.gg/roocode):** रीयल-टाइम सहायता और चर्चा के लिए समुदाय में शामिल हों।
- **[रेडिट समुदाय](https://www.reddit.com/r/RooCode):** अपने अनुभव साझा करें और देखें कि दूसरे क्या बना रहे हैं।
- **[गिटहब मुद्दे](https://github.com/RooCodeInc/Roo-Code/issues):** बग की रिपोर्ट करें और विकास को ट्रैक करें।
- **[सुविधा अनुरोध](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop):** क्या आपके पास कोई विचार है? इसे डेवलपर्स के साथ साझा करें।
---
## स्थानीय सेटअप और विकास
1. **क्लोन** करें रेपो:
```sh
git clone https://github.com/RooCodeInc/Roo-Code.git
```
2. **निर्भरताएँ स्थापित करें**:
```sh
pnpm install
```
3. **एक्सटेंशन चलाएँ**:
रू कोड एक्सटेंशन को चलाने के कई तरीके हैं:
### विकास मोड (F5)
सक्रिय विकास के लिए, वीएसकोड के अंतर्निहित डिबगिंग का उपयोग करें:
वीएसकोड में `F5` दबाएं (या **रन** → **डीबगिंग प्रारंभ करें** पर जाएं)। यह Roo Code एक्सटेंशन के साथ एक नई वीएसकोड विंडो खोलेगा।
- वेबव्यू में किए गए परिवर्तन तुरंत दिखाई देंगे।
- कोर एक्सटेंशन में किए गए परिवर्तन भी स्वचालित रूप से हॉट रीलोड हो जाएंगे।
### स्वचालित VSIX स्थापना
एक्सटेंशन को सीधे वीएसकोड में VSIX पैकेज के रूप में बनाने और स्थापित करने के लिए:
```sh
pnpm install:vsix [-y] [--editor=<command>]
```
यह कमांड करेगा:
- पूछेगा कि कौन सा संपादक कमांड उपयोग करना है (कोड/कर्सर/कोड-इनसाइडर्स) - डिफ़ॉल्ट रूप से 'कोड'
- एक्सटेंशन के किसी भी मौजूदा संस्करण को अनइंस्टॉल करें।
- नवीनतम VSIX पैकेज बनाएं।
- नए बनाए गए VSIX को स्थापित करें।
- परिवर्तनों को प्रभावी करने के लिए आपको वीएस कोड को पुनरारंभ करने के लिए संकेत देगा।
विकल्प:
- `-y`: सभी पुष्टिकरण संकेतों को छोड़ दें और डिफ़ॉल्ट का उपयोग करें
- `--editor=<command>`: संपादक कमांड निर्दिष्ट करें (जैसे, `--editor=cursor` या `--editor=code-insiders`)
### मैनुअल VSIX स्थापना
यदि आप VSIX पैकेज को मैन्युअल रूप से स्थापित करना पसंद करते हैं:
1. पहले, VSIX पैकेज बनाएं:
```sh
pnpm vsix
```
2. `bin/` डायरेक्टरी में एक `.vsix` फ़ाइल जनरेट होगी (जैसे, `bin/roo-cline-<version>.vsix` )।
3. इसे वीएसकोड सीएलआई का उपयोग करके मैन्युअल रूप से इंस्टॉल करें:
```sh
code --install-extension bin/roo-cline-<version>.vsix
```
---
हम वर्जनिंग और प्रकाशन के लिए [चेंजसेट्स](https://github.com/changesets/changesets) का उपयोग करते हैं। रिलीज नोट्स के लिए हमारी `CHANGELOG.md` देखें।
---
@ -174,16 +67,6 @@ pnpm install:vsix [-y] [--editor=<command>]
---
## योगदान
हमें सामुदायिक योगदान पसंद है! हमारी [CONTRIBUTING.md](CONTRIBUTING.md) पढ़कर शुरुआत करें।
---
## लाइसेंस
[Apache 2.0 © 2025 Roo Code, Inc.](../../LICENSE)
---
**Roo Code का आनंद लें!** चाहे आप इसे छोटी लगाम में रखें या इसे स्वायत्त रूप से घूमने दें, हम यह देखने के लिए इंतजार नहीं कर सकते कि आप क्या बनाते हैं। यदि आपके कोई प्रश्न या सुविधा के विचार हैं, तो हमारी [रेडिट समुदाय](https://www.reddit.com/r/RooCode/) या [डिस्कॉर्ड](https://discord.gg/roocode) पर आएं। हैप्पी कोडिंग!

62
locales/id/CODE_OF_CONDUCT.md generated
View file

@ -1,62 +0,0 @@
<div align="center">
<sub>
[English](../../CODE_OF_CONDUCT.md) • [Català](../ca/CODE_OF_CONDUCT.md) • [Deutsch](../de/CODE_OF_CONDUCT.md) • [Español](../es/CODE_OF_CONDUCT.md) • [Français](../fr/CODE_OF_CONDUCT.md) • [हिंदी](../hi/CODE_OF_CONDUCT.md) • <b>Bahasa Indonesia</b> • [Italiano](../it/CODE_OF_CONDUCT.md) • [日本語](../ja/CODE_OF_CONDUCT.md)
</sub>
<sub>
[한국어](../ko/CODE_OF_CONDUCT.md) • [Nederlands](../nl/CODE_OF_CONDUCT.md) • [Polski](../pl/CODE_OF_CONDUCT.md) • [Português (BR)](../pt-BR/CODE_OF_CONDUCT.md) • [Русский](../ru/CODE_OF_CONDUCT.md) • [Türkçe](../tr/CODE_OF_CONDUCT.md) • [Tiếng Việt](../vi/CODE_OF_CONDUCT.md) • [简体中文](../zh-CN/CODE_OF_CONDUCT.md) • [繁體中文](../zh-TW/CODE_OF_CONDUCT.md)
</sub>
</div>
# Kode Etik Kontributor Covenant
## Janji Kami
Demi memupuk lingkungan yang terbuka dan ramah, kami sebagai kontributor dan maintainer berjanji untuk menjadikan partisipasi dalam proyek dan komunitas kami sebagai pengalaman bebas pelecehan bagi semua orang, tanpa memandang usia, ukuran tubuh, disabilitas, etnis, karakteristik seksual, identitas dan ekspresi gender, tingkat pengalaman, pendidikan, status sosial-ekonomi, kebangsaan, penampilan pribadi, ras, agama, atau identitas dan orientasi seksual.
## Standar Kami
Contoh perilaku yang berkontribusi dalam menciptakan lingkungan positif meliputi:
- Menggunakan bahasa yang ramah dan inklusif
- Menghargai sudut pandang dan pengalaman yang berbeda
- Menerima kritik konstruktif dengan lapang dada
- Berfokus pada apa yang terbaik untuk komunitas
- Menunjukkan empati terhadap anggota komunitas lainnya
Contoh perilaku yang tidak dapat diterima oleh peserta meliputi:
- Penggunaan bahasa atau gambar yang seksual dan perhatian atau ajakan seksual yang tidak diinginkan
- Trolling, komentar menghina/merendahkan, dan serangan pribadi atau politik
- Pelecehan publik atau pribadi
- Mempublikasikan informasi pribadi orang lain, seperti alamat fisik atau elektronik, tanpa izin eksplisit
- Perilaku lain yang secara wajar dapat dianggap tidak pantas dalam lingkungan profesional
## Tanggung Jawab Kami
Maintainer proyek bertanggung jawab untuk memperjelas standar perilaku yang dapat diterima dan diharapkan mengambil tindakan korektif yang sesuai dan adil sebagai respons terhadap setiap contoh perilaku yang tidak dapat diterima.
Maintainer proyek memiliki hak dan tanggung jawab untuk menghapus, mengedit, atau menolak komentar, commit, kode, editan wiki, isu, dan kontribusi lainnya yang tidak sesuai dengan Kode Etik ini, atau untuk melarang sementara atau permanen kontributor mana pun karena perilaku lain yang mereka anggap tidak pantas, mengancam, menyinggung, atau berbahaya.
## Ruang Lingkup
Kode Etik ini berlaku baik di dalam ruang proyek maupun di ruang publik ketika seseorang mewakili proyek atau komunitasnya. Contoh mewakili proyek atau komunitas meliputi penggunaan alamat email proyek resmi, posting melalui akun media sosial resmi, atau bertindak sebagai perwakilan yang ditunjuk pada acara online atau offline. Representasi proyek dapat lebih lanjut didefinisikan dan diperjelas oleh maintainer proyek.
## Penegakan
Contoh perilaku kasar, melecehkan, atau perilaku lain yang tidak dapat diterima dapat dilaporkan dengan menghubungi tim proyek di support@roocode.com. Semua keluhan akan ditinjau dan diselidiki dan akan menghasilkan respons yang dianggap perlu dan sesuai dengan keadaan. Tim proyek wajib menjaga kerahasiaan sehubungan dengan pelapor insiden. Detail lebih lanjut tentang kebijakan penegakan spesifik dapat diposting secara terpisah.
Maintainer proyek yang tidak mengikuti atau menegakkan Kode Etik dengan itikad baik dapat menghadapi dampak sementara atau permanen sebagaimana ditentukan oleh anggota lain dari kepemimpinan proyek.
## Atribusi
Kode Etik ini diadaptasi dari [versi Cline][cline_coc] dari [Contributor Covenant][homepage], versi 1.4, tersedia di https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[cline_coc]: https://github.com/cline/cline/blob/main/CODE_OF_CONDUCT.md
[homepage]: https://www.contributor-covenant.org
Untuk jawaban atas pertanyaan umum tentang kode etik ini, lihat
https://www.contributor-covenant.org/faq

141
locales/id/CONTRIBUTING.md generated
View file

@ -1,141 +0,0 @@
<div align="center">
<sub>
[English](../../CONTRIBUTING.md) • [Català](../ca/CONTRIBUTING.md) • [Deutsch](../de/CONTRIBUTING.md) • [Español](../es/CONTRIBUTING.md) • [Français](../fr/CONTRIBUTING.md) • [हिंदी](../hi/CONTRIBUTING.md) • <b>Bahasa Indonesia</b> • [Italiano](../it/CONTRIBUTING.md) • [日本語](../ja/CONTRIBUTING.md)
</sub>
<sub>
[한국어](../ko/CONTRIBUTING.md) • [Nederlands](../nl/CONTRIBUTING.md) • [Polski](../pl/CONTRIBUTING.md) • [Português (BR)](../pt-BR/CONTRIBUTING.md) • [Русский](../ru/CONTRIBUTING.md) • [Türkçe](../tr/CONTRIBUTING.md) • [Tiếng Việt](../vi/CONTRIBUTING.md) • [简体中文](../zh-CN/CONTRIBUTING.md) • [繁體中文](../zh-TW/CONTRIBUTING.md)
</sub>
</div>
# Berkontribusi pada Roo Code
Roo Code adalah proyek yang digerakkan oleh komunitas, dan kami sangat menghargai setiap kontribusi. Untuk menyederhanakan kolaborasi, kami beroperasi dengan dasar [Pendekatan Masalah-Dulu](#pendekatan-masalah-dulu), yang berarti semua [Pull Request (PR)](#mengajukan-pull-request) harus terlebih dahulu ditautkan ke Masalah GitHub. Harap tinjau panduan ini dengan cermat.
## Daftar Isi
- [Sebelum Anda Berkontribusi](#sebelum-anda-berkontribusi)
- [Menemukan & Merencanakan Kontribusi Anda](#menemukan--merencanakan-kontribusi-anda)
- [Proses Pengembangan & Pengajuan](#proses-pengembangan--pengajuan)
- [Hukum](#hukum)
## Sebelum Anda Berkontribusi
### 1. Kode Etik
Semua kontributor harus mematuhi [Kode Etik](./CODE_OF_CONDUCT.md) kami.
### 2. Peta Jalan Proyek
Peta jalan kami memandu arah proyek. Sejajarkan kontribusi Anda dengan tujuan-tujuan utama ini:
### Keandalan Utama
- Pastikan pengeditan diff dan eksekusi perintah secara konsisten andal.
- Kurangi titik gesekan yang menghalangi penggunaan rutin.
- Jamin kelancaran operasi di semua lokal dan platform.
- Perluas dukungan yang kuat untuk berbagai penyedia dan model AI.
### Pengalaman Pengguna yang Ditingkatkan
- Sederhanakan UI/UX untuk kejelasan dan intuitivitas.
- Terus tingkatkan alur kerja untuk memenuhi harapan tinggi yang dimiliki pengembang untuk alat yang digunakan sehari-hari.
### Memimpin dalam Kinerja Agen
- Tetapkan tolok ukur evaluasi (eval) yang komprehensif untuk mengukur produktivitas dunia nyata.
- Permudah semua orang untuk menjalankan dan menafsirkan eval ini dengan mudah.
- Kirimkan perbaikan yang menunjukkan peningkatan yang jelas dalam skor eval.
Sebutkan keselarasan dengan area-area ini di PR Anda.
### 3. Bergabunglah dengan Komunitas Roo Code
- **Utama:** Bergabunglah dengan [Discord](https://discord.gg/roocode) kami dan kirim DM ke **Hannes Rudolph (`hrudolph`)**.
- **Alternatif:** Kontributor berpengalaman dapat terlibat langsung melalui [Proyek GitHub](https://github.com/orgs/RooCodeInc/projects/1).
## Menemukan & Merencanakan Kontribusi Anda
### Jenis Kontribusi
- **Perbaikan Bug:** Mengatasi masalah kode.
- **Fitur Baru:** Menambahkan fungsionalitas.
- **Dokumentasi:** Meningkatkan panduan dan kejelasan.
### Pendekatan Masalah-Dulu
Semua kontribusi dimulai dengan Masalah GitHub menggunakan template ramping kami.
- **Periksa masalah yang ada**: Cari di [Masalah GitHub](https://github.com/RooCodeInc/Roo-Code/issues).
- **Buat masalah** menggunakan:
- **Penyempurnaan:** Template "Permintaan Penyempurnaan" (bahasa sederhana yang berfokus pada manfaat pengguna).
- **Bug:** Template "Laporan Bug" (repro minimal + yang diharapkan vs aktual + versi).
- **Ingin mengerjakannya?** Beri komentar "Mengklaim" pada masalah tersebut dan kirim DM ke **Hannes Rudolph (`hrudolph`)** di [Discord](https://discord.gg/roocode) untuk ditugaskan. Penugasan akan dikonfirmasi di utas.
- **PR harus menautkan ke masalah.** PR yang tidak tertaut dapat ditutup.
### Memutuskan Apa yang Akan Dikerjakan
- Periksa [Proyek GitHub](https://github.com/orgs/RooCodeInc/projects/1) untuk masalah "Masalah [Belum Ditugaskan]".
- Untuk dokumentasi, kunjungi [Dokumentasi Roo Code](https://github.com/RooCodeInc/Roo-Code-Docs).
### Melaporkan Bug
- Periksa laporan yang ada terlebih dahulu.
- Buat bug baru menggunakan [template "Laporan Bug"](https://github.com/RooCodeInc/Roo-Code/issues/new/choose) dengan:
- Langkah-langkah reproduksi yang jelas dan bernomor
- Hasil yang diharapkan vs aktual
- Versi Roo Code (wajib); penyedia/model API jika relevan
- **Masalah keamanan**: Laporkan secara pribadi melalui [saran keamanan](https://github.com/RooCodeInc/Roo-Code/security/advisories/new).
## Proses Pengembangan & Pengajuan
### Pengaturan Pengembangan
1. **Fork & Klon:**
```
git clone https://github.com/NAMA_PENGGUNA_ANDA/Roo-Code.git
```
2. **Instal Ketergantungan:**
```
pnpm install
```
3. **Debugging:** Buka dengan VS Code (`F5`).
### Pedoman Menulis Kode
- Satu PR terfokus per fitur atau perbaikan.
- Ikuti praktik terbaik ESLint dan TypeScript.
- Tulis komitmen yang jelas dan deskriptif yang merujuk pada masalah (mis., `Memperbaiki #123`).
- Sediakan pengujian menyeluruh (`npm test`).
- Rebase ke cabang `main` terbaru sebelum pengajuan.
### Mengajukan Pull Request
- Mulailah sebagai **PR Draf** jika mencari umpan balik awal.
- Jelaskan perubahan Anda dengan jelas mengikuti Templat Pull Request.
- Tautkan masalah di deskripsi/judul PR (mis., "Memperbaiki #123").
- Sediakan tangkapan layar/video untuk perubahan UI.
- Tunjukkan jika pembaruan dokumentasi diperlukan.
### Kebijakan Pull Request
- Harus merujuk pada Masalah GitHub yang ditugaskan. Untuk ditugaskan: beri komentar "Mengklaim" pada masalah tersebut dan kirim DM ke **Hannes Rudolph (`hrudolph`)** di [Discord](https://discord.gg/roocode). Penugasan akan dikonfirmasi di utas.
- PR yang tidak tertaut dapat ditutup.
- PR harus lulus tes CI, selaras dengan peta jalan, dan memiliki dokumentasi yang jelas.
### Proses Peninjauan
- **Triase Harian:** Pemeriksaan cepat oleh pengelola.
- **Tinjauan Mendalam Mingguan:** Penilaian komprehensif.
- **Iterasi dengan cepat** berdasarkan umpan balik.
## Hukum
Dengan berkontribusi, Anda setuju bahwa kontribusi Anda akan dilisensikan di bawah Lisensi Apache 2.0, sesuai dengan lisensi Roo Code.

117
locales/id/README.md generated
View file

@ -1,32 +1,11 @@
<p align="center">
<a href="https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline"><img src="https://img.shields.io/badge/VS_Code_Marketplace-007ACC?style=flat&logo=visualstudiocode&logoColor=white" alt="VS Code Marketplace"></a>
<a href="https://x.com/roocode"><img src="https://img.shields.io/badge/roocode-000000?style=flat&logo=x&logoColor=white" alt="X"></a>
<a href="https://youtube.com/@roocodeyt?feature=shared"><img src="https://img.shields.io/badge/YouTube-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube"></a>
<a href="https://discord.gg/roocode"><img src="https://img.shields.io/badge/Join%20Discord-5865F2?style=flat&logo=discord&logoColor=white" alt="Join Discord"></a>
<a href="https://www.reddit.com/r/RooCode/"><img src="https://img.shields.io/badge/Join%20r%2FRooCode-FF4500?style=flat&logo=reddit&logoColor=white" alt="Join r/RooCode"></a>
</p>
<p align="center">
<em>Dapatkan bantuan cepat → <a href="https://discord.gg/roocode">Gabung Discord</a> • Lebih suka asinkron? → <a href="https://www.reddit.com/r/RooCode/">Gabung r/RooCode</a></em>
</p>
# Roo Code
> Tim dev bertenaga AI-mu, langsung di editor kamu
## Yang Baru di v3.53.0
> ### Plugin Roo Code tidak akan hilang.
>
> Kamu mungkin sudah melihat [pengumuman baru-baru ini](https://x.com/mattrubens/status/2046636598859559114) bahwa Roo Code mencapai 3 juta instalasi dan tim aslinya sepenuhnya fokus ke Roomote. Kami tahu berita itu berat bagi banyak dari kalian. Plugin ini sangat berarti bagi kami dan bagi kamu, dan kami mendengarmu.
>
> Kabar baiknya: **sebuah tim komunitas telah maju untuk melanjutkan Roo Code**, dan kami sedang bekerja sama dengan mereka untuk serah terima resmi agar plugin yang kamu andalkan tetap dirawat dan ditingkatkan.
**Yang baru di rilis ini:**
- Menambahkan dukungan GPT-5.5 melalui provider OpenAI Codex.
- Menambahkan dukungan Claude Opus 4.7 di Vertex AI.
- Menambahkan kontrol navigasi checkpoint sebelumnya di chat agar kamu bisa melangkah mundur melalui checkpoint sebelumnya dengan lebih mudah.
<details>
<summary>🌐 Bahasa yang tersedia</summary>
@ -75,96 +54,10 @@ Roo Code beradaptasi dengan cara Anda bekerja, bukan sebaliknya:
Pelajari lebih lanjut: [Menggunakan Mode](https://docs.roocode.com/basic-usage/using-modes) • [Mode Kustom](https://docs.roocode.com/advanced-usage/custom-modes)
## Video Tutorial & Fitur
<div align="center">
| | | |
| :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <a href="https://www.youtube.com/watch?v=Mcq3r1EPZ-4"><img src="https://img.youtube.com/vi/Mcq3r1EPZ-4/maxresdefault.jpg" width="100%"></a><br><b>Menginstal Roo Code</b> | <a href="https://www.youtube.com/watch?v=ZBML8h5cCgo"><img src="https://img.youtube.com/vi/ZBML8h5cCgo/maxresdefault.jpg" width="100%"></a><br><b>Mengonfigurasi Profil</b> | <a href="https://www.youtube.com/watch?v=r1bpod1VWhg"><img src="https://img.youtube.com/vi/r1bpod1VWhg/maxresdefault.jpg" width="100%"></a><br><b>Pengindeksan Basis Kode</b> |
| <a href="https://www.youtube.com/watch?v=iiAv1eKOaxk"><img src="https://img.youtube.com/vi/iiAv1eKOaxk/maxresdefault.jpg" width="100%"></a><br><b>Mode Kustom</b> | <a href="https://www.youtube.com/watch?v=Ho30nyY332E"><img src="https://img.youtube.com/vi/Ho30nyY332E/maxresdefault.jpg" width="100%"></a><br><b>Pos Pemeriksaan</b> | <a href="https://www.youtube.com/watch?v=HmnNSasv7T8"><img src="https://img.youtube.com/vi/HmnNSasv7T8/maxresdefault.jpg" width="100%"></a><br><b>Manajemen Konteks</b> |
</div>
<p align="center">
<a href="https://docs.roocode.com/tutorial-videos">Video tutorial dan fitur cepat lainnya...</a>
</p>
## Sumber daya
- **[Dokumentasi](https://docs.roocode.com):** Panduan resmi untuk menginstal, mengonfigurasi, dan menguasai Roo Code.
- **[Saluran YouTube](https://youtube.com/@roocodeyt?feature=shared):** Tonton tutorial dan lihat fitur-fitur dalam aksi.
- **[Server Discord](https://discord.gg/roocode):** Bergabunglah dengan komunitas untuk bantuan dan diskusi real-time.
- **[Komunitas Reddit](https://www.reddit.com/r/RooCode):** Bagikan pengalaman Anda dan lihat apa yang sedang dibangun orang lain.
- **[Masalah GitHub](https://github.com/RooCodeInc/Roo-Code/issues):** Laporkan bug dan lacak pengembangan.
- **[Permintaan Fitur](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop):** Punya ide? Bagikan dengan para pengembang.
---
## Pengaturan & Pengembangan Lokal
1. **Clone** repo:
```sh
git clone https://github.com/RooCodeInc/Roo-Code.git
```
2. **Instal dependensi**:
```sh
pnpm install
```
3. **Jalankan ekstensi**:
Ada beberapa cara untuk menjalankan ekstensi Roo Code:
### Mode Pengembangan (F5)
Untuk pengembangan aktif, gunakan debugging bawaan VSCode:
Tekan `F5` (atau buka **Run** → **Start Debugging**) di VSCode. Ini akan membuka jendela VSCode baru dengan ekstensi Roo Code berjalan.
- Perubahan pada webview akan segera muncul.
- Perubahan pada ekstensi inti juga akan di-hot reload secara otomatis.
### Instalasi VSIX Otomatis
Untuk membangun dan menginstal ekstensi sebagai paket VSIX langsung ke VSCode:
```sh
pnpm install:vsix [-y] [--editor=<command>]
```
Perintah ini akan:
- Menanyakan perintah editor mana yang akan digunakan (code/cursor/code-insiders) - defaultnya adalah 'code'
- Mencopot pemasangan versi ekstensi yang ada.
- Membangun paket VSIX terbaru.
- Menginstal VSIX yang baru dibangun.
- Meminta Anda untuk me-restart VS Code agar perubahan dapat diterapkan.
Pilihan:
- `-y`: Lewati semua prompt konfirmasi dan gunakan default
- `--editor=<command>`: Tentukan perintah editor (misalnya, `--editor=cursor` atau `--editor=code-insiders`)
### Instalasi VSIX Manual
Jika Anda lebih suka menginstal paket VSIX secara manual:
1. Pertama, bangun paket VSIX:
```sh
pnpm vsix
```
2. File `.vsix` akan dibuat di direktori `bin/` (misalnya, `bin/roo-cline-<version>.vsix`).
3. Instal secara manual menggunakan VSCode CLI:
```sh
code --install-extension bin/roo-cline-<version>.vsix
```
---
Kami menggunakan [changesets](https://github.com/changesets/changesets) untuk pembuatan versi dan publikasi. Periksa `CHANGELOG.md` kami untuk catatan rilis.
---
@ -174,16 +67,6 @@ Kami menggunakan [changesets](https://github.com/changesets/changesets) untuk pe
---
## Berkontribusi
Kami menyukai kontribusi komunitas! Mulailah dengan membaca [CONTRIBUTING.md](CONTRIBUTING.md) kami.
---
## Lisensi
[Apache 2.0 © 2025 Roo Code, Inc.](../../LICENSE)
---
**Selamat menikmati Roo Code!** Baik Anda mengendalikannya dengan ketat atau membiarkannya berkeliaran secara otonom, kami tidak sabar untuk melihat apa yang Anda bangun. Jika Anda memiliki pertanyaan atau ide fitur, kunjungi [komunitas Reddit](https://www.reddit.com/r/RooCode/) atau [Discord](https://discord.gg/roocode) kami. Selamat membuat kode!

90
locales/it/CODE_OF_CONDUCT.md generated
View file

@ -1,90 +0,0 @@
<div align="center">
<sub>
[English](../../CODE_OF_CONDUCT.md) • [Català](../ca/CODE_OF_CONDUCT.md) • [Deutsch](../de/CODE_OF_CONDUCT.md) • [Español](../es/CODE_OF_CONDUCT.md) • [Français](../fr/CODE_OF_CONDUCT.md) • [हिंदी](../hi/CODE_OF_CONDUCT.md) • [Bahasa Indonesia](../id/CODE_OF_CONDUCT.md) • <b>Italiano</b> • [日本語](../ja/CODE_OF_CONDUCT.md)
</sub>
<sub>
[한국어](../ko/CODE_OF_CONDUCT.md) • [Nederlands](../nl/CODE_OF_CONDUCT.md) • [Polski](../pl/CODE_OF_CONDUCT.md) • [Português (BR)](../pt-BR/CODE_OF_CONDUCT.md) • [Русский](../ru/CODE_OF_CONDUCT.md) • [Türkçe](../tr/CODE_OF_CONDUCT.md) • [Tiếng Việt](../vi/CODE_OF_CONDUCT.md) • [简体中文](../zh-CN/CODE_OF_CONDUCT.md) • [繁體中文](../zh-TW/CODE_OF_CONDUCT.md)
</sub>
</div>
# Codice di Condotta del Patto del Contributore
## Il Nostro Impegno
Nell'interesse di promuovere un ambiente aperto e accogliente, noi, in qualità di
contributori e manutentori, ci impegniamo a rendere la partecipazione al nostro progetto e
alla nostra comunità un'esperienza libera da molestie per tutti, indipendentemente da età, corporatura,
disabilità, etnia, caratteristiche sessuali, identità ed espressione di genere,
livello di esperienza, istruzione, stato socio-economico, nazionalità, aspetto
personale, razza, religione o identità e orientamento sessuale.
## I Nostri Standard
Esempi di comportamento che contribuiscono a creare un ambiente positivo
includono:
- Usare un linguaggio accogliente e inclusivo
- Essere rispettosi dei diversi punti di vista ed esperienze
- Accettare con grazia le critiche costruttive
- Concentrarsi su ciò che è meglio per la comunità
- Mostrare empatia verso gli altri membri della comunità
Esempi di comportamento inaccettabile da parte dei partecipanti includono:
- L'uso di linguaggio o immagini sessualizzate e attenzioni o
avances sessuali indesiderate
- Trolling, commenti offensivi/dispregiativi e attacchi personali o politici
- Molestie pubbliche o private
- Pubblicare informazioni private altrui, come un indirizzo fisico o elettronico,
senza esplicito permesso
- Altri comportamenti che potrebbero ragionevolmente essere considerati inappropriati in un
contesto professionale
## Le Nostre Responsabilità
I manutentori del progetto sono responsabili di chiarire gli standard di comportamento
accettabile e ci si aspetta che prendano azioni correttive appropriate ed eque in
risposta a qualsiasi caso di comportamento inaccettabile.
I manutentori del progetto hanno il diritto e la responsabilità di rimuovere, modificare o
rifiutare commenti, commit, codice, modifiche wiki, issue e altri contributi
che non sono allineati a questo Codice di Condotta, o di bandire temporaneamente o
permanentemente qualsiasi contributore per altri comportamenti che ritengono inappropriati,
minacciosi, offensivi o dannosi.
## Ambito
Questo Codice di Condotta si applica sia negli spazi del progetto che negli spazi pubblici
quando un individuo rappresenta il progetto o la sua comunità. Esempi di
rappresentazione di un progetto o comunità includono l'utilizzo di un indirizzo e-mail ufficiale del progetto,
la pubblicazione tramite un account ufficiale sui social media o l'agire come rappresentante designato
ad un evento online o offline. La rappresentazione di un progetto può essere
ulteriormente definita e chiarita dai manutentori del progetto.
## Applicazione
Casi di comportamento abusivo, molesto o altrimenti inaccettabile possono essere
segnalati contattando il team del progetto all'indirizzo support@roocode.com. Tutti i reclami
saranno esaminati e indagati e risulteranno in una risposta che
è ritenuta necessaria e appropriata alle circostanze. Il team del progetto è
obbligato a mantenere la riservatezza nei confronti di chi segnala un incidente.
Ulteriori dettagli su politiche di applicazione specifiche possono essere pubblicati separatamente.
I manutentori del progetto che non seguono o non fanno rispettare il Codice di Condotta in buona
fede possono affrontare ripercussioni temporanee o permanenti determinate da altri
membri della leadership del progetto.
## Attribuzione
Questo Codice di Condotta è adattato dalla [versione di Cline][cline_coc] del [Patto del Contributore][homepage], versione 1.4,
disponibile su https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[cline_coc]: https://github.com/cline/cline/blob/main/CODE_OF_CONDUCT.md
[homepage]: https://www.contributor-covenant.org
Per risposte alle domande comuni su questo codice di condotta, vedi
https://www.contributor-covenant.org/faq

141
locales/it/CONTRIBUTING.md generated
View file

@ -1,141 +0,0 @@
<div align="center">
<sub>
[English](../../CONTRIBUTING.md) • [Català](../ca/CONTRIBUTING.md) • [Deutsch](../de/CONTRIBUTING.md) • [Español](../es/CONTRIBUTING.md) • [Français](../fr/CONTRIBUTING.md) • [हिंदी](../hi/CONTRIBUTING.md) • [Bahasa Indonesia](../id/CONTRIBUTING.md) • <b>Italiano</b> • [日本語](../ja/CONTRIBUTING.md)
</sub>
<sub>
[한국어](../ko/CONTRIBUTING.md) • [Nederlands](../nl/CONTRIBUTING.md) • [Polski](../pl/CONTRIBUTING.md) • [Português (BR)](../pt-BR/CONTRIBUTING.md) • [Русский](../ru/CONTRIBUTING.md) • [Türkçe](../tr/CONTRIBUTING.md) • [Tiếng Việt](../vi/CONTRIBUTING.md) • [简体中文](../zh-CN/CONTRIBUTING.md) • [繁體中文](../zh-TW/CONTRIBUTING.md)
</sub>
</div>
# Contribuire a Roo Code
Roo Code è un progetto guidato dalla comunità e apprezziamo profondamente ogni contributo. Per semplificare la collaborazione, operiamo su una base [Issue-First](#approccio-issue-first), il che significa che tutte le [Pull Request (PR)](#invio-di-una-pull-request) devono prima essere collegate a un'issue di GitHub. Si prega di leggere attentamente questa guida.
## Sommario
- [Prima di contribuire](#prima-di-contribuire)
- [Trovare e pianificare il tuo contributo](#trovare-e-pianificare-il-tuo-contributo)
- [Processo di sviluppo e invio](#processo-di-sviluppo-e-invio)
- [Legale](#legale)
## Prima di contribuire
### 1. Codice di condotta
Tutti i contributori devono attenersi al nostro [Codice di condotta](./CODE_OF_CONDUCT.md).
### 2. Roadmap del progetto
La nostra roadmap guida la direzione del progetto. Allinea i tuoi contributi a questi obiettivi chiave:
### Affidabilità prima di tutto
- Assicurati che la modifica dei diff e l'esecuzione dei comandi siano costantemente affidabili.
- Riduci i punti di frizione che scoraggiano l'uso regolare.
- Garantisci un funzionamento fluido in tutte le localizzazioni e piattaforme.
- Espandi un supporto solido per un'ampia varietà di provider e modelli di intelligenza artificiale.
### Esperienza utente migliorata
- Semplifica l'interfaccia utente/esperienza utente per chiarezza e intuitività.
- Migliora continuamente il flusso di lavoro per soddisfare le elevate aspettative che gli sviluppatori hanno per gli strumenti di uso quotidiano.
### Leader nelle prestazioni degli agenti
- Stabilisci benchmark di valutazione completi (eval) per misurare la produttività nel mondo reale.
- Semplifica per tutti l'esecuzione e l'interpretazione di queste valutazioni.
- Fornisci miglioramenti che dimostrino chiari aumenti nei punteggi di valutazione.
Menziona l'allineamento con queste aree nelle tue PR.
### 3. Unisciti alla community di Roo Code
- **Principale:** Unisciti al nostro [Discord](https://discord.gg/roocode) e invia un DM a **Hannes Rudolph (`hrudolph`)**.
- **Alternativa:** I contributori esperti possono interagire direttamente tramite i [progetti GitHub](https://github.com/orgs/RooCodeInc/projects/1).
## Trovare e pianificare il tuo contributo
### Tipi di contributi
- **Correzioni di bug:** risoluzione di problemi di codice.
- **Nuove funzionalità:** aggiunta di funzionalità.
- **Documentazione:** miglioramento di guide e chiarezza.
### Approccio Issue-First
Tutti i contributi iniziano con un'issue di GitHub utilizzando i nostri modelli snelli.
- **Controlla le issue esistenti**: cerca nelle [issue di GitHub](https://github.com/RooCodeInc/Roo-Code/issues).
- **Crea un'issue** utilizzando:
- **Miglioramenti:** modello "Richiesta di miglioramento" (linguaggio semplice incentrato sul vantaggio per l'utente).
- **Bug:** modello "Segnalazione di bug" (riproduzione minima + previsto vs effettivo + versione).
- **Vuoi lavorarci?** Commenta "Rivendico" sull'issue e invia un DM a **Hannes Rudolph (`hrudolph`)** su [Discord](https://discord.gg/roocode) per essere assegnato. L'assegnazione verrà confermata nel thread.
- **Le PR devono essere collegate all'issue.** Le PR non collegate possono essere chiuse.
### Decidere su cosa lavorare
- Controlla il [progetto GitHub](https://github.com/orgs/RooCodeInc/projects/1) per le issue "Issue [Non assegnata]".
- Per la documentazione, visita [Roo Code Docs](https://github.com/RooCodeInc/Roo-Code-Docs).
### Segnalazione di bug
- Controlla prima le segnalazioni esistenti.
- Crea un nuovo bug utilizzando il [modello "Segnalazione di bug"](https://github.com/RooCodeInc/Roo-Code/issues/new/choose) con:
- Passaggi di riproduzione chiari e numerati
- Risultato previsto vs effettivo
- Versione di Roo Code (obbligatoria); provider/modello di intelligenza artificiale se pertinente
- **Problemi di sicurezza**: segnala in privato tramite [avvisi di sicurezza](https://github.com/RooCodeInc/Roo-Code/security/advisories/new).
## Processo di sviluppo e invio
### Configurazione dello sviluppo
1. **Esegui il fork e clona:**
```
git clone https://github.com/TUO_NOME_UTENTE/Roo-Code.git
```
2. **Installa le dipendenze:**
```
pnpm install
```
3. **Debug:** apri con VS Code (`F5`).
### Linee guida per la scrittura del codice
- Una PR mirata per funzionalità o correzione.
- Segui le migliori pratiche di ESLint e TypeScript.
- Scrivi commit chiari e descrittivi che facciano riferimento alle issue (ad es. `Risolve #123`).
- Fornisci test approfonditi (`npm test`).
- Esegui il rebase sul ramo `main` più recente prima dell'invio.
### Invio di una Pull Request
- Inizia come **bozza di PR** se cerchi un feedback iniziale.
- Descrivi chiaramente le tue modifiche seguendo il modello di Pull Request.
- Collega l'issue nella descrizione/titolo della PR (ad es. "Risolve #123").
- Fornisci screenshot/video per le modifiche all'interfaccia utente.
- Indica se sono necessari aggiornamenti alla documentazione.
### Politica sulle Pull Request
- Deve fare riferimento a un'issue di GitHub assegnata. Per essere assegnato: commenta "Rivendico" sull'issue e invia un DM a **Hannes Rudolph (`hrudolph`)** su [Discord](https://discord.gg/roocode). L'assegnazione verrà confermata nel thread.
- Le PR non collegate possono essere chiuse.
- Le PR devono superare i test di integrazione continua, essere in linea con la roadmap e avere una documentazione chiara.
### Processo di revisione
- **Triage giornaliero:** controlli rapidi da parte dei manutentori.
- **Revisione approfondita settimanale:** valutazione completa.
- **Itera prontamente** in base al feedback.
## Legale
Contribuendo, accetti che i tuoi contributi siano concessi in licenza con la licenza Apache 2.0, in coerenza con la licenza di Roo Code.

117
locales/it/README.md generated
View file

@ -1,32 +1,11 @@
<p align="center">
<a href="https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline"><img src="https://img.shields.io/badge/VS_Code_Marketplace-007ACC?style=flat&logo=visualstudiocode&logoColor=white" alt="VS Code Marketplace"></a>
<a href="https://x.com/roocode"><img src="https://img.shields.io/badge/roocode-000000?style=flat&logo=x&logoColor=white" alt="X"></a>
<a href="https://youtube.com/@roocodeyt?feature=shared"><img src="https://img.shields.io/badge/YouTube-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube"></a>
<a href="https://discord.gg/roocode"><img src="https://img.shields.io/badge/Join%20Discord-5865F2?style=flat&logo=discord&logoColor=white" alt="Join Discord"></a>
<a href="https://www.reddit.com/r/RooCode/"><img src="https://img.shields.io/badge/Join%20r%2FRooCode-FF4500?style=flat&logo=reddit&logoColor=white" alt="Join r/RooCode"></a>
</p>
<p align="center">
<em>Ottieni aiuto velocemente → <a href="https://discord.gg/roocode">Unisciti a Discord</a> • Preferisci l'asincrono? → <a href="https://www.reddit.com/r/RooCode/">Unisciti a r/RooCode</a></em>
</p>
# Roo Code
> Il tuo team di sviluppo con IA, direttamente nel tuo editor
## Novità in v3.53.0
> ### Il plugin Roo Code non sta per sparire.
>
> Potresti aver visto l'[annuncio recente](https://x.com/mattrubens/status/2046636598859559114): Roo Code ha raggiunto 3 milioni di installazioni e il team originale si sta concentrando completamente su Roomote. Sappiamo che questa notizia è stata dura per molti di voi. Questo plugin significa tanto per noi e per te, e ti ascoltiamo.
>
> La buona notizia: **un team della community si è fatto avanti per portare avanti Roo Code**, e stiamo lavorando con loro a un passaggio di consegne ufficiale, così il plugin su cui conti continuerà a essere mantenuto e migliorato.
**Novità in questa versione:**
- Aggiunto supporto a GPT-5.5 tramite il provider OpenAI Codex.
- Aggiunto supporto a Claude Opus 4.7 su Vertex AI.
- Aggiunti controlli di navigazione dei checkpoint precedenti nella chat così puoi tornare indietro più facilmente attraverso i checkpoint precedenti.
<details>
<summary>🌐 Lingue disponibili</summary>
@ -75,96 +54,10 @@ Roo Code si adatta al tuo modo di lavorare, non il contrario:
Scopri di più: [Usare le Modalità](https://docs.roocode.com/basic-usage/using-modes) • [Modalità personalizzate](https://docs.roocode.com/advanced-usage/custom-modes)
## Tutorial e video sulle funzionalità
<div align="center">
| | | |
| :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <a href="https://www.youtube.com/watch?v=Mcq3r1EPZ-4"><img src="https://img.youtube.com/vi/Mcq3r1EPZ-4/maxresdefault.jpg" width="100%"></a><br><b>Installazione di Roo Code</b> | <a href="https://www.youtube.com/watch?v=ZBML8h5cCgo"><img src="https://img.youtube.com/vi/ZBML8h5cCgo/maxresdefault.jpg" width="100%"></a><br><b>Configurazione dei profili</b> | <a href="https://www.youtube.com/watch?v=r1bpod1VWhg"><img src="https://img.youtube.com/vi/r1bpod1VWhg/maxresdefault.jpg" width="100%"></a><br><b>Indicizzazione della codebase</b> |
| <a href="https://www.youtube.com/watch?v=iiAv1eKOaxk"><img src="https://img.youtube.com/vi/iiAv1eKOaxk/maxresdefault.jpg" width="100%"></a><br><b>Modalità personalizzate</b> | <a href="https://www.youtube.com/watch?v=Ho30nyY332E"><img src="https://img.youtube.com/vi/Ho30nyY332E/maxresdefault.jpg" width="100%"></a><br><b>Checkpoint</b> | <a href="https://www.youtube.com/watch?v=HmnNSasv7T8"><img src="https://img.youtube.com/vi/HmnNSasv7T8/maxresdefault.jpg" width="100%"></a><br><b>Gestione del Contesto</b> |
</div>
<p align="center">
<a href="https://docs.roocode.com/tutorial-videos">Altri video tutorial e funzionalità rapide...</a>
</p>
## Risorse
- **[Documentazione](https://docs.roocode.com):** La guida ufficiale per installare, configurare e padroneggiare Roo Code.
- **[Canale YouTube](https://youtube.com/@roocodeyt?feature=shared):** Guarda i tutorial e le funzionalità in azione.
- **[Server Discord](https://discord.gg/roocode):** Unisciti alla community per aiuto e discussioni in tempo reale.
- **[Comunità Reddit](https://www.reddit.com/r/RooCode):** Condividi le tue esperienze e guarda cosa stanno costruendo gli altri.
- **[Problemi GitHub](https://github.com/RooCodeInc/Roo-Code/issues):** Segnala bug e tieni traccia dello sviluppo.
- **[Richieste di funzionalità](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop):** Hai un'idea? Condividila con gli sviluppatori.
---
## Configurazione e sviluppo locale
1. **Clona** il repository:
```sh
git clone https://github.com/RooCodeInc/Roo-Code.git
```
2. **Installa le dipendenze**:
```sh
pnpm install
```
3. **Esegui l'estensione**:
Ci sono diversi modi per eseguire l'estensione Roo Code:
### Modalità di sviluppo (F5)
Per lo sviluppo attivo, usa il debug integrato di VSCode:
Premi `F5` (o vai su **Esegui** → **Avvia debug**) in VSCode. Si aprirà una nuova finestra di VSCode con l'estensione Roo Code in esecuzione.
- Le modifiche alla webview appariranno immediatamente.
- Anche le modifiche all'estensione principale verranno ricaricate automaticamente a caldo.
### Installazione automatizzata di VSIX
Per compilare e installare l'estensione come pacchetto VSIX direttamente in VSCode:
```sh
pnpm install:vsix [-y] [--editor=<command>]
```
Questo comando:
- Chiederà quale comando dell'editor usare (code/cursor/code-insiders) - il default è 'code'
- Disinstallerà qualsiasi versione esistente dell'estensione.
- Compilerà l'ultimo pacchetto VSIX.
- Installerà il VSIX appena compilato.
- Ti chiederà di riavviare VS Code affinché le modifiche abbiano effetto.
Opzioni:
- `-y`: Salta tutte le richieste di conferma e usa i valori predefiniti
- `--editor=<command>`: Specifica il comando dell'editor (ad es. `--editor=cursor` o `--editor=code-insiders`)
### Installazione manuale di VSIX
Se preferisci installare manualmente il pacchetto VSIX:
1. Per prima cosa, compila il pacchetto VSIX:
```sh
pnpm vsix
```
2. Un file `.vsix` verrà generato nella directory `bin/` (ad es. `bin/roo-cline-<version>.vsix`).
3. Installalo manualmente usando la CLI di VSCode:
```sh
code --install-extension bin/roo-cline-<version>.vsix
```
---
Usiamo [changesets](https://github.com/changesets/changesets) per il versioning e la pubblicazione. Controlla il nostro `CHANGELOG.md` per le note di rilascio.
---
@ -174,16 +67,6 @@ Usiamo [changesets](https://github.com/changesets/changesets) per il versioning
---
## Contribuire
Adoriamo i contributi della community! Inizia leggendo il nostro [CONTRIBUTING.md](CONTRIBUTING.md).
---
## Licenza
[Apache 2.0 © 2025 Roo Code, Inc.](../../LICENSE)
---
**Buon divertimento con Roo Code!** Che tu lo tenga a guinzaglio corto o lo lasci libero di agire in autonomia, non vediamo l'ora di vedere cosa costruirai. Se hai domande o idee per nuove funzionalità, passa dalla nostra [comunità Reddit](https://www.reddit.com/r/RooCode/) o da [Discord](https://discord.gg/roocode). Buona programmazione!

91
locales/ja/CODE_OF_CONDUCT.md generated
View file

@ -1,91 +0,0 @@
<div align="center">
<sub>
[English](../../CODE_OF_CONDUCT.md) • [Català](../ca/CODE_OF_CONDUCT.md) • [Deutsch](../de/CODE_OF_CONDUCT.md) • [Español](../es/CODE_OF_CONDUCT.md) • [Français](../fr/CODE_OF_CONDUCT.md) • [हिंदी](../hi/CODE_OF_CONDUCT.md) • [Bahasa Indonesia](../id/CODE_OF_CONDUCT.md) • [Italiano](../it/CODE_OF_CONDUCT.md) • <b>日本語</b>
</sub>
<sub>
[한국어](../ko/CODE_OF_CONDUCT.md) • [Nederlands](../nl/CODE_OF_CONDUCT.md) • [Polski](../pl/CODE_OF_CONDUCT.md) • [Português (BR)](../pt-BR/CODE_OF_CONDUCT.md) • [Русский](../ru/CODE_OF_CONDUCT.md) • [Türkçe](../tr/CODE_OF_CONDUCT.md) • [Tiếng Việt](../vi/CODE_OF_CONDUCT.md) • [简体中文](../zh-CN/CODE_OF_CONDUCT.md) • [繁體中文](../zh-TW/CODE_OF_CONDUCT.md)
</sub>
</div>
# コントリビューター行動規範
## 私たちの誓約
オープンで歓迎的な環境を育むために、私たちは
コントリビューターおよびメンテナーとして、年齢、体格、
障害、民族、性的特徴、性自認と性表現、経験レベル、
教育、社会経済的地位、国籍、個人的外見、人種、
宗教、または性的同一性と指向に関係なく、誰もが私たちのプロジェクトと
コミュニティへの参加をハラスメントフリーな体験にすることを誓います。
## 私たちの標準
前向きな環境を作り出すことに貢献する行動の例には、
以下があります：
- 歓迎的かつ包括的な言葉を使用する
- 異なる視点や経験を尊重する
- 建設的な批判を優雅に受け入れる
- コミュニティにとって何が最善かに焦点を当てる
- 他のコミュニティメンバーに共感を示す
参加者による容認できない行動の例には、以下があります：
- 性的な言葉や画像の使用、および不快な性的注目または
誘いかけ
- 荒らし行為、侮辱的/軽蔑的なコメント、個人的または政治的攻撃
- 公的または私的なハラスメント
- 明示的な許可なく、物理的または電子的
アドレスなど、他者の個人情報を公開すること
- 職業的な場において不適切と合理的に
考えられるその他の行為
## 私たちの責任
プロジェクトメンテナーは、許容される行動の基準を明確にする
責任があり、容認できない行動に対して適切かつ公正な
是正措置を取ることが期待されています。
プロジェクトメンテナーは、この行動規範に沿わないコメント、コミット、
コード、ウィキ編集、イシュー、およびその他の貢献を
削除、編集、または拒否する権利と責任を持ち、
不適切、脅迫的、攻撃的、または有害と判断される
他の行動に対してプロジェクトコントリビューターを一時的または
永久に追放する権利を持ちます。
## 範囲
この行動規範は、個人がプロジェクトまたはそのコミュニティを代表している場合に、
プロジェクト空間内および公共空間の両方に適用されます。プロジェクトまたは
コミュニティを代表する例としては、公式プロジェクトの電子メールアドレスの使用、
公式ソーシャルメディアアカウントを通じた投稿、またはオンラインあるいはオフラインの
イベントで任命された代表として行動することが含まれます。プロジェクトの代表は、
プロジェクトメンテナーによってさらに定義され明確化される場合があります。
## 施行
虐待的、嫌がらせ、またはその他容認できない行動の事例は、
support@roocode.com でプロジェクトチームに連絡することで報告することができます。
すべての苦情は審査・調査され、状況に応じて必要かつ適切と
判断される対応がとられます。プロジェクトチームは
インシデント報告者に関する守秘義務を守る義務があります。
具体的な施行ポリシーの詳細は別途掲載される場合があります。
行動規範を誠実に遵守または施行しないプロジェクトメンテナーは、
プロジェクトのリーダーシップの他のメンバーによって決定される
一時的または永久的な影響に直面する場合があります。
## 帰属
この行動規範は、[Clineのバージョン][cline_coc]の[Contributor Covenant][homepage]、バージョン1.4から適用されています。
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html から入手可能です。
[cline_coc]: https://github.com/cline/cline/blob/main/CODE_OF_CONDUCT.md
[homepage]: https://www.contributor-covenant.org
この行動規範に関する一般的な質問への回答については、
https://www.contributor-covenant.org/faq をご覧ください。

141
locales/ja/CONTRIBUTING.md generated
View file

@ -1,141 +0,0 @@
<div align="center">
<sub>
[English](../../CONTRIBUTING.md) • [Català](../ca/CONTRIBUTING.md) • [Deutsch](../de/CONTRIBUTING.md) • [Español](../es/CONTRIBUTING.md) • [Français](../fr/CONTRIBUTING.md) • [हिंदी](../hi/CONTRIBUTING.md) • [Bahasa Indonesia](../id/CONTRIBUTING.md) • [Italiano](../it/CONTRIBUTING.md) • <b>日本語</b>
</sub>
<sub>
[한국어](../ko/CONTRIBUTING.md) • [Nederlands](../nl/CONTRIBUTING.md) • [Polski](../pl/CONTRIBUTING.md) • [Português (BR)](../pt-BR/CONTRIBUTING.md) • [Русский](../ru/CONTRIBUTING.md) • [Türkçe](../tr/CONTRIBUTING.md) • [Tiếng Việt](../vi/CONTRIBUTING.md) • [简体中文](../zh-CN/CONTRIBUTING.md) • [繁體中文](../zh-TW/CONTRIBUTING.md)
</sub>
</div>
# Roo Codeへの貢献
Roo Codeはコミュニティ主導のプロジェクトであり、すべての貢献を深く評価しています。共同作業を円滑にするため、私たちは[課題第一のアプローチ](#課題第一のアプローチ)で運営しています。つまり、すべての[プルリクエスト（PR）](#プルリクエストの提出)は、まずGitHubの課題にリンクされている必要があります。このガイドを注意深く確認してください。
## 目次
- [貢献する前に](#貢献する前に)
- [貢献内容の検索と計画](#貢献内容の検索と計画)
- [開発と提出のプロセス](#開発と提出のプロセス)
- [法務](#法務)
## 貢献する前に
### 1. 行動規範
すべての貢献者は、私たちの[行動規範](./CODE_OF_CONDUCT.md)に従う必要があります。
### 2. プロジェクトのロードマップ
私たちのロードマップは、プロジェクトの方向性を示しています。あなたの貢献をこれらの主要な目標に合わせてください。
### 信頼性第一
- 差分編集とコマンド実行が一貫して信頼できることを確認します。
- 定期的な使用を妨げる摩擦点を減らします。
- すべてのロケールとプラットフォームでスムーズな操作を保証します。
- さまざまなAIプロバイダーとモデルに対する堅牢なサポートを拡大します。
### ユーザーエクスペリエンスの向上
- 明確さと直感性のためにUI/UXを合理化します。
- 開発者が日常的に使用するツールに期待する高い期待に応えるために、ワークフローを継続的に改善します。
### エージェントパフォーマンスのリード
- 現実世界の生産性を測定するための包括的な評価ベンチマーク（evals）を確立します。
- 誰もがこれらの評価を簡単に実行および解釈できるようにします。
- 評価スコアの明確な増加を示す改善を出荷します。
PRでこれらの分野との連携について言及してください。
### 3. Roo Codeコミュニティに参加する
- **プライマリ：** [Discord](https://discord.gg/roocode)に参加し、**Hannes Rudolph (`hrudolph`)**にDMしてください。
- **代替：** 経験豊富な貢献者は、[GitHubプロジェクト](https://github.com/orgs/RooCodeInc/projects/1)を介して直接関与できます。
## 貢献内容の検索と計画
### 貢献の種類
- **バグ修正：** コードの問題への対処。
- **新機能：** 機能の追加。
- **ドキュメント：** ガイドと明確さの向上。
### 課題第一のアプローチ
すべての貢献は、私たちのスキニーテンプレートを使用してGitHubの課題から始まります。
- **既存の課題を確認する**：[GitHubの課題](https://github.com/RooCodeInc/Roo-Code/issues)で検索します。
- **課題を作成する**：
- **機能強化：** 「機能強化リクエスト」テンプレート（ユーザーの利益に焦点を当てた平易な言葉）。
- **バグ：** 「バグレポート」テンプレート（最小限の再現+期待値と実際値+バージョン）。
- **それに取り組みたいですか？** 課題に「Claiming」とコメントし、[Discord](https://discord.gg/roocode)で**Hannes Rudolph（`hrudolph`）**にDMして割り当てを受けてください。割り当てはスレッドで確認されます。
- **PRは課題にリンクする必要があります。** リンクされていないPRはクローズされる場合があります。
### 何に取り組むかを決める
- 「課題[未割り当て]」の課題については、[GitHubプロジェクト](https://github.com/orgs/RooCodeInc/projects/1)を確認してください。
- ドキュメントについては、[Roo Codeドキュメント](https://github.com/RooCodeInc/Roo-Code-Docs)をご覧ください。
### バグの報告
- 最初に既存のレポートを確認してください。
- 次の情報を含む[「バグレポート」テンプレート](https://github.com/RooCodeInc/Roo-Code/issues/new/choose)を使用して新しいバグを作成します。
- 明確で番号付きの再現手順
- 期待される結果と実際の結果
- Roo Codeのバージョン（必須）。関連する場合はAPIプロバイダー/モデル
- **セキュリティの問題**：[セキュリティアドバイザリ](https://github.com/RooCodeInc/Roo-Code/security/advisories/new)を介して非公開で報告してください。
## 開発と提出のプロセス
### 開発のセットアップ
1. **フォークとクローン：**
```
git clone https://github.com/あなたのユーザー名/Roo-Code.git
```
2. **依存関係のインストール：**
```
pnpm install
```
3. **デバッグ：** VS Codeで開きます（`F5`）。
### コーディングのガイドライン
- 機能または修正ごとに1つの焦点を絞ったPR。
- ESLintとTypeScriptのベストプラクティスに従ってください。
- 課題を参照する明確で説明的なコミットを作成します（例：`Fixes #123`）。
- 徹底的なテストを提供します（`npm test`）。
- 提出前に最新の`main`ブランチにリベースします。
### プルリクエストの提出
- 早期のフィードバックを求める場合は、**ドラフトPR**として開始します。
- プルリクエストテンプレートに従って、変更内容を明確に説明します。
- PRの説明/タイトルに課題をリンクします（例：「Fixes #123」）。
- UIの変更については、スクリーンショット/ビデオを提供します。
- ドキュメントの更新が必要かどうかを示します。
### プルリクエストポリシー
- 割り当てられたGitHubの課題を参照する必要があります。割り当てを受けるには、課題に「Claiming」とコメントし、[Discord](https://discord.gg/roocode)で**Hannes Rudolph（`hrudolph`）**にDMしてください。割り当てはスレッドで確認されます。
- リンクされていないPRはクローズされる場合があります。
- PRはCIテストに合格し、ロードマップに沿っており、明確なドキュメントが必要です。
### レビュープロセス
- **毎日のトリアージ：** メンテナーによる簡単なチェック。
- **毎週の詳細なレビュー：** 包括的な評価。
- フィードバックに基づいて**迅速に反復**します。
## 法務
貢献することにより、あなたの貢献がRoo Codeのライセンスと一致するApache 2.0ライセンスの下でライセンスされることに同意したことになります。

117
locales/ja/README.md generated
View file

@ -1,32 +1,11 @@
<p align="center">
<a href="https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline"><img src="https://img.shields.io/badge/VS_Code_Marketplace-007ACC?style=flat&logo=visualstudiocode&logoColor=white" alt="VS Code Marketplace"></a>
<a href="https://x.com/roocode"><img src="https://img.shields.io/badge/roocode-000000?style=flat&logo=x&logoColor=white" alt="X"></a>
<a href="https://youtube.com/@roocodeyt?feature=shared"><img src="https://img.shields.io/badge/YouTube-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube"></a>
<a href="https://discord.gg/roocode"><img src="https://img.shields.io/badge/Join%20Discord-5865F2?style=flat&logo=discord&logoColor=white" alt="Join Discord"></a>
<a href="https://www.reddit.com/r/RooCode/"><img src="https://img.shields.io/badge/Join%20r%2FRooCode-FF4500?style=flat&logo=reddit&logoColor=white" alt="Join r/RooCode"></a>
</p>
<p align="center">
<em>すぐに助けを得る → <a href="https://discord.gg/roocode">Discordに参加</a> • 非同期を好む？ → <a href="https://www.reddit.com/r/RooCode/">r/RooCodeに参加</a></em>
</p>
# Roo Code
> あなたのエディタの中に、AIで強化された開発チームを
## v3.53.0 の新機能
> ### Roo Code プラグインはなくなりません。
>
> Roo Code のインストール数が300万に達し、元のチームが Roomote に全力で取り組むという[先日のお知らせ](https://x.com/mattrubens/status/2046636598859559114)をご覧になったかもしれません。この知らせが多くの方にとって辛いものだったことは承知しています。このプラグインは私たちにとっても、あなたにとっても大切な存在であり、皆さんの声はしっかり届いています。
>
> 良いお知らせです：**コミュニティチームが Roo Code を受け継いで前進させることを引き受けてくれました**。頼りにしているこのプラグインが引き続きメンテナンスと改善を受けられるよう、私たちは彼らと公式な引き継ぎを進めています。
**今回のリリースの新機能:**
- OpenAI Codex プロバイダー経由で GPT-5.5 のサポートを追加。
- Vertex AI 上での Claude Opus 4.7 のサポートを追加。
- 以前のチェックポイントに簡単に戻れるように、チャットに以前のチェックポイントへのナビゲーションコントロールを追加。
<details>
<summary>🌐 利用可能な言語</summary>
@ -75,96 +54,10 @@ Roo Codeは、あなたの働き方に合わせるように適応します。
詳しくは: [モードの使い方](https://docs.roocode.com/basic-usage/using-modes) • [カスタムモード](https://docs.roocode.com/advanced-usage/custom-modes)
## チュートリアルと機能のビデオ
<div align="center">
| | | |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <a href="https://www.youtube.com/watch?v=Mcq3r1EPZ-4"><img src="https://img.youtube.com/vi/Mcq3r1EPZ-4/maxresdefault.jpg" width="100%"></a><br><b>Roo Codeのインストール</b> | <a href="https://www.youtube.com/watch?v=ZBML8h5cCgo"><img src="https://img.youtube.com/vi/ZBML8h5cCgo/maxresdefault.jpg" width="100%"></a><br><b>プロファイルの設定</b> | <a href="https://www.youtube.com/watch?v=r1bpod1VWhg"><img src="https://img.youtube.com/vi/r1bpod1VWhg/maxresdefault.jpg" width="100%"></a><br><b>コードベースのインデックス作成</b> |
| <a href="https://www.youtube.com/watch?v=iiAv1eKOaxk"><img src="https://img.youtube.com/vi/iiAv1eKOaxk/maxresdefault.jpg" width="100%"></a><br><b>カスタムモード</b> | <a href="https://www.youtube.com/watch?v=Ho30nyY332E"><img src="https://img.youtube.com/vi/Ho30nyY332E/maxresdefault.jpg" width="100%"></a><br><b>チェックポイント</b> | <a href="https://www.youtube.com/watch?v=HmnNSasv7T8"><img src="https://img.youtube.com/vi/HmnNSasv7T8/maxresdefault.jpg" width="100%"></a><br><b>コンテキスト管理</b> |
</div>
<p align="center">
<a href="https://docs.roocode.com/tutorial-videos">その他のクイックチュートリアルと機能のビデオ...</a>
</p>
## リソース
- **[ドキュメント](https://docs.roocode.com):** Roo Codeのインストール、設定、習熟のための公式ガイド。
- **[YouTubeチャンネル](https://youtube.com/@roocodeyt?feature=shared):** チュートリアルを見て、実際の機能を確認できます。
- **[Discordサーバー](https://discord.gg/roocode):** コミュニティに参加して、リアルタイムのヘルプやディスカッションに参加できます。
- **[Redditコミュニティ](https://www.reddit.com/r/RooCode):** あなたの経験を共有し、他の人が何を構築しているかを見ることができます。
- **[GitHub Issues](https://github.com/RooCodeInc/Roo-Code/issues):** バグを報告し、開発を追跡します。
- **[機能リクエスト](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop):** アイデアがありますか？開発者と共有してください。
---
## ローカルセットアップと開発
1. **リポジトリをクローンする**:
```sh
git clone https://github.com/RooCodeInc/Roo-Code.git
```
2. **依存関係をインストールする**:
```sh
pnpm install
```
3. **拡張機能を実行する**:
Roo Code拡張機能を実行するにはいくつかの方法があります：
### 開発モード (F5)
アクティブな開発には、VSCodeの内蔵デバッグ機能を使用します：
VSCodeで`F5`キーを押すか、**実行** → **デバッグの開始**に移動します。これにより、Roo Code拡張機能が実行されている新しいVSCodeウィンドウが開きます。
- ウェブビューへの変更はすぐに表示されます。
- コア拡張機能への変更も自動的にホットリロードされます。
### 自動VSIXインストール
拡張機能をVSIXパッケージとしてビルドし、VSCodeに直接インストールするには：
```sh
pnpm install:vsix [-y] [--editor=<command>]
```
このコマンドは次のことを行います：
- どのエディタコマンドを使用するかを尋ねます（code/cursor/code-insiders） - デフォルトは「code」です
- 拡張機能の既存のバージョンをアンインストールします。
- 最新のVSIXパッケージをビルドします。
- 新しくビルドされたVSIXをインストールします。
- 変更を有効にするためにVS Codeを再起動するように求めます。
オプション：
- `-y`: すべての確認プロンプトをスキップし、デフォルト値を使用します
- `--editor=<command>`: エディタコマンドを指定します（例：`--editor=cursor`または`--editor=code-insiders`）
### 手動VSIXインストール
VSIXパッケージを手動でインストールしたい場合：
1. まず、VSIXパッケージをビルドします：
```sh
pnpm vsix
```
2. `.vsix`ファイルが`bin/`ディレクトリに生成されます（例：`bin/roo-cline-<version>.vsix`）。
3. VSCode CLIを使用して手動でインストールします：
```sh
code --install-extension bin/roo-cline-<version>.vsix
```
---
バージョニングと公開には[changesets](https://github.com/changesets/changesets)を使用しています。リリースノートについては`CHANGELOG.md`をご覧ください。
---
@ -174,16 +67,6 @@ VSIXパッケージを手動でインストールしたい場合：
---
## 貢献
私たちはコミュニティからの貢献を歓迎します！[CONTRIBUTING.md](CONTRIBUTING.md)を読んで始めましょう。
---
## ライセンス
[Apache 2.0 © 2025 Roo Code, Inc.](../../LICENSE)
---
**Roo Codeをお楽しみください！** 手綱を短く持って使うか、自律的に歩き回らせるかにかかわらず、あなたが何を構築するか楽しみにしています。質問や機能のアイデアがあれば、私たちの[Redditコミュニティ](https://www.reddit.com/r/RooCode/)または[Discord](https://discord.gg/roocode)にお立ち寄りください。ハッピーコーディング！

82
locales/ko/CODE_OF_CONDUCT.md generated
View file

@ -1,82 +0,0 @@
<div align="center">
<sub>
[English](../../CODE_OF_CONDUCT.md) • [Català](../ca/CODE_OF_CONDUCT.md) • [Deutsch](../de/CODE_OF_CONDUCT.md) • [Español](../es/CODE_OF_CONDUCT.md) • [Français](../fr/CODE_OF_CONDUCT.md) • [हिंदी](../hi/CODE_OF_CONDUCT.md) • [Bahasa Indonesia](../id/CODE_OF_CONDUCT.md) • [Italiano](../it/CODE_OF_CONDUCT.md) • [日本語](../ja/CODE_OF_CONDUCT.md)
</sub>
<sub>
<b>한국어</b> • [Nederlands](../nl/CODE_OF_CONDUCT.md) • [Polski](../pl/CODE_OF_CONDUCT.md) • [Português (BR)](../pt-BR/CODE_OF_CONDUCT.md) • [Русский](../ru/CODE_OF_CONDUCT.md) • [Türkçe](../tr/CODE_OF_CONDUCT.md) • [Tiếng Việt](../vi/CODE_OF_CONDUCT.md) • [简体中文](../zh-CN/CODE_OF_CONDUCT.md) • [繁體中文](../zh-TW/CODE_OF_CONDUCT.md)
</sub>
</div>
# 기여자 서약 행동 강령
## 우리의 약속
개방적이고 환영하는 환경을 조성하기 위해, 우리는
기여자와 관리자로서 프로젝트와
우리 커뮤니티에 참여하는 것이 나이, 신체
크기, 장애, 민족, 성 특성, 성 정체성과 표현,
경험 수준, 교육, 사회 경제적 지위, 국적, 개인적
외모, 인종, 종교, 또는 성적 정체성과 지향에 관계없이 모두에게 괴롭힘 없는 경험이 되도록 약속합니다.
## 우리의 표준
긍정적인 환경을 조성하는 데 기여하는 행동의 예는
다음과 같습니다:
- 환영하고 포용적인 언어 사용
- 다양한 관점과 경험 존중
- 건설적인 비판을 우아하게 수용
- 커뮤니티에 가장 좋은 것에 집중
- 다른 커뮤니티 구성원에 대한 공감 보여주기
참가자에 의한 용납될 수 없는 행동의 예는 다음과 같습니다:
- 성적 언어나 이미지 사용 및 원치 않는 성적 관심이나
접근
- 트롤링, 모욕적/비하적 댓글, 개인적 또는 정치적 공격
- 공개적 또는 개인적 괴롭힘
- 명시적 허가 없이 다른 사람의 개인 정보 공개, 예를 들어 물리적 또는 전자적
주소
- 전문적 환경에서 부적절하다고 합리적으로 간주될 수 있는 기타 행동
## 우리의 책임
프로젝트 관리자는 허용 가능한 행동의 기준을 명확히 할 책임이 있으며
부적절한 행동의 모든 사례에 대해 적절하고 공정한 시정 조치를 취할 것으로 예상됩니다.
프로젝트 관리자는 이 행동 강령에 부합하지 않는 댓글, 커밋, 코드, 위키 편집, 이슈 및 기타 기여를 제거, 편집 또는
거부할 권리와 책임이 있으며, 부적절하다고 판단되는 다른 행동에 대해 기여자를 일시적으로 또는
영구적으로 추방할 수 있습니다.
## 범위
이 행동 강령은 개인이 프로젝트나 그 커뮤니티를 대표할 때 프로젝트 공간과 공공 공간 모두에 적용됩니다. 프로젝트나
커뮤니티를 대표하는 예로는 공식 프로젝트 이메일 사용,
공식 소셜 미디어 계정을 통한 게시, 온라인 또는 오프라인 이벤트에서 지정된 대표로 활동하는 것이 있습니다. 프로젝트의 대표는
프로젝트 관리자에 의해 추가로 정의되고 명확히 될 수 있습니다.
## 시행
학대, 괴롭힘 또는 기타 용납할 수 없는 행동의 사례는
support@roocode.com으로 프로젝트 팀에 연락하여 보고할 수 있습니다. 모든 불만 사항은
검토되고 조사되며 상황에 필요하고 적절하다고 판단되는 대응으로 이어질 것입니다. 프로젝트 팀은
사건의 보고자와 관련하여 기밀을 유지할 의무가 있습니다.
특정 시행 정책의 추가 세부 사항은 별도로 게시될 수 있습니다.
행동 강령을 선의로 따르거나 시행하지 않는 프로젝트 관리자는
프로젝트 리더십의 다른 구성원이 결정한 대로 일시적 또는 영구적인 영향에 직면할 수 있습니다.
## 출처
이 행동 강령은 [Cline의 버전][cline_coc]에서 수정된 [기여자 서약][homepage], 버전 1.4,
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 에서 이용 가능
[cline_coc]: https://github.com/cline/cline/blob/main/CODE_OF_CONDUCT.md
[homepage]: https://www.contributor-covenant.org
이 행동 강령에 관한 일반적인 질문에 대한 답변은
https://www.contributor-covenant.org/faq 를 참조하세요

141
locales/ko/CONTRIBUTING.md generated
View file

@ -1,141 +0,0 @@
<div align="center">
<sub>
[English](../../CONTRIBUTING.md) • [Català](../ca/CONTRIBUTING.md) • [Deutsch](../de/CONTRIBUTING.md) • [Español](../es/CONTRIBUTING.md) • [Français](../fr/CONTRIBUTING.md) • [हिंदी](../hi/CONTRIBUTING.md) • [Bahasa Indonesia](../id/CONTRIBUTING.md) • [Italiano](../it/CONTRIBUTING.md) • [日本語](../ja/CONTRIBUTING.md)
</sub>
<sub>
<b>한국어</b> • [Nederlands](../nl/CONTRIBUTING.md) • [Polski](../pl/CONTRIBUTING.md) • [Português (BR)](../pt-BR/CONTRIBUTING.md) • [Русский](../ru/CONTRIBUTING.md) • [Türkçe](../tr/CONTRIBUTING.md) • [Tiếng Việt](../vi/CONTRIBUTING.md) • [简体中文](../zh-CN/CONTRIBUTING.md) • [繁體中文](../zh-TW/CONTRIBUTING.md)
</sub>
</div>
# Roo Code에 기여하기
Roo Code는 커뮤니티 기반 프로젝트이며 모든 기여를 소중하게 생각합니다. 협업을 간소화하기 위해 [이슈 우선 접근 방식](#이슈-우선-접근-방식)으로 운영됩니다. 즉, 모든 [풀 리퀘스트(PR)](#풀-리퀘스트-제출)는 먼저 GitHub 이슈에 연결되어야 합니다. 이 가이드를 주의 깊게 검토해 주세요.
## 목차
- [기여하기 전에](#기여하기-전에)
- [기여 찾기 및 계획하기](#기여-찾기-및-계획하기)
- [개발 및 제출 절차](#개발-및-제출-절차)
- [법률](#법률)
## 기여하기 전에
### 1. 행동 강령
모든 기여자는 [행동 강령](./CODE_OF_CONDUCT.md)을 준수해야 합니다.
### 2. 프로젝트 로드맵
로드맵은 프로젝트의 방향을 안내합니다. 기여를 다음 주요 목표에 맞게 조정하세요.
### 안정성 우선
- diff 편집 및 명령어 실행이 일관되게 안정적인지 확인합니다.
- 정기적인 사용을 방해하는 마찰 지점을 줄입니다.
- 모든 로케일 및 플랫폼에서 원활한 작동을 보장합니다.
- 다양한 AI 제공업체 및 모델에 대한 강력한 지원을 확대합니다.
### 향상된 사용자 경험
- 명확하고 직관적인 UI/UX를 위해 간소화합니다.
- 개발자가 매일 사용하는 도구에 대해 기대하는 높은 수준을 충족하도록 워크플로를 지속적으로 개선합니다.
### 에이전트 성능 선도
- 실제 생산성을 측정하기 위한 포괄적인 평가 벤치마크(evals)를 수립합니다.
- 누구나 이러한 평가를 쉽게 실행하고 해석할 수 있도록 합니다.
- 평가 점수의 명확한 증가를 보여주는 개선 사항을 제공합니다.
PR에 이러한 영역과의 연관성을 언급하세요.
### 3. Roo Code 커뮤니티에 참여하세요
- **기본:** [Discord](https://discord.gg/roocode)에 참여하여 **Hannes Rudolph (`hrudolph`)**에게 DM을 보내세요.
- **대안:** 숙련된 기여자는 [GitHub 프로젝트](https://github.com/orgs/RooCodeInc/projects/1)를 통해 직접 참여할 수 있습니다.
## 기여 찾기 및 계획하기
### 기여 유형
- **버그 수정:** 코드 문제 해결.
- **새로운 기능:** 기능 추가.
- **문서:** 가이드 및 명확성 향상.
### 이슈 우선 접근 방식
모든 기여는 간소화된 템플릿을 사용하여 GitHub 이슈에서 시작됩니다.
- **기존 이슈 확인**: [GitHub 이슈](https://github.com/RooCodeInc/Roo-Code/issues)에서 검색합니다.
- **이슈 생성**:
- **개선 사항:** "개선 요청" 템플릿 (사용자 혜택에 초점을 맞춘 평이한 언어).
- **버그:** "버그 보고" 템플릿 (최소한의 재현 + 예상 대 실제 + 버전).
- **작업하고 싶으신가요?** 이슈에 "Claiming"이라고 댓글을 달고 [Discord](https://discord.gg/roocode)에서 **Hannes Rudolph (`hrudolph`)**에게 DM을 보내 할당을 받으세요. 할당은 스레드에서 확인됩니다.
- **PR은 이슈에 연결되어야 합니다.** 연결되지 않은 PR은 종료될 수 있습니다.
### 작업할 내용 결정하기
- "이슈 [할당되지 않음]" 이슈는 [GitHub 프로젝트](https://github.com/orgs/RooCodeInc/projects/1)를 확인하세요.
- 문서는 [Roo Code 문서](https://github.com/RooCodeInc/Roo-Code-Docs)를 방문하세요.
### 버그 신고하기
- 먼저 기존 보고서가 있는지 확인하세요.
- ["버그 보고" 템플릿](https://github.com/RooCodeInc/Roo-Code/issues/new/choose)을 사용하여 새 버그를 생성하세요.
- 명확하고 번호가 매겨진 재현 단계
- 예상 결과 대 실제 결과
- Roo Code 버전 (필수), 관련이 있는 경우 API 제공업체/모델
- **보안 문제**: [보안 권고](https://github.com/RooCodeInc/Roo-Code/security/advisories/new)를 통해 비공개로 보고하세요.
## 개발 및 제출 절차
### 개발 설정
1. **포크 및 클론:**
```
git clone https://github.com/사용자이름/Roo-Code.git
```
2. **의존성 설치:**
```
pnpm install
```
3. **디버깅:** VS Code로 엽니다 (`F5`).
### 코드 작성 가이드라인
- 기능 또는 수정당 하나의 집중된 PR.
- ESLint 및 TypeScript 모범 사례를 따릅니다.
- 이슈를 참조하는 명확하고 설명적인 커밋을 작성합니다 (예: `Fixes #123`).
- 철저한 테스트를 제공합니다 (`npm test`).
- 제출하기 전에 최신 `main` 브랜치로 리베이스합니다.
### 풀 리퀘스트 제출
- 초기 피드백을 원하면 **초안 PR**로 시작하세요.
- 풀 리퀘스트 템플릿에 따라 변경 사항을 명확하게 설명하세요.
- PR 설명/제목에 이슈를 연결하세요 (예: "Fixes #123").
- UI 변경 사항에 대한 스크린샷/동영상을 제공하세요.
- 문서 업데이트가 필요한지 표시하세요.
### 풀 리퀘스트 정책
- 할당된 GitHub 이슈를 참조해야 합니다. 할당을 받으려면: 이슈에 "Claiming"이라고 댓글을 달고 [Discord](https://discord.gg/roocode)에서 **Hannes Rudolph (`hrudolph`)**에게 DM을 보내세요. 할당은 스레드에서 확인됩니다.
- 연결되지 않은 PR은 종료될 수 있습니다.
- PR은 CI 테스트를 통과하고 로드맵과 일치하며 명확한 문서를 포함해야 합니다.
### 검토 절차
- **매일 분류:** 유지 관리자의 빠른 확인.
- **매주 심층 검토:** 포괄적인 평가.
- 피드백을 바탕으로 **신속하게 반복**합니다.
## 법률
기여함으로써 귀하는 귀하의 기여가 Roo Code의 라이선스와 일치하는 Apache 2.0 라이선스에 따라 라이선스가 부여된다는 데 동의합니다.

117
locales/ko/README.md generated
View file

@ -1,32 +1,11 @@
<p align="center">
<a href="https://marketplace.visualstudio.com/items?itemName=RooVeterinaryInc.roo-cline"><img src="https://img.shields.io/badge/VS_Code_Marketplace-007ACC?style=flat&logo=visualstudiocode&logoColor=white" alt="VS Code Marketplace"></a>
<a href="https://x.com/roocode"><img src="https://img.shields.io/badge/roocode-000000?style=flat&logo=x&logoColor=white" alt="X"></a>
<a href="https://youtube.com/@roocodeyt?feature=shared"><img src="https://img.shields.io/badge/YouTube-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube"></a>
<a href="https://discord.gg/roocode"><img src="https://img.shields.io/badge/Join%20Discord-5865F2?style=flat&logo=discord&logoColor=white" alt="Join Discord"></a>
<a href="https://www.reddit.com/r/RooCode/"><img src="https://img.shields.io/badge/Join%20r%2FRooCode-FF4500?style=flat&logo=reddit&logoColor=white" alt="Join r/RooCode"></a>
</p>
<p align="center">
<em>빠른 도움 받기 → <a href="https://discord.gg/roocode">Discord 가입하기</a> • 비동기 선호? → <a href="https://www.reddit.com/r/RooCode/">r/RooCode 가입하기</a></em>
</p>
# Roo Code
> AI로 강화된 너의 개발 팀, 네 에디터 안에
## v3.53.0의 새로운 기능
> ### Roo Code 플러그인은 사라지지 않아요.
>
> Roo Code가 300만 설치를 돌파했고, 원래 팀이 Roomote에 전념하기로 했다는 [최근 발표](https://x.com/mattrubens/status/2046636598859559114)를 보셨을 거예요. 많은 분들께 이 소식이 힘들게 다가왔다는 걸 알고 있어요. 이 플러그인은 저희와 여러분 모두에게 큰 의미가 있고, 여러분의 목소리를 듣고 있어요.
>
> 좋은 소식이 있어요: **커뮤니티 팀이 Roo Code를 계속 이어가기로 나섰어요**. 여러분이 의지하는 이 플러그인이 계속 유지 관리되고 개선될 수 있도록, 저희는 그들과 공식적인 인수인계를 진행하고 있어요.
**이번 릴리스의 새로운 기능:**
- OpenAI Codex 제공업체를 통해 GPT-5.5 지원을 추가했어요.
- Vertex AI에서 Claude Opus 4.7 지원을 추가했어요.
- 이전 체크포인트로 더 쉽게 돌아갈 수 있도록 채팅에 이전 체크포인트 탐색 컨트롤을 추가했어요.
<details>
<summary>🌐 사용 가능한 언어</summary>
@ -75,96 +54,10 @@ Roo Code는 당신의 작업 방식에 맞춰 적응합니다.
자세히: [모드 사용](https://docs.roocode.com/basic-usage/using-modes) • [사용자 지정 모드](https://docs.roocode.com/advanced-usage/custom-modes)
## 튜토리얼 및 기능 비디오
<div align="center">
| | | |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| <a href="https://www.youtube.com/watch?v=Mcq3r1EPZ-4"><img src="https://img.youtube.com/vi/Mcq3r1EPZ-4/maxresdefault.jpg" width="100%"></a><br><b>Roo Code 설치하기</b> | <a href="https://www.youtube.com/watch?v=ZBML8h5cCgo"><img src="https://img.youtube.com/vi/ZBML8h5cCgo/maxresdefault.jpg" width="100%"></a><br><b>프로필 구성하기</b> | <a href="https://www.youtube.com/watch?v=r1bpod1VWhg"><img src="https://img.youtube.com/vi/r1bpod1VWhg/maxresdefault.jpg" width="100%"></a><br><b>코드베이스 인덱싱</b> |
| <a href="https://www.youtube.com/watch?v=iiAv1eKOaxk"><img src="https://img.youtube.com/vi/iiAv1eKOaxk/maxresdefault.jpg" width="100%"></a><br><b>사용자 지정 모드</b> | <a href="https://www.youtube.com/watch?v=Ho30nyY332E"><img src="https://img.youtube.com/vi/Ho30nyY332E/maxresdefault.jpg" width="100%"></a><br><b>체크포인트</b> | <a href="https://www.youtube.com/watch?v=HmnNSasv7T8"><img src="https://img.youtube.com/vi/HmnNSasv7T8/maxresdefault.jpg" width="100%"></a><br><b>컨텍스트 관리</b> |
</div>
<p align="center">
<a href="https://docs.roocode.com/tutorial-videos">더 많은 빠른 튜토리얼 및 기능 비디오...</a>
</p>
## 리소스
- **[문서](https://docs.roocode.com):** Roo Code 설치, 구성 및 마스터하기 위한 공식 가이드.
- **[YouTube 채널](https://youtube.com/@roocodeyt?feature=shared):** 튜토리얼을 시청하고 실제 기능을 확인하세요.
- **[Discord 서버](https://discord.gg/roocode):** 커뮤니티에 가입하여 실시간 도움과 토론에 참여하세요.
- **[Reddit 커뮤니티](https://www.reddit.com/r/RooCode):** 경험을 공유하고 다른 사람들이 무엇을 만들고 있는지 확인하세요.
- **[GitHub 문제](https://github.com/RooCodeInc/Roo-Code/issues):** 버그를 보고하고 개발을 추적하세요.
- **[기능 요청](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop):** 아이디어가 있으신가요? 개발자들과 공유하세요.
---
## 로컬 설정 및 개발
1. **리포지토리 복제**:
```sh
git clone https://github.com/RooCodeInc/Roo-Code.git
```
2. **의존성 설치**:
```sh
pnpm install
```
3. **확장 프로그램 실행**:
Roo Code 확장 프로그램을 실행하는 방법에는 여러 가지가 있습니다:
### 개발 모드 (F5)
활성 개발을 위해 VSCode의 내장 디버깅을 사용하세요:
VSCode에서 `F5`를 누르거나 **실행** → **디버깅 시작**으로 이동하세요. 그러면 Roo Code 확장 프로그램이 실행되는 새 VSCode 창이 열립니다.
- 웹뷰 변경 사항은 즉시 나타납니다.
- 핵심 확장 프로그램 변경 사항도 자동으로 핫 리로드됩니다.
### 자동 VSIX 설치
확장 프로그램을 VSIX 패키지로 빌드하여 VSCode에 직접 설치하려면:
```sh
pnpm install:vsix [-y] [--editor=<command>]
```
이 명령은 다음을 수행합니다:
- 사용할 편집기 명령을 묻습니다(code/cursor/code-insiders) - 기본값은 'code'입니다.
- 기존 확장 프로그램 버전을 제거합니다.
- 최신 VSIX 패키지를 빌드합니다.
- 새로 빌드된 VSIX를 설치합니다.
- 변경 사항을 적용하려면 VS Code를 다시 시작하라는 메시지를 표시합니다.
옵션:
- `-y`: 모든 확인 프롬프트를 건너뛰고 기본값을 사용합니다.
- `--editor=<command>`: 편집기 명령을 지정합니다(예: `--editor=cursor` 또는 `--editor=code-insiders`).
### 수동 VSIX 설치
VSIX 패키지를 수동으로 설치하려면:
1. 먼저 VSIX 패키지를 빌드합니다:
```sh
pnpm vsix
```
2. `.vsix` 파일이 `bin/` 디렉터리에 생성됩니다(예: `bin/roo-cline-<version>.vsix`).
3. VSCode CLI를 사용하여 수동으로 설치합니다:
```sh
code --install-extension bin/roo-cline-<version>.vsix
```
---
버전 관리 및 게시는 [changesets](https://github.com/changesets/changesets)를 사용합니다. 릴리스 노트는 `CHANGELOG.md`를 확인하세요.
---
@ -174,16 +67,6 @@ VSIX 패키지를 수동으로 설치하려면:
---
## 기여하기
우리는 커뮤니티의 기여를 사랑합니다! [CONTRIBUTING.md](CONTRIBUTING.md)를 읽고 시작하세요.
---
## 라이선스
[Apache 2.0 © 2025 Roo Code, Inc.](../../LICENSE)
---
**Roo Code를 즐기세요!** 짧은 줄에 묶어두든 자율적으로 돌아다니게 하든, 여러분이 무엇을 만들지 기대됩니다. 질문이나 기능 아이디어가 있으면 저희 [Reddit 커뮤니티](https://www.reddit.com/r/RooCode/)나 [Discord](https://discord.gg/roocode)에 들러주세요. 즐거운 코딩 되세요!

61
locales/nl/CODE_OF_CONDUCT.md generated
View file

@ -1,61 +0,0 @@
<div align="center">
<sub>
[English](../../CODE_OF_CONDUCT.md) • [Català](../ca/CODE_OF_CONDUCT.md) • [Deutsch](../de/CODE_OF_CONDUCT.md) • [Español](../es/CODE_OF_CONDUCT.md) • [Français](../fr/CODE_OF_CONDUCT.md) • [हिंदी](../hi/CODE_OF_CONDUCT.md) • [Bahasa Indonesia](../id/CODE_OF_CONDUCT.md) • [Italiano](../it/CODE_OF_CONDUCT.md) • [日本語](../ja/CODE_OF_CONDUCT.md)
</sub>
<sub>
[한국어](../ko/CODE_OF_CONDUCT.md) • <b>Nederlands</b> • [Polski](../pl/CODE_OF_CONDUCT.md) • [Português (BR)](../pt-BR/CODE_OF_CONDUCT.md) • [Русский](../ru/CODE_OF_CONDUCT.md) • [Türkçe](../tr/CODE_OF_CONDUCT.md) • [Tiếng Việt](../vi/CODE_OF_CONDUCT.md) • [简体中文](../zh-CN/CODE_OF_CONDUCT.md) • [繁體中文](../zh-TW/CODE_OF_CONDUCT.md)
</sub>
</div>
# Contributor Covenant Gedragscode
## Onze Belofte
In het belang van het bevorderen van een open en gastvrije omgeving, beloven wij als bijdragers en beheerders om deelname aan ons project en onze community een ervaring zonder intimidatie te maken voor iedereen, ongeacht leeftijd, lichaamsgrootte, handicap, etniciteit, geslachtskenmerken, genderidentiteit en -expressie, ervaringsniveau, opleiding, sociaal-economische status, nationaliteit, uiterlijk, ras, religie of seksuele identiteit en oriëntatie.
## Onze Standaarden
Voorbeelden van gedrag dat bijdraagt aan het creëren van een positieve omgeving zijn onder andere:
- Gebruik van gastvrije en inclusieve taal
- Respect tonen voor verschillende standpunten en ervaringen
- Constructieve kritiek gracieus accepteren
- Focus op wat het beste is voor de community
- Empathie tonen voor andere communityleden
Voorbeelden van onacceptabel gedrag van deelnemers zijn onder andere:
- Het gebruik van seksueel getinte taal of beelden en ongewenste seksuele aandacht of toenadering
- Trollgedrag, beledigende/denigrerende opmerkingen en persoonlijke of politieke aanvallen
- Openbare of privé-intimidatie
- Het publiceren van andermans privé-informatie, zoals een fysiek of elektronisch adres, zonder uitdrukkelijke toestemming
- Ander gedrag dat redelijkerwijs als ongepast kan worden beschouwd in een professionele omgeving
## Onze Verantwoordelijkheden
Projectbeheerders zijn verantwoordelijk voor het verduidelijken van de normen voor acceptabel gedrag en worden geacht passende en eerlijke corrigerende maatregelen te nemen in reactie op gevallen van onacceptabel gedrag.
Projectbeheerders hebben het recht en de verantwoordelijkheid om opmerkingen, commits, code, wiki-bewerkingen, issues en andere bijdragen die niet in overeenstemming zijn met deze Gedragscode te verwijderen, te bewerken of te weigeren, of om elke bijdrager tijdelijk of permanent te verbannen voor ander gedrag dat zij ongepast, bedreigend, beledigend of schadelijk achten.
## Toepassingsgebied
Deze Gedragscode is van toepassing binnen projectruimtes en in openbare ruimtes wanneer een individu het project of de community vertegenwoordigt. Voorbeelden van vertegenwoordiging van een project of community zijn het gebruik van een officieel project-e-mailadres, posten via een officieel socialmedia-account of optreden als een aangestelde vertegenwoordiger op een online of offline evenement. De definitie van vertegenwoordiging van een project kan verder worden gespecificeerd door projectbeheerders.
## Handhaving
Voorvallen van beledigend, intimiderend of anderszins onacceptabel gedrag kunnen worden gemeld door contact op te nemen met het projectteam via support@roocode.com. Alle klachten zullen worden beoordeeld en onderzocht en zullen resulteren in een reactie die passend wordt geacht voor de omstandigheden. Het projectteam is verplicht vertrouwelijkheid te bewaren met betrekking tot de melder van het incident. Verdere details over specifiek handhavingsbeleid kunnen afzonderlijk worden gepubliceerd.
Projectbeheerders die de Gedragscode niet te goeder trouw volgen of handhaven, kunnen tijdelijke of permanente gevolgen ondervinden zoals bepaald door andere leden van het leiderschap van het project.
## Toeschrijving
Deze Gedragscode is gebaseerd op [Cline's versie][cline_coc] van de [Contributor Covenant][homepage], versie 1.4, beschikbaar op https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[cline_coc]: https://github.com/cline/cline/blob/main/CODE_OF_CONDUCT.md
[homepage]: https://www.contributor-covenant.org
Voor antwoorden op veelgestelde vragen over deze gedragscode, zie https://www.contributor-covenant.org/faq

141
locales/nl/CONTRIBUTING.md generated
View file

@ -1,141 +0,0 @@
<div align="center">
<sub>
[English](../../CONTRIBUTING.md) • [Català](../ca/CONTRIBUTING.md) • [Deutsch](../de/CONTRIBUTING.md) • [Español](../es/CONTRIBUTING.md) • [Français](../fr/CONTRIBUTING.md) • [हिंदी](../hi/CONTRIBUTING.md) • [Bahasa Indonesia](../id/CONTRIBUTING.md) • [Italiano](../it/CONTRIBUTING.md) • [日本語](../ja/CONTRIBUTING.md)
</sub>
<sub>
[한국어](../ko/CONTRIBUTING.md) • <b>Nederlands</b> • [Polski](../pl/CONTRIBUTING.md) • [Português (BR)](../pt-BR/CONTRIBUTING.md) • [Русский](../ru/CONTRIBUTING.md) • [Türkçe](../tr/CONTRIBUTING.md) • [Tiếng Việt](../vi/CONTRIBUTING.md) • [简体中文](../zh-CN/CONTRIBUTING.md) • [繁體中文](../zh-TW/CONTRIBUTING.md)
</sub>
</div>
# Bijdragen aan Roo Code
Roo Code is een door de gemeenschap gedreven project en we waarderen elke bijdrage ten zeerste. Om de samenwerking te stroomlijnen, werken we op basis van een [Issue-First-aanpak](#issue-first-aanpak), wat betekent dat alle [Pull Requests (PR's)](#een-pull-request-indienen) eerst gekoppeld moeten zijn aan een GitHub Issue. Lees deze handleiding zorgvuldig door.
## Inhoudsopgave
- [Voordat je bijdraagt](#voordat-je-bijdraagt)
- [Je bijdrage vinden en plannen](#je-bijdrage-vinden-en-plannen)
- [Ontwikkelings- en indieningsproces](#ontwikkelings-en-indieningsproces)
- [Juridisch](#juridisch)
## Voordat je bijdraagt
### 1. Gedragscode
Alle bijdragers moeten zich houden aan onze [Gedragscode](./CODE_OF_CONDUCT.md).
### 2. Projectroadmap
Onze roadmap stuurt de richting van het project. Lijn je bijdragen uit met deze belangrijke doelen:
### Betrouwbaarheid voorop
- Zorg ervoor dat het bewerken van diffs en het uitvoeren van commando's consistent betrouwbaar zijn.
- Verminder wrijvingspunten die regelmatig gebruik ontmoedigen.
- Garandeer een soepele werking in alle locales en op alle platforms.
- Breid robuuste ondersteuning uit voor een breed scala aan AI-providers en -modellen.
### Verbeterde gebruikerservaring
- Stroomlijn de UI/UX voor duidelijkheid en intuïtiviteit.
- Verbeter continu de workflow om te voldoen aan de hoge verwachtingen die ontwikkelaars hebben van dagelijks gebruikte tools.
### Toonaangevend in prestaties van agenten
- Stel uitgebreide evaluatiebenchmarks (evals) op om de productiviteit in de praktijk te meten.
- Maak het voor iedereen gemakkelijk om deze evals uit te voeren en te interpreteren.
- Lever verbeteringen die duidelijke stijgingen in de eval-scores aantonen.
Vermeld de afstemming met deze gebieden in je PR's.
### 3. Word lid van de Roo Code-community
- **Primair:** Word lid van onze [Discord](https://discord.gg/roocode) en stuur een DM naar **Hannes Rudolph (`hrudolph`)**.
- **Alternatief:** Ervaren bijdragers kunnen rechtstreeks deelnemen via [GitHub Projects](https://github.com/orgs/RooCodeInc/projects/1).
## Je bijdrage vinden en plannen
### Soorten bijdragen
- **Bugfixes:** het aanpakken van codeproblemen.
- **Nieuwe functies:** het toevoegen van functionaliteit.
- **Documentatie:** het verbeteren van handleidingen en duidelijkheid.
### Issue-First-aanpak
Alle bijdragen beginnen met een GitHub Issue met behulp van onze slanke sjablonen.
- **Controleer bestaande issues**: Zoek in [GitHub Issues](https://github.com/RooCodeInc/Roo-Code/issues).
- **Maak een issue** aan met:
- **Verbeteringen:** sjabloon "Verbeteringsverzoek" (eenvoudige taal gericht op gebruikersvoordeel).
- **Bugs:** sjabloon "Bugrapport" (minimale repro + verwacht vs. feitelijk + versie).
- **Wil je eraan werken?** Reageer met "Claiming" op de issue en stuur een DM naar **Hannes Rudolph (`hrudolph`)** op [Discord](https://discord.gg/roocode) om toegewezen te worden. De toewijzing wordt in de thread bevestigd.
- **PR's moeten naar de issue linken.** Niet-gekoppelde PR's kunnen worden gesloten.
### Beslissen waaraan je wilt werken
- Controleer het [GitHub Project](https://github.com/orgs/RooCodeInc/projects/1) voor "Issue [Niet-toegewezen]" issues.
- Ga voor documentatie naar [Roo Code Docs](https://github.com/RooCodeInc/Roo-Code-Docs).
### Bugs rapporteren
- Controleer eerst bestaande rapporten.
- Maak een nieuwe bug aan met het ["Bugrapport"-sjabloon](https://github.com/RooCodeInc/Roo-Code/issues/new/choose) met:
- Duidelijke, genummerde reproductiestappen
- Verwacht vs. feitelijk resultaat
- Roo Code-versie (vereist); API-provider/model indien relevant
- **Beveiligingsproblemen**: Rapporteer privé via [beveiligingsadviezen](https://github.com/RooCodeInc/Roo-Code/security/advisories/new).
## Ontwikkelings- en indieningsproces
### Ontwikkelingsopstelling
1. **Fork & Klonen:**
```
git clone https://github.com/JOUW_GEBRUIKERSNAAM/Roo-Code.git
```
2. **Afhankelijkheden installeren:**
```
pnpm install
```
3. **Debuggen:** Openen met VS Code (`F5`).
### Richtlijnen voor het schrijven van code
- Eén gerichte PR per functie of fix.
- Volg de best practices van ESLint en TypeScript.
- Schrijf duidelijke, beschrijvende commits die verwijzen naar issues (bijv. `Fixes #123`).
- Zorg voor grondige tests (`npm test`).
- Rebase naar de nieuwste `main`-tak vóór indiening.
### Een Pull Request indienen
- Begin als een **Concept-PR** als je vroege feedback wilt.
- Beschrijf je wijzigingen duidelijk volgens het Pull Request-sjabloon.
- Koppel de issue in de PR-beschrijving/titel (bijv. "Fixes #123").
- Zorg voor schermafbeeldingen/video's voor UI-wijzigingen.
- Geef aan of documentatie-updates nodig zijn.
### Pull Request-beleid
- Moet verwijzen naar een toegewezen GitHub Issue. Om toegewezen te worden: reageer met "Claiming" op de issue en stuur een DM naar **Hannes Rudolph (`hrudolph`)** op [Discord](https://discord.gg/roocode). De toewijzing wordt in de thread bevestigd.
- Niet-gekoppelde PR's kunnen worden gesloten.
- PR's moeten slagen voor CI-tests, in lijn zijn met de roadmap en duidelijke documentatie hebben.
### Beoordelingsproces
- **Dagelijkse triage:** Snelle controles door onderhouders.
- **Wekelijkse diepgaande beoordeling:** Uitgebreide beoordeling.
- **Itereer snel** op basis van feedback.
## Juridisch
Door bij te dragen, ga je ermee akkoord dat je bijdragen onder de Apache 2.0-licentie worden gelicentieerd, in overeenstemming met de licentieverlening van Roo Code.

Some files were not shown because too many files have changed in this diff Show more