@codyswann/lisa 4.81.3 → 4.81.5

package/plugins/lisa/.codex-plugin/skills/lisa-session-manager/scripts/token.mjs

@@ -1,7 +1,8 @@
 /**
  * The Telegram bot token the manager needs: validated, stored in
  * `<stateDir>/.env` (dir 0700, file 0600), read from the operator's terminal
- * with echo off, and never put in argv, a return value, an error message or a
+ * with echo off or from the clipboard (`--from-clipboard`, for when no TTY is
+ * reachable), and never put in argv, a return value, an error message or a
  * log line. An existing token is replaced only on request. Split out of
  * launch.mjs, which re-exports everything here.
  * @module token
@@ -10,6 +11,7 @@ import { randomUUID } from "node:crypto";
 import * as nodeFs from "node:fs";
 import path from "node:path";
 
+import { readClipboard } from "./clipboard.mjs";
 import { LaunchError, resolveStateDir } from "./state-dir.mjs";
 
 /** The shape of a BotFather token: `<bot id>:<secret>`. */
@@ -94,41 +96,110 @@ function shellQuote(word) {
  *   input - Script and project locations, and whether to carry `--replace`
  * @returns {string} One shell line
  */
-export function buildStoreTokenCommand({ scriptsDir, projectRoot, replace }) {
+export function buildStoreTokenCommand({
+  scriptsDir,
+  projectRoot,
+  replace,
+  fromClipboard = false,
+}) {
   const script = shellQuote(path.join(scriptsDir, "session-manager.mjs"));
-  const flag = replace ? " --replace" : "";
-  return `node ${script} store-token${flag} --project-root ${shellQuote(projectRoot)}`;
+  const flags =
+    (replace ? " --replace" : "") + (fromClipboard ? " --from-clipboard" : "");
+  return `node ${script} store-token${flags} --project-root ${shellQuote(projectRoot)}`;
+}
+
+/** Why `store-token` cannot prompt here, and the two ways forward. */
+const NO_TTY_HINT =
+  "No terminal to prompt on, and Claude Code's ! prefix has no TTY either. " +
+  "Run `command` in a separate terminal app, or copy the token from " +
+  "BotFather and run `clipboardCommand`.";
+
+/** The `invalid` outcome; names the expected shape, never the input. */
+const INVALID = Object.freeze({
+  stored: false,
+  reason: "invalid",
+  message:
+    "That does not look like a Telegram bot token " +
+    "(expected <digits>:<30 or more letters, digits, _ or ->).",
+});
+
+/**
+ * Refuse to overwrite an existing token unless `replace` was asked for: a
+ * second project that shares this state dir by mistake would otherwise
+ * silently take over the first project's bot.
+ * @param {string} stateDir - Resolved state dir
+ * @param {boolean} replace - `--replace`
+ * @param {{ fs?: { existsSync?: (p: string) => boolean } }} io - Seams
+ */
+function assertReplaceable(stateDir, replace, io) {
+  const existing = path.join(stateDir, TOKEN_FILE_NAME);
+  const exists = io.fs?.existsSync ?? nodeFs.existsSync;
+  if (!replace && exists(existing)) {
+    throw new LaunchError(
+      `A bot token already exists at ${existing}. Nothing was changed. ` +
+        `Re-run store-token with --replace to overwrite it.`
+    );
+  }
+}
+
+/**
+ * Store the bot token from the system clipboard, with no TTY needed.
+ *
+ * Same validation and the same existing-token rule as the prompt. The
+ * clipboard is cleared only after a successful store, so a failed attempt
+ * leaves the operator's copy in place to retry with. The token is never
+ * returned, and an invalid value is reported by shape, never echoed.
+ * @param {{ stateDir: string, replace?: boolean,
+ *   env?: Record<string, string | undefined>, homedir?: string,
+ *   io?: { readClipboard?: typeof readClipboard, fs?: object } }} input -
+ *   Configured state dir, the `--replace` flag and seams
+ * @returns {{ stored: true, path: string, clipboardCleared: boolean } |
+ *   { stored: false, reason: "empty" | "invalid" | "unsupported" |
+ *     "unavailable" | "failed", message: string }} Outcome
+ */
+export function storeTokenFromClipboard(input) {
+  const { replace = false, io = {} } = input;
+  const stateDir = resolveStateDir(input.stateDir, input);
+  assertReplaceable(stateDir, replace, io);
+  const clip = (io.readClipboard ?? readClipboard)();
+  if (!clip.ok) {
+    return { stored: false, reason: clip.reason, message: clip.message };
+  }
+  const token = clip.text.trim();
+  if (!token) {
+    return {
+      stored: false,
+      reason: "empty",
+      message: "The clipboard is empty.",
+    };
+  }
+  if (!validateBotToken(token)) return { ...INVALID };
+  const written = writeTokenFile(stateDir, token, io);
+  return { stored: true, ...written, clipboardCleared: clip.clear() };
 }
 
 /**
  * Prompt for the bot token on the operator's terminal and store it.
  *
- * An existing token is never overwritten without `replace`: a second project
- * that shares this state dir by mistake would otherwise silently take over the
- * first project's bot. With no TTY this does not prompt and does not fail: it
- * returns the exact command for the operator to run themselves, because an
- * agent's Bash can never answer a prompt and a hung setup looks like a slow
- * one.
+ * An existing token is never overwritten without `replace`. With no TTY this
+ * does not prompt and does not fail: it returns the exact command for the
+ * operator to run in a separate terminal app, and the `--from-clipboard` form
+ * of it, because an agent's Bash (and Claude Code's `!` prefix) can never
+ * answer a prompt and a hung setup looks like a slow one.
  * @param {{ stateDir: string, scriptsDir: string, projectRoot: string,
  *   replace?: boolean, env?: Record<string, string | undefined>,
  *   homedir?: string, io?: { canPrompt?: () => boolean,
  *   promptSecret?: (message: string) => string, fs?: object } }} input -
  *   Configured state dir, locations, the `--replace` flag and seams
  * @returns {Promise<{ stored: true, path: string } |
- *   { stored: false, reason: "no-tty", command: string } |
+ *   { stored: false, reason: "no-tty", message: string, command: string,
+ *     clipboardCommand: string } |
  *   { stored: false, reason: "empty" | "invalid", message: string }>} Outcome
  */
 export async function storeToken(input) {
   const { scriptsDir, projectRoot, replace = false, io = {} } = input;
   const stateDir = resolveStateDir(input.stateDir, input);
-  const existing = path.join(stateDir, TOKEN_FILE_NAME);
-  const exists = io.fs?.existsSync ?? nodeFs.existsSync;
-  if (!replace && exists(existing)) {
-    throw new LaunchError(
-      `A bot token already exists at ${existing}. Nothing was changed. ` +
-        `Re-run store-token with --replace to overwrite it.`
-    );
-  }
+  assertReplaceable(stateDir, replace, io);
   const loaded =
     io.canPrompt && io.promptSecret ? null : await loadPromptSecret();
   const canPrompt = io.canPrompt ?? (() => loaded.canPrompt());
@@ -138,7 +209,14 @@ export async function storeToken(input) {
     return {
       stored: false,
       reason: "no-tty",
+      message: NO_TTY_HINT,
       command: buildStoreTokenCommand({ scriptsDir, projectRoot, replace }),
+      clipboardCommand: buildStoreTokenCommand({
+        scriptsDir,
+        projectRoot,
+        replace,
+        fromClipboard: true,
+      }),
     };
   }
   const typed = promptSecret(
@@ -147,15 +225,7 @@ export async function storeToken(input) {
   if (!typed) {
     return { stored: false, reason: "empty", message: "Nothing entered." };
   }
-  if (!validateBotToken(typed)) {
-    return {
-      stored: false,
-      reason: "invalid",
-      message:
-        "That does not look like a Telegram bot token " +
-        "(expected <digits>:<30 or more letters, digits, _ or ->).",
-    };
-  }
+  if (!validateBotToken(typed)) return { ...INVALID };
   return { stored: true, ...writeTokenFile(stateDir, typed, io) };
 }
 

package/plugins/lisa/.codex-plugin/skills/lisa-setup-session-manager/SKILL.md

@@ -44,16 +44,31 @@ writes `$SM`, and pass `--project-root "$ROOT"` (the absolute project root) on e
 
 1. Preview: `node "$SM/session-manager.mjs" init-config --project-root "$ROOT"`. It detects
    `projects/*/.lisa.config.json` and proposes `name`, `interval`, `repos`, `capacity`, `stall` and a
-   per-project `notify.stateDir`. Show the block to the operator.
+   per-project `notify.stateDir`. Repo detection leaves out linked worktrees and keeps one checkout
+   per remote, so ticket worktrees and second clones under `projects/` are not proposed. Show the
+   block to the operator and ask whether any repo is missing or should not be routed.
 2. Write it: the same command with `--write`. It adds only non-secret fields and never overwrites an
    existing block (`reason: "exists"` means keep it).
-3. Ask the operator to replace each repo's starter `hints` with the technologies and areas that
-   identify it (e.g. `api`: `["NestJS","migrations"]`, `web`: `["Expo","screens"]`), and whether to
+3. Each repo's `hints` are a draft: its name plus one per well-known dependency (`NestJS`, `Expo`,
+   `AWS CDK`, ...). Ask the operator to correct them and add the areas that identify the repo
+   (e.g. `api`: `["NestJS","migrations"]`, `web`: `["Expo","screens"]`), and whether to
    set `sessionManager.trustedAuthorIds`. Without it, any author's Ready item reaches a
    bypass-permissions worker; say so plainly. The list holds stable tracker user ids as strings,
    never logins: the GitHub numeric user id (`gh api users/<login> --jq .id`), the Jira
    `accountId`, or the Linear user id. A login matches no one and silently excludes every item.
-4. `node "$SM/session-manager.mjs" validate --project-root "$ROOT"` must print `valid: true`.
+4. Set `sessionManager.operatorIds` to a non-empty **array** holding the operator's own tracker
+   user id, e.g. `"operatorIds": ["<operator-id>"]` (a bare string fails `validate`). Look up the
+   OPERATOR, not the credential: `gh api user` / `viewer.id` return whoever the tracker credential
+   belongs to, which is the agent account in exactly the case this key exists for. The manager dispatches
+   the operator's assigned items first, then items assigned to the tracker credential's identity
+   ("me"), then unassigned ones, and skips items assigned to anyone else. When the tracker
+   credential is not the operator's (an agent or bot account), leaving this unset means the
+   operator's own Ready items are never dispatched; say so plainly. Unlike `trustedAuthorIds`, this
+   is matched against the assignee, exactly and case-sensitively, so use the same kind of id as
+   "me", spelled as the tracker API returns it: the GitHub **login** (`gh api users/<login> --jq
+   .login`), the Jira `accountId`, or the Linear user id (the operator's entry in the team's member
+   list, or `viewer.id` only when the operator runs the lookup with their own credential).
+5. `node "$SM/session-manager.mjs" validate --project-root "$ROOT"` must print `valid: true`.
 
 ## Step 3: Store the bot token
 
@@ -63,8 +78,14 @@ The operator creates a bot with @BotFather, one per project. Then run
 - `stored: true`: done.
 - Exit 2 because a token already exists: keep it (re-running setup is safe). Only when the operator
   says the stored token is wrong or belongs to another project, re-run with `store-token --replace`.
-- `reason: "no-tty"` (an agent's Bash has no terminal): print `command` from the output and ask the
-  operator to run it in their own terminal, where it prompts with echo off. Wait for them to confirm.
+- `reason: "no-tty"` (an agent's Bash has no terminal): offer the operator both routes, and say
+  plainly that Claude Code's `!` prefix has no terminal either, so it fails the same way:
+  - **Clipboard (simplest):** they copy the token from the BotFather chat and tell you; then run
+    `clipboardCommand` from the output (`store-token --from-clipboard`). It validates the token,
+    stores it, never prints it, and clears the clipboard. On `stored: false`, say what `message`
+    reports and ask them to copy it again.
+  - **Separate terminal app:** print `command` and ask them to run it in Terminal, iTerm or similar,
+    outside the agent, where it prompts with echo off. Wait for them to confirm.
 - `empty` / `invalid`: say what was wrong and ask again.
 
 Never ask for the token in chat, never echo, log or commit it, and never put it in
@@ -99,14 +120,24 @@ If `.lisa/automations/session-manager.runbook.md` does not exist, copy
 `$SM/../references/runbook-template.md` there. Never overwrite an existing runbook: it is the
 project's. It is checked in, like every automation runbook (`automation-runbook-contract`).
 
-## Step 7: Coexistence warning
-
-Tell the operator, before starting: if this project also runs the scheduled `intake-repair` loop, it
-can re-dispatch an item a local worker is still building (it treats a claimed item with no tracker
-activity for `intake.repair.staleAfterHours` as stalled). `intake-tickets` competes for the same
-Ready items. Recommend tearing down `intake-tickets` (`/lisa:tear-down-automations intake-tickets`)
-and either raising `intake.repair.staleAfterHours` above `stall.noOutputMinutes × stall.maxAttempts`
-or tearing down `intake-repair`.
+## Step 7: Check for competing intake loops
+
+The scheduled `intake-repair` loop can re-dispatch an item a local worker is still building (it treats
+a claimed item with no tracker activity for `intake.repair.staleAfterHours` as stalled), and
+`intake-tickets` competes for the same Ready items. Find out whether either is running before you
+start the manager; do not leave the operator to check.
+
+1. Run `node "$SM/session-manager.mjs" coexistence --project-root "$ROOT"`. For each loop it reports
+   the last run recorded in this project's run log and whether that is `recent`. `live` lists the
+   loops that ran recently.
+2. A run log is evidence, not proof: also list your runtime's scheduler for those loop names (Claude
+   Code: the `/schedule` listing of claude.ai routines; Codex: automations; a `lisa-<loop>.yml`
+   workflow with a `schedule:` trigger on GitHub Actions).
+3. Report what you found, per loop, in one line each. Only for a loop that is live (a recent run, or a
+   scheduler entry): recommend tearing down `intake-tickets` (`/lisa:tear-down-automations
+   intake-tickets`) and either raising `intake.repair.staleAfterHours` above
+   `stall.noOutputMinutes × stall.maxAttempts` or tearing down `intake-repair`. When neither is live,
+   say so and move on.
 
 ## Step 8: Accept workspace trust in each worker repo
 
@@ -115,12 +146,15 @@ folder?" prompt: until someone has accepted it in a directory, `claude --bg` ref
 and `spawn` exits 2 saying so. Do this once per routed repo (or once for the root on a single-repo
 project), on every machine that runs the manager:
 
-1. List the directories workers start in. Single-repo: the project root. Multi-repo: for each key in
-   `sessionManager.repos.entries`,
-   `node "$SM/session-manager.mjs" repo-dir --repo <key> --raw --project-root "$ROOT"`.
-2. Ask the operator, in their own terminal, to run `claude` once in that directory,
-   accept the trust prompt, then exit. An agent's Bash cannot answer that prompt, so never try to
-   accept it for them.
+1. Run `node "$SM/session-manager.mjs" trust-status --project-root "$ROOT"`. It lists every
+   directory workers start in (each routed repo, or the root on a single-repo project) with whether
+   Claude Code has already recorded trust for it. `needsTrust` lists the ones that are not
+   `trusted: true`. When it is empty, this step is done: say so.
+2. For each directory in `needsTrust`, ask the operator, in a separate terminal app (not the agent's
+   Bash or Claude Code's `!` prefix), to run `claude` once in that directory, accept the trust prompt,
+   then exit. An agent's Bash cannot answer that prompt, so never try to accept it for them. Then
+   re-run `trust-status` to confirm. (`trusted: "unknown"` means Claude Code's state file could not be
+   read; treat it as needing trust.)
 3. Re-run this step whenever a repo is added to `sessionManager.repos`.
 
 ## Step 9: Start and pair
@@ -154,5 +188,6 @@ confirm the "Session manager Telegram isolation?" check is green. Fix every warn
 `node "$SM/session-manager.mjs" status --project-root "$ROOT"` should show the manager running.
 
 Report: the config block written (or kept), where the token lives (the path, never the value), the
-plugin scope result, the runbook path, which repo dirs had workspace trust accepted, the manager's
-tmux session name, and the doctor result.
+plugin scope result, the runbook path, which repo dirs were already trusted and which the operator
+accepted trust in, what the competing-loop check found, the manager's tmux session name, and the
+doctor result.

package/plugins/lisa/rules/reference/config-resolution.md

@@ -733,6 +733,7 @@ bypassed). `/lisa:setup:session-manager` writes it, detecting a multi-repo layou
 | `sessionManager.notify.provider` | no | `telegram` | Only `telegram` is implemented. |
 | `sessionManager.notify.stateDir` | **yes** | — | This project's own Telegram state dir. Never the shared default `~/.claude/channels/telegram`, because one bot per state dir is how projects stay isolated. Setup writes `~/.claude/channels/telegram-<project>`. |
 | `sessionManager.trustedAuthorIds` | no | — | Optional list of **stable tracker user ids**, as strings: the GitHub numeric user id (`gh api users/<login> --jq .id`), the Jira `accountId`, or the Linear user id. Not logins or display names: matching compares ids, so a login silently matches no one and excludes every item. When set, the manager takes only items authored by these people. |
+| `sessionManager.operatorIds` | no | — | Optional, non-empty list of the people the manager works for, as tracker user ids matched against the **assignee** the same way "me" is: the GitHub **login**, the Jira `accountId`, or the Linear user id, spelled exactly as the tracker API returns it (matching is case-sensitive, so look the OPERATOR up rather than typing from memory: `gh api users/<operator-login> --jq .login` returns the canonical GitHub spelling. Do not use `gh api user`, which returns whoever the credential belongs to — the agent account, when that is the case this key exists for). Dispatch order is assigned to an operator, then to "me" (the tracker credential's identity), then unassigned; items assigned to anyone else are skipped. Set it whenever the tracker credential is not the operator's own (an agent account), or the operator's Ready items are never dispatched. |
 
 - **Non-secret only.** The bot token lives in `<stateDir>/.env` (directory 0700, file 0600),
   written by setup. A credential-named field or a token-shaped value anywhere in this block is a

package/plugins/lisa/scripts/ready-queue-order.mjs

@@ -1,15 +1,20 @@
 #!/usr/bin/env node
 /**
- * Vendor-neutral Ready-queue normalization and mine-first dispatch order.
+ * Vendor-neutral Ready-queue normalization and operator-first dispatch order.
  *
  * ## Why this exists
  *
  * Intake has always taken Ready work in whatever order the tracker returned
  * it, and `intake.assignee` only NARROWS a selection — it never ranks one. A
  * dispatcher that runs several workers at once needs a stable answer to "what
- * next?": the work already assigned to me first (somebody chose me for it),
- * then unassigned work, most urgent and oldest first. Work assigned to someone
- * else is theirs, so it is excluded, never re-ordered.
+ * next?": work assigned to the operator first (the person the dispatcher works
+ * for), then work assigned to me (the identity the tracker credential belongs
+ * to, often an agent account rather than the operator), then unassigned work,
+ * most urgent and oldest first. Work assigned to anyone else is theirs, so it
+ * is excluded, never re-ordered. When the credential IS the operator's, the
+ * first two groups coincide. With "me" as the only identity, an operator whose
+ * credential is an agent account had every one of their own items excluded as
+ * someone else's (CodySwannGT/lisa#4467).
  *
  * The three trackers disagree on every field this needs — GitHub has priority
  * LABELS, Linear a native 0..4 number where 0 means "none", Jira a priority
@@ -252,12 +257,18 @@ function shape(input) {
  * Order matters only for the reason reported: an item can fail several rules,
  * and "someone else owns it" is the most useful thing to say about it.
  * @param {Record<string, any>} item
- * @param {{ me: string | null, trusted: ReadonlySet<string>, humanNeededLabel: string }} context
+ * @param {{ me: string | null, operators: ReadonlySet<string>, trusted: ReadonlySet<string>, humanNeededLabel: string }} context
  * @returns {string | null}
  */
 function exclusionReason(item, context) {
   const assignee = idOrNull(item.assigneeId);
-  if (assignee !== null && assignee !== context.me) return "assigned-to-other";
+  if (
+    assignee !== null &&
+    assignee !== context.me &&
+    !context.operators.has(assignee)
+  ) {
+    return "assigned-to-other";
+  }
   if (item.isContainer === true) return "container";
   if (
     isHumanGated({
@@ -293,20 +304,25 @@ function compareWithinGroup(left, right) {
 }
 
 /**
- * Order normalized Ready items for dispatch, mine first.
+ * Order normalized Ready items for dispatch: the operator's, then mine, then
+ * unassigned.
  *
- * Group 0 is assigned to `me`, group 1 unassigned; within a group, priority
- * rank ascending, then creation time ascending, then ref as a stable
- * tiebreak. Excluded items keep their input order. With no `me`, every
- * assigned item is someone else's — the safe direction, since claiming
- * assigned work steals it.
+ * Group 0 is assigned to an operator, group 1 to `me`, group 2 unassigned;
+ * within a group, priority rank ascending, then creation time ascending, then
+ * ref as a stable tiebreak. Excluded items keep their input order. With no
+ * `me` and no operators, every assigned item is someone else's — the safe
+ * direction, since claiming assigned work steals it.
+ *
+ * `operators` match the way `me` does, against the normalized assignee id:
+ * GitHub login, Jira accountId, Linear user id.
  * @param {readonly Record<string, any>[]} items - Normalized items
- * @param {{ me?: string | null, trustedAuthorIds?: readonly unknown[], humanNeededLabel?: string }} [options]
+ * @param {{ me?: string | null, operators?: readonly unknown[], trustedAuthorIds?: readonly unknown[], humanNeededLabel?: string }} [options]
  * @returns {{ ordered: Record<string, any>[], excluded: { ref: string, reason: string }[] }}
  */
 export function orderReadyQueue(items, options = {}) {
   const context = {
     me: idOrNull(options.me),
+    operators: new Set((options.operators ?? []).map(idOrNull).filter(Boolean)),
     trusted: new Set(
       (options.trustedAuthorIds ?? []).map(idOrNull).filter(Boolean)
     ),
@@ -319,7 +335,11 @@ export function orderReadyQueue(items, options = {}) {
   const eligible = judged
     .filter(one => one.reason === null)
     .map(one => one.item);
-  const group = item => (idOrNull(item.assigneeId) === null ? 1 : 0);
+  const group = item => {
+    const assignee = idOrNull(item.assigneeId);
+    if (assignee === null) return 2;
+    return context.operators.has(assignee) ? 0 : 1;
+  };
 
   return {
     ordered: [...eligible].sort(

package/plugins/lisa/skills/lisa-secrets-access/scripts/validate-config.mjs

@@ -727,6 +727,35 @@ function findCredentials(value, path) {
   );
 }
 
+/**
+ * Validate `sessionManager.operatorIds`: the people the manager works for,
+ * whose assigned items it dispatches first. Matched against the assignee the
+ * way "me" is, so the GitHub entry is a login, not the numeric id
+ * `trustedAuthorIds` takes. An empty list reads as configured but names no
+ * one, so it is refused like an empty `trustedAuthorIds`.
+ * @param {unknown} ids The value, if present.
+ * @returns {string[]} Problems found.
+ */
+function validateOperatorIds(ids) {
+  if (ids === undefined) return [];
+  if (
+    !Array.isArray(ids) ||
+    !ids.every(id => typeof id === "string" && id.trim() !== "")
+  ) {
+    return [
+      `sessionManager.operatorIds must be an array of tracker user ids as ` +
+        `strings, matched against the assignee: the GitHub login, the Jira ` +
+        `accountId or the Linear user id.`,
+    ];
+  }
+  return ids.length === 0
+    ? [
+        `sessionManager.operatorIds must name at least one person. Remove ` +
+          `the key instead if the manager works only for its own identity.`,
+      ]
+    : [];
+}
+
 /**
  * Validate the opt-in `sessionManager` block.
  *
@@ -786,6 +815,7 @@ export function validateSessionManager(block) {
             `if every author's item may be dispatched.`,
         ]
       : []),
+    ...validateOperatorIds(block.operatorIds),
     ...findCredentials(block, "sessionManager"),
   ];
 }

package/plugins/lisa/skills/lisa-session-manager/SKILL.md

@@ -23,9 +23,9 @@ channels (Telegram) and cross-session messaging (`SendMessage`, `crossSessionInb
 | Runtime | lisa-setup-session-manager | lisa-session-manager (manager) | `managedBy=` |
 |---|---|---|---|
 | Claude Code | supported | supported (reference). Needs `claude` ≥ 2.1.224, `tmux`, `bun` | supported |
-| Codex | config, token and runbook are supported. `start` launches a Claude Code manager, so it works when the `claude` CLI is installed | the skill ships, but `cycle` refuses to run here (no `/loop`, channels or `SendMessage`); tell the operator to run `start` | rejected with the gap message |
+| Codex | config, token (prompt or `--from-clipboard`), runbook, `trust-status` and `coexistence` are supported. `trust-status` reads Claude Code's trust record, which is the one that matters (workers are Claude Code); accepting trust needs the `claude` CLI. `coexistence` sees only run logs, so also list Codex automations. `start` launches a Claude Code manager, so it works when the `claude` CLI is installed | the skill ships, but `cycle` refuses to run here (no `/loop`, channels or `SendMessage`); tell the operator to run `start` | rejected with the gap message |
 | Cursor / Antigravity (agy) / Copilot / Devin | same as Codex | same as Codex | rejected |
-| OpenCode | config and token are supported; script resolution relies on the npm rung, so `queue` and `record-cycle` need the npm package | gap | rejected |
+| OpenCode | same setup subcommands as Codex, but script resolution relies on the npm rung: the CLI imports plugin-level scripts the skill-folder copy lacks, so every subcommand needs the npm package | gap | rejected |
 
 On any runtime other than Claude Code, `cycle` stops with: "The session manager runs on Claude Code
 only (background sessions, channels, cross-session messaging). Run `/lisa:session-manager start`
@@ -66,7 +66,12 @@ the manager.
   claims go through `lisa-tracker-claim`. Never call a vendor API around them.
 - **"Me".** Resolve once per manager run and store it with `ledger control --me <id>`: GitHub
   `gh api user --jq .login`; Jira the accountId from the `lisa-atlassian-access` identity probe;
-  Linear `viewer.id` through `lisa-linear-access`.
+  Linear `viewer.id` through `lisa-linear-access`. "Me" is whoever the tracker credential belongs
+  to, which is often an agent account.
+- **Operators.** `sessionManager.operatorIds` names the people the manager works for (the same
+  kind of id as "me": GitHub login, Jira accountId, Linear user id). Their assigned items come
+  first, then items assigned to "me", then unassigned. Items assigned to anyone else are never
+  dispatched. Never treat an operator's item as someone else's.
 - **Workers** start only through `spawn`. The worker prompt is exactly
   `/lisa:implement <REF> managedBy=<manager-name>`; `lisa-implement` owns what `managedBy=` means.
   Never start a worker another way, and never reuse a worker for another item or a new attempt.
@@ -207,8 +212,8 @@ Skip while `capacity` reports `paused`. Otherwise:
      Raw Jira issues carry `key` and `fields` (summary, priority, assignee, created, labels,
      description, reporter, issuetype, subtasks); raw Linear nodes carry identifier, title, priority,
      createdAt, assignee, labels, description, creator and children with their state type.
-   - `ordered` is the dispatch order (mine, then unassigned, then priority, then age). `excluded`
-     needs no action.
+   - `ordered` is the dispatch order: assigned to an operator, then to "me", then unassigned; each
+     group by priority, then age. `excluded` needs no action.
 2. **While `capacity` says `can_spawn`** and items remain, take the next item that has no pending
    question in the ledger:
    1. Read it fully (`lisa-tracker-read`): title, description, labels, project, parent, comments.
@@ -223,9 +228,11 @@ Skip while `capacity` reports `paused`. Otherwise:
       `cd "$(node "$SM/session-manager.mjs" repo-dir --repo <key> --raw --project-root "$ROOT")"`
       (omit `--repo` on a single-repo project), invoke `lisa-tracker-claim <ref>`, then
       `cd "$ROOT" && pwd` and confirm the path. Continue only on `claimed` or `reused` with the
-      assignee equal to "me"; anything else means skip. Then re-read the item with
-      `lisa-tracker-read`: if the re-read shows a different assignee, or shows the state did not
-      change to the `claimed` role, skip it (someone else holds it, or the claim did not land).
+      assignee equal to "me" or to one of `sessionManager.operatorIds` (the claim assigns only an
+      unassigned item, so an operator's item keeps the operator); anything else means skip. Then
+      re-read the item with `lisa-tracker-read`: if the re-read shows an assignee that is neither
+      "me" nor an operator, or shows the state did not change to the `claimed` role, skip it
+      (someone else holds it, or the claim did not land).
       Never spawn on the claim's word alone.
    4. **Spawn.** `spawn <ref> [--repo <key>]`.
       - exit 0: post `[<REF>] started in <repo> (<name>)` to Telegram.

package/plugins/lisa/skills/lisa-session-manager/references/runbook-template.md

@@ -18,9 +18,10 @@ session list from `claude agents`; and the project's own Telegram chat.
 
 ## Candidate selection
 
-Leaf items in the `ready` role, ordered: assigned to the operator, then unassigned, then by priority,
-then oldest. Items assigned to someone else, containers, human-held items and (when configured)
-items by untrusted authors are skipped. As many as the machine has capacity for.
+Leaf items in the `ready` role, ordered: assigned to an operator (`sessionManager.operatorIds`),
+then to the manager's own tracker identity, then unassigned; within each, by priority, then oldest.
+Items assigned to someone else, containers, human-held items and (when configured) items by
+untrusted authors are skipped. As many as the machine has capacity for.
 
 ## Scope/bounds
 

package/plugins/lisa/skills/lisa-session-manager/scripts/cli-manager.mjs

@@ -1,6 +1,7 @@
 /**
- * Manager and setup subcommands of the session-manager CLI: start, stop,
- * status, repo-dir, validate, init-config and store-token.
+ * Manager subcommands of the session-manager CLI: start, stop, status,
+ * repo-dir and validate. The setup ones (init-config, store-token,
+ * trust-status, coexistence) live in cli-setup.mjs.
  *
  * `start` hosts the manager in tmux. It refuses (exit 2) unless the bot
  * token file exists with owner-only permissions in the project's own state
@@ -11,15 +12,11 @@
  * manager's tmux session: workers hold claimed work and keep running.
  * @module session-manager/cli-manager
  */
-import { existsSync, readFileSync, writeFileSync } from "node:fs";
-import path from "node:path";
-
 import {
   CliError,
   EXIT,
   GLOBAL_CONFIG_FILE,
   asSetupError,
-  asSetupErrorAsync,
   intFlag,
   listAgents,
   loadProject,
@@ -28,12 +25,8 @@ import {
   requireLisaRepo,
   run,
 } from "./cli-runtime.mjs";
-import { buildDefaultBlock, detectRepos, resolveRepoDir } from "./config.mjs";
-import {
-  defaultProjectSlug,
-  probeOwnSession,
-  sessionSurvives,
-} from "./isolation.mjs";
+import { resolveRepoDir } from "./config.mjs";
+import { probeOwnSession, sessionSurvives } from "./isolation.mjs";
 import {
   assertTokenPresent,
   buildForegroundCommand,
@@ -41,7 +34,6 @@ import {
   buildManagerLaunch,
   buildStopManager,
   resolveStateDir,
-  storeToken as storeTokenFile,
 } from "./launch.mjs";
 import { readLedger } from "./ledger.mjs";
 import { parseWorkerName, scrubWorkerEnv } from "./workers.mjs";
@@ -208,69 +200,6 @@ export function validate(ctx) {
   };
 }
 
-/**
- * `init-config [--slug <slug>] [--write]`: the default block for this
- * project, written to `.lisa.config.json` only with `--write` and only when
- * no block exists. Non-secret fields only; the token never goes here.
- * @param {object} ctx - CLI context
- * @returns {{ json: object }} `{written,block,...}`
- */
-export function initConfig(ctx) {
-  const { global } = loadProject(ctx.root);
-  if (global?.sessionManager) {
-    return {
-      json: { written: false, reason: "exists", block: global.sessionManager },
-    };
-  }
-  const slug =
-    ctx.values.slug ?? defaultProjectSlug(ctx.root, global?.github?.repo);
-  const block = asSetupError(() =>
-    buildDefaultBlock({
-      projectSlug: slug,
-      detectedRepos: detectRepos(ctx.root),
-    })
-  );
-  if (!ctx.values.write) return { json: { written: false, block } };
-
-  const file = path.join(ctx.root, GLOBAL_CONFIG_FILE);
-  if (!existsSync(file)) {
-    throw new CliError(
-      `${file} does not exist; set up Lisa in this project first.`,
-      EXIT.SETUP
-    );
-  }
-  const current = JSON.parse(readFileSync(file, "utf8"));
-  writeFileSync(
-    file,
-    `${JSON.stringify({ ...current, sessionManager: block }, null, 2)}\n`
-  );
-  return { json: { written: true, path: file, block } };
-}
-
-/**
- * `store-token [--replace]`: prompt for the bot token on the operator's
- * terminal and write `<stateDir>/.env`. An existing token is kept (exit 2)
- * unless `--replace` is given. With no TTY it prints the command the operator
- * must run themselves and exits 0 with `stored:false`.
- * @param {object} ctx - CLI context
- * @returns {Promise<{ json: object, exitCode: number }>} Outcome
- */
-export async function storeToken(ctx) {
-  const config = requireConfig(ctx);
-  const result = await asSetupErrorAsync(() =>
-    storeTokenFile({
-      stateDir: config.notify?.stateDir,
-      scriptsDir: ctx.scriptsDir,
-      projectRoot: ctx.root,
-      replace: ctx.values.replace === true,
-      env: ctx.env,
-      homedir: ctx.homedir,
-    })
-  );
-  const refused = result.stored === false && result.reason !== "no-tty";
-  return { json: result, exitCode: refused ? EXIT.SETUP : EXIT.OK };
-}
-
 /**
  * `status`: is the manager's tmux session up, and what does the ledger say
  * about each worker it dispatched.