@kosuke-ai/cli 5.7.0 → 5.9.0

package/dist/generated/commands/workspaces/stop-sandboxes.js

@@ -24,8 +24,8 @@ export const operation = {
     "multipart": null,
     "attachments": false,
     "anonymous": false,
-    "sandboxToken": false,
-    "orchestratorToken": false,
-    "cronToken": false,
-    "leadToken": false
+    "sandboxToken": true,
+    "orchestratorToken": true,
+    "cronToken": true,
+    "leadToken": true
 };

package/dist/generated/commands/workspaces/usage.js

@@ -29,8 +29,8 @@ export const operation = {
     "multipart": null,
     "attachments": false,
     "anonymous": false,
-    "sandboxToken": false,
-    "orchestratorToken": false,
-    "cronToken": false,
+    "sandboxToken": true,
+    "orchestratorToken": true,
+    "cronToken": true,
     "leadToken": true
 };

package/dist/program.js

@@ -32,11 +32,9 @@ export function createProgram(options = {}) {
         output: (outcome) => runtimeFor().output(outcome),
     };
     attachAuthCommands(program, lazy, options.auth);
-    // A sandbox holds a credential the platform admits to a handful of
-    // operations, so the tree shows those and `kosuke --help` there is true
-    // rather than a list of 403s. It matters most for the orchestrator, whose
-    // input is channel text anyone can write: a help tree advertising every
-    // workspace command invites the attempt and spends the turn on refusals.
+    // An agent's credential reaches what its member's API key does, less the
+    // deletes and the personal credentials, so the tree shows that and
+    // `kosuke --help` there is true rather than a list of 403s.
     // Read from the env alone, which keeps `--help` off the credentials file.
     const token = (options.process?.env ?? process.env).KOSUKE_API_KEY;
     const narrowedTo = isSandboxAgentToken(token)
@@ -53,11 +51,10 @@ export function createProgram(options = {}) {
         : operations;
     for (const operation of reachable)
         attachOperation(program, operation, lazy);
-    // A member's own Claude Code or Codex, or their Lead, which reads the digest
-    // first; never an agent inside a Chat Session, a Cron Run or Slack triage.
-    if (narrowedTo === null || narrowedTo === 'leadToken') {
-        attachAgentCommands(program, lazy, options.agent);
-    }
+    // Every agent token reads the digest's two lists as its member. Only a
+    // member's own key and their Lead may mark Activity seen, so the others
+    // read it with `--peek`.
+    attachAgentCommands(program, lazy, options.agent);
     // The job stream admits a member's API key only; it closes 4401 on every narrower token.
     if (narrowedTo === null)
         attachWatchCommand(program, lazy, options.watch);