Models, Tools, and Runtime Paths

Raydo is not trying to replace every tool you already use. It is trying to pull those entry points back into a clearer workspace.

Model access

Raydo can manage common model services and compatible endpoints from one place. For most users, the point is not how many connection types exist behind the scenes. The point is being able to view, switch, and use them in one desktop.

Runtime paths

In the public product story, the three main runtime paths to understand are:

• Raydo's built-in OpenClaw runtime
• local Codex workflows
• local Claude Code workflows

These are not meant to feel like disconnected products. They are brought together under one control surface.

Channels and outside entry points

Raydo can connect with common communication surfaces so updates, collaboration, or notifications do not have to stay inside the desktop alone. The exact range should follow what the current version shows in the product.

Feishu / Lark connection: one entry, two service regions

Raydo presents Feishu China and Lark Global as one entry. Users do not need to learn two different capabilities. They only need to choose the workspace version during setup:

• Feishu China uses the feishu.cn authorization and API domains.
• Lark Global uses the larksuite.com authorization and API domains.

This choice only decides which platform domain Raydo uses. The workflow inside Raydo stays the same.

Feishu / Lark setup has two layers, and they do different jobs:

• App ID / App Secret in Channel settings are app-level credentials. They come from the Feishu Open Platform app and identify which app is starting the connection. Raydo uses them to start OAuth, exchange the authorization code, and refresh access tokens.
• Connect account in App Connections is user-level authorization. After the user grants access in the browser, Raydo can work with the Feishu resources that account is allowed to use. The authorization result is managed by Raydo's connection secret storage and is not written to openclaw.json.

Recommended flow:

1. Choose the service region in Raydo Channel settings: Feishu China or Lark Global.
2. Create the app in the matching Open Platform and enter the App ID / App Secret.
3. In the same app, add the callback URL shown by Raydo. The default local desktop callback is http://localhost:1456/connections/feishu/oauth/callback.
4. Return to Raydo App Connections, choose Feishu / Lark, and connect the account.
5. After browser authorization succeeds, return to Raydo and grant the connection to the relevant project, role, or capability.

If the authorization page reports that the redirect URL is invalid, the callback registered in the matching Open Platform does not exactly match the URL used by Raydo, or the wrong service region was selected. Check the protocol, host, port, and path character by character. This error happens on the Feishu / Lark side before Raydo's local callback receives the authorization result.

MCP and tool connection

If you already use MCP or other local tools, Raydo helps by pulling configuration and connection work back into one place instead of leaving it spread across separate files and entry points.

Why this layer matters

Models change. Tools change. Team habits change. Raydo tries to keep the upper workspace steady, so the user experience stays more consistent even when the underlying mix evolves.