dsh-fork-relink

DSH's fork operation inherits conversation history under a new session ID, but sub-agents attached to the old parent session do not follow automatically. The sub-agent panel on the new branch ends up empty, and all working records appear to vanish even though they are still on disk, just detached from the new conversation. dsh-fork-relink exists to solve exactly this: it listens to the official session/created event and, the moment a forked child session enters the store, it calls the official agents.create API to build a full clone of every direct sub-agent from the old session and attaches them to the new parent.

The clone is not a mere reference. The seed is a line-by-line copy of the original sub-agent's complete persistent log, agentOptions inherits the provider and model from the descriptor, and meta fields such as parentSession, origin, and delegationDepth are written correctly at creation time. Composition is injected via the official agentPresets.composeFrom entry point. The entire sub-agent tree is cloned recursively, and each clone is released as a cold session immediately after persistence to avoid write-lease conflicts that would block message delivery. Running sub-agents and seed-orphans (abandoned branches) are safely skipped.

This plugin is ideal for DSH users who frequently fork branches and have sub-agents attached to their sessions. The semantics are copy, not move: the old branch keeps using the original sub-agents, the new branch uses the clones, and both branches operate independently. The sub-agent cloning path has zero external dependencies and zero file rewrites; everything goes through the official API, so any entry point that performs an official fork is covered.