Alternatives
Products that do what Patchwork does
Just Tab It
- 1
Xcode 26.3▲326Leverage coding agents to tackle complex tasks autonomously
Feb 2026 · developer.apple.com
- 2
- 3
- 4
- 5
- 6PO
Hi HN! We’re Asankhaya and Rohan and we are building Patchwork. Patchwork tackles development gruntwork—like reviews, docs, linting, and security fixes—through customizable, code-first 'patchflows' using LLMs and modular code management steps, all in Python. Here's a quick overview video: https://youtu.be/MLyn6B3bFMU From our time building DevSecOps tools, we experienced first-hand the frustrations our users faced as they built complex delivery pipelines. Almost a third of developer time is spent on code management tasks[1], yet backlogs remain. Patchwork lets you combine…
2024 · github.com
- 7
Dropstone 3▲206I’ve been trying out Dropstone, a new IDE with a self-learning AI that actually adapts to how you code. Unlike Cursor or Claude, it runs locally, has no token limits, and gets better the more you use it. What impressed me is that it learns from your edits and naming patterns while keeping everything private on your own system. It even explains its reasoning for every suggestion and has quick undo and fallback options that keep you in flow. It genuinely feels like coding with an assistant that remembers you.
Feb 2026 · dropstone.io
- 8
Deep Work Plan▲114Models matter. Context matters more. Give your agent a plan.
Jun 2026 · deepworkplan.com
- 9
- 10
- 112C
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com
- 12
- 13
- 14
- 15
- 16
- 17
AgentGrid▲77Hi HN, I’m Michael, I built AgentGrid with my friend Souren because we were tired of losing our coding sessions and couldn't keep track of what was actually being built across our many projects. Our approach was to use an infinite canvas desktop app for the TUIs we already know and love, mainly claude + codex. We drew inspiration from Figma and Railway. Overtime we added image nodes, notes, terminals, coding editors, source control, etc. I wasn't sure about it at first. It took me a month to give the first version Souren built a real try. What got me was an Apple System Update I've been…
Jul 2026 · agentgrid.sh
- 18CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
- 19PO
Hi HN, We are excited to share patchwork - an open-source CLI for dev chore automation that you can use with your LLM of choice. Dev Teams can orchestrate custom workflows (called ‘patchflows’) using a combination of reusable steps and prompt templates to fix vulnerabilities, upgrade breaking dependencies, generate documentation, and more. We built scanning tools in the past, and saw how overwhelmed developers get with their DevSecOps pipelines. LLMs have the potential to help - but there is a need for an 'outer-loop' solution that can be customized to accommodate the processes, priorities,…
2024 · github.com
- 20RT
Now that AI is capable of writing large volumes of production-quality code, our role as developers is changing. Our primary job is no longer writing code. It’s planning and communicating software design and architecture. We have to do this collaboratively with agents and then review and iterate on their implementations. IDEs were not built for this workflow. So about three months ago I decided to try to build what I thought this new interface should look like. Runner is a coding agent purpose-built for this new “plan and review” workflow. It’s not for vibe coding. It’s for professional…
Sep 2025 · runnercode.com
- 21
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 22
- 23WI
Hi, as the LLM models are getting smarter in coding tasks, we will soon be using agents as co workers, as current tools like github copilot and cursor are not optimized for team collaboration, we began building PhantomX, please give your feedback, if you think we are in the right direction or what should be changed for finding the optimized development workflow which works for both humans and agents.
Jan 2026 · phantomx.dev
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →