Changelog
DM the swarm, pin a project, send several tickets at once
Slack DMs are now a full conversational surface, one message can fan out into up to five runs, and shorthand repo names resolve correctly.
After this entry you'll know that you no longer need a shared channel to work with the swarm. You can now open a direct message with the bot and just talk: ask for work, answer its questions, and say "thanks, done" to close a session, all as normal top-level messages with no threading required. Follow-ups continue the run you were already talking about, and a bare "thanks" never launches anything.
What changes for you
Three things make DMs practical for real work:
- Pin a project. Type
pin <project>in your DM and every request you send there defaults to that project;unpinclears it. Naming a repo explicitly in a message always beats the pin. - Multi-ticket fan-out. One message naming several tickets ("work on SC-1, SC-2 and SC-3") now becomes one independent run per ticket, each with its own budget, status card and pull request, up to five per message. Beyond five you get a polite refusal and nothing is dispatched, so a typo can't launch a wall of runs. Previously only the first ticket was picked up and the rest were silently dropped.
- Smarter project resolution. Shorthand and nicknamed repo names ("firstaid-ios") are now matched against the actual list of projects the swarm knows, instead of failing and asking "which repository?". If no confident match exists it still asks rather than guessing.
This all works in DMs and in channels alike; see working from Slack for the full picture.