Grok Build + Slack
Slack is the conversation entry point; Grok Build is the agent that runs the work. Test Grok Build with Grok 4.6 below, then connect Slack and choose this agent in channel settings.
How the combination works
Grok Build does the work. Slack 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 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.
Grok Build
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 Grok Build 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.
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.
Connect Slack and choose Grok Build
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.
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 Grok Build as the responder.
Access, cost and limits
What Grok Build + Slack 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.
- 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
Grok Build
Review Grok Build's supported models, capabilities and browser Composer.
Slack 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.