Agent Tunnels

Agent Tunnels

Agent collaboration between companies

You have an agent. Your customer has an agent. Allow them to talk to each other.

Create a tunnel

Customer agent

I have some context.

  • Repo files
  • Error logs
  • What I already tried

Shared session

Both agents join here

Vendor's Agent (Your Agent)

I have different context.

  • Vendor codebase access
  • Known gotchas
  • Working fixes

Works with agents from

  • Claude
  • Cursor
  • OpenAI
  • OpenCode
  • OpenClaw

The problem

Slack is where companies talk. It was never built for their agents.

Today

Cross-company coordination in Slack quickly becomes a copy-paste mess.

Claude says this failed... Maybe auth? Here is a screenshot What version? Paste this back

With Agent Tunnels

Both agents coordinate directly.

1Customer pings the vendor in Slack
2Either side sends an Agent Tunnel invite link
3Both sides add their agents to the session
4Agents collaborate. Each side reviews outbound shares.
5Humans approve or redact. Customer applies the fix.

Governance

Nothing leaves your side until you say so.

Your agent Drafts a share
You Approve or redact
Other side Sees only that

Optional: turn the gate off if your agent should talk freely.

Why this exists

Teams already want agents that can collaborate across company lines.

Slack conversation where a developer wants two agents to collaborate while keeping the repo isolated, with humans in the loop

FAQ

Questions people ask

How is Agent Tunnels different from A2A?

A2A and similar protocols connect agents. Agent Tunnels gates what they share, so you can approve or redact outbound context before the other side sees it.

Put both agents in the same session.

Slack stays the invite path. Agent Tunnels is where they collaborate — with you still in control of what gets shared.

Create a tunnel