HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
plandex-ai
plandex
Go2024–2025
plandex-ai / plandex

plandex

Open source AI coding agent. Designed for large projects and real world tasks.

6Distinct people
63Mentions
0Explicit recommenders
15.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open source AI coding agent. Designed for large projects and real world tasks.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month63 dated mentions

Observed mentions: 2024-03-31 18:28:20 UTC to 2025-09-26 15:26:11 UTC.

051015202024-03-01 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsMar 20242024-04-01 00:00:00 UTC to 2024-05-01 00:00:00 UTC (exclusive): 21 mentions; 1 submissions, 20 comments2024-05-01 00:00:00 UTC to 2024-06-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2024-06-01 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2024-07-01 00:00:00 UTC to 2024-08-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2024-08-01 00:00:00 UTC to 2024-09-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-09-01 00:00:00 UTC to 2024-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-01 00:00:00 UTC to 2024-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-11-01 00:00:00 UTC to 2024-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 20242025-01-01 00:00:00 UTC to 2025-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-01 00:00:00 UTC to 2025-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-01 00:00:00 UTC to 2025-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 20242024-03-01 00:00:00 UTC2024-04-01 00:00:00 UTC202
Apr 20242024-04-01 00:00:00 UTC2024-05-01 00:00:00 UTC21120
May 20242024-05-01 00:00:00 UTC2024-06-01 00:00:00 UTC716
Jun 20242024-06-01 00:00:00 UTC2024-07-01 00:00:00 UTC312
Jul 20242024-07-01 00:00:00 UTC2024-08-01 00:00:00 UTC211
Aug 20242024-08-01 00:00:00 UTC2024-09-01 00:00:00 UTC303
Sep 20242024-09-01 00:00:00 UTC2024-10-01 00:00:00 UTC000
Oct 20242024-10-01 00:00:00 UTC2024-11-01 00:00:00 UTC000
Nov 20242024-11-01 00:00:00 UTC2024-12-01 00:00:00 UTC000
Dec 20242024-12-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
Jan 20252025-01-01 00:00:00 UTC2025-02-01 00:00:00 UTC000
Feb 20252025-02-01 00:00:00 UTC2025-03-01 00:00:00 UTC000
Mar 20252025-03-01 00:00:00 UTC2025-04-01 00:00:00 UTC101
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC927
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC11011
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC101
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC202
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC000
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC101

What Hacker News says

9 sources
A few concrete examples of multi-agent collaboration being useful in my project Plandex[1]: - While it uses Sonnet 3.7 by default for creating the edit snippet when writing code, calls related to applying the snippet and validating the result (and falling back to a whole file write if needed) use o3-mini (soon to be o4-mini) which is 1/3 the cost, much faster, and actually more accurate and reliable than Sonnet for this particular narrow task. - If Sonnet 3.7's context limit is exceeded in the planning stages, it can switch to a Gemini model for planning, then go back to Sonnet again for the implementation steps (since these only need the files relevant to each step). - It eagerly summarizes the conversation after each response so that the summary can be used later if the conversation gets too long. This is only practical because much sma
Read the rest
ller models than the main planning/coding models are sufficient for a good summary. Otherwise it would be way too expensive. It's definitely more complex, but I think in these cases at least, there's a real payoff for the trouble. 1 - https://github.com/plandex-ai/plandex
In Show HN: Rowboat – Open-source IDE for multi-agent systems
I built Plandex[1] to try to enable a more sustainable approach to vibe coding. It writes all of the model's changes to a cumulative version-controlled sandbox by default, which in my experience helps a lot to address many of the points raised in the article. While there are still categories of tasks I'd rather do myself than vibe code, the default-sandbox approach makes it feel a lot less risky to give something a shot. On another note, a related but somewhat different technique that I think is still under-appreciated is "vibe debugging", i.e. repeatedly executing commands (builds, tests, typechecks, dependency installs, etc.) until they run successfully. This helps a lot with what imo are some of the most tedious tasks in software development—stuff like getting your webpack server to startup correctly, getting a big C project to compile
Read the rest
for the first time, fixing random dependency installation errors, getting your CloudFormation template to deploy without errors, and so on. It's not so much that these tasks are 'difficult' really. They just require a lot of trial-and-error and have a slow feedback loop, which makes them naturally a good fit for AI. I put a lot of focus on execution control in Plandex in order to make it helpful for these kinds of problems. It's built to be transactional—you can apply the changes from the sandbox, run pending commands, and then roll back all changes if the commands fail. You can do this repeatedly, even letting it continue automatically for some number of tries until the commands succeed (or you hit the tries limit). While there are some limitations to the terminal modality in terms of UX, I think this is an area where a CLI-based agent can really shine. 1 - https://github.com/plandex-ai/plandex
In Vibe Coding is not an excuse for low-quality work
There's Aider, Plandex and Goose, all of which let you chose various providers and models. Aider also has a well known benchmark[0] that you can check out to help select models. - Aider - https://aider.chat/ | https://github.com/Aider-AI/aider - Plandex - https://plandex.ai/ | https://github.com/plandex-ai/plandex - Goose - https://block.github.io/goose/ | https://github.com/block/goose [0] https://aider.chat/docs/leaderboards/
In Claude Code: Best practices for agentic coding
danenania·Apr 16, 2025Submission

Show HN: Plandex v2 – open source AI coding agent for large projects and tasks

Hey HN! I’m Dane, the creator of Plandex (https://github.com/plandex-ai/plandex), an open source AI coding agent focused especially on tackling large tasks in real world software projects. You can watch a 2 minute demo of Plandex in action here: https://www.youtube.com/watch?v=SFSu2vNmlLk And here’s more of a tutorial style demo showing how Plandex can automatically debug a browser application: https://www.youtube.com/watch?v=g-_76U_nK0Y. I launched Plandex v1 here on HN a little less than a year ago (https://news.ycombinator.com/item?id=39918500). Now I’m launching a major update, Plandex v2, which is the result of 8 months of heads down work, and is in effect a whole new project/product. In short, Plandex is now a top-tier coding agent with fully autonomous capabilities. It combines models from Anthropic, OpenAI, and Google to achieve b
Read the rest
etter results, more reliable agent behavior, better cost efficiency, and better performance than is possible by using only a single provider’s models. I believe it is now one of the best tools available for working on large tasks in real world codebases with AI. It has an effective context window of 2M tokens, and can index projects of 20M tokens and beyond using tree-sitter project maps (30+ languages are supported). It can effectively find relevant context in massive million-line projects like SQLite, Redis, and Git. A bit more on some of Plandex’s key features: - Plandex has a built-in diff review sandbox that helps you get the benefits of AI without leaving behind a mess in your project. By default, all changes accumulate in the sandbox until you approve them. The sandbox is version-controlled. You can rewind it to any previous point, and you can also create branches to try out alternative approaches. - It offers a ‘full auto mode’ that can complete large tasks autonomously end-to-end, including high level planning, context loading, detailed planning, implementation, command execution (for dependencies, builds, tests, etc.), and debugging. - The autonomy level is highly configurable. You can move up and down the ladder of autonomy depending on the task, your comfort level, and how you weigh cost optimization vs. effort and results. - Models and model settings are also very configurable. There are built-in models and model packs for different use cases. You can also add custom models and model packs, and customize model settings like temperature or top-p. All model changes are version controlled, so you can use branches to try out the same task with different models. The newly released OpenAI models and the paid Gemini 2.5 Pro model will be integrated in the default model pack soon. - It can be easily self-hosted, including a ‘local mode’ for a very fast local single-user setup with Docker. - Cloud hosting is also available for added convenience with a couple of subscription tiers: an ‘Integrated Models’ mode that requires no other accounts or API keys and allows you to manage billing/budgeting/spending alerts and track usage centrally, and a ‘BYO API Key’ mode that allows you to use your own OpenAI/OpenRouter accounts. I’d love to get more HNers in the Plandex Discord (https://discord.gg/plandex-ai). Please join and say hi! And of course I’d love to hear your feedback, whether positive or negative. Thanks so much!
257 points · Open discussion
Cool to see more interesting terminal based options! Looking forward to trying this out. I've been working on something related—Plandex[1], an open source AI coding agent that is particularly focused on large projects and complex tasks. I launched the v2 a few weeks ago and it is now running well. In terms of how to place it in the landscape, it’s more agentic than aider, more configurable and tightly controlled than Devin, and more provider-agnostic/multi-provider/open source than Claude Code or this new competitor from OpenAI. I’m still working on getting the very latest models integrated. Gemini Pro 2.5 and these new OpenAI models will be integrated into the defaults by the end of the week I hope. Current default model pack is a mix of Sonnet 3.7, o3-mini with various levels of reasoning effort, and Gemini 1.5 Pro for large context pla
Read the rest
nning. Currently by default, it supports 2M tokens of context directly and can index and work with massive projects of 20M tokens and beyond. Very interested to hear HN’s thoughts and feedback if anyone wants to try it. I'd also welcome honest comparisons to alternatives, including Codex CLI. I’m planning a Show HN within the next few days. 1 - https://github.com/plandex-ai/plandex
In OpenAI Codex CLI: Lightweight coding agent that runs in your terminal
Plandex[1] uses a similar “wasteful” approach for file edits (note: I’m the creator). It orchestrates a race between diff-style replacements plus validation, writing the whole file with edits incorporated, and (on the cloud service) a specialized model plus validation. While it sounds wasteful, the calls are all very cheap since most of the input tokens are cached, and once a valid result is achieved, other in-flight requests are cancelled. It’s working quite well, allowing for quick results on easy edits with fallbacks for more complex changes/large files that don’t feel incredibly slow. 1 - https://github.com/plandex-ai/plandex
In Wasting Inferences with Aider
danenania·Apr 3, 2025Submission

Show HN: Plandex v2 – OSS AI coding agent w/ diff sandbox, full auto, 2M context

Hey HN! I’m Dane, the creator of Plandex (https://github.com/plandex-ai/plandex), an open source AI coding agent focused especially on tackling large tasks in real world software projects. You can watch a 2 minute demo of Plandex in action here: https://www.youtube.com/watch?v=SFSu2vNmlLk And here’s more of a tutorial style demo showing how Plandex can automatically debug a browser app: https://www.youtube.com/watch?v=VCegxOCAPq0 I launched Plandex v1 here on HN a little less than a year ago (https://news.ycombinator.com/item?id=39918500). It got a positive reception overall (plus some skepticism, which is fair enough), and a lot of early users and contributors. HNers helped to push it to the top repo on GitHub trending, where it remained for a few days, racking up over 8k stars. Now I’m launching a major update, Plandex v2, which is the
Read the rest
result of 8 months of heads down work, and is in effect a whole new project/product. In short, Plandex is now a top-tier coding agent with fully autonomous capabilities. It combines models from Anthropic, OpenAI, and Google to achieve better results, more reliable agent behavior, better cost efficiency, and better performance than is possible by using only a single provider’s models. I believe it is now one of the best tools available for working on large tasks in real world codebases with AI. It has an effective context window of 2M tokens, and can index projects of 20M tokens and beyond using tree-sitter project maps (30+ languages are supported). It can effectively find relevant context in massive million-line projects like SQLite, Redis, and Git. There are also some major UX improvements. Plandex v1 offered just a git-like CLI interface. You’d send prompts via the `plandex tell` command, either passing a string, a prompt file path, or popping up vim/nano. While that CLI interface still exists, there’s now a much more intuitive chat-like REPL experience that gives you fuzzy autocomplete for commands and file paths. This is the new default/recommended way to use Plandex, though having the CLI interface available is also useful for scripting, or for piping in context/prompts from other commands. A bit more on some of Plandex’s key features: - Plandex has a built-in diff review sandbox that helps you get the benefits of AI without leaving behind a mess in your project. By default, all changes accumulate in the sandbox until you approve them. The sandbox is version-controlled. You can rewind it to any previous point, and you can also create branches to try out alternative approaches. - It offers a ‘full auto mode’ that can complete large tasks autonomously end-to-end, including high level planning, context loading, detailed planning, implementation, command execution (for dependencies, builds, tests, etc.), and debugging. - The autonomy level is highly configurable. You can move up and down the ladder of autonomy depending on the task, your comfort level, and how you weigh cost optimization vs. effort and results. The default autonomy level is ‘semi-auto’, which loads context automatically, but requires your approval before applying changes to your project and executing commands. - Models and model settings are also very configurable. There are built-in models and model packs for different use cases, including `daily-driver` (the default pack), `reasoning` (to use Claude 3.7 thinking in place of plain 3.7), `strong` (for the toughest tasks where extra cost and latency are acceptable), `cheap` (for smaller tasks), and `oss` (for an all open source pack, which currently leans strongly on DeepSeek R1/V3), and `gemini-exp` for a pack fronted by Gemini 2.5 pro. You can also add custom models and model packs, and customize model settings like temperature or top-p. All model changes are version controlled, so you can use branches to try out the same task with different models. - It can be easily self-hosted, including a ‘local mode’ for a very fast local single-user setup with Docker. Self-hosting requires OpenAI and OpenRouter.ai accounts/api keys. - Cloud hosting is also available for added convenience with a couple of subscription tiers: an ‘Integrated Models’ mode that requires no other accounts or API keys and allows you to manage billing/budgeting/spending alerts and track usage centrally, and a ‘BYO API Key’ mode that allows you to use your own OpenAI/OpenRouter accounts. I’m having a blast building Plandex. The more I improve it, the faster I can add features to Plandex itself, which is a great motivator! I have a long list of feature ideas that I think can make a big impact, and I’m also working on building a sustainable and successful company around Plandex so that both the product side and the open source project side can continue to grow and support each other’s growth. On that note, if you’re interested in working on Plandex in some capacity, either as a contributor or for pay, please either jump into the repo (here’s a development guide - https://docs.plandex.ai/development) or get in touch (via email - dane@plandex.ai)—while I’m not hiring at the moment, I hope to start before too long and would love to connect with talented folks who might be interested in joining me in the future. I’d also love to get more HNers in the Plandex Discord (https://discord.gg/plandex-ai). Please join and say hi! And of course I’d love to hear your feedback, whether positive or negative. Thanks so much!
4 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.