You mention in the README these tools operate at different layers and are complementary rather than competing — this is one of those.
AgentGit handles the step after task assignment: branch isolation per task, then a deterministic validation script (real exit code, not an agent's report) before an automated merge. It's git-only, no server/DB — different tradeoff than swarm-protocol's Postgres-backed MCP approach, which is why I think it's complementary rather than overlapping.
Not asking for an adapter or integration right now, just flagging it in case it's useful context for where the "what's missing" list goes next. Repo: https://github.com/Tryboy869/AgentGit (MIT, pre-alpha).
You mention in the README these tools operate at different layers and are complementary rather than competing — this is one of those.
AgentGit handles the step after task assignment: branch isolation per task, then a deterministic validation script (real exit code, not an agent's report) before an automated merge. It's git-only, no server/DB — different tradeoff than swarm-protocol's Postgres-backed MCP approach, which is why I think it's complementary rather than overlapping.
Not asking for an adapter or integration right now, just flagging it in case it's useful context for where the "what's missing" list goes next. Repo: https://github.com/Tryboy869/AgentGit (MIT, pre-alpha).