plandex looks very exciting but has some blockers

[ahundt]

Hey, I looked into plandex and found a lot to be excited about based on the description and some of the demos, in particular I liked that:

1. It records the history of what the agent does in git
2. it supports worktrees for development of different components
3. well organized workflow and good descriptions of what is happening
4. sandboxing is important to reduce the chance of wrecking someone's computer

but once I dug a bit deeper I found a few critical blockers:

1. can't run multiple parallel agents simultaneously
2. history is actually a hand-spun setup
3. can't use my regular tools to check how things are going
4. doesn't appear to be set up for multi-repo projects
5. Not sure how it is possible to track how things are going.

Some things that could help address some of the blockers are:

1. switch the .plandex to contain just another git repository
2. git has api hooks that can help with this to record all the ai history and
3. potentially either the .plandex repo can track main repo versions too, or let the main repo store git history if the user wants.
4. at least let the main repo be a different subdir from the plandex cwd (and document that if it is already possible)

Feel free to do or not do these things, this looks a cool project and I just wanted to provide some suggestions for more parallel workflows, thanks for listening.

[taqtiqa-mark]

@ahundt some pointers that might help, and that you might have feedback on:

Hey, I looked into plandex and found a lot to be excited about based on the description and some of the demos, in particular I liked that:

4. sandboxing is important to reduce the chance of wrecking someone's computer

This can be further improved by using shims that run Plandex containerized: See #298

but once I dug a bit deeper I found a few critical blockers:

1. can't run multiple parallel agents simultaneously

If you copy a pdx containerized shim script into a project folder they can be run in parallel across different projects.
If you want parallel runs in one project, you'd need the shim script to accept an argument allowing for multiple plandex-home-N folders and just map the Nth host folder to the container /work/.plandex-v2, etc. and run the shim multiple times, each with a different argument.

4. doesn't appear to be set up for multi-repo projects

I use git subrepo to have a project with multiple repos. Whether that is a workaround or best practice I have no-opinion, but it might help?