diff --git a/AGENTS.md b/AGENTS.md
index 9cbe9f4..65c48e4 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -72,6 +72,8 @@ git diff --check
 zig zen
 ```
 
-Use `just invite` for admin-minted invite codes and `just bench ...` for local
+Use `just invite` for admin-minted invite codes. Assume `ZDS_ADMIN_TOKEN` is
+set in the repo `.env`; source it before running the target, for example
+`set -a; . ./.env; set +a; just invite`. Use `just bench ...` for local
 performance probes. Keep commits small. Amend only when asked. Do not revert
 user or sibling-repo changes unless asked.
diff --git a/docs/invite-codes.md b/docs/invite-codes.md
index c8e4983..e9d8ef8 100644
--- a/docs/invite-codes.md
+++ b/docs/invite-codes.md
@@ -47,22 +47,24 @@ happen in the same SQLite transaction while the store lock is held, so racing
 requests cannot both consume a one-use code.
 
 When invite-required mode starts against an empty database, ZDS creates one
-bootstrap code and logs it. After that, mint codes through the XRPC endpoint:
+bootstrap code and logs it. After that, mint codes through the XRPC endpoint.
+For local admin operations, assume `ZDS_ADMIN_TOKEN` is set in the repo `.env`
+and source it before running the Just target:
 
 ```sh
-ZDS_ADMIN_TOKEN='...' just invite https://pds.zat.dev
+set -a; . ./.env; set +a; just invite https://pds.zat.dev
 ```
 
 For a multi-use code:
 
 ```sh
-ZDS_ADMIN_TOKEN='...' just invite https://pds.zat.dev 3
+set -a; . ./.env; set +a; just invite https://pds.zat.dev 3
 ```
 
 For a code assigned to a specific DID:
 
 ```sh
-ZDS_ADMIN_TOKEN='...' just invite https://pds.zat.dev 1 did:plc:...
+set -a; . ./.env; set +a; just invite https://pds.zat.dev 1 did:plc:...
 ```
 
 ## reference notes