Cosine Swarm

Honestly the parallel angle is what scares me. Every time I've tried coordinating two agents on the same repo they end up stepping on each other's files and I spend the saved time resolving merges. Does Swarm coordinate which files each agent can touch, or is it more of a post-hoc merge thing?

congrats on the launch!

The Orchestrator and Task Owner split is a cleaner hierarchy than I usually see in swarm setups. I am curious how the Orchestrator decides when to fan out versus keep something in a single thread. Is that driven by the task graph it builds up front, or is there a heuristic about codebase scope that triggers parallel branching?

Swarm is such a game changer. We were able to generate a fully-functional, design system-aligned mobile version of our website with a single swarm and prompt. It even included tests!

The orchestrator/task owner/worker hierarchy is a smart decomposition for parallel agent work. Most multi-agent coding setups I have tried fall apart when two subagents touch the same files. Curious how Cosine handles merge conflicts between parallel workers. Does the orchestrator prevent overlapping file edits upfront, or is there a resolution layer that reconciles after the fact?

Such an exciting release. I’ve been loving using Swarm mode. As someone working in ops, it’s been a game changer for my workflow - helping with research, project planning, spreadsheet analysis, reporting, and turning messy information into clear outputs I can actually use. It’s also been great for hobby projects too. I even used it to build an interactive intro-to-coding app! Really excited for more people to try it 😊

Swarm has expanded my workflow so much. I can start up multiple swarms to tackle seriously big new features, additions or tackle tough bugs. I just have to check out the branch afterwards, give it a quick once over, and it's done.If ever a mono-agent is failing you just kick it into swarm mode, trust me

Swarm has been pretty fantastic so far. It's been quite a nice workflow to just hand over a large task, let it work through it, come back later and review what it did.I can finally feel my backlog of tasks and experiments start to clear... Well, it's got a higher throughput at least. Theres always another idea to experiment with

I cant tell you how nuts this feature is.Here was my workflow previously:get on the trainstart 5 tasksget to work and debug the code for each and iterate back and forth, taking up most of my time for the dayget the 5 tasks in by EODHere's my workflow now:get on the trainstart 5 swarmsget to work, start 5 morecome back to each, find that everything already works (because all the code has already been thoroughly reviewed, QA'ed and iterated on)keep merging them and starting more throughout the dayget praised for how much work im getting doneprofitEOD ive merged 10-15 featuresIts genuinely changing the game, this is what AI coding has been promising to be for so long and it finally is

This is huge. Biggest problem I have with AI coding is context rot. Problem is too big to digest and AI just starts making sh*t up.Cosine has give the AI the ability to go from coder to Tech Team HR, spinning up a whole org chart to make big problems easy to digest.Congrats!

Congrats on the relaunch, Yang.The orchestrator/task owner/worker hierarchy makes sense on paper. It mirrors how real engineering teams divide work. The hard question is whether the coordination overhead between agents stays manageable on genuinely messy, real-world codebases, or whether complex tasks still quietly derail in ways that only surface at review time."Assign tasks in the evening, find PRs ready by morning" is a bold promise. What's the failure mode when it goes wrong? Does Cosine surface a clean explanation of where it got stuck, or do you end up debugging the agent's decisions as much as the code itself?

Hey Product Hunt! 👋I’m Yang, co-founder of Cosine (cosine.sh), along with @alistair_pullen. We’re excited to introduce Cosine Swarm!For the past year, we’ve seen AI coding move from simple autocomplete to bounded task agents. At Cosine, we believe that the system surrounding the model intelligence has become increasingly important.💡What is Cosine?Cosine is an AI software engineering agent that works across every surface developers use. Instead of stitching together separate AI tools for the terminal, editor, desktop, and remote execution, Cosine gives you one shared runtime across all of them.You can start in the CLI, coordinate through the desktop app, and scale tasks in the cloud without changing products or workflows.👾 Unleash the SwarmCosine Swarm lets a single prompt launch parallel subagents for research, exploration, implementation, QA, and coordination. Each subagent works in its own isolated context, with its own tools and trajectory, so complex work can branch safely, stay reviewable, and move faster without turning into chaos.Instead of a single-agent thread straining under the weight of multiple tasks, Swarm mode creates a coordinated hierarchy. An Orchestrator breaks down goals, Task Owners manage workstreams, and Workers execute tactical changes in parallel. Assign complex tasks in the evening and find them completed, tested, and ready for review by the morning.🖥️ Available now across our entire ecosystemI’m incredibly proud of our team for this release. We built Cosine to feel less like a collection of disconnected agent experiences and more like a real system for AI-native software engineering.Swarm mode is available now across CLI, Desktop, and the Cloud.We’re looking for feedback from developers and teams working across large codebases, multiple tools, and complex workflows – especially anyone who wants more control, better collaboration, and a coding agent that scales beyond a single interface.🎁 Grab 1 month of FREE access to our Hobby tier using the code above. 20M tokens to swarm with.→ Get started with Cosine: cosine.sh→ Read the docs: cosine.sh/docsI'll be in the thread all day answering questions!