Expand description
Provider-neutral workspace forks (roadmap phase 81).
A fork is a writable workspace copy or session derived from a source workspace — backing a thread, subagent lane, task branch, or experiment. Providers implement concrete storage/compute behavior (Git worktrees, Rift copy-on-write snapshots, remote sandboxes); core code only sees these types. Forks are not inference providers and are not GitHub repository forks.
Structs§
- Fork
Capabilities - Fork
Policy - Source-state policy applied before fork creation.
- Fork
Provenance - Provider-recorded provenance. All fields optional so local and remote providers can populate what they actually know; never secret-bearing.
- Fork
Provider Descriptor - Fork
Request - Remove
Fork Policy - Removal is destructive and always path-confirmed: the caller must name the exact fork workspace being removed.
- Remove
Fork Result - Workspace
Fork
Enums§
- Fork
Cleanup Policy - Fork
Reason - Why a fork is being created; recorded for provenance/audit only.
- Fork
Status
Traits§
- Fork
Provider - Provider contract for workspace forks. Registered through the extension
registry (
ProvidedService::ForkProvider); providers declare their capabilities and must not assume ambient authority beyond them.
Type Aliases§
- ForkId
- Provider-scoped fork identifier. Stable and resolvable by the provider
alone (e.g. the absolute worktree path for
git-worktree). - Fork
Provider Id