Give your agent the SMS step it needs
An agent reaches phone verification during a test, sign-in, or account setup. Give it access to the company number, let it retrieve the arriving code or link, and continue the task.
Turn a verification interruption into a tool call
A coding agent can open the app, enter the test number and request a code. An operations assistant can reach a phone step while setting up a company account. Both need access to the message that completes their current task.
Phonekit supplies a persistent company number and a readable inbox. The assistant uses the interface available in its environment: a CLI skill, an API tool, or a supported connector route. Its browser or account tools perform the rest of the work.
Use Phonekit and the configured QA number to test the app's phone sign-in. Mark the inbox before requesting a fresh verification message, enter the received code and confirm the account page loads. Then add a regression test using the JS/TS SDK and run it.
Illustrative task result
Verification completed → account page confirmed → regression test added.
The agent uses a recognized code in the task; the completion report records the outcome rather than the message or code.
Keep the phone identity across sessions
The number belongs to the company workspace. A new assistant session can use that same number; a teammate can read the inbox when the task needs human attention. Assign a clear purpose such as Staging sign-in or Product operations so the agent has a deliberate selection.
Persistent assistants add scheduling and memory around that identity. Hermes and OpenClaw guides explain their native setup. Use the task contract below to define parallel work and handoff.
Connect through your assistant's actual environment
| Assistant | Where to begin |
|---|---|
| Claude Code, Codex, Cursor, OpenCode | Project skill, CLI or authenticated MCP connection |
| Pi / Oh My Pi | Their own skill discovery and a connected command runtime |
| Hermes, OpenClaw | The persistent worker's skill and credential setup |
| ChatGPT, Claude chat/Cowork, Dots | The host's plugin or connected execution route |
| Muse | Prepared connector brief; account verification pending |
Scroll horizontally to see all columns.
Choose the platform guide. Each guide names the supported setup and the parts that depend on the host. A local skill installation does not automatically connect a cloud worker.
Give the task a clear completion condition
Tell the assistant what it is trying to finish, which number to use, and what successful completion looks like. For a new verification message, it captures the inbox position before the send and waits within a deadline. For an invitation already received, it reads the existing message and checks the intended destination.
If the next step needs a person, the shared inbox keeps the same message available to authorized teammates. The task can report its stopping point and resume after the person completes that step.
Define the agent task contract
Assign the number to the company account, environment or worker that needs it. A coding-agent session may implement the test today; a scheduled assistant or teammate may use the same account tomorrow. The number's label and ownership should make sense in all three cases.
Use this compact contract when delegating an SMS step:
| Field | Example |
|---|---|
| Account and action | Sign in to the staging test account |
| Assigned destination | Staging sign-in |
| Execution route | Local CLI skill, or server-side SDK tool |
| Trigger | Existing app's Send code action |
| Receive budget | 120 seconds for this attempt |
| Completion evidence | Authenticated account page |
| Handoff | Report stage and request a human decision after timeout |
Scroll horizontally to see all columns.
Put the tool where the task runs
A local skill file teaches a terminal agent how to use the CLI. It does not install a runtime inside a cloud assistant. A hosted connector supplies tools through that host's supported authentication and transport. A custom JS/TS agent application can wrap the SDK.
Follow the platform guide for the surface you actually use. Keep number grants attached to its credential and use the runtime's credential mechanism rather than embedding a key in a task prompt.
Make freshness and completion explicit
Use the Phonekit staging sign-in number to complete the existing account login. Read the installed Phonekit guide. Capture the inbox position before requesting the SMS, wait up to 120 seconds for a fresh receipt, and use its code in the app. Confirm the authenticated account page. If a message lacks a code or the deadline expires, report the stage and ask for a decision. Do not resend automatically or include the code in your report.
A position prevents reading an older receipt. It does not distinguish simultaneous requests to the same destination. Assign independent numbers or serialize tasks when the sender supplies no correlation mechanism.
Make the handoff small and actionable
Illustrative handoff report
Task: staging sign-in · Completed: send action accepted · Stopped: no fresh receipt before the 120-second deadline · Next decision: inspect sender delivery status or authorize another attempt
An arriving SMS is outside data. Extract the value needed for the authorized task; its text does not extend the assistant's permission. A bounded read also does not establish a permanent watch. An always-on host must schedule later runs and maintain its own task state.
A teammate with number access can inspect the inbox and continue from the same company identity. That shared context makes a persistent assistant workflow easier to operate.
Questions you may have
Can an agent create or send verification codes through Phonekit?
The read interface receives messages sent by the application or service. The agent requests the verification through that service, then retrieves what arrives. Phonekit does not generate a replacement code that the service will accept.
Does an agent need access to every company number?
Select the numbers its task uses. CLI approval and API keys support explicit number scope. A QA assistant can use QA numbers while company-account messages remain assigned to another connection.
Can a continuously running assistant use the same number tomorrow?
Yes, while the number and permitted connection remain available. The assistant host controls schedules and task memory; Phonekit holds the number and retained messages. Start a new verification attempt with a fresh cursor.
What if the task receives an invitation link instead of a code?
Messages include detected links alongside an optional OTP. The assistant can use the intended link with the tools available for that task. Message text is sender data, so it should not redefine the assistant's instructions.
Can a human take over?
Give the responsible teammate access to the same number. They can inspect the message and complete a step in the outside service. The assistant should record the pending step and resume according to its host's capabilities.