context-fork-guide

You can isolate heavy research tasks by forking the execution context into a separate window, which prevents session bloat and keeps the main conversation uncluttered. Add context: fork to the skill's frontmatter to enable this.

Running multi-file analysis slows down your current context because the process bloats the session. Forking the execution context into a separate window prevents this degradation and maintains session responsiveness.

The best way to run exploratory skills without degrading context performance is forking the execution context into a separate window. This isolation ensures long-running tasks remain responsive and do not clutter the main session.

To configure skill frontmatter for a forked context window, add context: fork to the frontmatter. You must include at least name and description, while optional components like scripts and references can be declared as needed.

You need to fork context for skills that pull external data when the tasks are heavy and would otherwise degrade the current context. This isolation ensures the main session remains clean and responsive during complex workflows.

Yes, you can use context isolation for skills that perform vault searches. Forking the execution context isolates these heavy research tasks into a separate window, preventing session bloat and keeping the main conversation uncluttered.