Загрузка видео...

Не удалось загрузить видео

На главную

An open-source, self-hostable layer that turns your agents into a team working toward shared goals. It's called Rowboat, and it can bring Claude Code, Codex, and Hermes into one team. Any agent that supports MCP can join too, so you stop being the glue between your AI agents. You...

10,198 просмотров • 3 дней назад •via X (Twitter)

Комментарии: 29

Фото профиля Akshay 🚀
Akshay 🚀3 дней назад

Rowboat GitHub: (don't forget to star 🌟)

Фото профиля Luca Iaconelli
Luca Iaconelli3 дней назад

All the projects at my software house run on Codex with Opus coordinating, so Claude and Codex in one team is already my everyday setup

Фото профиля Emly
Emly3 дней назад

This sounds like a powerful tool for AI agent collaboration.

Фото профиля Jay Song
Jay Song3 дней назад

we kept one agent as the glue on purpose: workers report only to it, never to each other

Фото профиля Nash
Nash3 дней назад

Being the glue between agents is real, but the messy part is two of them editing the same file. Does Rowboat lock work or just let them merge after?

Фото профиля Niv Asayag · YardCrew
Niv Asayag · YardCrew3 дней назад

Shared goals are the easy part. Two agents editing the same files at once is where agent teams break.

Фото профиля SingIt
SingIt3 дней назад

For a Rowboat team buying API access, give the whole task a shared spending cap. Separate agent allowances can add up even when every agent stays within its own limit.

Фото профиля Mohammad Vazin
Mohammad Vazin3 дней назад

Before I'd let several agents share goals, I'd want to know who holds the credentials. If every MCP agent on the team calls the same tools with the same token, one bad prompt reaches all of them.

Фото профиля Amir | Unreached
Amir | Unreached3 дней назад

being the glue between agents is not the career i was promised

Фото профиля Boyd
Boyd3 дней назад

This is interesting. I've been having GrokBot use Cursor sessions to do similar but this is much more visible in one place. I'll have to give it a try.

Фото профиля AI Ferryman Alex
AI Ferryman Alex3 дней назад

Joining agents into one team is the easy demo — the hard part isn't the joining, it's shared state. When two agents disagree on the same file, who wins, and who tells the user?

Фото профиля Hailu 🍏
Hailu 🍏3 дней назад

This is a clever solution for agent collaboration.

Фото профиля Gunars Mie
Gunars Mie3 дней назад

i run about 10 bots on one shared box. handoffs were never teh hard part tbh, hard budgets per bot were. without them they just loop

Фото профиля verbal72.exe
verbal72.exe3 дней назад

Shared goals is where ours slipped. Our reply runs each looked fine alone, but across six days they answered one account 10 times. No single agent saw it; only reading all the logs together did. Does Rowboat give the team one shared log, or just pass messages?

Фото профиля SunsetSyntax
SunsetSyntax3 дней назад

On the two-agents-one-file questions: Harbor doesn't lock. Each edit is proposed against a base version and merged line by line, three-way. Clean edits merge, same-line edits come back as a conflict with the current content so the agent retries, and every change is attributed.

Фото профиля Hamza 🌙
Hamza 🌙3 дней назад

Nice work on Rowboat! Seeing each handoff and being able to step in makes coordinating a team of agents feel much more manageable.

Фото профиля Ashish Khandelwal
Ashish Khandelwal3 дней назад

Finally. I've been the human copy-paste between my agents for way too long.

Фото профиля Daniel Zambrini
Daniel Zambrini3 дней назад

Open source and self-hosted, love that combo

Фото профиля Raúl Nogales 🇪🇸🇺🇸
Raúl Nogales 🇪🇸🇺🇸3 дней назад

The super agent is the real product here, not the individual agents. Deciding which agents a job needs, asking permission to create them and passing work along in threads only works if failures are visible and recoverable. The audit trail of every handoff is what will earn trust.

Фото профиля ಪಬ್‌ಸಬ್ ಲಾಗ್
ಪಬ್‌ಸಬ್ ಲಾಗ್1 день назад

MCP as the join point is the right call. but one question: who owns the shared state? if two agents write the same file the team gets messy fast.

Фото профиля ವಾಚರ್ ವರ್ಕ್‌ಶಾಪ್
ವಾಚರ್ ವರ್ಕ್‌ಶಾಪ್2 дней назад

open-source and self-hostable is the right call. the question is where run state lives when two agents touch the same goal. MCP gives you handoff, not coordination.

Фото профиля The SI Maximalist
The SI Maximalist3 дней назад

Choosing my own mix of agents and hosting the team myself is a very tempting pitch

Фото профиля Max Petrusenko
Max Petrusenko3 дней назад

a handoff breaks when a worker makes a change, then crashes before marking the task done. a retry can make that change twice.

Фото профиля Agentik
Agentik3 дней назад

what happens when two of them want the same file, does rowboat lock it or do they just fight it out

Фото профиля xelA31B
xelA31B3 дней назад

an agent that hires agents. middle management finally got automated

Фото профиля NaLi
NaLi3 дней назад

This is a fascinating concept for AI agent collaboration.

Фото профиля Nathan Esquenazi
Nathan Esquenazi3 дней назад

Looks great! I’m curious what folks think of an adjacent approach I open sourced just recently called agent-mailbox - a universal secure protocol for agents across all vendors and harnesses to communicate Feedback welcome!

Фото профиля Vesper🪐
Vesper🪐3 дней назад

This sounds like a game-changer for agent collaboration.

Фото профиля ಲೂಪ್ ಮ್ಯಾಪ್
ಲೂಪ್ ಮ್ಯಾಪ್3 дней назад

MCP as the join key is the right call. but 'stop being the glue' is the claim I'd want tested — retries, partial failures, and who owns the state between agents? show me the loop closing end to end and I'm in.

Похожие видео

Another insane Jev use case! Jev makes it incredibly cheap to evaluate and classify agent runs at scale. And finally, someone open-sourced a self-improving memory layer that can put that capability to work across agent harnesses. It turns your agent sessions into a compounding knowledge layer, where every successful run can make future agents smarter across: - Codex - Claude Code - Cursor - OpenCode and 20+ more Beacon by Asymptote Labs continuously builds a shared history across your agent harnesses and uses Jev to identify the runs worth learning from. It then turns the best workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐) Most agent runs are messy. They contain exploration, failed commands, dead ends, and one-off fixes that should never become permanent memory. So Beacon preserves the full session history, while Jev helps decide what should be promoted, reviewed, or discarded. The recording below shows this in action. Beacon found 579 sessions across 5 coding-agent harnesses and normalized them into one consistent history. From there, Jev surfaces the lessons worth keeping and makes them available across your agent stack. - A pattern learned in Cursor can carry into OpenCode. - A lesson from Claude Code can improve the next Codex run. Every successful run adds to the shared knowledge layer, making future agents smarter. If you want to dive deeper into Jev, I also wrote a breakdown of how it works. The article is quoted below.

Akshay 🚀

121,206 просмотров • 1 месяц назад

this is pure f*cking treasure 10 GitHub repos with 165K+ combined stars to build your own AI agent team that works 24/7 most people still use one AI chat for everything. these repos turn Claude into a whole team: one agent researches, one codes, one reviews, and a lead runs them all one resource per step, from your first 3 agents to a full swarm running Claude and Codex together (1/10) CrewAI the easiest way to assemble a team of agents: give them roles and tasks, then hit kickoff ▸ (2/10) LangGraph connect agents into a graph with checkpoints, so if something fails it resumes instead of starting over ▸ (3/10) wshobson/agents ready-made agents for Claude Code (backend, frontend, security, tests, devops) plus an orchestrator to run them ▸ (4/10) oh-my-team 12 specialist agents for Claude Code that split the work and merge the results ▸ (5/10) agent-swarm your own self-hosted AI company: one lead agent hires workers and runs them 24/7 ▸ (6/10) Open-Agents spawns many Claude agents in parallel, so 6 tasks run at once instead of one after another ▸ (7/10) swarms an enterprise-grade framework for when your team grows from 5 agents to 50 ▸ (8/10) Microsoft Agent Framework Microsoft's new framework, the AutoGen successor, for workflows, agents and runtime in one place ▸ (9/10) CLI Agent Orchestrator runs Claude, Codex and other CLIs side by side as one team, with a supervisor watching all of them ▸ (10/10) ensemble launches Codex and Claude together, so they build and ship as one ▸ the loop: assemble → plug in → run → scale → orchestrate pick one, click, let it run, and while everyone else is still typing prompts, your agents are already shipping ↓

Noisy

15,433 просмотров • 1 месяц назад