pi + Lark

Lark is the conversation entry point; pi is the agent that runs the work. Test pi with GPT-5.6 Sol below, then connect Lark and choose this agent in channel settings.

A task starts here in your browser. To receive messages through Lark, connect Lark on your Channels page. Channel setup opens separately; it does not automatically bind this new task.

How the combination works

pi does the work. Lark carries the conversation.

Pi runs a compact coding and tool-use loop that can inspect files, execute commands, and iterate on a bounded task.

Connect your organization once. Everyone shares the workspace; each conversation can continue a task or start a new one.

  • pi

    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 pi 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 pi in the Composer

The Composer above selects pi and its current recommended model, GPT-5.6 Sol. Use a small task with an answer you can inspect before connecting a shared channel.

02

Connect Lark and choose pi

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.

03

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

Access, cost and limits

What pi + Lark establishes

Focused engineering tasks where a lightweight agent loop and quick iteration matter more than a large orchestration layer.

Configure and verify

  • pi 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

Test pi, then connect Lark.

Open the Composer