Kimi Code + Lark
Lark is the conversation entry point; Kimi Code is the agent that runs the work. Test Kimi Code with Kimi K3 below, then connect Lark and choose this agent in channel settings.
How the combination works
Kimi Code does the work. Lark carries the conversation.
Kimi Code supplies a repository-focused coding loop for reading large code contexts, editing files, and running validation in a cloud workspace.
Connect your organization once. Everyone shares the workspace; each conversation can continue a task or start a new one.
Kimi Code
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 Kimi Code 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 Kimi Code in the Composer
The Composer above selects Kimi Code and its current recommended model, Kimi K3. Use a small task with an answer you can inspect before connecting a shared channel.
Connect Lark and choose Kimi Code
In Channels, choose Lark. Register your organization’s bot and publish it. Send the temporary connection code to your bot, in a direct chat or group.
Verify the real channel path
Send a small task and check the reply in Lark. Use /new for a separate session. Check that the reply arrives in the intended Lark conversation and that the dashboard still names Kimi Code as the responder.
Access, cost and limits
What Kimi Code + Lark establishes
Repository work that benefits from Kimi Code's coding workflow and long-context model options.
Configure and verify
- Kimi Code and Kimi K3 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
Kimi Code
Review Kimi Code's supported models, capabilities and browser Composer.
Lark channel
Review the channel-specific authorization, pairing and troubleshooting guide.
Kimi Code + Kimi K3
Review the current default agent and model combination.
Pricing
Review model, active-computer, tool and connector charges.