OTORO 2.0

Sign in to your ORSO account and work with Otoro Code directly in VS Code. OTORO keeps its blue identity, a compact layout, and a focused composer.

Start coding

1. Install OTORO (extension ID OTORO.otoro) and reload VS Code when prompted.
2. Open a trusted folder and select OTORO in the activity bar.
3. Choose Sign in with your ORSO account. Your browser opens the website, where you sign in or create an account and approve the connection.
4. Return to VS Code. Once your account is confirmed, the composer appears. Send a request and watch progress and the response in the sidebar.

Browser sign-in and sidebar coding work on Windows, macOS, and Linux without a CLI installation or WSL. Access and refresh tokens stay in VS Code SecretStorage. The sidebar receives only account status, never credentials. An existing session is checked when you open OTORO; expired sessions are refreshed, and sign-out removes the stored connection.

Otoro Code is the only model. Requests use the same authenticated platform transport as the CLI. Generated projects save to your website account; use Open saved project to view them. This does not automatically edit files in your local repository or upload your workspace. Only your submitted request or explicitly selected text is sent.

Working in VS Code

• OTORO: Start Session opens the account-gated sidebar (Ctrl+Alt+O, or Cmd+Alt+O on macOS).
• OTORO: Run Request… submits a request to the sidebar (Ctrl+Alt+R, or Cmd+Alt+R).
• OTORO: Run Request from Selection sends explicitly selected text, up to 2,000 characters.
• OTORO: Sign In opens browser approval. Sign Out disconnects your account.
• The actions menu includes new conversation, saved project, optional CLI tools, and connection details.
• Use the stop button to cancel the current request. Failed requests retain your draft.

Optional terminal tools

Local terminal workflows and authorized assessment tools continue to use the separate CLI. Install Node.js 22.6 or newer and the CLI for those commands. These terminal tools require a POSIX shell: Linux, macOS, or a VS Code WSL connection on Windows. Use OTORO: Sign In to the Separate CLI to connect that installation. Sidebar sign-in and coding are independent of this optional setup.

Permission policy, verbosity, and executable-path settings apply to the separate CLI. The platform-origin setting selects the website account connection; credentials are isolated by origin. Workspace Trust is required.

Updates

Marketplace installations receive published updates when VS Code extension auto-updates are enabled. You can also use Extensions: Check for Extension Updates, or install a supplied VSIX manually. Version 2.0.2 adds the account-gated browser sign-in and native sidebar coding flow.

The optional CLI updates separately: run otoro upgrade for instructions.

Development

npm run check builds the shared Code transport and checks extension syntax and behavior. npm run package runs these checks and packages the extension. Runtime code has no third-party dependencies. Authentication and coding tests cover approval, secure-storage boundaries, session restoration, cancellation, account isolation, and rejecting unsigned-in requests.