I see, it sounds like \continue is the issue—this command is designed to continue with implementation rather than with a chat, so it switches you into 'tell mode'. I'll try to make that clearer, or to make it better handle chat mode. I can definitely see how it would be confusing.

The model pack shouldn't be resetting, but a potential gotcha is that model settings are version controlled, so if you rewind to a point in the plan before the model settings were changed, you can undo those changes. Any chance that's what happened? It's a bit of a tradeoff since having those settings version controlled can also be useful in various ways.

This feedback is very valuable, so thanks again!

A few differences:

- Plandex is more agentic—it can complete a complex task, updating many files, all in one go.

- Changes are applied to a sandbox by default rather than directly to project files, helping you prevent unintended changes.

- Plandex can automatically find the context it needs in the project.

- Plandex can execute commands (like installing dependencies, running tests, etc.) and auto-debug if they fail.

- Plandex should be more reliable on file edits—it uses an enhanced version of aider's diff-style edit that is resilient to multiple occurrences, but it also has validation, a whole file fallback, and on the cloud service, a custom fast apply model is also added to the mix. Will be publishing benchmarks on this soon.

Email pins are disabled based on a LOCAL_MODE environment variable, which is set in the docker-compose config. I'll take a look.

Thanks, I appreciate the feedback.

> Oddly, in the default mode out of box it does not want to discuss the plan with me but just jumps to implementation.

It should be starting you out in "chat mode". Do you mean that you're prompted to begin implementation at the end of the chat response? You can just choose the 'no' option if that's the case and keep chatting.

Once you're in 'tell mode', you can always switch back to chat mode with the '\chat' command if you don't want anything to be implemented.

> And when it's done writing code it aggressively wants me to decide whether to apply -- there's no option to discuss changes, rewind back to planning, etc. Just "APPLY OR REJECT!!!". Even Ctrl-C does not work! Not what I expected from software focused on planning...

This is just a menu to make the commands you're most likely to need after a set of changes is finished. If you press 'enter', you'll return back to the repl prompt where you can discuss the changes (switch back to chat mode with \chat if you only want to discuss, rather than iterate), or use commands (like \rewind) as needed.

Hi, thanks! Yes, you could either:

- Add that directory to either .gitignore (in a git repo) or a .plandexignore file (which uses gitignore syntax).

- You can switch to a mode where context is not loaded automatically and you choose the files yourself instead (more on this here: https://docs.plandex.ai/core-concepts/autonomy).