@hanskristoffer/agentpool 0.19.0 → 0.20.0

package/README.md

@@ -93,7 +93,7 @@ One instance per provider covers every account; the daemon switches eligible acc
 
 ### Hand threads between machines
 
-Start a thread on your laptop, hand it to an always-on server while you are away, and hand it back to test and push. A handed-off thread moves with its Claude session and its code: unpushed commits and uncommitted and untracked files (respecting `.gitignore`). Code travels directly between the two machines over Tailscale, or end-to-end encrypted through the relay; nothing is pushed to `origin`.
+Start a thread on your laptop, hand it to an always-on server while you are away, and hand it back to test and push. A handed-off thread moves with its Claude session and its code: unpushed commits and uncommitted and untracked files (respecting `.gitignore`), plus your changes to the repository's [env files](#env-files-between-machines). Code travels directly between the two machines over Tailscale, or end-to-end encrypted through the relay; nothing is pushed to `origin`.
 
 Connect agentgate to the T3 Code on each machine once: on the T3 Code page open **Machines** and choose **Connect T3 Code** in that machine's row, or run `agentgate t3 connect` there (`--node srv` sets up another machine from the one you are on). T3 Code must be running on that machine; its own `t3` command creates a pairing link that agentgate redeems right away, over that machine only. Pair again the same way when agentgate asks. If that machine has no `t3` command, create a link in T3 Code under **Settings → Connections** (turn on **Network access**, then **Create link** with **Standard** permissions) and paste it into **Connect with a pasted link**, or run `agentgate t3 connect <link>`. The machines must be paired over Tailscale or in the same relay group. A handoff moves the session between the Claude homes T3 Code's Claude provider uses on each machine, whether that is `~/.claude` or the agentgate home above.
 
@@ -181,6 +181,20 @@ Bundles must contain a nonempty root `SKILL.md`, with unique portable paths and
 
 Repository-owned skills are mirrored only when you opt in with **Share repo skills between Claude and Codex** in a project's ⋯ menu in Projects. Mirroring creates relative links that can be reviewed and committed. Stopping mirroring stops future maintenance and leaves existing links in place; repository-owned links are preserved.
 
+## Env files between machines
+
+Gitignored files such as `.env.local` or `apps/expo-app/.env` follow a repository to your other machines. If the repository uses [buncargo](https://github.com/HansKristoffer/buncargo), its file store (`~/.buncargo/files`) syncs on its own: save a file there with buncargo and every machine's store gets it. Otherwise, in a checkout run:
+
+```sh
+agentgate project files add .env.local apps/expo-app/.env   # save them for every machine
+agentgate project files ls
+agentgate project files rm .env.local
+```
+
+In the app, choose **Env files** in a repository's menu on the Projects page to see its files, add one from a checkout on that machine, or stop syncing one; a repository's row lists its files and says when they are not syncing. Run `add` again to save a newer version; the newest save of each file wins. A checkout agentgate creates, through a handoff or a clone, gets the files: buncargo's `files pull` where the repository uses buncargo, otherwise each file that is missing, never replacing one that is there. A handoff also carries the thread's own changes to those files. Files buncargo marks as machine-only stay on their machine.
+
+Only github.com repositories sync, and all of a repository's files together can be about 700 KiB. Every machine must run this agentgate release first. The files sync like MCP secrets: end-to-end encrypted through the relay, and stored unencrypted in each machine's `agentgate.db`. `agentgate export --no-secrets` leaves them out.
+
 ## Your MCP servers and skills in Grok
 
 Assistants such as Grok only accept an MCP server URL and an `Authorization` header. A **virtual project** gives them one: in Projects, choose **New virtual project**, pick its MCP servers and skills, then **Connect to Grok** and copy the URL and `Authorization` value into Grok. One of your machines (an always-on server by default) answers through the relay. Grok also gets `skills__list` and `skills__read` tools, so it can find a skill and follow its SKILL.md.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hanskristoffer/agentpool",
-  "version": "0.19.0",
+  "version": "0.20.0",
   "license": "UNLICENSED",
   "repository": {
     "type": "git",
@@ -22,9 +22,9 @@
     "agentgate": "bin/agentpool.js"
   },
   "optionalDependencies": {
-    "agentpool-darwin-arm64": "0.19.0",
-    "agentpool-darwin-x64": "0.19.0",
-    "agentpool-linux-x64": "0.19.0",
-    "agentpool-linux-arm64": "0.19.0"
+    "agentpool-darwin-arm64": "0.20.0",
+    "agentpool-darwin-x64": "0.20.0",
+    "agentpool-linux-x64": "0.20.0",
+    "agentpool-linux-arm64": "0.20.0"
   }
 }