# OpenCode on iMessage: read and reply, no API keys | SealGate

Let OpenCode read, triage, and reply across iMessage, no API keys required. Routed through SealGate's firewall, policy-checked and logged. Updated for 2026.

Source: https://sealgate.ai/connect/imessage/opencode

---

[Docs](https://sealgate.ai/docs/) [Product](https://sealgate.ai/product) By role

[Security teams See every agent, prove control](https://sealgate.ai/product#for-security-leaders) [IT & platform Kill shadow MCP, clear the ticket queue](https://sealgate.ai/product#for-it-teams) [Engineering teams Keep your agents, skip the blocks](https://sealgate.ai/product#for-developers) [Compliance & enterprise Govern to the standards you answer to](https://sealgate.ai/product#for-compliance)

By feature

[Discovery Find and quarantine shadow MCP](https://sealgate.ai/product#discovery) [MCP gateway One enforcement point for every call](https://sealgate.ai/product#mcp-gateway) [Supply chain security Pin tools, catch silent changes](https://sealgate.ai/product#supply-chain) [Detection and Response Stop data leaving in real time](https://sealgate.ai/product#detection-response) [Risk scoring Score every session Low to High](https://sealgate.ai/product#risk-scoring) [Agent inventory & records One control plane for the fleet](https://sealgate.ai/product#system-of-actions) [Audit-ready Forensic trail for every action](https://sealgate.ai/product#audit-ready) [Chrome extension Track ChatGPT and Claude tool calls](https://sealgate.ai/chrome) [Self-hosting Run it in your own VPC or air-gapped](https://sealgate.ai/self-hosting)

[Developers](https://sealgate.ai/dev) AI Data Leaks [Cursor/VSCode Data Leak](https://www.linkedin.com/posts/eito-miyamura-157305121_cursor-github-mcp-can-lead-to-private-keys-activity-7383899320326160384-tMCX) [ChatGPT Gmail/Outlook Data Leak](https://www.linkedin.com/feed/update/urn:li:activity:7372306174253256704/) [Perplexity Comet Bankruptcy](https://www.linkedin.com/feed/update/urn:li:activity:7386434090901671936/) [Postgres Data Exfiltration](https://www.youtube.com/watch?v=cqvC7hGXy8Y) [Claude Desktop Data Leak](https://gatlingx.notion.site/Calendar-only-exfiltration-23e89dcc2f088029ade9e81e7d1c275f) [Claude Code Outlook Data Leak](https://www.youtube.com/watch?v=Wldae7-SN5E) [Confluence Insider Threat](https://www.youtube.com/watch?v=SpXUPto90IA)

[Blog](https://sealgate.ai/blog/) [Pricing](https://sealgate.ai/pricing) [Book a demo](https://cal.com/eito80/demo)

[Docs](https://sealgate.ai/docs/) [Product](https://sealgate.ai/product) [Developers](https://sealgate.ai/dev) [Pricing](https://sealgate.ai/pricing) [Self-hosting](https://sealgate.ai/self-hosting) AI Data Leaks [Cursor/VSCode Data Leak](https://www.linkedin.com/posts/eito-miyamura-157305121_cursor-github-mcp-can-lead-to-private-keys-activity-7383899320326160384-tMCX) [ChatGPT Gmail/Outlook Data Leak](https://www.linkedin.com/feed/update/urn:li:activity:7372306174253256704/) [Perplexity Comet Bankruptcy](https://www.linkedin.com/feed/update/urn:li:activity:7386434090901671936/) [Postgres Data Exfiltration](https://www.youtube.com/watch?v=cqvC7hGXy8Y) [Claude Desktop Data Leak](https://gatlingx.notion.site/Calendar-only-exfiltration-23e89dcc2f088029ade9e81e7d1c275f) [Claude Code Outlook Data Leak](https://www.youtube.com/watch?v=Wldae7-SN5E) [Confluence Insider Threat](https://www.youtube.com/watch?v=SpXUPto90IA)

[Blog](https://sealgate.ai/blog/) [Book a demo](https://cal.com/eito80/demo)

→

OpenCode

# Connect iMessage to OpenCode

Let OpenCode read, triage, and reply across iMessage, governed by SealGate and policy-checked on every call.

Part of the [iMessage setup guide](https://sealgate.ai/connect/imessage) , which covers every agent and how the connection works under the hood.

Paste this into your coding agent, or run it yourself in a terminal.

Agent prompt easier Terminal faster

## Set up OpenCode for iMessage, step by step

- 1 ### Create your SealGate account from this link If you do not already have a SealGate account, sign up at the link below. Starting from it pre-approves the Beeper connector for your new account, so after you install there is nothing to approve by hand. Already have an account? Skip ahead and you will approve Beeper once in the dashboard (last step). https://dashboard.sealgate.ai/start/personal-messaging?utm_source=sealgate.ai&utm_campaign=seo-connect&utm_content=imessage-opencode
- 2 ### Install the messaging connector Run the one-line installer for your OS (macOS or Windows). It installs sealgate-stdiod and the Beeper connector, which bridges your messaging accounts through the Beeper desktop app on your own logins, and connects it to your SealGate account. If you signed up through the link above it is approved automatically; otherwise it waits for a one-time approval in your dashboard. macOS / Linux Windows (PowerShell) curl -fsSL https://sealgate.ai/install-beeper.sh | SEALGATE_UTM_CAMPAIGN=seo-connect SEALGATE_UTM_CONTENT=imessage-opencode bash $env:SEALGATE_UTM_CAMPAIGN='seo-connect'; $env:SEALGATE_UTM_CONTENT='imessage-opencode'; powershell -ExecutionPolicy Bypass -Command "irm https://sealgate.ai/install-beeper.ps1 | iex"
- 3 ### Add SealGate to OpenCode Register the gateway as a remote MCP server, then sign in. The auth command opens your browser for OAuth, and opencode mcp list should show sealgate as connected afterwards. opencode mcp add sealgate --url https://mcp.sealgate.ai/mcp opencode mcp auth sealgate
- 4 ### Approve the connector if you skipped the signup link If you created your account through the signup link above, Beeper is already approved, so you are done. Otherwise, open the SealGate dashboard and approve the Beeper connector once. Either way every call the agent makes is policy-checked and logged, and you can keep it read-only until you want the agent to reply on your behalf.
- 5 ### Ask OpenCode to work with your messages Start OpenCode in your terminal and ask for something concrete. OpenCode calls the messaging tools through SealGate, and every call is policy-checked and logged. Summarize my unread messages and draft replies for me to approve.

Please help me connect iMessage to OpenCode through SealGate on my machine. If I do not already have a SealGate account, have me sign up at https://dashboard.sealgate.ai/start/personal-messaging?utm_source=sealgate.ai&utm_campaign=seo-connect&utm_content=imessage-opencode first, since starting there pre-approves the Beeper connector. Then follow the setup steps at https://sealgate.ai/connect/imessage/opencode.md and stop whenever I need to act myself: approving this device in the browser when the installer asks, and, only if I already had an account, approving the Beeper connector in the SealGate dashboard.

Requires macOS or Windows (Linux is experimental) with the Beeper desktop app installed.

## Connecting OpenCode

OpenCode adds the SealGate gateway as a remote MCP server with one CLI command and signs in with OAuth, so the open-source coding agent can work with your messages right from the terminal. See the [OpenCode setup guide](https://sealgate.ai/docs/getting-started) for the exact steps.

## What OpenCode can do with iMessage

- Triage unread texts and draft replies in your own voice for you to send.

- Summarize a long thread so you catch up in seconds.

- Find that address, link, or photo someone texted you weeks ago.

- Turn a text conversation into a task or calendar note.

Ready to let OpenCode handle your iMessage? Paste the setup prompt into your coding agent and you are connected in a couple of minutes.

Copy setup prompt [New to SealGate? Create your account first](https://dashboard.sealgate.ai/start/personal-messaging?utm_source=sealgate.ai&utm_campaign=seo-connect&utm_content=imessage-opencode)

## Why connect iMessage through SealGate

One setup for every app, works with cloud and mobile agents, fully governed and logged, and your messages are never stored.

### One setup, every network

The same command connects your whole unified inbox, so you are not wiring up a separate bridge for each app.

### Works with cloud and mobile agents

A local daemon tunnels the connector out, so ChatGPT, Claude, and other cloud agents can use it, not just CLI tools.

### Governed and logged

Every tool call runs through SealGate policies and lands in an audit trail that records only metadata, never your message content, so access stays under your control.

### SealGate never stores your messages

Message content only passes through in transit to be checked against your policies, and is never stored or read by anyone at SealGate.

## Related guides

[Use ChatGPT with iMessage](https://sealgate.ai/connect/imessage/chatgpt) [iMessage to Claude](https://sealgate.ai/connect/imessage/claude) [Connect Codex to iMessage](https://sealgate.ai/connect/imessage/codex) [iMessage to Devin](https://sealgate.ai/connect/imessage/devin) [GitHub Copilot on iMessage](https://sealgate.ai/connect/imessage/copilot) [Connect Grok to iMessage](https://sealgate.ai/connect/imessage/grok) [Grokbot on iMessage](https://sealgate.ai/connect/imessage/grokbot) [iMessage to Hermes](https://sealgate.ai/connect/imessage/hermes) [Use OpenClaw with iMessage](https://sealgate.ai/connect/imessage/openclaw) [Connect Lovable to iMessage](https://sealgate.ai/connect/imessage/lovable) [iMessage to Replit](https://sealgate.ai/connect/imessage/replit) [iMessage to Muse](https://sealgate.ai/connect/imessage/muse) [iMessage to Town](https://sealgate.ai/connect/imessage/town) [Connect OpenCode to WhatsApp](https://sealgate.ai/connect/whatsapp/opencode) [OpenCode on Telegram](https://sealgate.ai/connect/telegram/opencode) [Connect OpenCode to LinkedIn DMs](https://sealgate.ai/connect/linkedin/opencode) [Use OpenCode with Signal](https://sealgate.ai/connect/signal/opencode) [Connect OpenCode to Instagram DMs](https://sealgate.ai/connect/instagram/opencode) [OpenCode on Messenger](https://sealgate.ai/connect/messenger/opencode) [Connect OpenCode to X DMs](https://sealgate.ai/connect/x/opencode) [Use OpenCode with Discord DMs](https://sealgate.ai/connect/discord/opencode) [Connect OpenCode to LINE](https://sealgate.ai/connect/line/opencode) [All iMessage setups](https://sealgate.ai/connect/imessage) [SealGate vs other MCP gateways](https://sealgate.ai/comparison)

## Connecting iMessage to OpenCode: FAQ

Can OpenCode read and send iMessage messages? Yes. OpenCode adds the SealGate gateway as a remote MCP server, which lets it use your iMessage tools. Whichever model provider you run OpenCode with, every call goes through SealGate, where it is policy-checked and logged.

Do I need a Mac? iMessage runs on Apple's network, so connecting it through the Beeper desktop app needs an Apple device signed in to iMessage. Once connected, any agent you point at it can use it.

Where do my messages go? Your iMessage history and login are never stored on SealGate's servers. When your agent makes a call, the request and response route through SealGate to be policy checked in memory, and only metadata about the call is logged (which tool ran, when, and which agent ran it). SealGate never stores the message content itself.

What does SealGate store about my messages? SealGate routes each tool call to your connector and back, holding the request and response in memory only long enough to apply your policies, then discarding them. That check is automated: the gateway inspects the traffic programmatically to enforce your rules, and no one at SealGate can read your messages. They are never persisted and never used to train any model. SealGate keeps only call metadata (which tool ran, when, and which agent ran it), never the tool-call parameters or results, so your conversations and who you are talking to are never stored on SealGate's servers.

Can the agent send texts, or only read them? Both. You decide through SealGate policies whether a given agent can only read, or can also send, and every send is recorded in the audit log as metadata (that it happened, when, and by which agent), never the text of the message itself.

Want the full walkthrough? Read the [documentation](https://sealgate.ai/docs/) or email [hello@sealgate.ai](mailto:hello@sealgate.ai) .

### Contact Us

SealGate (GPU-EVM LTD)

3rd Floor, 86-90 Paul Street

London EC2A 4NE

Email: hello@sealgate.ai

### Legal

[Terms of Service](https://sealgate.ai/terms-of-service) [Privacy Policy](https://sealgate.ai/privacy-policy) [Subprocessors](https://sealgate.ai/subprocessors) [Data Processing Addendum](https://sealgate.ai/dpa)

### Quick Links

[Home](https://sealgate.ai/) [Product](https://sealgate.ai/product) [Pricing](https://sealgate.ai/pricing) [For developers](https://sealgate.ai/dev) [Self-hosting](https://sealgate.ai/self-hosting) [Chrome extension](https://sealgate.ai/chrome) [Security](https://sealgate.ai/security) [Comparison](https://sealgate.ai/comparison) [For your team](https://sealgate.ai/for) [About](https://sealgate.ai/about) [Contact](https://sealgate.ai/contact) [Brand](https://sealgate.ai/brand) [Press](https://sealgate.ai/press) [Docs](https://sealgate.ai/docs/) [Developer docs](https://sealgate.ai/docs/developers) [Guides](https://sealgate.ai/guides/) [MCP gateway guide](https://sealgate.ai/guides/mcp-gateway) [Blog](https://sealgate.ai/blog/)

### Connect

[Connect AI to messaging](https://sealgate.ai/connect) [WhatsApp](https://sealgate.ai/connect/whatsapp) [iMessage](https://sealgate.ai/connect/imessage) [Telegram](https://sealgate.ai/connect/telegram) [LinkedIn DMs](https://sealgate.ai/connect/linkedin) [Signal](https://sealgate.ai/connect/signal) [Instagram DMs](https://sealgate.ai/connect/instagram) [Messenger](https://sealgate.ai/connect/messenger) [X DMs](https://sealgate.ai/connect/x) [Discord DMs](https://sealgate.ai/connect/discord) [LINE](https://sealgate.ai/connect/line) [Beeper](https://sealgate.ai/beeper)

### Follow Us