You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To use Roo Code Cloud features (like the provider proxy), you need to authenticate:
135
+
Normal CLI usage is login-free. Use `--provider` with your own API key, or set the provider environment variable directly.
136
136
137
-
```bash
138
-
# Log in to Roo Code Cloud (opens browser)
139
-
roo auth login
137
+
Roo Code Router has been removed from the CLI. The remaining `auth` commands only help inspect or delete any legacy Roo auth token still stored from older releases:
140
138
141
-
# Check authentication status
139
+
```bash
140
+
# Check whether a legacy Roo auth token is still stored
142
141
roo auth status
143
142
144
-
#Log out
143
+
#Remove an old stored Roo auth token
145
144
roo auth logout
146
145
```
147
146
148
-
The `auth login` command:
149
-
150
-
1. Opens your browser to authenticate with Roo Code Cloud
151
-
2. Receives a secure token via localhost callback
152
-
3. Stores the token in `~/.config/roo/credentials.json`
153
-
154
-
Tokens are valid for 90 days. The CLI will prompt you to re-authenticate when your token expires.
155
-
156
-
**Authentication Flow:**
157
-
158
-
```
159
-
┌──────┐ ┌─────────┐ ┌───────────────┐
160
-
│ CLI │ │ Browser │ │ Roo Code Cloud│
161
-
└──┬───┘ └────┬────┘ └───────┬───────┘
162
-
│ │ │
163
-
│ Open auth URL │ │
164
-
│─────────────────>│ │
165
-
│ │ │
166
-
│ │ Authenticate │
167
-
│ │─────────────────────>│
168
-
│ │ │
169
-
│ │<─────────────────────│
170
-
│ │ Token via callback │
171
-
│<─────────────────│ │
172
-
│ │ │
173
-
│ Store token │ │
174
-
│ │ │
175
-
```
147
+
If you never used Roo Code Router, you can ignore this section entirely.
|`ROO_WEB_APP_URL`| Override the Roo Code Cloud URL (default: `https://app.roocode.com`) |
227
-
228
192
## Architecture
229
193
230
194
```
@@ -268,7 +232,7 @@ The CLI will look for API keys in environment variables if not provided via `--a
268
232
269
233
```bash
270
234
# Run directly from source (no build required)
271
-
pnpm dev --provider roo --api-key $ROO_API_KEY --print "Hello"
235
+
pnpm dev --provider openrouter --api-key $OPENROUTER_API_KEY --print "Hello"
272
236
273
237
# Run tests
274
238
pnpm test
@@ -280,10 +244,10 @@ pnpm check-types
280
244
pnpm lint
281
245
```
282
246
283
-
By default the `start` script points `ROO_CODE_PROVIDER_URL` at `http://localhost:8080/proxy` for local development. To point at the production API instead, override the environment variable:
247
+
By default the dev script still points `ROO_CODE_PROVIDER_URL` at `http://localhost:8080/proxy` for local extension-host development. The CLI provider selection itself should use a non-Router provider such as OpenRouter. To point the backend URL at production instead, override the environment variable:
284
248
285
249
```bash
286
-
ROO_CODE_PROVIDER_URL=https://api.roocode.com/proxy pnpm dev --provider roo --api-key $ROO_API_KEY --print "Hello"
250
+
ROO_CODE_PROVIDER_URL=https://api.roocode.com/proxy pnpm dev --provider openrouter --api-key $OPENROUTER_API_KEY --print "Hello"
0 commit comments