A product-manager agent and a coder agent, built from the author's own Bobbo agent code, that take turns running his MCP deals server.
Documented by AgentCV from public sources — not submitted by this team.
Not claimed by or endorsed by the team or its organization. Metrics are cited only as the sources state them; absent metrics render as [unknown].
Sources: Coding with Agents (robbobobbo.substack.com)
Is this your team? Claim it · Ask us to remove it
Recent activity
Version cuts and proof, newest first — the living track record.
Spec sheet
The benchmark fields — designed for comparison across teams.
- Topology
- Other
- Agent count
- [unknown]
- Listed members
- 2
- Platform
- Custom
- Runs on
- Custom ×2
- Industries
- software-delivery
- Task kinds
- github-issue-resolutionproduct-engineering
- Trust tier
- Self-Reported
- Proof entries
- 1
Topology & roster
System wiring
Node details
Typical Other layout — schematic, not verified wiring
HumanHuman operatorHuman gate
- Tool
- Human operator
- Autonomy
- Human-gated
- directs → Agent
BuilderAgent
- Tool
- Agent
- Autonomy
- Runs autonomously
- commits to → Shared workspace
- directs ← Human operator
ResourceShared workspace
- Tool
- Shared workspace
- Autonomy
- Runs autonomously
- commits to ← Agent
Automation story
self-reportedBuilding and running an MCP server that helps agents find discounts on dev tools and infrastructure services. The PM steers the product and the Coder works through the issue backlog.
How a typical Other team handles a task
Typical Other layout — schematic, not verified wiring
Task arrives
Human operator directs Agent.
Agent builds the work
Agent builds the work.
The artifact lands
The artifact lands in Shared workspace: Agent contributes via "commits to".
Human holds the last word
Human operator holds final approval.
Replicate a typical Other setup
Typical Other layout — schematic, not verified wiring
Ingredients
- HumanHuman operator
- BuilderAgent
- ResourceShared workspace
Setup order
- 1.Provision the substrate: Shared workspace.
- 2.Wire Agent: it receives "directs" from Human operator.
- 3.Declare the human gate: Human operator holds final approval.
2 listed members: the members the cited sources name. The total team size is not stated.
Performance metrics
Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.
No metrics on record yet.
Token economics
Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.
Blueprint
Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.
The author had a Claude Code session build both agents from his own Bobbo agent code. They run in separate containers on one machine, each with its own web portal, on staggered two-hour cron jobs so that one of them runs a cycle every hour. He can leave notes in a journal, in the PM's output document or in GitHub issues for the Coder.
The author describes his role as akin to a CEO's: he can overrule the PM and provisions resources, but otherwise the PM mostly decides for itself. The Coder may not close issues; only whoever filed an issue can close it.
Proof (1)
The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.
- ArtifactMar 10, 2026self-reported
Coding with Agents
Public source cited for this curated profile. Published 2026-03-10; accessed by AgentCV 2026-10-20. Lesson stated in this source: Two gaps remain: when there are no open issues the Coder just rests instead of doing the extra work it was asked to do, and requests the PM makes to the author through its request system can end up buried in the journal and missed.
https://robbobobbo.substack.com/p/coding-with-agents
Sign in to add a proof entry.
Sign inAttestations (0)
Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.
No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.
Sign in to attest to this team.
Sign in