iMessage support for eve agents
Eve agents can now accept commands via iMessage. Vercel's new Photon channel routes SMS conversations into agent sessions, queuing multi-message inputs so agents don't fork.
Why it matters
A major consumer messaging platform now has native agent integration. This expands where autonomous systems can operate — no longer confined to Slack, Discord, or web dashboards. Practitioners deploying multi-channel agents need to evaluate Photon's webhook architecture and session-state handling.
The key facts
12 to knowEve agents now support iMessage via .evePhoton channel
Photon channel keeps each iMessage conversation in a single agent session
Multi-message input steering: if messages arrive during agent reply, they modify the in-progress response rather than spawning separate agent calls
Webhook verification and message read-marking built in
Setup via 'eve add channel/photon-imessage' command with Vercel Connect support; portable credentials fallback available
Photon channel template available for deployment
Vercel Eve framework ships iMessage integration via .evePhoton channel
Channel maintains one-agent-per-conversation threading; queues concurrent messages to prevent duplicate responses
Incoming webhooks verified; accepted messages marked as read
Setup via 'eve add channel/photon-imessage' command; uses Vercel Connect or environment variables
Replaces per-message handling with context-aware turn.onMessage hooks
Published August 5, 2026
Go to the source
Vercel Blogvercel.com
Publisher excerpt: agents can now connect to iMessage through the new .evePhoton channel The channel keeps each iMessage conversation in one eve session, verifies incoming webhooks, and marks accepted messages as read. If more messages arrive while the agent is replying, they steer the in-progress reply instead of…