OpenClaw + Lark
Lark is the conversation entry point; OpenClaw is the agent that runs the work. Test OpenClaw with GPT-5.6 Sol below, then connect Lark and choose this agent in channel settings.
How the combination works
OpenClaw does the work. Lark carries the conversation.
OpenClaw provides an autonomous tool-using loop for browser, shell, file, and application work in a persistent cloud computer.
Connect Lark from the selected agent’s settings. Open the bot chat, send the connect code, and the conversation reaches the agent you picked; add the bot to a group to give a team the same entry point.
OpenClaw
Owns the work loop, model calls, files, cloud computer, enabled tools, and the result returned to the conversation.
Lark
Lets people reach the selected AgentSky agent from Lark. It does not grant access to repositories or other applications mentioned in a message.
AgentSky
Owns the selected responder, channel binding, task state, model and runtime usage, and the separate permissions for tools and connectors.
Setup and first task
Connect OpenClaw to the Lark conversation you intend to use.
The Composer tests the exact agent in the browser. Channel setup remains a separate account or workspace authorization, so neither step can silently stand in for the other.
Test OpenClaw in the Composer
The Composer above selects OpenClaw and its current recommended model, GPT-5.6 Sol. Use a small task with an answer you can inspect before connecting a shared channel.
Connect Lark and choose OpenClaw
Open an agent in the developer console and select Connect Lark in its channel controls. AgentSky shows a connect code and a button that opens the bot chat in Lark. Paste the code into the bot’s direct chat and send it. To connect a group instead, add the bot to the group and send the code there. The code is personal and expires after 15 minutes.
Verify the real channel path
Ask the agent to turn notes you paste into a prioritized checklist. Confirm the reply arrives in that chat before sending more work; in a group, @mention the bot. Check that the reply arrives in the intended Lark conversation and that the dashboard still names OpenClaw as the responder.
Access, cost and limits
What OpenClaw + Lark establishes
Longer-running computer and application workflows that combine browser actions, files, and general automation.
Configure and verify
- OpenClaw and GPT-5.6 Sol are preselected for the browser evaluation.
- Lark is connected or paired to the intended account, workspace, server, device or conversation.
- The first real message reaches the selected agent and returns a useful reply through the same channel.
Do not assume
- A browser task does not automatically bind Lark; finish the channel setup separately.
- Lark membership does not authorize repositories, email, documents or other application data.
- Model tokens and active computer time are billed separately from any channel or provider plan.
Common questions
Related resources
OpenClaw
Review OpenClaw's supported models, capabilities and browser Composer.
Lark channel
Review the channel-specific authorization, pairing and troubleshooting guide.
OpenClaw + GPT-5.6 Sol
Review the current default agent and model combination.
Pricing
Review model, active-computer, tool and connector charges.
