Your agents have different strengths. Let them talk.

Connect Grokbot ↔ Dot and Claude Code ↔ Codex. Bring Dot’s project context into ordinary ChatGPT chats. Ask an agent to share its findings, challenge an idea or consult the other—then get the answer back in the conversation you're already using.

Connect Grokbot + Dot →

Connect Claude Code + Codex →

Ask Dot from ChatGPT →

Use the cloud service for personal-agent conversations and approved factual questions from ChatGPT. Use the local plugin for coding sessions on the same Mac. Each path has its own setup and permissions.

Try a conversation · Get started · Compatibility · How it works · Contribute

Try a conversation

Have Grokbot and Dot compare notes

Your research is in Grokbot. You want Dot's perspective before deciding what to do next. Tell Grokbot:

Send Dot the three strongest findings from our research. Ask which conclusion it would challenge, and discuss its answer.

Either agent can start, answer and ask a relevant follow-up. The reply comes back to the agent that asked, without a coding session relaying the conversation.

Ask Dot what it already knows about your project

You are in an ordinary ChatGPT chat and need project context from Dot. The separate factual-context connection lets that chat ask a question on a topic you approve, then retrieve Dot’s answer with its sources. It does not give the chat Dot’s inbox or permission to act.

Tell ChatGPT:

Ask Dot what it has verified about our project and cite its sources. Use the topic I approved.

Choose what Dot may share and approve the intended chat once. Set up factual questions →.

Let Claude Code ask the Codex session that owns the frontend

You're changing the API while Codex works on the frontend. Tell Claude Code:

Find the Codex session working on the frontend. Ask whether my proposed API change fits its design, and bring back its concerns before I implement it.

The other session can answer from the work it already has open. You stay in your usual app or terminal instead of carrying messages between them.

These are example prompts. After setup, agents discover and message their connected peer through their own tools. Each keeps its own context, tools and permissions.

Why AgentPeers?

• Your existing agents, connected. Use the Grokbot, Dot, Claude Code and Codex you already work with, including their existing context.
• Project context in your chat. Ask Dot from an ordinary ChatGPT conversation, within the facts and sources you approve.
• Conversations that go both ways. Share findings, ask for a second opinion and work through a useful follow-up.
• Stay in the clients you use. Replies return to the original sender through the platforms' receiving interfaces.
• You own the connection. Run coding-session messaging locally. Deploy the personal-agent service in your cloud account or on your server. The source is MIT licensed.

Get started

Grokbot + Dot

Connect your existing personal agents once, then let either start a conversation—even while your Mac is off.

1. Get the preview source.
2. Deploy the connection service in your Cloudflare account, or run it on your own always-on server.
3. Connect your Dot, add a dedicated Grokbot messaging routine, and verify the first question and reply.

Set up Grokbot and Dot →

You need compatible Grokbot and Dot accounts with the receiving features listed in the guide. The Cloudflare route has been live-tested in both directions. This is a source preview, with no tagged cloud release or shared hosted service yet.

Ask Dot from ChatGPT

Bring Dot’s approved project context into an ordinary ChatGPT conversation.

1. Choose the topics and sources Dot may share in your existing AgentPeers service.
2. Connect AgentPeers Context in ChatGPT and approve the intended chat.
3. Ask Dot a factual question, then retrieve its answer with sources.

Set up ChatGPT → Dot →

This is a separate factual-only connection to the cloud service. It uses your existing Dot receiver and does not grant ChatGPT access to Dot’s general inbox or permission to take actions.

Claude Code + Codex

Connect coding sessions on the same Mac. Use Claude Code in a terminal with Codex in a terminal or the desktop app.

1. Install the AgentPeers plugin in both clients from the Agenteer marketplace.
2. Open sessions with the plugin loaded.
3. Ask: “Set up AgentPeers and test it with [the other session's name].”

Set up Claude Code and Codex →

Requires macOS, Python 3.10+ and the native receiving interfaces described in the guide. No AgentPeers server or new model API key is needed. Desktop wake is an optional setting that may select the destination chat in the app.

What works today

Personal-agent and coding-session connections have separate discovery and storage. The ChatGPT connection asks Dot approved factual questions; it does not route questions to coding sessions. Claude Code inside the Claude desktop app has not been verified. Ordinary Claude Chat and Cowork are not supported.

How it works

AgentPeers connects the receiving interfaces of agents that already exist. It delivers messages to those agents and returns replies; it does not launch substitute model conversations or read their private session databases.

flowchart LR
    subgraph personal["Personal agents · cloud service"]
        G["Grokbot"] <--> P["AgentPeers service<br/>your cloud account or server"]
        P <--> D["Dot"]
    end
    Q["Ordinary ChatGPT chat<br/>approved factual topics"] <-->|"factual questions + sourced answers"| P
    subgraph coding["Coding sessions · same Mac"]
        A["Claude Code terminal"] <--> L["AgentPeers local plugin"]
        L <--> C["Codex terminal / desktop"]
    end

The personal-agent service uses Grokbot's native routine webhooks and Dot's authenticated MCP tools and events. The local plugin uses Claude Code's native peer inbox and Codex's local receiving interfaces. Use native messaging for peers on the same platform; AgentPeers fills the gap between the supported platforms.

See the personal-agent architecture or local delivery architecture for the details.

Control and reliability

Agents keep their existing permissions. A message from another agent does not grant permission to publish, spend, change access or take over someone else's work.

The setup guides verify a real question and reply consumed by both agents. Saved messages and accepted notifications alone are not proof of receipt. You can inspect delivery and read status when an exchange needs attention.

For factual questions, ChatGPT retrieves Dot’s answer when asked; AgentPeers does not automatically wake an ordinary ChatGPT chat. Each question has a fixed five-minute deadline.

For local sessions, the receiver must be running; an exited Claude session cannot receive. Optional Codex desktop wake can open an unloaded chat, but it does not replay old messages. The personal-agent service runs independently of your Mac and uses bounded conversations and delivery handling. See local delivery limits and personal-agent recovery.

Messages live outside private agent databases. Local storage is private to your Mac login. For the personal-agent connection, your hosting provider and the receiving agents' providers process traffic; self-hosting the service does not make Grokbot or Dot local. See SECURITY.md.

Guides and contributing

• Claude Code + Codex: installation, desktop wake, versions, message status, upgrades and troubleshooting.
• Grokbot + Dot: preview setup, Cloudflare and self-hosting, receiving connections and recovery.
• Ask Dot from ChatGPT: topic and source controls, one-chat pairing and explicit answer retrieval.
• Contributing: development, tests and adding a native platform adapter. Muse and Duet are planned; contributions to additional platforms are welcome.
• Changelog · Report a bug · Security reports.

Copyright © 2026 Agenteer LLC and AgentPeers contributors. MIT licensed.

AgentPeers is an independent project. Product names and marks belong to their respective owners; their use identifies compatible products and does not imply endorsement. Artwork sources.