Quick comparison
WebView mode
Best when you already use the provider’s web app and want its familiar interface inside the workspace.
API mode
Best when a supported workflow should send a defined task and context directly to a provider.
Local mode
Best when a supported local runtime is available and you want work to remain on the computer.
Use WebView mode
Open the provider, sign in with the provider account, and work in the embedded web experience. Capture important results back to the project when they are ready.
The provider’s own plan, limits, and browser-session behavior still apply.
Use API mode
Add the provider credentials in the supported settings area, choose an available model, and review usage costs in the provider account.
API keys should never be pasted into project notes, support tickets, screenshots, or handoff packages.
Choose per task
Conversation or provider-native feature
Use WebView when the provider’s normal interface is important.
Repeatable project task
Use API mode when the workflow benefits from direct routing and structured capture.
Private local work
Use a local provider when the runtime and model support the task.
Review what is sent
Connection mode does not remove the need to review context. Send only the material needed for the task and appropriate for that provider.
Ask LobeWork about this guide.
The question will be placed into the support widget so you can continue from the exact topic.