Volumes

Volumes store instructions, skills, and shared files outside git for reuse across threads.

​

Scopes

* Not used for instructions or skills; holds automation state and persisted work between runs. Organization and Project volumes are shared with the organization’s members. Personal and Project + personal volumes aren’t browsable by other members. All scopes stay within one organization.

​

Global instructions

A volume’s root AGENTS.md supplies instructions to threads in its scope.

Add “Use conventional-commit PR titles” to AGENTS.md in my personal volume. Preserve existing instructions.

See Instructions for repository and file-specific rules.

​

Reusable skills

Volume skills live at skills/<name>/SKILL.md and load on demand.

Create a release-checklist skill in our project volume from the release procedure we agreed on.

​

Save and update files

Save the approved launch checklist in our project volume for future threads.

Capy can update or remove saved files on request. Changes save automatically as work completes, without a git commit or separate publish step. Checkout and scratch files aren’t included.

​

Browse files and history

Open More → Volumes, or Volumes if pinned in the sidebar. History lists saved versions and their originating threads. The viewer is read-only; ask Capy to edit files or recover a retained version.

​

Storage limits

Limits are 100 MiB per file, 2 GiB per saved volume version, and 10 GiB per organization. History doesn’t retain every intermediate version.