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
AgentFleet OSS
Every device a ship. One coordinated AI fleet.
Self-hosted orchestrator that turns every device into a ship in a cross-device AI fleet — auto-detects the agent CLIs you already have (Claude Code, Codex, Cursor, Aider, Gemini, Qwen...) and coordinates them across machines, LAN-first with a cloud-relay fallback.
I built AgentFleet because every agent CLI I already use lived on a different machine and none of them knew the others existed. Codex on the laptop, Claude Code on the home server, Cursor on the work box, Aider on a spare NUC.
Most multi-agent frameworks want you to rebuild agents inside their runtime. Remote-access tools just hand one task from device to device. AgentFleet treats each device as a first-class ship and coordinates them into one fleet — LAN-first, cloud relay as fallback.
What's actually measured (reproducible, scripts in the repo):
• 303 tasks/s scheduler throughput; 377 tasks/s at 1000 tasks
• 8 devices × 24 agents, 1000 tasks, a device killed mid-run → 1000/1000 completed, 0 lost. Running tasks migrate back to queued and get re-dispatched.
• Disconnect detection ~1s (was ~35s)
• One scheduling fix: 13 → 414 tasks/s (30×) after removing three O(n²) DB lookups from the dispatch loop
• Real cloud servers: 1 Ubuntu + 2 Windows, real codex/claude CLI, 5/5 completed with zero account login
Honest status: only the Grok adapter is fully stable today; the other ~12 are scaffolds — install/discovery/gateway routing work, direct headless CLI execution still needs per-platform testing. That's exactly where I'd love help.
What feedback would help most: if you run any of these CLIs across more than one machine, tell me what breaks first. Cross-device state is where the real bugs hide, not throughput.
AgentFleet OSS was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #401 on the daily leaderboard. Self-hosted orchestrator that turns every device into a ship in a cross-device AI fleet — auto-detects the agent CLIs you already have (Claude Code, Codex, Cursor, Aider, Gemini, Qwen...) and coordinates them across machines, LAN-first with a cloud-relay fallback.
On the analytics side, AgentFleet OSS competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how AgentFleet OSS performed against the three products that launched closest to it on the same day.
Who hunted AgentFleet OSS?
AgentFleet OSS was hunted by Narkco. 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 AgentFleet OSS including community comment highlights and product details, visit the product overview.
Maker here 👋
I built AgentFleet because every agent CLI I already use lived on a different machine and none of them knew the others existed. Codex on the laptop, Claude Code on the home server, Cursor on the work box, Aider on a spare NUC.
Most multi-agent frameworks want you to rebuild agents inside their runtime. Remote-access tools just hand one task from device to device. AgentFleet treats each device as a first-class ship and coordinates them into one fleet — LAN-first, cloud relay as fallback.
What's actually measured (reproducible, scripts in the repo):
• 303 tasks/s scheduler throughput; 377 tasks/s at 1000 tasks
• 8 devices × 24 agents, 1000 tasks, a device killed mid-run → 1000/1000 completed, 0 lost. Running tasks migrate back to queued and get re-dispatched.
• Disconnect detection ~1s (was ~35s)
• One scheduling fix: 13 → 414 tasks/s (30×) after removing three O(n²) DB lookups from the dispatch loop
• Real cloud servers: 1 Ubuntu + 2 Windows, real codex/claude CLI, 5/5 completed with zero account login
Honest status: only the Grok adapter is fully stable today; the other ~12 are scaffolds — install/discovery/gateway routing work, direct headless CLI execution still needs per-platform testing. That's exactly where I'd love help.
What feedback would help most: if you run any of these CLIs across more than one machine, tell me what breaks first. Cross-device state is where the real bugs hide, not throughput.
Repo: https://github.com/narkco-kang/agent-fleet (MIT, Node v24 + TypeScript)