@brutalsystems/muster 0.8.2 → 0.8.3

package/README.md

@@ -66,9 +66,11 @@ used to look identical to a hung or crashed launch. Muster now reads
 `hasTrustDialogAccepted` for the working directory out of the profile's
 `.claude.json` when a Claude launch times out with nothing registered, and
 either names the untrusted directory and the one-time fix or rules trust out
-and points at the remaining consent screens — a login prompt, or the
-confirmation Claude asks for the first time a profile uses bypass-permissions
-mode. That read happens only on the failure path and only ever reads. A
+and sends you to the terminal for whatever else is holding the session — a
+login prompt, or another one-time confirmation. It deliberately does not guess
+which: trust is the only one of them Muster can check, and a message that names
+the wrong screen costs what the vague one did. That read happens only on the
+failure path and only ever reads. A
 `--kind task` launch into the same directory is the cheap discriminator by
 hand: it runs headless and never sees the dialog.
 
@@ -694,6 +696,18 @@ need it), and resume/fork (#32) cannot assume a copy is still there.
 Launching without `--identity` sets none of this: behaviour is exactly as
 before, using the ambient environment.
 
+**That is the right choice for profile work, which is counter-intuitive.** If
+you already work in a shell whose `CLAUDE_CONFIG_DIR` selects an account —
+`~/.claude-armdev`, say — a launch with no `--identity` inherits it, and the
+session lands on that account with no flag at all. `launchEnv` blocks
+`CLAUDECODE`, `CLAUDE_CODE_*`, `CODEX_THREAD_ID`, `TMUX`, `TMUX_PANE` and
+`MCP_*` from reaching the child, and deliberately lets `CLAUDE_CONFIG_DIR`
+through for exactly this reason. Passing `--identity` there does not add
+containment to that account — it **replaces** it, pointing the runtime at a
+copy of a different one, so the session appears under an account you did not
+mean to use. Reach for `--identity` to choose an account Muster manages, not to
+harden the one your shell already selected.
+
 Session discovery follows the same relocated path, so a Claude identity's
 sessions are found even though `CLAUDE_CONFIG_DIR` no longer points at
 `~/.claude` — this was previously refused outright as an unsupported

package/dist/identity/claude.js

@@ -62,10 +62,13 @@ export async function claudeWorkspaceTrusted(env, cwd) {
  *
  * A session sitting on a consent screen has no registry record at all, so the
  * timeout looks identical to a hung or crashed launch. Several unrelated
- * screens produce it — workspace trust, login, the first use of
- * bypass-permissions mode — and the old message guessed at two of them
- * together. Trust is the one Muster can actually check, so it is either named
- * or ruled out; the rest are listed only once it has been ruled out.
+ * screens can produce it, and the old message guessed at two of them together.
+ * Trust is the one Muster can actually check, so it is either named or ruled
+ * out. Nothing else is named: a first-use bypass-permissions confirmation was
+ * a plausible account of one report, but no profile on this machine carries a
+ * key for it the way they carry `hasSeenAutoModeEntryWarning` and its
+ * siblings, so this says "another one-time confirmation" rather than sending
+ * the reader after a screen nobody has demonstrated.
  *
  * A `--kind task` launch into the same directory is the cheap discriminator:
  * it runs headless and never sees the dialog, so it succeeds where a session
@@ -77,9 +80,9 @@ export function claudeRegistryDiagnostic(trusted, cwd, configDir) {
             `accepted for ${cwd} in ${configDir} — accept it once with ` +
             `\`cd ${cwd} && claude\`, then retry (trust is per-directory and is ` +
             `not inherited from a parent directory)`);
-    return (`no Claude session registry found (${cwd} is trusted, so check the ` +
-        `terminal for a login prompt, or for the one-time confirmation Claude ` +
-        `asks for the first time a profile uses bypass-permissions mode)`);
+    return (`no Claude session registry found (${cwd} is trusted for this profile, ` +
+        `so the session is stopped on something else — check the terminal for a ` +
+        `login prompt or another one-time confirmation)`);
 }
 export async function resolveClaude(root, env, deadline) {
     const dir = claudeSessionsDir(env);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brutalsystems/muster",
-  "version": "0.8.2",
+  "version": "0.8.3",
   "description": "Launch instructed, reachable local agent sessions",
   "type": "module",
   "engines": {