# Pin the agent setup and restore it precisely on another machine

> Pin the agent setup and restore it precisely on another machine: 0 companies fully do it, 1 with a limit, 1 carry the tag. Every listing in Agent package managers with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/agent-packages.pin-and-restore/
- Markdown: https://www.anchorterminal.com/niches/agent-packages.pin-and-restore/index.md (~750 tokens)
- Slim: https://www.anchorterminal.com/niches/agent-packages.pin-and-restore/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/agent-packages.pin-and-restore/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 1 | 1 | 23 | 9 |

## What counts as done

A lockfile records each skill, plugin and MCP server by commit and content hash, one documented command restores precisely those files on a clean machine, it fails rather than drifts when a hash differs, and project-level and user-level installs are both covered.

Measured, for our own tests: two clean restores from the same lock give byte-identical staged files.

How agents ask for it: lock our skills and MCP servers like a package-lock; set this project up the same on my other laptop; install everything from the lockfile; why does CI's agent have a different skill

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Agentpack (No legal entity found. The licence reads Copyright (c) olegpustovit and contributors, and the docs name Oleg Pustovit as author)**: pack.lock records commit plus sha256-tree-v1 content hash and sync stops on a mismatch. But there is no sync --frozen (issue #16 open), the lock is project-only (user layer #24 open), PyPI and docker MCP servers are not resolved, and a ref-less add can lock a stale commit (#11).

## What stops agents finishing

- lock written only for global installs
- no install-from-lock command
- a ref-less add resolves to a commit cached from another project
- MCP servers launched as npx latest with no version recorded

## Around it

Before: agent-packages.install-package. After: agent-harnesses.fix-failing-ci, agent-packages.update-on-purpose.

## Where this comes from

Weight 23 of 100 in Agent package managers: 7 of 31 accounts have this as their main job (share 22.6, rounded by largest remainder to sum 100)

As data: https://www.anchorterminal.com/api/v1/use-cases/agent-packages.pin-and-restore.json, or the MCP tool get_use_case with id agent-packages.pin-and-restore. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
