Starting git workspace for Cursor Cloud Agents: clone this repository (or fork it) as the base repo cloud agents use for branches, hooks, and shared tooling.
- Cloud agents clone your repository and work on a separate branch; you need read/write access to this repo and any submodules it references. See Cloud Agents.
- Self-Hosted Pool workers run from a checked-out copy of the repo; project skills under
.cursor/skills/(or.agents/skills/) are available on workers.
This repo includes the DataKnifeAI/agent-skills repository as a submodule at .cursor/skills/agent-skills/.
After clone, initialize submodules:
git submodule update --init --recursiveTo update the skills pointer later:
cd .cursor/skills/agent-skills && git fetch && git checkout <revision> && cd ../../..
git add .cursor/skills/agent-skills && git commit -m "Bump agent-skills submodule"Optional project hooks live in .cursor/hooks.json (see Hooks).
Tracked template: git/git-path.placeholder — replace the placeholder URL with your default application repo (or copy to git/git-path, which is gitignored, and keep the placeholder file as documentation).
On Coder, clone other projects under /home/coder/agent-workspace/git/<project>/ (one folder per repo) so you can open multiple repositories in parallel—separate Cursor windows or a multi-root .code-workspace—without mixing them into this template. That is separate from Cursor’s /worktree isolation (see Worktrees), which uses ~/.cursor/worktrees by default. Details for agents: .cursor/rules/coder-workspace.mdc.