I got a lot of questions on how updated agent orchestration works in Row-Bot. Here is the architecture.

Row-Bot can now take on bigger jobs by splitting the work across multiple agents, while keeping one agent responsible for the final result.

Research, coding, and review can all happen at the same time. If one part fails, you can retry or stop it without losing the rest of the work. And if Row-Bot restarts halfway through, it can pick up from its saved state instead of starting over.

The parent agent stays in charge throughout. It plans the job, delegates tasks in parallel or in the right order, waits for the results it needs, and brings everything together into one final response.

Each child agent can have its own model, context, tools, permissions, and workspace. Read-only agents can research safely, while agents that edit files use writer locks or isolated Git worktrees to prevent conflicts.

Essential tasks must finish before the final response is delivered. Background work can continue without holding everything up. Runs, events, approvals, checkpoints, and delivery state are all stored locally, with sensible limits on concurrency and resource use.

It’s multi-agent collaboration without losing control of the task.

https://github.com/siddsachar/row-bot