diff --git a/docs/credits/overview.md b/docs/credits/overview.md index b9f1ceec..e7572902 100644 --- a/docs/credits/overview.md +++ b/docs/credits/overview.md @@ -42,7 +42,7 @@ The monthly subscription to the Team plan simply unlocks advanced functionality. ## How do I get free credits or free minutes or free tokens? -When you sign up for a Roo Code Cloud account, you'll be given a number of "Free Minutes" to try the product out (you'll see a cute icon). Those free minutes cover both the [Cloud Agent](/roo-code-cloud/cloud-agents) run time _and_ inference via the Roo Code Cloud provider (both of which normally cost credits). Those can't be used in the extension – they're there for you to try the magic of Cloud Agents. +When you sign up for a Roo Code Cloud account, you'll be given a number of "Free Minutes" to try the product out (you'll see a cute icon). Those free minutes cover both the [Cloud Agent](https://help.roocode.com/cloud-agents/) run time _and_ inference via the Roo Code Cloud provider (both of which normally cost credits). Those can't be used in the extension – they're there for you to try the magic of Cloud Agents. If you want free inference in the extension, look for a free model when available (or use another provider which may offer it to you for free). diff --git a/docs/index.mdx b/docs/index.mdx index 9dcffc27..2c4fbef2 100644 --- a/docs/index.mdx +++ b/docs/index.mdx @@ -19,7 +19,7 @@ Roo's approach is to trade tokens for quality. If you want the best and most eff Roo Code is available in two ways: - [ Roo Code VS Code Extension](/getting-started/installing) works locally in your VS Code IDE and gives you full control over your coding experience. It's great for deep or highly iterative solo development work. It's highly customizable and fits into your existing workflow. -- [ Roo Code Cloud Agents](/roo-code-cloud/cloud-agents) are an autonomous AI development team working 24/7, as a team, collaborating with you and other co-workers on a wide range of tasks. It meets you where you do work (Slack, Github, etc) and allows for large parts of software development to happen entirely away from an IDE. +- [ Roo Code Cloud Agents](https://help.roocode.com/cloud-agents/) are an autonomous AI development team working 24/7, as a team, collaborating with you and other co-workers on a wide range of tasks. It meets you where you do work (Slack, Github, etc) and allows for large parts of software development to happen entirely away from an IDE. The two options are highly complementary and built on the same shared foundation, achieving similarly excellent results. @@ -44,7 +44,7 @@ The most successful Roo users tend to embrace the following ideas: ## Getting Started - [With the Extension](/getting-started/installing) -- [With Roo Code Cloud](/roo-code-cloud/overview) +- [With Roo Code Cloud](https://help.roocode.com) ## Tutorial & Feature Videos diff --git a/docs/roo-code-cloud/analytics.mdx b/docs/roo-code-cloud/analytics.mdx deleted file mode 100644 index f617e453..00000000 --- a/docs/roo-code-cloud/analytics.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -description: Monitor token usage, track costs, and analyze agent performance with Roo Code Cloud Analytics. -keywords: - - analytics - - token usage - - cost tracking - - agent performance - - roi - - team insights - - credits -redirect_from: - - /roo-code-cloud/dashboard - - /roo-code-cloud/dashboard/ - - /roo-code-cloud/dashboard#usage-analytics-page ---- - -# Usage Analytics - -Roo Code Cloud provides comprehensive analytics to help you understand how your team is using AI, optimize costs, and measure productivity. - -Analytics Dashboard - -## Access - -Go to the [Analytics](https://app.roocode.com/usage) tab in Roo Code Cloud. - ---- - -## Capabilities - -With the UI controls available, you can slice and dice all of these together: - - - - - - - - - - - - - - - - -
MetricsAggregationsFilters
- - Number of tasks - - Number of tokens - - Inference cost (as reported by the provider) - - Cloud usage run time - - - User - - Cloud Agent - - Model - - Repository - - - Task source (Cloud Agent or workspace/IDE) - - Creator - - Repository - - PR - - Provider - - Timeframe -
- -## What gets tracked? - -- For Cloud Agents, all tasks are tracked and considered for analytics -- For the extension, only tasks you run while logged in and with [Task Sync](/roo-code-cloud/task-sync) enabled get reported for analytics. You can turn off task sync so the contents of tasks aren't sent to Cloud, but usage numbers are always reported while you're logged into the extension. That allows you to keep the contents of certain tasks away from Cloud while still benefiting from usage analytics. diff --git a/docs/roo-code-cloud/cloud-agents.mdx b/docs/roo-code-cloud/cloud-agents.mdx deleted file mode 100644 index f279789e..00000000 --- a/docs/roo-code-cloud/cloud-agents.mdx +++ /dev/null @@ -1,137 +0,0 @@ ---- -description: Comprehensive guide to Roo Code Cloud's autonomous agents - specialized AI workers that plan, code, review, and fix software independently. -keywords: - - Cloud Agents - - Autonomous Agents - - PR Reviewer - - PR Fixer - - Coder Agent - - Planner Agent - - Explainer Agent - - AI orchestration - - hosted execution - - credits ---- - -# Cloud Agents - -Cloud Agents are specialized, autonomous AI workers that run in the cloud. - -They upend the way most people think about software development: instead of a highly specialized activity that can only happen in a specialized IDE, it encapsulates the relevant aspects of each part of the process into agents that can run on their own (but will take your guidance if you choose). - -In other words: instead of doing all of your learning, investigating, coding, testing and shipping from your IDE, you can delegate work to focused agents which operate as a team. And it's your choice how much you lean into it. - -Cloud Agents are available in all Roo Code Cloud plans, including the free one. - -Sounds like wishful thinking? Read on and we'll show you how to use them. - ---- - -## How to work with Cloud Agents - -We at Roo have been developing Roo Code mostly with Cloud Agents for several months and learned that the following practices lead to the best results: - -- **When in doubt, start in the Cloud**: unless it's a very small change, it's usually easier to fire off several tasks to Cloud Agents (especially as you start or finish your day) and check in as they become ready. The Agents are excellent at getting things 50-80% done (often more), doing most of the heavy lifting. You can then iterate from there (be it with Cloud Agents or locally). -- **Embrace pull requests as the main unit of work**: to ensure Cloud Agents don't break things, they work on isolated branches and deliver work via PRs. They can be created, iterated upon, reviewed and fixed without you ever checking out code locally. -- **Let go of individual PRs**: be ready to throw stuff away once in a while, since LLMs aren't flawless. Quantity has a quality all of its own, so being generative pays off. -- **Invest in preview environments**: if your project allows for it (eg it's a web app), set up a preview environment (like [Vercel's Deployments](https://vercel.com/docs/git)) so you can check in on PRs without running them locally. -- **AI Coding isn't just for codes**: while only people with Engineer in the title may open IDEs in your company, everyone has questions and ideas for your product. Give access to cloud agents to everyone in our team (you don't pay per seat) and encourage people to get answers to their questions directly from them. We've seen customer support, product, design and marketing people understand code behavior and make small (and not-so-small) changes without having to open an IDE. -- **Develop collective learning in public**: if your team works on Slack, call agent in public channels, so everyone can see their answers and the result of their work. It organically gets people on the same page. - - -## The Cloud Agent Team - -The current line up available to your is below. Keep in mind we let you rename them as you please – we really believe in making them part of your team. - -### The Explainer -**Job:** Technical Educator - -Explains code, concepts, and technical documentation. It helps you understand complex parts of a codebase without needing to read every line. - -- **Best for:** Onboarding to a new codebase, understanding legacy code, debugging conceptual issues. - - -### The Planner -**Job:** Implementation Planning and Architecture - -The Planner agent maps out implementation plans and navigates complex technical decisions. It's designed to take a high-level idea or a Product Requirement Document (PRD) and break it down into a thorough, step-by-step implementation plan which can the be given to coding agent (or a human!). - -- **Best for:** New feature planning, system architecture design, complex refactoring strategies. - -### The Coder -**Job:** Full-scale across all languages - -The Coder agent writes code, creates pull requests, and implements features. It is the workhorse of the platform, capable of handling end-to-end coding tasks. - -- **Best for:** Building features, fixing bugs, refactoring components, writing tests. - -### The PR Reviewer -**Job:** Code reviews - -The PR Reviewer agent automatically provides comprehensive code reviews with actionable comments. It can monitor your repositories and review incoming Pull Requests. - -- **Best for:** Automated code quality checks, catching bugs early, enforcing coding standards. - -### The PR Fixer -**Job:** Focused fixes - -The PR Fixer agent is specialized in resolving issues identified in Pull Requests. It listens for feedback and autonomously implements fixes. - -- **Best for:** Resolving PR comments, fixing CI/CD failures, addressing review feedback. - -:::info More agents coming -While this cast of characters can get most jobs done, user feedback informs the development of new agents. We have a few [currently in development](#upcoming-agents) -::: ---- - -## How Cloud Agents Work - -### General workflow - -1. **Start:** Agents can be called: - - Manually via [the Web UI](https://app.roocode.com) (New Task button) - New task button - - - Automatically via [GitHub](/roo-code-cloud/github-integration) (e.g., new PR opened) - PR Review comments - - - Manually from [GitHub](/roo-code-cloud/github-integration) (`@Roomote` mention). - Github comment @mention - - - Manually manually via [Slack Integration](/roo-code-cloud/slack-integration) (`@Roomote` mention). - New task button - -2. **Run:** The agent spins up a secure, isolated cloud environment to perform its task. It clones your repository, analyzes the context, and executes the required actions. -3. **Complete:**: Once the task is done, the agent reports back with the results in the same place where you started. -4. **Control:** You can intervene at any time by going to the task. -5. **Look back:** all tasks are accessible in your Roo Code Cloud account. - -### Credits & Usage - -Cloud Agents consume **Cloud Credits**. Usage is measured based on the model used and the duration of the task. -- **Free Tier:** Includes access to free models for standard tasks. -- **Pro Tier:** Unlocks concurrent agent execution and priority queueing. - -There’s a [pricing page](https://roocode.com/pricing) if you want to learn more. - -### Settings - -The specific set of configuration options for each agent type varies (and are accessible in the ⚙️ icon in the agent page), but the main ones you'll find are: - -- **Name:** which is how the agent is referenced in the app. -- **Model:** the model powering inference for that agent. You can mix and match providers and models across your agent team. -- **Repositories:** the repos the agent has access to. Keep in mind we'll only lists the one you allowed when connecting to Github. If any are missing, Update your Github connection. -- **PR Creation Action:** for agents that make code changes, you can choose if they do it by creating a full PR, a draft PR or just pushing a branch. -- **Additional guidance:** any specific instructions for that agent, like things for the Reviewer to pay more attention to, coding practices for the Coder to follow, etc. It's a free text box, so you can type whatever you want, but keep in mind too many instructions may reduce the quality of results, so keep it concise and focused. - - -Most people will only have one agent of each type, but you may want to more tha one instance to have different configurations, especially model (main agent with good model, another agent with expensive model) or custom instructions (for specific repositories). - -## Upcoming Agents - -- **Improver:** a "meta agent" which analyzes agent feedback and PR reviews to maintain and improve [custom instructions](/features/custom-instructions#what-are-custom-instructions). -- **Security Auditor:** conducts security audits and identifies vulnerabilities regularly, across the codebase (and not just individual PRs) -- **Documentation Writer:** a tech writer that understands your code and writes actionable user-facing documentation. -- **Translator:** translates strings with accuracy and following your brand voice. - -[Write us](mailto:support@roocode.com) if you're interested in trying them out in Beta or if you have other suggestions. diff --git a/docs/roo-code-cloud/connect.mdx b/docs/roo-code-cloud/connect.mdx deleted file mode 100644 index b2ec8a33..00000000 --- a/docs/roo-code-cloud/connect.mdx +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Connect the Extension to Cloud -description: Connect your Roo Code extension to Roo Code Cloud for syncing, history, and collaboration. -keywords: - - Roo Code Cloud login - - authentication - - connect account - - sign in ---- - -import Codicon from '@site/src/components/Codicon'; - -Connect Roo Code to Roo Code Cloud to link your editor with the web app for task syncing, online history, and collaboration features. - -## Quickstart - -1. In Roo Code, click the cloud icon and select Connect. -2. Choose a sign-in method (GitHub/Google OAuth or Email) on app.roocode.com. -3. You’ll be returned to VS Code with your account connected. diff --git a/docs/roo-code-cloud/environments.mdx b/docs/roo-code-cloud/environments.mdx deleted file mode 100644 index 712834fc..00000000 --- a/docs/roo-code-cloud/environments.mdx +++ /dev/null @@ -1,495 +0,0 @@ ---- -description: Configure multi-port preview environments with automatic domain routing and environment variable injection for full-stack applications. -keywords: - - Preview Environments - - Multi-port - - Named Ports - - Environment Variables - - Full Stack - - Services - - Postgres - - Redis - - Detached Commands - - Tool Versions - - mise - - Initial Path - - Subdomain Routing ---- - -# Preview Environments - -Preview environments let you run multiple services in a cloud container with automatic domain routing. Each port you configure gets a unique public URL, and environment variables are injected so your applications can communicate with each other. - -## Overview - -When you spawn an environment, Roo Code Cloud: - -1. Creates a cloud container with your configured ports exposed -2. Generates unique HTTPS domains for each port -3. Injects environment variables like `ROO_WEB_HOST` and `ROO_API_HOST` into your container -4. Clones your repositories, starts services, and runs your commands - -This allows you to run a complete stack—frontend, API, workers—in a single preview environment where all the pieces can talk to each other. - -## Configuration - -Environments are configured in YAML format. Here's the complete schema: - -```yaml -name: My Full Stack App -description: Frontend and API running together - -repositories: - - repository: myorg/frontend - commands: - - name: Install - run: npm install - - name: Start - run: npm run dev - detached: true - - - repository: myorg/backend - commands: - - name: Install - run: npm install - - name: Start - run: npm run dev - detached: true - -ports: - - name: WEB - port: 3000 - - name: API - port: 3001 - -services: - - postgres16 - - redis7 - -env: - NODE_ENV: development -``` - -## Named Ports - -The `ports` section defines which ports to expose and what to call them: - -```yaml -ports: - - name: WEB - port: 3000 - - name: API - port: 3001 - - name: ADMIN - port: 3002 - initial_path: /dashboard -``` - -### Port Configuration Fields - -| Field | Description | Required | -|-------|-------------|----------| -| `name` | Identifier for the port (used to generate environment variables) | Yes | -| `port` | The port number to expose | Yes | -| `initial_path` | Default path to append to the preview URL | No | -| `subdomain` | Subdomain to set on the `Host` header when forwarding requests to the app | No | - -For each named port, an environment variable is injected into your container: - -| Port Config | Environment Variable | Example Value | -|-------------|---------------------|---------------| -| `name: WEB, port: 3000` | `ROO_WEB_HOST` | `https://abc123.preview.roocode.cloud` | -| `name: API, port: 3001` | `ROO_API_HOST` | `https://def456.preview.roocode.cloud` | -| `name: ADMIN, port: 3002` | `ROO_ADMIN_HOST` | `https://ghi789.preview.roocode.cloud` | - -### Naming Rules - -Port names must: -- Start with a letter -- Contain only letters, numbers, and underscores -- Be 1-50 characters long - -The name is converted to uppercase for the environment variable (e.g., `web` becomes `ROO_WEB_HOST`). - -### Limits - -You can configure up to **4 named ports** per environment. - -### Initial Path - -Use `initial_path` to specify the default URL path for a port's preview link. This is useful when your application's entry point isn't at the root path. - -For example, if your app requires authentication and the login page is at `/login`: - -```yaml -ports: - - name: WEB - port: 3000 - initial_path: /login -``` - -When the environment starts, the preview URL provided in the UI and task will be `https://abc123.preview.roocode.cloud/login` instead of the root URL. - -:::note -The `ROO__HOST` environment variable always contains the base URL without the initial path (e.g., `https://abc123.preview.roocode.cloud`). The `initial_path` only affects the preview link shown in the UI. -::: - -#### Validation Rules - -The `initial_path` must: -- Start with a forward slash (`/`) -- Contain only valid URI characters - -Query parameters and hash fragments are allowed. Valid examples: -- `/login` -- `/dashboard` -- `/api/v1/health` -- `/app/projects/123` -- `/login?redirect=home` -- `/docs#getting-started` - -Invalid examples: -- `login` (missing leading slash) - -### Subdomain Routing - -Use the `subdomain` field to enable subdomain-based routing for frameworks that rely on the `Host` header to distinguish tenants or admin panels (e.g., Rails, Django, Phoenix). - -When a port has a `subdomain` configured, the proxy rewrites the `Host` and `X-Forwarded-Host` headers to `{subdomain}.localhost:{port}` before forwarding the request to your application. The browser URL stays unchanged -- the rewriting happens internally inside the sandbox. - -```yaml -ports: - - name: WEB - port: 3000 - subdomain: admin -``` - -With this configuration, your application receives requests with `Host: admin.localhost:3000`, allowing it to route based on the subdomain without any DNS or infrastructure changes. WebSocket connections also receive the rewritten `Host` header. - -#### Validation Rules - -The `subdomain` value must be a valid DNS hostname: -- Lowercase alphanumeric characters, hyphens, and dots only -- Must start and end with an alphanumeric character -- 1-253 characters long - -Valid examples: -- `admin` -- `tenant1` -- `us-west.api` - -Invalid examples: -- `Admin` (uppercase not allowed) -- `-admin` (cannot start with a hyphen) -- `admin-` (cannot end with a hyphen) - -#### Use Cases - -- **Multi-tenant apps**: Route `tenant1.localhost:3000` and `tenant2.localhost:3000` to different tenants in a single application -- **Admin panels**: Serve an admin interface on `admin.localhost:3000` while the main app runs on the root domain -- **Subdomain APIs**: Frameworks like Rails can use `api.localhost:3000` to route API requests to a separate controller namespace - -## Using Environment Variables in Your Code - -Use the `ROO__HOST` variables instead of hardcoded URLs so your services can find each other in both preview and local environments: - -```typescript -// Backend: configure CORS with the injected frontend URL -app.use(cors({ - origin: process.env.ROO_WEB_HOST || 'http://localhost:3000' -})); - -// Frontend (Vite): pass the API URL at build time -// vite.config.ts -export default defineConfig({ - define: { - 'import.meta.env.API_URL': JSON.stringify(process.env.ROO_API_HOST || 'http://localhost:3001') - } -}) -``` - -For static site frameworks (Vite, Next.js, CRA), the API URL needs to be set at build time via command-level `env`: - -```yaml -commands: - - name: Build - run: npm run build - env: - VITE_API_URL: ${ROO_API_HOST} -``` - -## Repositories - -List the repositories to clone into your environment: - -```yaml -repositories: - - repository: myorg/frontend - commands: - - name: Install dependencies - run: npm install - - name: Build - run: npm run build - - name: Start dev server - run: npm run dev - detached: true - logfile: /tmp/frontend.log - - - repository: myorg/backend - commands: - - name: Install dependencies - run: npm install - - name: Run migrations - run: npm run db:migrate - - name: Start server - run: npm run start - detached: true - logfile: /tmp/backend.log -``` - -### Repository Format - -Use the `owner/repo` format (e.g., `myorg/my-app`). - -### Commands - -Each repository can have its own commands that run in order. Commands support: - -| Field | Description | Default | -|-------|-------------|---------| -| `name` | Display name for the command | Required | -| `run` | The shell command to execute | Required | -| `working_dir` | Relative directory to run the command in | Repository root | -| `cwd` | Absolute path to run the command in | Repository root | -| `env` | Command-specific environment variables | None | -| `timeout` | Maximum seconds to wait | 600 | -| `continue_on_error` | Keep going if command fails | false | -| `detached` | Run in the background (see below) | false | -| `logfile` | File path to write stdout/stderr when `detached` is true | None | - -### Background Processes - -To start a long-running process like a dev server, use `detached: true`. This runs the command in the background so subsequent commands can execute immediately: - -```yaml -commands: - - name: Install - run: npm install - - name: Start dev server - run: npm run dev - detached: true - logfile: /tmp/dev-server.log -``` - -When `detached` is true, the command runs via `nohup` and the worker moves on after confirming the process started. If `logfile` is set, stdout and stderr are written to that path — useful for debugging startup issues. - -### Automatic Tool Installation - -If a repository contains a `.tool-versions` file (used by [mise](https://mise.jdx.dev/) / asdf), Roo Code Cloud automatically runs `mise install` after cloning. This installs the correct versions of tools like Node.js, Python, Ruby, Go, or any other runtime your project requires — before any of your setup commands execute. - -``` -# .tool-versions -nodejs 20.11.0 -python 3.12.1 -``` - -## Services - -Add managed database and cache services: - -```yaml -services: - - redis7 - - postgres16 -``` - -### Available Services - -| Service | Default Port | Connection Variables | -|---------|--------------|---------------------| -| `redis6` | 6379 | `REDIS_URL` | -| `redis7` | 6379 | `REDIS_URL` | -| `postgres15` | 5432 | `DATABASE_URL`, `POSTGRES_*` | -| `postgres16` | 5432 | `DATABASE_URL`, `POSTGRES_*` | -| `postgres17` | 5432 | `DATABASE_URL`, `POSTGRES_*` | -| `mysql8` | 3306 | `DATABASE_URL`, `MYSQL_*` | -| `mariadb10` | 3306 | `DATABASE_URL`, `MARIADB_*` | -| `clickhouse` | 9000 | `CLICKHOUSE_URL` | - -### Custom Ports - -If you need a service on a non-default port: - -```yaml -services: - - name: postgres16 - port: 5433 -``` - -## Environment Variables - -Define environment variables available to all commands: - -```yaml -env: - NODE_ENV: development - LOG_LEVEL: debug - FEATURE_FLAGS: "new-ui,beta-api" -``` - -These are merged with: -1. Service connection variables (e.g., `DATABASE_URL`) -2. Named port variables (e.g., `ROO_WEB_HOST`) -3. Command-specific variables (highest priority) - -## Complete Example - -Here's a full-stack application with a React frontend, Hono API, and background worker: - -```yaml -name: E-Commerce Platform -description: Full stack with frontend, API, and worker - -repositories: - - repository: acme/storefront - commands: - - name: Install - run: npm install - - name: Build - run: npm run build - env: - VITE_API_URL: ${ROO_API_HOST} - - name: Serve - run: npx serve -s dist -l 3000 - detached: true - logfile: /tmp/storefront.log - - - repository: acme/api - commands: - - name: Install - run: npm install - - name: Migrate - run: npm run db:push - - name: Start - run: npm run start - detached: true - logfile: /tmp/api.log - env: - ALLOWED_ORIGINS: ${ROO_WEB_HOST} - - - repository: acme/worker - commands: - - name: Install - run: npm install - - name: Start - run: npm run start - detached: true - logfile: /tmp/worker.log - -ports: - - name: WEB - port: 3000 - - name: API - port: 3001 - - name: WORKER - port: 3002 - -services: - - postgres16 - - redis7 - -env: - NODE_ENV: production - LOG_LEVEL: info -``` - -After the environment starts, you'll get unique URLs for each port. Visit the WEB URL to access your running application. - -## Common Issues - -### CORS Errors - -In a preview environment, your frontend and backend run on different domains (e.g., `https://abc123.preview.roocode.cloud` and `https://def456.preview.roocode.cloud`). Browsers block cross-origin requests by default, so you need to configure both sides: the backend must allow the frontend's origin, and the frontend dev server must accept the preview domain. - -Make sure both ports are defined so the `ROO_*_HOST` variables get injected: - -```yaml -ports: - - name: WEB - port: 3000 - - name: API - port: 3001 -``` - -#### Backend: Allow the frontend origin - -Use `ROO_WEB_HOST` to configure your backend's CORS policy: - -```typescript -// Express -import cors from 'cors'; -app.use(cors({ origin: process.env.ROO_WEB_HOST || 'http://localhost:3000' })); - -// Hono -import { cors } from 'hono/cors'; -app.use(cors({ origin: process.env.ROO_WEB_HOST || 'http://localhost:3000' })); - -// Fastify -app.register(import('@fastify/cors'), { - origin: process.env.ROO_WEB_HOST || 'http://localhost:3000' -}); -``` - -#### Frontend: Allow the preview domain - -Dev servers like Vite and Next.js reject requests from unrecognized hosts by default. You need to allow the preview domain so the dev server responds to requests on `https://.preview.roocode.cloud`: - -```typescript -// Vite — vite.config.ts -export default defineConfig({ - server: { - allowedHosts: process.env.ROO_WEB_HOST - ? [new URL(process.env.ROO_WEB_HOST).hostname] - : [], - } -}) - -// Next.js — next.config.ts -export default { - allowedDevOrigins: process.env.ROO_WEB_HOST - ? [process.env.ROO_WEB_HOST] - : [], -} -``` - -### Managing Frontend API URLs with `.env` Files - -Frontends typically need the API URL at build time. If your project already uses `.env` files (via dotenv, dotenvx, or framework built-ins like Vite's `.env.local`), you can write the injected `ROO_API_HOST` into a `.env` file as a setup command — no code changes needed: - -```yaml -repositories: - - repository: myorg/frontend - commands: - - name: Configure API URL - run: echo "VITE_API_URL=${ROO_API_HOST}" >> .env.local - - name: Install - run: npm install - - name: Start - run: npm run dev - detached: true -``` - -This works with any framework that reads `.env` files: - -| Framework | File | Variable prefix | -|-----------|------|-----------------| -| Vite | `.env.local` | `VITE_` | -| Next.js | `.env.local` | `NEXT_PUBLIC_` | -| Create React App | `.env.local` | `REACT_APP_` | - -This approach keeps your environment config simple and avoids modifying application code. - -## Tips - -- **Use `ROO_*_HOST` variables, not hardcoded URLs.** Always fall back to localhost for local dev: `process.env.ROO_API_HOST || 'http://localhost:3001'`. -- **Use consistent uppercase port names.** `WEB`, `API`, `ADMIN` — not `frontend`, `BACKEND_API`, `Admin_Panel`. diff --git a/docs/roo-code-cloud/github-integration.mdx b/docs/roo-code-cloud/github-integration.mdx deleted file mode 100644 index ac7ba86e..00000000 --- a/docs/roo-code-cloud/github-integration.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -description: Integrate Roo Code Cloud agents with GitHub to automate pull request reviews and fixes. -keywords: - - GitHub Integration - - PR Reviewer - - PR Fixer - - automated code review - - automated bug fixing - - GitHub App ---- - -# GitHub Integration - -Roo Code Cloud integrates directly with GitHub to bring your autonomous Cloud Agent team into your pull request workflow. By installing the Roo Code GitHub App, you can enable agents to create branches, automatically review code and fix issues. - ---- - -## Integration Touchpoints - -Here are the ways [Cloud Agents](/roo-code-cloud/cloud-agents) integrate with GitHub: -- **Code creation:** the Coder agent delivers its work via git. When you ask it to create/change something, it will make changes in its container environment, commit them locally, push to the remote repository and create a PR describing it all. You can change its settings to create a draft (not regular) PR, or to just push to the remote branch, without creating a PR. -- **Code review:** the Reviewer agent delivers its work via Github PR comments. It will automatically review newly created PRs (including by the Coder!) in the repositories where it's enabled, by adding comments. It will also review subsequent commits which get pushed to that branch. You can control criteria for what PRs get reviewed in its settings. -- **Code fixes:** the Fixer agent delivers its work via pushes to Github branches (and comments). When you invoke it from a PR (see below) it will read through comments (made by humans or Cloud Agents) and implement proper fixes, taking any additional instructions you give it into consideration. It will do so by checking out the PR branch in its environment, committing changes and pushing them to the branch (and leaving a comment when its done so you can know). - - -## Setting Up - -You'll be prompted to connect to Github when first creating your Cloud Agent team. If you haven't done that yet, [do it now](https://app.roocode.com/cloud-agents/setup) and make sure to create at least a PR Reviewer and PR Fixer agent. - -This will take you through an OAuth process with Github, where you will: - -1. Choose the accounts to link - The first step - -2. Choose what repositories to make visible to the agents - The second step - - You can control individual agent access to repos [in agent settings](/roo-code-cloud/cloud-agents#settings). - -Now your Cloud Agents are able to work with Github. - -## Calling agents - -By default, any PR Reviewer agents you have will continuously monitor for new PRs according to the criteria you define in [their settings](/roo-code-cloud/cloud-agents#settings). So when a new PR is created, you'll see a comment like this: - -The Rooviewer agent responding - -You can also call the PR Fixer agent to address any feedback you may have in the PR by calling **@Roomote** like this: - -Mentioning @roomote to call the fixer - -You can also assign tasks to the Reviewer and Fixer from their own pages or the New Task button up top. - -The New Task page for them lets you paste a relevant URL: - -New task for the reviewer - -You can then follow the task from the web UI and see the results in the PR itself. - -:::info It's always @Roomote -Please note that you can't call specific agents by name. When you use **@Roomote**, you're mentioning the Roo Code GitHub App, which handles the integration. The app will then smartly call the appropriate agent for the context. -::: \ No newline at end of file diff --git a/docs/roo-code-cloud/login.mdx b/docs/roo-code-cloud/login.mdx deleted file mode 100644 index 159b6324..00000000 --- a/docs/roo-code-cloud/login.mdx +++ /dev/null @@ -1,53 +0,0 @@ ---- -sidebar_label: Sign in from the Extension -description: Learn how to connect your Roo Code extension to Roo Code Cloud for task syncing, online history, and collaboration features. -keywords: - - Roo Code Cloud login - - authentication - - connect account - - sign up - - GitHub login ---- - -import Codicon from '@site/src/components/Codicon'; - -# Login/Signup - -Connect your Roo Code extension to Roo Code Cloud to sync your prompts, access online task history, and enable sharing and collaboration features. - -## Getting Started - -To connect your extension to Roo Code Cloud: - -1. Go to the **Cloud** tab in the top right corner of the Roo Code extension. - Tab location in the extension -2. Click on the big blue button (and click on "Open" if asked). -3. Sign up for or sign in to your account, using the auth method of your choice -4. Review and accept the terms of service and privacy policy -5. The next page will attempt to redirect you back to VS Code, accept it - Account creation confirmation popup -6. You'll be logged in - -## Troubleshooting - -If you're not taken to your IDE, from this screen: - -IDE selector for VS Code forks - -You can: -- Click on the logo for your IDE (eg VS Code, Trae, Cursor) and see if the popup appears, or -- Copy the URL from the box below and, in the extension, click on "Having Trouble?" and paste it in - -Your Roo Code VS Code extension is now connected to Roo Code Cloud and ready to sync your data and enable collaboration features. - -If you never even see the screen above, go back to the extension, click on "Start Over" and try again. It should work now. - -## Authentication Security - -Roo Code Cloud uses industry-standard OAuth with GitHub and Google, plus traditional email authentication to ensure secure access to your account: - -- **OAuth 2.0 Protocol** - Secure authentication through trusted providers (GitHub and Google) -- **No Password Storage** - When using OAuth, Roo Code never stores your GitHub or Google passwords -- **Encrypted Connections** - All authentication requests use HTTPS encryption -- **Token-Based Access** - Secure tokens manage your session without exposing credentials -- **Email Authentication** - Traditional email/password option with secure password hashing \ No newline at end of file diff --git a/docs/roo-code-cloud/overview.md b/docs/roo-code-cloud/overview.md deleted file mode 100644 index 29eda464..00000000 --- a/docs/roo-code-cloud/overview.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -description: Roo Code Cloud transforms AI development with autonomous agents that work independently in the cloud, accessible from GitHub, Slack, or the web. -keywords: - - Roo Code Cloud - - Autonomous Agents - - Cloud Agents - - AI development platform - - GitHub integration - - Slack integration - - Free AI models ---- - -# Roo Code Cloud Overview - -Roo Code Cloud transforms AI development with autonomous [Cloud Agents](./cloud-agents) that work independently in the cloud. Instead of just assisting you in your editor, these agents can plan, code, review, and fix issues autonomously, accessible directly from **GitHub PRs**, **Slack messages**, or the **web browser**. - -It also augments the Roo Code VS Code extension capabilities by adding: -- Access to the [Roo Code Router](/roo-code-router/overview) -- [Task Sync](./task-sync) to access your entire task history in one place -- [Task sharing](./task-sharing) to access specific tasks with friends or co-workers -- [Token usage analytics](./analytics) to understand where your tokens and dollars are going - -And, in the [Team plan](./team-plan), adds team-oriented features: -- Centralized LLM inference billing without managing API keys (with the [Roo Code Router](/roo-code-router/overview)) -- Team-wide task history and token usage analytics -- Shared Cloud Agent team (with centralized billing) -- Centralized integration with Github and Slack (not one per user) -- Extension configuration enforcement (providers/models, MCP servers and more) - ---- - -## Getting Started - -To use it, you'll need an account. You can: -- **[Directly sign up for a Roo Code account](https://app.roocode.com/sign-up)** and set up your agent team -- Or **[sign up for a Roo Code account from the VS Code extension](/roo-code-cloud/login)** to your account - -If you chose the Roo Code Router when signing up, you already have an account and only need to sign in. - -## Managing your account - -You can manage all of your account settings (including cancellation) from the [web UI](https://app.roocode.com) and clicking on the user avatar menu, in the top right: - -
- The user menu for Personal and Team accounts. -
The user menu for Personal and Team accounts, respectively.
-
- -- **Account switcher:** to switch between multiple accounts associated to the same email address (if you have them). -- **Billing and credits:** to add [credits](/credits/overview), configure auto top-up, change payment method, upgrade plans. -- **My Settings:** to change settings specific to you or to cancel/delete your personal Roo Code cloud account (under "Open Profile"). -- **Organization Settings:** to change [global settings](/roo-code-cloud/team-plan#capabilities) for your Team. -- **Docs:** to come here, so meta :) -- **Help:** to start an in-app chat with our team diff --git a/docs/roo-code-cloud/slack-integration.mdx b/docs/roo-code-cloud/slack-integration.mdx deleted file mode 100644 index 735250a5..00000000 --- a/docs/roo-code-cloud/slack-integration.mdx +++ /dev/null @@ -1,90 +0,0 @@ ---- -description: Use Roo Code Cloud agents directly from Slack to plan features, explain code, and trigger tasks. -keywords: - - Slack Integration - - ChatOps - - "@Roomote" - - Slack bot - - AI planning - - collaborative coding - - team collaboration - - remote tasks ---- - -# Slack Integration - -The Roo Code Slack integration brings your Cloud Agent team directly into your chat workspace. You can summon agents to explain code, plan new features, or execute coding tasks without leaving Slack, and they get along quite well with humans. - -Summoning agents from Slack in public channels is an effective way to bring the entire team into the process, to learn by example how to best leverage Cloud Agents (and the information/outcomes they produce). - ---- - -## Setting Up - -You'll be prompted to connect to Slack when first signing up for your account. But if you dismiss it, you can do it later: - -1. Go to your personal or org settings (if available) in the top right user menu -2. Click on "Connect" and follow the process -3. Add the `@Roomote` bot to the channels where you want it to be available - -**Note:** The Slack integration will not watch your conversations unless you specifically mention `@Roomote`. - -## Calling Agents - -1. To interact with Roo Code agents, simply mention `@Roomote` in any channel where the bot is present to start a thread, giving it instructions. It will react with 👀 to acknowledge it. - -2. Then, the app will ask you what Agent to use with what repository. You can choose "all repositories", but the more focused you can make the agent, the higher the chances of good results. - The Slack app checking what agent and repo to use - - Keep in mind not all agents appear in this list, as some don't make sense (eg the PR Reviewer) - -3. If the agent has any questions, it will get back to you with options, like this: - The Slack app asking for an answer - -4. Once done, the agent will never directly modify your code. If it was a coding task, it will push a branch or create a PR, depending on how it's configured, but it will never touch `main`/`master` or production. - -You can always send messages directly though by mentioning **@Roomote** again in the thread. It will keep context. - -:::info It's always @Roomote -Please note that you can't call specific agents by name. When you use **@Roomote**, you're mentioning the Roo Code Slack App, which handles the integration. That's why the app will ask you to pick an agent. -::: - -## Examples - -### Planning Projects - -Start a thread to discuss and plan a new feature with your team and the AI. - -> **@Roomote** We need to add a 'Forgot Password' flow to the user service. Can you plan this out? - -Pick a Planner agent wait for the plan. You can then run it by your team or give it to the Coder agent to build. - -### Explaining Code - -Ask questions about your codebase to get immediate answers. Great for understanding bugs or confusing behavior. - -> **@Roomote** why may users be getting double confirmation emails after completing their purchase? - -But wait, agents are actually smart enough to understand the context of threads. So you can, after some back-and-forth with a colleague, simply ask: - -> **@Roomote** why is this happening? - -And it will know what to do. - -### Writing Code - -Trigger coding tasks directly from chat. - -> **@Roomote** create a new API endpoint for user profile updates, including support for profile image upload - -> **@Roomote** fix this bug: `` - -> **@Roomote** build this: `[paste an implementation plan from the planner]` - -The possibilities are enormous. - -## Limitations - -- **Mention required in channels** — Generic channel messages without @Roomote are ignored -- **Images only** — Non-image files aren't processed; images must be under 10MB -- **Active subscription** — Requires funded Cloud credits diff --git a/docs/roo-code-cloud/task-sharing.mdx b/docs/roo-code-cloud/task-sharing.mdx deleted file mode 100644 index e804b233..00000000 --- a/docs/roo-code-cloud/task-sharing.mdx +++ /dev/null @@ -1,76 +0,0 @@ ---- -description: Learn how to share your Roo Code tasks and collaborate with others using shareable links. Share from the extension or web UI. -keywords: - - task sharing - - collaboration - - shareable links - - Roo Code Cloud - - team collaboration ---- - -import Codicon from '@site/src/components/Codicon'; - -# Task Sharing - -This allows you to share Roo Code tasks (in the extension or from Cloud Agents) with secure links with whoever you choose. This allows you to help others understand how you're using Roo, debug a problem or help your teammates learn. - -You can choose whether to share with your organization (Team plan only) or publicly (anyone with the link). - -:::note Organization Policy -If your organization disables task sharing, the Share button is disabled and shows a tooltip indicating sharing is disabled. On the web dashboard, the Share action may also be unavailable if you don’t have permission to share that task. -::: - ---- - -## Sharing from the Roo Code Extension - -1. Open the Share menu - - In an active task, click the Share icon in the task header (right side). - Share icon in the active task header - -2. Choose who can access - - Pick one: - - **Share with Organization** — Only members of your organization can access - - **Share Publicly** — Anyone with the link can access - - Default: If not specified, the extension uses Organization visibility by default. - Share options showing Organization and Public visibility choices - -3. Create the link - - Roo generates the link and copies it to your clipboard. A brief success message appears in the UI. - Share link created and copied confirmation - -## Sharing from Roo Code Cloud - -1. Go to [Roo Code Cloud](https://app.roocode.com) and open the task you want to share. - -2. Click the **Share** button to open sharing options. - -3. Create and manage links - - Choose Organization or Public, then click **Create Share Link**. - - Expiration: - - Personal accounts: links expire after 30 days. - - Organizations: expiry is set by your org (1–365 days; default 30). - - From this screen you can: - - Copy link - - Create another link - - See recent links (last 3 shown, with a "+N more" summary) - - Delete links (org admins can delete any org link; members can delete links they created) - -## Privacy & Security - -#### Controlled sharing -- Tasks are **private by default** — nothing is shared until you create a link. -- You choose Organization vs Public visibility per link. -- You can revoke access anytime by deleting the link. - -#### Expiring links -- Personal accounts: links expire after 30 days. -- Organizations: expiry is set by your org admin (1–365 days; default 30). - -#### Data control -- Delete share links anytime from the dashboard. -- View recent links in the dialog. - -## Caveats -- There's no link tracking at the moment. -- Personal account links always expire after 30 days. diff --git a/docs/roo-code-cloud/task-sync.mdx b/docs/roo-code-cloud/task-sync.mdx deleted file mode 100644 index 471beffc..00000000 --- a/docs/roo-code-cloud/task-sync.mdx +++ /dev/null @@ -1,50 +0,0 @@ ---- -description: Task Sync streams task activity from your local VS Code to Roo Code Cloud so you can monitor progress from any device — free for all users. -keywords: - - task sync - - monitoring - - realtime updates - - task history - - mobile monitoring - - roo code cloud ---- - -# Task Sync/Monitoring - -Task Sync streams task activity from your local VS Code to Roo Code Cloud so you can monitor progress from any device and access tasks later. This feature is free for all users. - -It creates a live, one-way stream of your task messages and status from your local VS Code to Roo Code Cloud so you can: -- Monitor long-running tasks from your phone while away from your desk -- See near real-time updates (polled every few seconds): messages, mode changes, and status -- Check when a task completes without sitting in front of your IDE -- Review your cloud task history anytime - -Roo Code Cloud home showing workspaces and tasks - -:::info IDE Cloud -Keep in mind Task Sync sends tasks from your IDE to Roo Code Cloud, but not vice-versa. For example, it doesn't sync tasks across devices at the moment. -::: - ---- - -## Getting Started - -1. [Connect your IDE](/roo-code-cloud/connect) (or see [Login/Signup](/roo-code-cloud/login)) -2. Open or start a task in your local Roo Code extension -3. Visit the homescreen at https://app.roocode.com to monitor in near real time - -- Personal accounts: Task Sync is enabled by default and can be toggled in Settings. -- Organization accounts: Task Sync is managed by your org admins and is off by default for members unless enabled at the org level. - -## Limitations - -- One-way monitoring only; no cloud commands are sent to your IDE -- For live updates, your IDE must be open and connected -- Internet connection required for live updates - -You can review cloud task history anytime, even when your IDE is closed. - -## Privacy & Security - -- Your data is never used for training or advertising purposes -- The Roo Code team doesn't have access to the contents of your tasks, unless explicitly authorized by you to debug any issues diff --git a/docs/roo-code-cloud/team-plan.mdx b/docs/roo-code-cloud/team-plan.mdx deleted file mode 100644 index d239f131..00000000 --- a/docs/roo-code-cloud/team-plan.mdx +++ /dev/null @@ -1,127 +0,0 @@ ---- -description: Understand the functionality available in the Roo Code Cloud Team plan. -keywords: - - team - - corporate - - enterprise - - shared - - members - - invite ---- - -# Team Plan - -The team plan is designed for teams to work together using the Roo Code suite, be it the Extension, Cloud or a combination of both. - -It allows for: -- Centralized LLM inference billing without managing API keys (with [Roo Code Router](/roo-code-router/overview)) -- Team-wide task history and token usage analytics -- Shared Cloud Agent team (with centralized billing) -- Centralized integration with Github and Slack (not one per user) -- Extension configuration enforcement (providers/models, MCP servers and more) - ---- - -## Access - -You can access Team functionality by starting a free 14-day trial. - -If you already have a Roo Code Cloud account, you can [upgrade here](https://app.roocode.com/checkout/team). If you don't, sign up from our [pricing page](https://roocode.com/pricing). - - -## Capabilities - -Most of the team functionality can be accessed from your [Organization Settings](https://app.roocode.com/) page (from your user avatar menu) - -How to access your organization settings - -From there, you'll be able to access all of the available settings: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SettingPurpose
**Team Members** - Invite, remove and manage permissions for team members (Admin or regular member) -
**Organization profile details** - Logo, name, etc -
**Integrations** - [Github](./github-integration) and [Slack](./slack-integration), for now -
**Cloud Model Providers** - For use with [Cloud Agents](./cloud-agents) -
**Extension Task Sync** - Whether to require task syncing, and visibility controls for who can see each others' tasks -
**Task Sharing** - Whether per-task sharing is enabled, to whom and link expiration time -
**Environment Variables** - Optional values to make available to Cloud Agents during runs, such as connection strings, package manager server URLs, keys, secrets, etc. - Encrypted in our secure secret store. -
**Marketplace MCPs** - Allow/deny-list MCPs from the Roo Code marketplace to make available for team members. -
**Custom MCPs** - Custom, vetted MCP servers to make available to all team members. -
**Extension Providers** - Allow/deny-list inference Providers to be made available to team members. - - Centralized API key management isn't currently supported, but let us know if you need it. -
**Organization Connection Policy** - Mechanism to require Roo Code VS Code Extension users to be logged in, so policies can be enforced. - - Works via a file to be distributed via our MDM tool. -
- -Additional Team plan functionality is available in: -- [Usage Analytics](./analytics) (showing team-wide activity and per-user filters) -- Task lists (in the Home and Agent pages, showing team-wide tasks) - - -We're constantly expanding and tweaking team-oriented functionality, so if you need something else, don't hesitate to get in touch via [support@roocode.com](mailto:support@roocode.com). diff --git a/docs/roo-code-cloud/what-is-roo-code-cloud.md b/docs/roo-code-cloud/what-is-roo-code-cloud.md deleted file mode 100644 index d6cfc5ea..00000000 --- a/docs/roo-code-cloud/what-is-roo-code-cloud.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -description: Roo Code Cloud extends your VS Code extension with cloud task syncing and sharing, usage analytics, and optional Cloud Agents—using your own model API keys. -keywords: - - Roo Code Cloud - - Cloud Agents - - cloud features - - collaboration - - task history - - usage analytics - - BYO keys ---- - -# What is Roo Code Cloud? - -Roo Code Cloud is the web platform companion to the Roo Code VS Code extension. It extends the extension's functionality (task syncing and sharing, usage analytics) and allows you to run tasks in the cloud, completely independent from the extension, via Cloud Agents. - -Some of the functionality is free, some of it is paid. All of it follows our philosophy of being model-agnostic and letting you bring your provider key to stay in control of inference models and costs. - -You can see the [pricing for different plans here](https://roocode.com/pricing). - -## Main Features - -| Feature | Description | Availability | -| :------ | :---------- | :----------- | -| [Connect the Extension to Cloud](/roo-code-cloud/connect) | Connect via GitHub, Google, or email for cloud sync | Free | -| [Analytics](/roo-code-cloud/analytics) | Track model tokens, tasks, estimated cost, and Cloud Agent credits | Free | -| [Task Sync](/roo-code-cloud/task-sync) | Real-time task updates and cloud task history across devices | Free | -| [Task Sharing](/roo-code-cloud/task-sharing) | Share tasks via secure, expiring links | Free | -| [Cloud Agents](/roo-code-cloud/cloud-agents) | Run Roo in the cloud with credit-based runtime and BYO provider keys | Paid | -| Billing & Plans | Manage subscriptions, trials, and credit purchasing | Paid | - - - -## Getting Started - -1. [Connect your account](/roo-code-cloud/connect) to link Roo Code with the cloud. -2. Open [app.roocode.com](https://app.roocode.com/) and confirm your tasks appear. -3. Turn on [Task Sync](/roo-code-cloud/task-sync) so activity syncs to the cloud. -4. [Share a task](/roo-code-cloud/task-sharing) when you're ready for feedback or handoff. -5. Optional: start a [Cloud Agent](/roo-code-cloud/cloud-agents). Manage plans in [pricing](https://roocode.com/pricing). diff --git a/docs/roo-code-router/overview.md b/docs/roo-code-router/overview.md index da6c3286..253b4a1c 100644 --- a/docs/roo-code-router/overview.md +++ b/docs/roo-code-router/overview.md @@ -16,7 +16,7 @@ You don't have to use our provider to use Roo Code (you can choose from dozens), - State of the art models from the top frontier labs (including Anthropic, OpenAI, Google, xAI, etc) - Tested open weight models from upcoming labs (Moonshot AI, MiniMax, GLM, etc) -Since it's integrated into the Roo Code suite of products, you don't need to manage API keys to use it – just connect your account. With the [Team plan](/roo-code-cloud/team-plan), you can extend access to your entire team, ending the days of provider API keys flying around. +Since it's integrated into the Roo Code suite of products, you don't need to manage API keys to use it – just connect your account. With the [Team plan](https://help.roocode.com/team-plan/), you can extend access to your entire team, ending the days of provider API keys flying around. ## Model Availability @@ -43,7 +43,7 @@ best to check the privacy policy of the vendors themselves. You can always find the current pricing [on our website](https://roocode.com/provider) or the Roo Code Cloud app, under ["Models"](https://app.roocode.com/models). :::info Looking for free inference? -When you sign up for a Roo Code Cloud account, you'll be given a number of "Free Minutes" to try the product out (you'll see a cute gift box icon). Those free minutes cover both the [Cloud Agent](/roo-code-cloud/cloud-agents) run time _and_ inference via Roo Code Router (which, as we established, cost credits). Those can't be used in the extension. +When you sign up for a Roo Code Cloud account, you'll be given a number of "Free Minutes" to try the product out (you'll see a cute gift box icon). Those free minutes cover both the [Cloud Agent](https://help.roocode.com/cloud-agents/) run time _and_ inference via Roo Code Router (which, as we established, cost credits). Those can't be used in the extension. If you want free inference in the extension, look for a free model when available (or use another provider which may offer it to you for free). ::: diff --git a/docusaurus.config.ts b/docusaurus.config.ts index 36cbeabe..49019eca 100644 --- a/docusaurus.config.ts +++ b/docusaurus.config.ts @@ -98,7 +98,6 @@ const config: Config = { { label: "Features", path: "features" }, { label: "Advanced Usage", path: "advanced-usage" }, { label: "Providers", path: "providers" }, - { label: "Roo Code Cloud", path: "roo-code-cloud" }, { label: "Release Notes", path: "update-notes" } ], useAllContextsWithNoSearchContext: true, @@ -307,6 +306,11 @@ const config: Config = { to: '/credits/overview', from: ['/roo-code-cloud/billing-subscriptions'], }, + // Redirect removed What is Roo Code Cloud page + { + to: '/', + from: ['/roo-code-cloud/what-is-roo-code-cloud'], + }, // Redirect removed Human Relay provider page { to: '/', @@ -323,9 +327,9 @@ const config: Config = { to: '/', from: ['/features/fast-edits'], }, - // Redirect removed Roomote Control page + // Redirect removed Roomote Control page (now on help site) { - to: '/roo-code-cloud/overview', + to: '/', from: ['/roo-code-cloud/roomote-control'], }, ], diff --git a/sidebars.ts b/sidebars.ts index 98c6c739..4ccd6b72 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -120,20 +120,9 @@ const sidebars: SidebarsConfig = { ], }, { - type: "category", - label: "Roo Code Cloud", - items: [ - "roo-code-cloud/overview", - "roo-code-cloud/login", - "roo-code-cloud/cloud-agents", - "roo-code-cloud/environments", - "roo-code-cloud/task-sync", - "roo-code-cloud/task-sharing", - "roo-code-cloud/analytics", - "roo-code-cloud/github-integration", - "roo-code-cloud/slack-integration", - "roo-code-cloud/team-plan", - ], + type: "link", + label: "Roo Code Cloud Help", + href: "https://help.roocode.com", }, { type: "doc", diff --git a/static/img/analytics/overview.png b/static/img/analytics/overview.png deleted file mode 100644 index 582ee68d..00000000 Binary files a/static/img/analytics/overview.png and /dev/null differ diff --git a/static/img/cloud-agents/cloud-agent-call-gh-auto.png b/static/img/cloud-agents/cloud-agent-call-gh-auto.png deleted file mode 100644 index 1984a484..00000000 Binary files a/static/img/cloud-agents/cloud-agent-call-gh-auto.png and /dev/null differ diff --git a/static/img/cloud-agents/cloud-agent-call-gh-mention.png b/static/img/cloud-agents/cloud-agent-call-gh-mention.png deleted file mode 100644 index 03250819..00000000 Binary files a/static/img/cloud-agents/cloud-agent-call-gh-mention.png and /dev/null differ diff --git a/static/img/cloud-agents/cloud-agent-call-slack.png b/static/img/cloud-agents/cloud-agent-call-slack.png deleted file mode 100644 index 718eaa91..00000000 Binary files a/static/img/cloud-agents/cloud-agent-call-slack.png and /dev/null differ diff --git a/static/img/cloud-agents/cloud-agent-call-web.png b/static/img/cloud-agents/cloud-agent-call-web.png deleted file mode 100644 index 7bd97ed2..00000000 Binary files a/static/img/cloud-agents/cloud-agent-call-web.png and /dev/null differ diff --git a/static/img/integrations/gh-auth-1.png b/static/img/integrations/gh-auth-1.png deleted file mode 100644 index a7e5f48e..00000000 Binary files a/static/img/integrations/gh-auth-1.png and /dev/null differ diff --git a/static/img/integrations/gh-auth-2.png b/static/img/integrations/gh-auth-2.png deleted file mode 100644 index 7dea1194..00000000 Binary files a/static/img/integrations/gh-auth-2.png and /dev/null differ diff --git a/static/img/integrations/gh-mention.png b/static/img/integrations/gh-mention.png deleted file mode 100644 index 03250819..00000000 Binary files a/static/img/integrations/gh-mention.png and /dev/null differ diff --git a/static/img/integrations/gh-new-task.png b/static/img/integrations/gh-new-task.png deleted file mode 100644 index 2e1623dc..00000000 Binary files a/static/img/integrations/gh-new-task.png and /dev/null differ diff --git a/static/img/integrations/gh-response-review.png b/static/img/integrations/gh-response-review.png deleted file mode 100644 index 1984a484..00000000 Binary files a/static/img/integrations/gh-response-review.png and /dev/null differ diff --git a/static/img/integrations/slack-confirm.png b/static/img/integrations/slack-confirm.png deleted file mode 100644 index 6952b9a3..00000000 Binary files a/static/img/integrations/slack-confirm.png and /dev/null differ diff --git a/static/img/integrations/slack-question.png b/static/img/integrations/slack-question.png deleted file mode 100644 index 76667922..00000000 Binary files a/static/img/integrations/slack-question.png and /dev/null differ diff --git a/static/img/login/login-0.png b/static/img/login/login-0.png deleted file mode 100644 index 9edcde57..00000000 Binary files a/static/img/login/login-0.png and /dev/null differ diff --git a/static/img/login/login-1.png b/static/img/login/login-1.png deleted file mode 100644 index 381befe4..00000000 Binary files a/static/img/login/login-1.png and /dev/null differ diff --git a/static/img/login/login-10.png b/static/img/login/login-10.png deleted file mode 100644 index 81245efb..00000000 Binary files a/static/img/login/login-10.png and /dev/null differ diff --git a/static/img/login/login-11.png b/static/img/login/login-11.png deleted file mode 100644 index 76af1df3..00000000 Binary files a/static/img/login/login-11.png and /dev/null differ diff --git a/static/img/login/login-12.png b/static/img/login/login-12.png deleted file mode 100644 index c7519f47..00000000 Binary files a/static/img/login/login-12.png and /dev/null differ diff --git a/static/img/login/login-13.png b/static/img/login/login-13.png deleted file mode 100644 index f7e867b3..00000000 Binary files a/static/img/login/login-13.png and /dev/null differ diff --git a/static/img/login/login-2.png b/static/img/login/login-2.png deleted file mode 100644 index 15832bae..00000000 Binary files a/static/img/login/login-2.png and /dev/null differ diff --git a/static/img/login/login-3.png b/static/img/login/login-3.png deleted file mode 100644 index bfc2e679..00000000 Binary files a/static/img/login/login-3.png and /dev/null differ diff --git a/static/img/login/login-4.png b/static/img/login/login-4.png deleted file mode 100644 index a16a659b..00000000 Binary files a/static/img/login/login-4.png and /dev/null differ diff --git a/static/img/login/login-5.png b/static/img/login/login-5.png deleted file mode 100644 index c35e9a92..00000000 Binary files a/static/img/login/login-5.png and /dev/null differ diff --git a/static/img/login/login-6.png b/static/img/login/login-6.png deleted file mode 100644 index 2dd2e1f7..00000000 Binary files a/static/img/login/login-6.png and /dev/null differ diff --git a/static/img/login/login-7.png b/static/img/login/login-7.png deleted file mode 100644 index 2dbb06a5..00000000 Binary files a/static/img/login/login-7.png and /dev/null differ diff --git a/static/img/login/login-8.png b/static/img/login/login-8.png deleted file mode 100644 index 8e6628d2..00000000 Binary files a/static/img/login/login-8.png and /dev/null differ diff --git a/static/img/login/login.png b/static/img/login/login.png deleted file mode 100644 index 55ae7ffb..00000000 Binary files a/static/img/login/login.png and /dev/null differ diff --git a/static/img/roo-code-cloud/user-menu.png b/static/img/roo-code-cloud/user-menu.png deleted file mode 100644 index cf7a268a..00000000 Binary files a/static/img/roo-code-cloud/user-menu.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-1.png b/static/img/task-sharing/task-sharing-1.png deleted file mode 100644 index 0caf7f50..00000000 Binary files a/static/img/task-sharing/task-sharing-1.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-10.png b/static/img/task-sharing/task-sharing-10.png deleted file mode 100644 index e86d7613..00000000 Binary files a/static/img/task-sharing/task-sharing-10.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-11.png b/static/img/task-sharing/task-sharing-11.png deleted file mode 100644 index 0a28e342..00000000 Binary files a/static/img/task-sharing/task-sharing-11.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-12.png b/static/img/task-sharing/task-sharing-12.png deleted file mode 100644 index ca66a64c..00000000 Binary files a/static/img/task-sharing/task-sharing-12.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-2.png b/static/img/task-sharing/task-sharing-2.png deleted file mode 100644 index f3ade40b..00000000 Binary files a/static/img/task-sharing/task-sharing-2.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-3.png b/static/img/task-sharing/task-sharing-3.png deleted file mode 100644 index 3030a3ec..00000000 Binary files a/static/img/task-sharing/task-sharing-3.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-4.png b/static/img/task-sharing/task-sharing-4.png deleted file mode 100644 index 8c339408..00000000 Binary files a/static/img/task-sharing/task-sharing-4.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-5.png b/static/img/task-sharing/task-sharing-5.png deleted file mode 100644 index 5908e2c5..00000000 Binary files a/static/img/task-sharing/task-sharing-5.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-6.png b/static/img/task-sharing/task-sharing-6.png deleted file mode 100644 index ea50f5dd..00000000 Binary files a/static/img/task-sharing/task-sharing-6.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-7.png b/static/img/task-sharing/task-sharing-7.png deleted file mode 100644 index 3f31155b..00000000 Binary files a/static/img/task-sharing/task-sharing-7.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-8.png b/static/img/task-sharing/task-sharing-8.png deleted file mode 100644 index 063f6505..00000000 Binary files a/static/img/task-sharing/task-sharing-8.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing-9.png b/static/img/task-sharing/task-sharing-9.png deleted file mode 100644 index d979fb0a..00000000 Binary files a/static/img/task-sharing/task-sharing-9.png and /dev/null differ diff --git a/static/img/task-sharing/task-sharing.png b/static/img/task-sharing/task-sharing.png deleted file mode 100644 index 8df379a8..00000000 Binary files a/static/img/task-sharing/task-sharing.png and /dev/null differ diff --git a/static/img/task-sync/task-sync.png b/static/img/task-sync/task-sync.png deleted file mode 100644 index 7efb4406..00000000 Binary files a/static/img/task-sync/task-sync.png and /dev/null differ diff --git a/static/img/team-plan/org-settings-menu.png b/static/img/team-plan/org-settings-menu.png deleted file mode 100644 index a92f4e0f..00000000 Binary files a/static/img/team-plan/org-settings-menu.png and /dev/null differ diff --git a/vercel.json b/vercel.json new file mode 100644 index 00000000..6699c239 --- /dev/null +++ b/vercel.json @@ -0,0 +1,17 @@ +{ + "redirects": [ + { "source": "/roo-code-cloud/overview", "destination": "https://help.roocode.com", "permanent": true }, + { "source": "/roo-code-cloud/login", "destination": "https://help.roocode.com/sign-in-from-extension/", "permanent": true }, + { "source": "/roo-code-cloud/connect", "destination": "https://help.roocode.com/connect/", "permanent": true }, + { "source": "/roo-code-cloud/cloud-agents", "destination": "https://help.roocode.com/cloud-agents/", "permanent": true }, + { "source": "/roo-code-cloud/environments", "destination": "https://help.roocode.com/environments/", "permanent": true }, + { "source": "/roo-code-cloud/task-sync", "destination": "https://help.roocode.com/task-sync/", "permanent": true }, + { "source": "/roo-code-cloud/task-sharing", "destination": "https://help.roocode.com/task-sharing/", "permanent": true }, + { "source": "/roo-code-cloud/analytics", "destination": "https://help.roocode.com/analytics/", "permanent": true }, + { "source": "/roo-code-cloud/github-integration", "destination": "https://help.roocode.com/github-integration/", "permanent": true }, + { "source": "/roo-code-cloud/slack-integration", "destination": "https://help.roocode.com/slack-integration/", "permanent": true }, + { "source": "/roo-code-cloud/team-plan", "destination": "https://help.roocode.com/team-plan/", "permanent": true }, + { "source": "/roo-code-cloud/:path*", "destination": "https://help.roocode.com/:path*", "permanent": true }, + { "source": "/roo-code-cloud", "destination": "https://help.roocode.com", "permanent": true } + ] +}