the persistent markdown approach to context drift is clever - treating state files as a first-class primitive rather than hoping the agent remembers between sessions is the right instinct.
one thing i've noticed: even with perfect context files, multi-agent setups still hit the physical isolation problem - multiple agents in the same working directory stepping on each other's files mid-session. the context drift and the file conflict problem are separate issues that both need solving.
i've been working on the isolation layer: pane gives each agent its own git worktree (isolated filesystem per feature) so context drift from file collisions is removed entirely. fully open source (agpl-3.0): github.com/Dcouple-Inc/Pane - the two approaches actually complement each other pretty cleanly.
one thing i've noticed: even with perfect context files, multi-agent setups still hit the physical isolation problem - multiple agents in the same working directory stepping on each other's files mid-session. the context drift and the file conflict problem are separate issues that both need solving.
i've been working on the isolation layer: pane gives each agent its own git worktree (isolated filesystem per feature) so context drift from file collisions is removed entirely. fully open source (agpl-3.0): github.com/Dcouple-Inc/Pane - the two approaches actually complement each other pretty cleanly.