Connect the whole collection
Review a two-way sync through a Kitrove snapshot backend.
That skill you found. The instructions you refined. Collect them with Kitrove, then choose what to bring to another agent tool or computer.
Open source. Local-first. You review the changes.
Built for people who
try more than one agent.
A collection you control
Kitrove starts with the skills already on your computer. The walkthrough takes you through each choice, with a preview before you confirm.
Scan user-level skills and see their names and source tools. Pick from a readable list, without copying long IDs.
Choose which skills to adopt. Review each plan. Kitrove keeps the original files in place.
Select a destination and review what transfers. If a destination has an unmanaged file in the way, Kitrove stops instead of overwriting it.
Laptop, desktop, next computer
Run the walkthrough on a second computer and choose how much of your collection to bring. Each computer keeps its own identity and destinations.
Set up another computerReview a two-way sync through a Kitrove snapshot backend.
Connect first, collect local skills, then review publishing the additions.
Import specific assets or packs once, without changing the remote.
Start here
Kitrove is a release candidate. Start with a small collection and review each change.
Install the preview with Homebrew, then open the guided setup.
brew install --cask kapital-labs/tap/kitrove-rc
kitrove init
Requires Homebrew. The cask currently supports Apple Silicon Macs only.
brew update
brew upgrade --cask kapital-labs/tap/kitrove-rc
kitrove configure
Homebrew updates the binary. Your collection and setup are separate.
Windows x86_64 release artifacts are available. We have not published a WinGet or Chocolatey package.
Use the release verification instructions before running a download. Windows lifecycle acceptance remains open.
Read the manual release guide →Linux x86_64 release artifacts are available. We have not published APT, DNF, or other Linux package-manager installs.
Use the release verification instructions before running a download. Native lifecycle testing is separate from building the archive.
Read the manual release guide →Know what moves
Agent tools have different capabilities. Kitrove preserves native details and reports transfer fidelity so you can decide what to apply.
Credentials, accounts, trust decisions, and machine-specific paths stay outside collection sync. You still install and authorize each agent tool on each computer.
Read the boundaries →Before you start
Yes, after you confirm the plan. The walkthrough suggests ~/Kitrove for your collection and shows a separate machine-local state location. You can choose another collection location.
No. You start a sync operation and review the plan. Full sync can publish local additions as well as bring remote changes back.
Adoption leaves source files in place. Applying is a separate confirmation. Kitrove refuses unmanaged destination conflicts rather than overwriting them.
No. RC4.1 is a prerelease. Clean-Mac online/offline first-launch testing, other native target coverage, and real two-machine acceptance remain separate open gates.