What problem does it solve?
Initial setup for a host project that wants to use Yoke. At v2.0.0, /yoke:bootstrap is the single entry point through which a host project's .yoke/config.yaml :: canonical_memory.provider lands. Two flows are supported: Flow A migrates from Yoke v1.x by detecting legacy configuration or memories.json and migrating to the v2.0.0 schema; Flow B performs a fresh bootstrap by loading providers.yaml, selecting a provider (interactive or via --provider), and writing the v2.0.0 config. It also creates .yoke/runtime/ and .yoke/.gitignore and guides the user to the next step.
Core Features & Use Cases
- Migrate existing v1.x setups or bootstrap a new Yoke v2.0.0 environment by configuring canonical_memory.provider in .yoke/config.yaml.
- Support both interactive provider selection via providers.yaml and non-interactive mode with --provider, plus the ability to auto-select when only one provider exists.
- Create required .yoke runtime artifacts (.yoke/runtime/ and .yoke/.gitignore) and guide the user to next steps, including /yoke:discover and CLAUDE.md handling.
Quick Start
Run /yoke:bootstrap in the host project root to bootstrap Yoke v2.0.0 and configure the initial .yoke/config.yaml.