This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Agent Tunnels
Agent collaboration between companies
Agent Tunnels puts a customer's coding agent and a vendor's support agent in one shared session. They can exchange context, ask questions, and suggest fixes while both people watch. The vendor agent cannot edit the customer's code. Free to use.
Hi Product Hunt. I built Agent Tunnels because I kept seeing the same awkward support workflow.
A customer hits an integration error in Claude Code, Cursor, or Codex and pastes the output into Slack. Someone on the vendor side copies it into another agent, gets a possible fix, and pastes that back. Both sides have agents, but the agents cannot talk.
Agent Tunnels puts both agents in one temporary session. The customer's agent brings repo context and error history. The vendor's agent brings product knowledge and known fixes. Both people can watch. The vendor agent cannot edit the customer's code.
Agent Tunnels is free. I am testing one thing: do developer-tool teams care enough about this problem to create a tunnel and invite a customer or vendor?
If this workflow is familiar, tell me how you handle it today. You can also create a tunnel and tell me where it breaks.
About Agent Tunnels on Product Hunt
“Agent collaboration between companies”
Agent Tunnels was submitted on Product Hunt and earned 5 upvotes and 1 comments, placing #73 on the daily leaderboard. Agent Tunnels puts a customer's coding agent and a vendor's support agent in one shared session. They can exchange context, ask questions, and suggest fixes while both people watch. The vendor agent cannot edit the customer's code. Free to use.
On the analytics side, Agent Tunnels competes within Developer Tools and Artificial Intelligence — topics that collectively have 993.3k followers on Product Hunt. The dashboard above tracks how Agent Tunnels performed against the three products that launched closest to it on the same day.
Who hunted Agent Tunnels?
Agent Tunnels was hunted by Lakshman Mody. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Agent Tunnels including community comment highlights and product details, visit the product overview.
Lakshman Mody
Hi Product Hunt. I built Agent Tunnels because I kept seeing the same awkward support workflow.
A customer hits an integration error in Claude Code, Cursor, or Codex and pastes the output into Slack. Someone on the vendor side copies it into another agent, gets a possible fix, and pastes that back. Both sides have agents, but the agents cannot talk.
Agent Tunnels puts both agents in one temporary session. The customer's agent brings repo context and error history. The vendor's agent brings product knowledge and known fixes. Both people can watch. The vendor agent cannot edit the customer's code.
Agent Tunnels is free. I am testing one thing: do developer-tool teams care enough about this problem to create a tunnel and invite a customer or vendor?
If this workflow is familiar, tell me how you handle it today. You can also create a tunnel and tell me where it breaks.