Problem Statement
If you want to work on several tasks simultaneously—for example, in a Rails app where database changes are made—having only a single local database can easily cause conflicts if two agents are working in parallel.
Possible Solution
The ideal approach is for Parallel Code to allow defining hooks in the project that run when a task starts, so you could, for instance, run rails db:prepare at the start and rails db:drop at the end.
Internally, the app is configured so that the database name somehow includes the git branch name or the worktree folder name, making it unique within the project.
Problem Statement
If you want to work on several tasks simultaneously—for example, in a Rails app where database changes are made—having only a single local database can easily cause conflicts if two agents are working in parallel.
Possible Solution
The ideal approach is for Parallel Code to allow defining hooks in the project that run when a task starts, so you could, for instance, run
rails db:prepareat the start andrails db:dropat the end.Internally, the app is configured so that the database name somehow includes the git branch name or the worktree folder name, making it unique within the project.