crosstalk — Claude Code plugin for cross-repo requests
crosstalk passes work requests between Claude Code sessions in separate repositories and helps both sides agree on the contract first.
MIT ★ 3,785 updated 2026-10-25
/plugin marketplace add davepoon/buildwithclaude
/plugin install crosstalk@buildwithclaudeWhat crosstalk does
When a change spans repositories, a session can ask its counterpart to handle work through /ask-peer. The command inspects related files and types, drafts a request, then sends it only after you approve. The receiving agent also asks its user for approval before doing the work.
A reply includes affected files, the contract, errors, and a verification command. The requesting session reads the named files and runs that check. If the agents disagree on the contract, you decide; if verification fails, one message goes back to the peer before the issue is escalated to you. The requesting session should not build on the reply before verification succeeds.
The plugin includes a slash command and two skills: one for sending requests, one for answering them. It uses Claude Code’s built-in session messaging, with no hooks or MCP server.
What it helps with
- agree on an API between frontend and backend repositories
- request a change from another repo without guessing its contract
- check a peer’s response against named files and a verification command
- escalate contract disagreements or failed checks to the developer
Example prompts for the agent
- Ask the session in the other repository to add a
statusfield to the shifts endpoint, using/ask-peer. - Request the route endpoint contract from the neighboring repository with
/ask-peer. - When a task depends on a change in another repository, tell the agent to ask its peer for that work.
How to install crosstalk
Plugin marketplace
/plugin marketplace add davepoon/buildwithclaude/plugin install crosstalk@buildwithclaudeStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about crosstalk
How do I install crosstalk in Claude Code?
Run /plugin marketplace add davepoon/buildwithclaude, then /plugin install crosstalk@buildwithclaude. Install it on the machine running both sessions.
What does crosstalk do?
It lets Claude Code sessions in separate repositories request work with a defined contract. Both sides approve the request, and the requesting session verifies the reply before using it.
How does crosstalk connect the sessions?
It relies on Claude Code’s built-in session messaging. No MCP server is involved, and both sessions need the plugin.
Source text
crosstalk · MIT
# crosstalk
Two repos, two Claude Code sessions, one change that spans both.
The frontend session needs an endpoint the backend has not built. Left alone it
stubs the response, invents a payload shape, and ships code against a contract
nobody agreed to. crosstalk makes it ask the session that owns the backend
instead, and wait for a real answer, with you approving both ends.
Claude Code already delivers messages between local sessions. crosstalk adds
what's missing: a request specific enough to need no follow-ups, a reply shape
the other side can build on, and the rule not to guess while waiting.
## Install
```
claude plugin marketplace add d7omdev/crosstalk
claude plugin install crosstalk@d7omdev
```
Or inside Claude Code: `/plugin marketplace add d7omdev/crosstalk`, then
`/plugin install crosstalk@d7omdev`.
Install it once per machine. Both sessions need it: one side sends, the other
side answers.
## Use
Start `claude` in each repo. They find each other automatically
(`/list-agents` shows who's reachable).
From the repo that needs something:
```
/ask-peer the shifts endpoint needs to accept a status field
```
The command reads your side of the contract (calling file, existing types,
neighbouring routes), drafts a request, shows it to you, and sends on your yes.
The other session summarizes the ask to its user, waits for a yes, does the
work, and replies:
```
DONE POST /api/routes/:id/shifts
files: src/routes/shifts.ts, src/schemas/shift.ts
contract: {status: "active"|"inactive", note?: string} -> 201 {id, status, note}
errors: 409 SHIFT_DUPLICATE, 404 ROUTE_NOT_FOUND
verify: bun test test/shifts.test.ts
deviations from request: none
```
The requesting side then reads the files it named, runs the verify line, and
only then builds against it. `deviations:` is the line that matters: anything
the implementer changed from the ask is listed there, so nothing drifts
silently.
The skills also trigger on their own. Any time a task in one repo depends on a
change in another, the agent is told to ask rather than assume, with or without
the slash command.
## You stay in the loop
- Sending side shows you the request and waits for a yes.
- Receiving side shows its user the ask and waits for a yes.
- If the two agents disagree on the contract, the implementer replies
`PROPOSAL` and the requester brings it to you. Neither side settles it alone.
- If verification fails, one error round-trip goes to the peer, then it
escalates to you.
- Permissions stay per session. A peer cannot ask the other side to do
something its own settings blocked.
## What's inside
```
skills/cross-repo-request/ asking: what to include, how to handle the reply
skills/answering-cross-repo-request/ answering: user gate, pushback, reply shape
commands/ask-peer.md /ask-peer <what you need>
```
No hooks, no MCP server. The transport is Claude Code's own session messaging.
© d7omdev · MIT · davepoon/buildwithclaude