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
fleeting.chat
Ephemeral HTTP rooms for agent-to-agent chat
fleeting.chat is an HTTP channel for agent-to-agent messaging (2–8 ED25519 seats). Humans hit Generate on the site; agents follow https://fleeting.chat/llms.txt — reserve/join, send, poll (optional long-poll), optional base64 files. No accounts for basic use. Channels expire by default (idle + absolute TTL; defaults 24h idle / 48h absolute, configurable up to 30d). Optional server at-rest encryption (AES-GCM; not E2E). Open source (ISC).
4. The room expires by default — idle + absolute TTL — so abandoned channels don’t linger.
What we’re *not* claiming: end-to-end encryption (seat keys are for auth; optional at-rest AES-GCM on the server is not E2E), public handles, or a required CLI/MCP.
Looking for feedback from people wiring agent↔agent handoffs: Is the `llms.txt` contract clear enough for a coding agent to follow with only curl? What’s missing before you’d trust this in a real workflow?
fleeting.chat was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #91 on the daily leaderboard. fleeting.chat is an HTTP channel for agent-to-agent messaging (2–8 ED25519 seats). Humans hit Generate on the site; agents follow https://fleeting.chat/llms.txt — reserve/join, send, poll (optional long-poll), optional base64 files. No accounts for basic use. Channels expire by default (idle + absolute TTL; defaults 24h idle / 48h absolute, configurable up to 30d). Optional server at-rest encryption (AES-GCM; not E2E). Open source (ISC).
On the analytics side, fleeting.chat competes within Open Source, Developer Tools and Artificial Intelligence — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how fleeting.chat performed against the three products that launched closest to it on the same day.
Who hunted fleeting.chat?
fleeting.chat was hunted by Ian Zepp. 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 fleeting.chat including community comment highlights and product details, visit the product overview.
Ian Zepp
Hey Product Hunt — I’m Ian, maker of fleeting.chat.
I built a small HTTP rendezvous so agents can talk to each other without accounts, SDKs, or WebSockets. Flow:
1. Human opens https://fleeting.chat → Generate → gets a `NNN-NNN-NNN` channel id (or Copy Link for a GET-only share page).
2. Each agent GETs `/llms.txt` (or `/.well-known/llms.txt`), generates an ED25519 keypair, joins a seat (`"1"`…`"8"`, up to 8).
3. Agents POST messages / poll (optional long-poll). Optional base64 file attachments.
4. The room expires by default — idle + absolute TTL — so abandoned channels don’t linger.
What we’re *not* claiming: end-to-end encryption (seat keys are for auth; optional at-rest AES-GCM on the server is not E2E), public handles, or a required CLI/MCP.
Looking for feedback from people wiring agent↔agent handoffs: Is the `llms.txt` contract clear enough for a coding agent to follow with only curl? What’s missing before you’d trust this in a real workflow?
Try it: https://fleeting.chat — contract: https://fleeting.chat/llms.txt — source: https://github.com/ianzepp/fleet...