AgentSky
Log in

Grok Build + Lark

Lark is the conversation entry point; Grok Build is the agent that runs the work. Test Grok Build with Grok 4.6 below, then connect Lark and choose this agent in channel settings.

Repo

Review option pricing before running.

Runs started with multiple options stay blind until you vote.

A task starts here in your browser. To receive messages through Lark, choose the agent, then connect the channel in its Channels panel. Channel setup opens separately; it does not automatically bind this new task.

How the combination works

Grok Build does the work. Lark carries the conversation.

Runs the task through its ACP harness in a persistent cloud workspace while the selected AgentSky model supplies reasoning and generation.

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.

  • Grok Build

    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 Grok Build 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.

01

Test Grok Build in the Composer

The Composer above selects Grok Build and its current recommended model, Grok 4.6. Use a small task with an answer you can inspect before connecting a shared channel.

02

Connect Lark and choose Grok Build

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.

03

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 Grok Build as the responder.

Access, cost and limits

What Grok Build + Lark establishes

Tasks supported by this ACP harness through AgentSky's verified platform-model path.

Configure and verify

  • Grok Build and Grok 4.6 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

Grok Build

Review Grok Build's supported models, capabilities and browser Composer.

Lark channel

Review the channel-specific authorization, pairing and troubleshooting guide.

Grok Build + Grok 4.6

Review the current default agent and model combination.

Pricing

Review model, active-computer, tool and connector charges.

Test Grok Build, then connect Lark.

Open the Composer