Delegating Work Across Multiple AI Sessions

A Dev.to tutorial by Abishaiama documents how Atlarix users can delegate work across multiple AI sessions by running /fork to copy a session with its history intact, then using send_message with a target session name or id to assign a task, optionally setting notify_when_done: true, a mode such as "build", and a model such as "claude-sonnet-5-5". The guide describes forking a feature session twice — one fork building the API half with mode: "build", the other writing tests with mode: "build" and a cheaper model — while integration work continues in the original session. The tutorial notes each session is independent: a delegate does not see what the leader does after the fork, and the leader does not see the delegate's intermediate steps, so context must be passed in the message and results retrieved via list_sessions with result_of.

Delegating Work Across Multiple AI Sessions Fork a session, send it a task, set its mode and model, and get notified when it finishes. Here is how to delegate work across multiple Atlarix sessions — the commands, the workflow, and what to watch for. Start with a session that has context — a plan, some exploration, a partial build. Run /fork t o copy it into a new session. The original is unchanged; the fork has the same history and can continue from there. Now you have two sessions, and you can send one a task while you work in the other. send message with a to the session's name or id and a message the task sends the task to that session. Add notify when done: true to get a notice when it finishes. The target session receives the message as a peer message and starts working on it. send message can also set the target's mode mode: "build" and model model: "claude-sonnet-5-5" . This is useful when you want the delegate to work differently from the leader — a cheaper model for tests, a faster model for exploration, a stronger model for the hard parts. When the delegate finishes, the leader gets a notice if it asked for one . It can also run list sessions with result of to see the delegate's latest turn: how it ended, its reply, and the files it changed. The leader can then review the work, merge it, or send follow-up tasks. You are building a feature with an API and tests. Fork the session twice. Send one fork the API half with mode: "build". Send the other the tests with mode: "build" and a cheaper model. Work on the integration in the original. When both forks finish, read their results and review the changes. Approve the good ones, reject the bad ones, and continue. Each session is independent. A delegate does not see what the leader does after the fork, and the leader does not see the delegate's intermediate steps. If the delegate needs context the leader has, send it in the message. If the leader needs to see the delegate's work, read the results or open the session. Task delegation builds on /fork 15.10 and peer messaging with mode and model control 15.11 . For the review step, see agentic code review. How do I delegate a task to another Atlarix session? Can I set a different model for a delegated task? Yes. send message can set the target's mode and model along with the task. Key Takeaways - •The original is unchanged; the fork has the same history and can continue from there. - •This story was reported by Dev.to , covering developments in the dev space. - •AI advancements continue to reshape industries — read the full article on Dev.to for complete coverage. 📖 Continue reading the full article: Read Full Article on Dev.to → https://dev.to/abishaiama/delegating-work-across-multiple-ai-sessions-32ja