@pushary/agent-hooks 0.64.3 → 0.64.4

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 0.64.4
+
+### The shell you ran setup in still exported the key it replaced
+
+0.64.3 stopped a stale export from hiding the working key on disk, and the rc
+file has been rewritten in place since 0.62. Neither reaches the shell you are
+standing in: the export there is still the old key, the environment wins over the
+config file at hook time, and the agent you start in that terminal a minute later
+talks to whichever workspace that key belongs to.
+
+`--connect app` mints on every run and is the command onboarding prints, so this
+is the ordinary case rather than an exotic one. Setup now says so under "Still to
+do": open a new terminal, or re-export. No key is printed in that line.
+
 ## 0.64.3
 
 ### A stale shell export hid the working key on disk

package/dist/bin/pushary-setup.js

@@ -1296,6 +1296,11 @@ var main = async () => {
   markStep("save-key");
   const rc = await saveApiKey(trimmedKey);
   const context = { rc };
+  if (envKey && envKey !== trimmedKey) {
+    noteManual(
+      `This shell still exports the previous key (${keyPrefix(envKey)}), and it wins over the one just saved. Open a new terminal before starting an agent here, or re-export PUSHARY_API_KEY.`
+    );
+  }
   const failed = [];
   const completed = [];
   const skipped = [];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pushary/agent-hooks",
-  "version": "0.64.3",
+  "version": "0.64.4",
   "description": "Permission hooks for AI coding agents: route tool approvals through Pushary push notifications",
   "keywords": [
     "pushary",