Conductor almost shut down. Eight days that made me check my own setup
Conductor announced its wind-down and reversed it eight days later. I wrote down what I keep under my own control, and how I run parallel agents in Splitkick.
On 4 November Conductor announced that it would join Meta and wind down. On 12 November the team took that back: development goes on. Congratulations to everyone who uses it. That is good news.
I build Splitkick, a free and open-source Mac app for running many AI agent sessions at once. So I am not neutral, and I am not asking anyone to switch. But for eight days a lot of developers had to plan a move they did not choose. That made me ask three questions about my own setup:
Where is my session history, and who controls it? Do my agents depend on the tool, or do they only run inside it? Could I keep the tool running myself if the company changed course?
The one idea to take away: a session holds the reasons behind your code. The dead ends, the decisions, the command that finally worked. Keep that history as files on your own disk, in a folder you back up. Then a vendor's change of plan costs you at most a window, and your agents, logins and history stay with you.
In the article I also show what Conductor gets right, one git worktree per task, and how I run parallel agents in Splitkick step by step, up to answering them from my phone.
