AgentSky
Log in

Codex + WhatsApp

WhatsApp is the conversation entry point; Codex is the agent that runs the work. Test Codex with GPT-5.6 Sol below, then connect WhatsApp 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 WhatsApp, 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

Codex does the work. WhatsApp carries the conversation.

Codex owns the coding-agent loop: it explores the repository, changes files, runs commands, and returns evidence from the cloud workspace.

Use the linked-device pairing flow to let incoming messages reach your selected agent. This is an unofficial connection; review the risks before choosing a number.

  • Codex

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

  • WhatsApp

    Lets people reach the selected AgentSky agent from WhatsApp. 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 Codex to the WhatsApp 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 Codex in the Composer

The Composer above selects Codex 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 WhatsApp and choose Codex

Select Connect WhatsApp in the agent’s channel controls. The consent explains that Meta can ban the linked number and recommends using a secondary number. On the phone for the number being paired, open WhatsApp Settings → Linked Devices → Link a Device. Scan the displayed QR; it rotates while waiting.

03

Verify the real channel path

Send a small request to the paired number from another account you control. Messages sent by the paired number itself do not reach the agent. Confirm the response and usage. Check that the reply arrives in the intended WhatsApp conversation and that the dashboard still names Codex as the responder.

Access, cost and limits

What Codex + WhatsApp establishes

Software engineering tasks that benefit from Codex's repository navigation, command execution, and iterative implementation loop.

Configure and verify

  • Codex and GPT-5.6 Sol are preselected for the browser evaluation.
  • WhatsApp 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 WhatsApp; finish the channel setup separately.
  • WhatsApp 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

Codex

Review Codex's supported models, capabilities and browser Composer.

WhatsApp channel

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

Codex + GPT-5.6 Sol

Review the current default agent and model combination.

Pricing

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

Test Codex, then connect WhatsApp.

Open the Composer