~/.agentx keeps the full history of your own skills.
When you need it
- A second machine: publish your own skills on one machine, and install them on another.
- A backup: export a snapshot of a machine, and restore it after a reinstall or on a new computer.
- Cloud agents: the cloud machine has no computer of its own, so its snapshot on the account remote is its only state. See Cloud agents.
What it holds
agentx writes two kinds of branches, and does not use any other branch, such asmain.
Create it
Create a repository on any Git host, such as GitHub or GitLab. Only these choices matter to agentx:- Private or public: make it private. A snapshot keeps each MCP server’s command, arguments and URL, and these can hold a token. Each machine then needs Git credentials for it, such as an SSH key or a credential helper, and a cloud agent needs a read-only token. A public account remote needs no credentials to read over HTTPS, but anyone can read your skills and snapshots. An SSH URL needs an SSH key, even for a public repository.
- First files: choose any. The repository can be empty, or have a README, a license or a
.gitignoreon its default branch, because agentx does not use that branch. - Access: a machine that publishes or exports needs write access. A machine that only installs and imports needs read access.
- A new repository: use a repository that is not a source on any machine. One repository cannot be both a shared source and the account remote.
Add it
On each machine, add the repository with--account: