Feature
Provider rendering
Assets become each provider’s native files, from a deterministic render plan.
A renderer turns assets into one provider’s files. A render plan is a deterministic description of which files must exist for one workspace target and one provider at one workspace revision; each planned file has a path, a content hash, an owner (the package@version that produced it) and a write mode.
The `wl` CLI renders and writes files for Claude (CLAUDE.md and .claude/), Codex (AGENTS.md and .codex/) and Gemini (GEMINI.md and .gemini/). The GitHub Copilot renderer (.github/copilot-instructions.md and .github/instructions/) is implemented in the registry’s render preview endpoint and is not yet wired into the CLI. Rendered files carry an ownership header naming their workspace, owner and content hash.
More features
All features →- 01
Organization packages
Scoped, immutable packages of skills, agents, prompts and configs, owned by your org.
- 02
Workspace desired state
Each workspace declares which packages, versions and providers every target gets.
- 03
Home profiles
Apply AI dev-env configuration to $HOME, attributed and cleanly removable.