Use a docly CLI working copy instead of git
-
What you'll see
Someone — often an AI coding agent on its first pass — looks for a
.gitdirectory to get version control before starting work, or for a git remote to clone the site from. Neither exists. -
What's actually happening
Docly has no git service. There is no git remote for a workspace or a folder, and no git URL to clone. Version control of a Docly site is not done with git.
The workspace is the live application. There is no working copy on the server — the files in the workspace are the running site.
The working copy you are looking for is the
doclyCLI.docly clonedownloads a folder into local files,docly statusanddocly diffshow what you changed against the server, and nothing goes live untildocly push. Writing is locked until someone opens one folder for writing, so the blast radius is bounded. Documents whose schema keeps versions also have server-side history (docly history).A CLI working copy is ordinary local files. If you want your own git history on top of it, you can run
git initin the working copy on your own disk — that is a private repository for you, not a connection to Docly, and it is never pushed anywhere by Docly. -
What to do
For a working copy, use the CLI:
docly login docly clone <folder> work && cd work # edit the files docly status docly diff docly unlock <folder> # writing is locked until a folder is opened docly pushRun
doclywith no arguments for the full command reference. For AI agents, see How an AI agent should use the docly CLI.Say in the workspace's agent instruction file that changes go through the CLI, so an agent does not have to guess — see Set up AI agent instruction files for a workspace.
Last reviewed 19 Oct 2026