AgentSky
Log in

Grok Build + iMessage

iMessage is the conversation entry point; Grok Build is the agent that runs the work. Test Grok Build with Grok 4.6 below, then connect iMessage 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 iMessage, 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. iMessage 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 iMessage by sending the pairing text to the number shown in AgentSky. The channel uses a US number and reaches the agent you select in the dashboard.

  • Grok Build

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

  • iMessage

    Lets people reach the selected AgentSky agent from iMessage. 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 iMessage 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 iMessage and choose Grok Build

Select an agent in the developer console and open its iMessage channel control. Use Open Messages, scan the QR with your iPhone, or copy the displayed number and code. Send the text from the account you intend to use.

03

Verify the real channel path

After pairing, ask for a checklist from a short set of notes. Verify that the selected agent replies before relying on the connection. Check that the reply arrives in the intended iMessage conversation and that the dashboard still names Grok Build as the responder.

Access, cost and limits

What Grok Build + iMessage 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.
  • iMessage 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 iMessage; finish the channel setup separately.
  • iMessage 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.

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

Open the Composer