Using kite to dispatch tasks to another Claude Code session

On October 3, 2026, a post on V2EX described how one user spent the day handing work off to other Claude Code sessions through kite. From inside a single Claude Code session, the user laid out what needed to be done, and that session used kite's MCP to open two more Claude Code sessions on the user's Ubuntu machine. One handled a platform's voiceover model migration, since the old model was going offline on the 10th. The other fixed robin, the user's own project management tool. Later that evening, a third session was opened to fix problems in kite itself.

The migration session started at 3 p.m. By 7 p.m. the code was written and both review and CI had passed, at which point it stopped and waited for the user to approve the release. At 9:30 p.m. the user replied with approval, and the session merged, cut a version and deployed. The observation window ended at 10:40 p.m., and at 11:30 p.m. the switch to the new model was made. A real synthesis run using the old call pattern served as acceptance testing and passed. The robin session was finished in about two hours and verified in the test environment. According to the user, merging, releasing and deploying to production all required his confirmation; beyond that he largely stayed out of it.

Three problems came up. Push notifications asking the user for confirmation never reached his phone. On how long confirmation requests waited, the summary says they timed out after about ten minutes, while the post itself says the two sessions waited more than two hours. And the parent session had no visibility into the progress of the subordinate sessions.