Drive

Capy Drive stores instructions, skills, and files outside git so every thread in a scope can use them. Use it for anything that isn’t code but should outlive one thread: team rules that span repositories, reusable skills, approved checklists, reference material, and state an automation carries between runs.

​

Scopes

Each scope is its own drive. Pick one by who should see it: * Not used for instructions or skills; holds automation state and persisted work between runs. Organization and Project drives are shared with the organization’s members. Personal and Project + personal drives aren’t browsable by other members. All scopes stay within one organization.

​

Instructions

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

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

See Instructions for repository and file-specific rules.

​

Skills

Drive skills live at skills/<name>/SKILL.md and load on demand in every thread in the scope. Create one with New skill in the drive, or ask Capy:

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

​

Save and update files

Save the approved launch checklist in our project drive 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 and edit

Open More → Drive, or Drive if pinned in the sidebar, then pick a scope. You can edit files in the browser, upload files, and add a skill or instructions by hand. History lists saved versions and the threads that made them. Restore brings back an earlier version as a new version, so nothing is lost.

​

Storage limits

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