cli.sgit.ai / Site / What moved from sgit.ai

What moved from sgit.ai

On 20 October 2026 the CLI's most technical pages moved here from sgit.ai, as the brief asks: the CLI now has a set of use cases of its own, and sgit.ai is the umbrella for the project and its commercial side. Each page kept its path, so sgit.ai/docs/quickstart.html is now cli.sgit.ai/docs/quickstart.html, and a redirect on sgit.ai is one rule.

The pages were taken from sgit.ai's markdown twins, which are generated from the same source as its HTML, at sgit.ai site v0.7.87, by admin/build/import_sgit_ai.py. The text is unchanged. Links to a page that moved now stay on this site; links to anything else go back to sgit.ai.

Was on sgit.aiIs nowSection here
https://sgit.ai/api/append-lanes.htmlAppend lanesHTTP API
https://sgit.ai/api/authentication.htmlAuthenticationHTTP API
https://sgit.ai/api/errors.htmlErrors and limitsHTTP API
https://sgit.ai/api/index.htmlThe HTTP APIHTTP API
https://sgit.ai/api/transfers.htmlThe transfer API, one encrypted handover, one linkHTTP API
https://sgit.ai/api/vault-objects.htmlVault objectsHTTP API
https://sgit.ai/docs/agents-sharing-one-vault.htmlAgents sharing one vaultGuides
https://sgit.ai/docs/agents.htmlWorking with AI agentsGuides
https://sgit.ai/docs/append-lane-messaging.htmlAppend-lane messaging between agents that hold no one else's vault keyGuides
https://sgit.ai/docs/credentials.htmlVault credentials: what each one can do, and what its prefix declaresSecurity
https://sgit.ai/docs/history-integrity.htmlHistory integrity: the format gate, verifying signatures, and rewindsGuides
https://sgit.ai/docs/how-to/claude-team-egress.htmlUsing sgit from Claude on a Team or Enterprise plan: the network allowlistGuides
https://sgit.ai/docs/installation.htmlInstallationGet started
https://sgit.ai/docs/key-management.htmlVault key management: where each key lives, and how it travelsSecurity
https://sgit.ai/docs/limitations.htmlWhen NOT to use sgitGet started
https://sgit.ai/docs/partial-clones.htmlPartial clones: a folder scope and a history depthGuides
https://sgit.ai/docs/pki.htmlKeys, signatures and encrypting to someone elseSecurity
https://sgit.ai/docs/quickstart.htmlQuickstartGet started
https://sgit.ai/docs/self-host-for-agents.htmlSelf-hosting a vault server for agentsGuides
https://sgit.ai/docs/send-a-vault-key.htmlSend a vault key to the registryGuides
https://sgit.ai/docs/sgit-for-git-users.htmlsgit for git usersGet started
https://sgit.ai/docs/two-branch-model.htmlThe two-branch modelGet started
https://sgit.ai/docs/update-to-0-18-0.htmlUpdate sgit-ai to 0.18.0Guides
https://sgit.ai/docs/update-to-0-21-0.htmlUpdate sgit-ai to 0.21.0Guides
https://sgit.ai/docs/vault-messaging.htmlSending messages between vaultsGuides
https://sgit.ai/docs/what-is-sgit.htmlWhat is sgitGet started
https://sgit.ai/security/index.htmlSecurity modelSecurity

What stayed on sgit.ai, and why

What sgit.ai still has to do

This site cannot change sgit.ai. Until sgit.ai's team acts, both copies exist, and the copy here is the one maintained from now on. The request to them, as recorded in the corrections file:

  1. Point each moved page at its new address: a link at the top, then a redirect.
  2. Point sgit.ai's docs hub and llms.txt at cli.sgit.ai for the CLI.
  3. Add cli.sgit.ai to the network directory (admin/content/sites/cli.md, the Cartographer's file).

This page as markdown · its source, admin/content/admin/moved.md