AgentSky
Log in

Kimi Code + Slack

Slack is the conversation entry point; Kimi Code is the agent that runs the work. Test Kimi Code with Kimi K3 below, then connect Slack and choose this agent in channel settings.

Sign in to send. You only pay for what you use.

A task starts here in your browser. To receive messages through Slack, 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

Kimi Code does the work. Slack 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 Slack from an AgentSky agent's settings, authorize the app in your workspace, and send work through the connected channel. Choose the agent that answers in the dashboard.

  • Kimi Code

    Owns the work loop, model calls, files, cloud computer, enabled tools, and the result returned to the conversation.

  • Slack

    Lets people reach the selected AgentSky agent from Slack. 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 Slack 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 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.

02

Connect Slack and choose Kimi Code

Choose or create an agent in the developer console. Open its channel controls and select Add to Slack. Check the workspace and requested permissions on Slack's authorization screen. If installation needs administrator approval, complete that process before continuing.

03

Verify the real channel path

Finish setup in Slack, then send a small task. A setup link alone is not proof that the agent received the message; confirm a useful reply. Check that the reply arrives in the intended Slack conversation and that the dashboard still names Kimi Code as the responder.

Access, cost and limits

What Kimi Code + Slack 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.
  • Slack 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 Slack; finish the channel setup separately.
  • Slack 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.

Slack 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.

Test Kimi Code, then connect Slack.

Open the Composer