diff --git a/tsgcoo-bootstrap-prompt.md b/tsgcoo-bootstrap-prompt.md
index 55332a6..50d43c0 100644
--- a/tsgcoo-bootstrap-prompt.md
+++ b/tsgcoo-bootstrap-prompt.md
@@ -76,14 +76,39 @@ you're aligned on the operating model before you start making changes.
 
 ### Then clone the working repos
 
+**Important: Use `clone-as.sh` to clone as a specific agent identity.** This
+sets up per-repo git identity so commits and pushes are attributed correctly.
+For the initial TSGCOO bootstrap work (before agents are provisioned), clone
+as `reachableceo`.
+
 ```bash
+# Set up the credential helper in ~/.gitconfig (once):
+git config --global credential."https://git.knownelement.com".helper \
+    "$HOME/projects/TSYSGroupAIOS/scripts/bw-git-credential.sh"
+
 cd ~/projects
 
-# The provisioning automation you'll be running
-git clone ssh://git@git.knownelement.com:29418/TSYSGroupCorporate/agent-identity-provisioning.git
+# Clone the provisioning automation
+~/projects/TSYSGroupAIOS/scripts/clone-as.sh reachableceo \
+    https://git.knownelement.com/TSYSGroupCorporate/agent-identity-provisioning.git
 
-# The org-buildout docs (full context on the transition plan)
-git clone ssh://git@git.knownelement.com:29418/reachableceo/org-buildout.git
+# Clone the org-buildout docs
+~/projects/TSYSGroupAIOS/scripts/clone-as.sh reachableceo \
+    https://git.knownelement.com/reachableceo/org-buildout.git
+```
+
+After agents are provisioned, when an agent needs to work in a repo, they
+clone it with their own identity:
+```bash
+# vp-techops cloning PFVCluster:
+~/projects/TSYSGroupAIOS/scripts/clone-as.sh vp-techops \
+    https://git.knownelement.com/KNEL/PFVCluster.git ~/projects/PFVCluster-vptechops
+```
+
+To switch agent context within the shell:
+```bash
+. ~/projects/TSYSGroupAIOS/scripts/agent-profile.sh vp-techops
+# Now git commits, tea commands, etc. all operate as vp-techops
 ```
 
 Read these for context: