@onklave/agent-cli 0.1.8 → 0.1.9

package/README.md

@@ -60,7 +60,9 @@ onklave run --task "Add unit tests for the auth module"
 ```
 
 Get a CLI token by signing in to the Onklave portal → **Settings → API Tokens →
-Generate new CLI token**.
+Generate new token**. Pick an expiry (Never / 30 days / 90 days / 1 year) and a
+descriptive name (e.g. `laptop-cli`). The plaintext is shown **once** — copy it
+immediately; it can't be retrieved later. Revoke any token from the same page.
 
 ---
 
@@ -226,6 +228,17 @@ Machine**.
 
 ---
 
+## Revoking access
+
+Tokens can be revoked instantly from the portal — **Settings → API Tokens** → ⋯ → Revoke.
+Revocation takes effect within ~5 minutes (cached resolves expire on that interval).
+
+If you suspect a token has been leaked, revoke it immediately. Existing CLI sessions
+that have already authenticated continue to work *for the user* but lose access on
+their next API call.
+
+---
+
 ## Diagnostics
 
 If something looks off:

package/main.js

@@ -189,7 +189,7 @@ async function loginCommand(args) {
     console.log("  2. Navigate to Settings > API Tokens");
     console.log("  3. Generate a new CLI token");
     console.log("  4. Run: onklave login --token <your-token>\n");
-    console.log("Note: Browser-based OAuth login will be available in v2.");
+    console.log("Tokens are bearer credentials. Treat them like passwords.");
     process.exitCode = 1;
     return;
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@onklave/agent-cli",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "Onklave Agent CLI — local agent runner with cloud orchestration",
   "bin": {
     "onklave": "./main.js"