| name | session-isolation |
| description | Use when orchestrating workflows that generate multiple files (designs, reviews, reports) to prevent file collisions across concurrent or sequential sessions with unique session directories. |
| keywords | ["session-isolation","artifact-isolation","file-collision","concurrent-sessions","sequential-workflows","session-directory","multi-artifact","session-metadata"] |
| plugin | multimodel |
| updated | "2026-01-20T00:00:00.000Z" |
Session Isolation Pattern
Session-based artifact isolation for multi-artifact workflows. Use when orchestrating workflows that generate multiple files (designs, reviews, reports) to prevent file collisions across concurrent or sequential sessions.
Problem
When multiple workflows run (even sequentially), artifacts with the same name collide:
Session 1 (SEO): writes ai-docs/plan-review-grok.md
Session 2 (API): writes ai-docs/plan-review-grok.md <-- OVERWRITES!
Solution
Use unique session folders to isolate artifacts:
ai-docs/sessions/agentdev-seo-20260105-143022-a3f2/
โโโ session-meta.json # Session tracking
โโโ design.md # Primary artifact
โโโ reviews/
โ โโโ plan-review/ # Plan review phase
โ โ โโโ internal.md
โ โ โโโ grok.md
โ โ โโโ consolidated.md
โ โโโ impl-review/ # Implementation review phase
โ โโโ internal.md
โ โโโ consolidated.md
โโโ report.md # Final report