I built an AI team that ships real work — and shows you the conversation

Description and use

<p>Most "multi-agent" demos are bots narrating to each other. The log is the product; the work is secondary. I wanted the opposite: one request in, real files out, and a trail I could audit afterwards.</p> <p><strong>Agent Team</strong> is an open-source (MIT), local-first runtime where a Master plans, a Researcher / Builder / Reviewer actually do the work, and you get the artifacts <strong>plus</strong> the real bot-to-bot messages, a timeline, and verification bound to each artifact revision.</p> <p>Repo: <a href="https://github.com/FORIFOR/Multibot" rel="noopener noreferrer">https://github.

Problem

<p>Most "multi-agent" demos are bots narrating to each other. The log is the product; the work is secondary. I wanted the opposite: one request in, real files out, and a trail I could audit afterwards.</p> <p><strong>Agent Team</strong> is an open-source (MIT), local-first runtime where a Master plans, a Researcher / Builder / Reviewer actually do the work, and you get the artifacts <strong>plus</strong> the real bot-to-bot messages, a timeline, and verification bound to each artifact revision.</p> <p>Repo: <a href="https://github.com/FORIFOR/Multibot" rel="noopener noreferrer">https://github.

Outcome

<p>Most "multi-agent" demos are bots narrating to each other. The log is the product; the work is secondary. I wanted the opposite: one request in, real files out, and a trail I could audit afterwards.</p> <p><strong>Agent Team</strong> is an open-source (MIT), local-first runtime where a Master plans, a Researcher / Builder / Reviewer actually do the work, and you get the artifacts <strong>plus</strong> the real bot-to-bot messages, a timeline, and verification bound to each artifact revision.</p> <p>Repo: <a href="https://github.com/FORIFOR/Multibot" rel="noopener noreferrer">https://github.

Evidence

I built an AI team that ships real work — and shows you the conversation

Source