Models, tools and control
Configure available models, respond to approvals and distinguish browser and native control.
Model services
Open model services in settings and inspect gateway, custom, own-account and local availability separately. Current mainline gateway and account-bridge UI still contains unavailable notices and disabled buttons; wrokCode login instructions do not apply automatically.
Custom connection management has an implemented entry. Fill the actual form with the required endpoint, credentials and model information, save and refresh the catalog. Saved configuration is not proof of complete conversation, tools, cancellation and recovery acceptance.
Select and authorize
Choose a model allowed by the current catalog. Resolve loading, access or capability errors rather than guessing model IDs.
Specify target, workspace and permitted effects when assigning work. Read an approval's action and scope before accepting it. Disconnecting MCP invalidates local credentials first; provider revocation may still need follow-up. For operator_required, confirm revocation in the provider's administration interface.
Browser and computer control
Browser work involves tabs, observation, input, takeover and Stop. Native control involves applications/windows and OS permission. Complete product journey acceptance remains open; follow the actual capability status.
Recheck after lock, sleep, permission changes or a missing target. Stopping does not roll back completed external effects.
wrok Bot model settings, OpenMyBot's host driver, wrokCode accounts and Acosmi API access are different entry points with separate credentials and quotas. See OpenMyBot and API docs.