@songsid/agend 2.1.5 → 2.1.6-beta.10

package/dist/general-knowledge/skills/credential-profiles/SKILL.md

@@ -0,0 +1,145 @@
+---
+name: credential-profiles
+description: Run agents on more than one subscription of the same backend. Use when someone asks for a worker on a different account, wants an agent moved to another subscription, or asks which subscription an agent is using. Currently kiro-cli only.
+roles: [general]
+---
+
+# Credential Profiles
+
+One AgEnD fleet normally shares one login per backend. A **credential profile**
+is a named, separate login for the same backend, so two agents can run on two
+subscriptions at once.
+
+`kiro-cli` and `codex` have profiles today. For any other backend, say so rather
+than setting an option that will be ignored.
+
+**The two behave differently when you switch, and it is not a setting.** Kiro
+keeps its conversations inside the same database as its login, so a different
+subscription is a different set of them: switching is a new conversation. Codex
+keeps its login in one file beside conversation stores that carry no account, so
+switching leaves the history where it is and both subscriptions see it. Say
+which one you are talking about.
+
+## Is a profile already set up?
+
+A profile exists once someone has logged into it on the host. AgEnD cannot log
+in for them: the login is a browser device flow.
+
+**A switch to a profile that has never been logged in is refused**, and the
+error carries the exact command to run. This is deliberate: kiro-cli does not
+start a signed-out session, it stops at "let's get you signed in!" and waits for
+a keypress, so the agent would sit on a login screen instead of working. Relay
+the command, do not try to work around the refusal.
+
+Ask the operator to run this on the host once per subscription:
+
+```
+XDG_DATA_HOME="${AGEND_HOME:-~/.agend}/credential-profiles/kiro-cli/<profile>" kiro-cli login
+```
+
+For codex the variable and the path are different:
+
+```
+CODEX_HOME="${AGEND_HOME:-~/.agend}/credential-profiles/codex/<profile>" codex login
+```
+
+## Create a worker on another subscription
+
+```
+create_instance(
+  name: "research-b",
+  working_directory: "/home/you/projects/app",
+  backend: "kiro-cli",
+  backend_options: { "kiro-cli": { "credential_profile": "personal" } },
+)
+```
+
+The profile name is yours to choose — `work`, `personal`, `team-b`. Reuse the
+same name for every agent that should share that subscription.
+
+## Move an existing agent to another subscription
+
+```
+update_instance_config(
+  name: "research-a",
+  config: { backend_options: { "kiro-cli": { "credential_profile": "personal" } } },
+)
+```
+
+The credentials are read when the CLI starts, so **the instance is restarted
+for you** and the reply says `restarted: true`.
+
+**For kiro**, a switch is always a **new conversation**, and the reply says so
+(`conversation_carried_over: false`). kiro keeps its conversations in the same
+database as its login, so a different subscription has a different set of them
+and there is nothing to resume — AgEnD does not even try. What it does instead
+is hand the new session a summary of what the old one was doing
+(`handover_chars` says how much), so the agent can pick the work up without the
+transcript. Tell the user plainly: the agent restarted on the other
+subscription, it knows what it was doing, it cannot quote what was said.
+
+**For codex** the reply says `conversation_carried_over: true` and carries a
+`conversation_note`. Relay it as what it is — a statement about where the
+history lives, not a promise about what happens next. The accurate sentence is
+"codex keeps its history outside the login, so both subscriptions share it".
+**Do not promise the agent will pick the thread back up**: whether codex reopens
+a conversation recorded under a different account has not been tested yet. If it
+does not, the agent starts a fresh conversation and carries on — nothing breaks,
+it just does not continue.
+
+`backend_options` merges per backend, so setting a kiro option leaves a codex
+option on the same instance alone.
+
+## Move an agent back to the default login
+
+A merge cannot remove a key, so send `null` for it:
+
+```
+update_instance_config(
+  name: "research-a",
+  config: { backend_options: { "kiro-cli": { "credential_profile": null } } },
+)
+```
+
+The agent goes back to the login the host uses with no profile set, and is
+restarted for the same reason as any other switch.
+
+## Answer "which subscription is this agent on?"
+
+Read it from the instance config (`get_fleet_config` or `describe_instance`):
+`backend_options["kiro-cli"].credential_profile`. **No profile means the shared
+login** — the one `kiro-cli login` uses on the host with no environment set.
+Say "the default login", not "no subscription".
+
+## Answer "how much is left on each subscription?"
+
+`get_usage` returns one row per subscription: `Kiro (work)` and
+`Kiro (personal)` rather than a single `Kiro`. Read them out separately — they
+are two quotas, and adding them together would give a number that is true of
+neither. An agent with no profile appears under the plain `Kiro` row.
+
+A profile that is configured but has never been logged in still gets a row,
+reading **Signed out — run `kiro-cli` to log in**. That is the reminder to go
+and log it in, so report it as such rather than as a missing subscription.
+
+## What to tell the user
+
+- Two agents with the same profile name share one login and one quota.
+- An agent with no profile uses the fleet's default login, exactly as before.
+- Quotas only add up if the profiles are genuinely different billing accounts.
+  Two profiles logged into the same account do not double anything, and it is
+  worth saying so before someone sets this up expecting more headroom.
+- Switching a profile does not carry the conversation across; the agent gets a
+  summary of the work, not the transcript. Say anything that must survive
+  verbatim in the channel before switching.
+
+## Do not
+
+- Do not invent a profile that has never been logged in and report success —
+  the switch is refused, and the refusal tells you what to relay.
+- Do not set `credential_profile` for a backend other than `kiro-cli` or
+  `codex`; it is ignored, and the config validator warns about it.
+- Do not tell a codex user their conversation will definitely continue across a
+  switch. Say the history is shared; that part is verified.
+- Do not use a profile name with slashes or spaces — it becomes a directory
+  name and is rejected.

package/dist/general-knowledge/skills/worker-collaboration/SKILL.md

@@ -10,7 +10,17 @@ roles: [worker]
 
 - Treat the assignment as the full scope unless the sender explicitly expands it.
 - Work without acknowledgment-only messages. Silence means the task is in progress.
-- Do not call `delegate_task`; delegation and fleet orchestration belong to General.
+- Fleet orchestration is not yours: you do not have `create_instance`,
+  `delete_instance`, `restart_instance`, `deploy_template`, the team tools, or
+  the tools that create, change or delete schedules. Calling one is refused
+  with an explanation rather than silently ignored. If the work needs more
+  capacity or another agent restarted, say so with `report_result` and let the
+  coordinator decide.
+- You can still *look*: `list_schedules`, `list_deployments`, `list_instances`
+  and the other read-only queries are yours, so check before asking.
+- You *can* `delegate_task`, because it only hands work to an instance that
+  already exists. Prefer reporting back over delegating sideways unless the
+  assignment said otherwise — delegation belongs to whoever is coordinating.
 
 ## Request missing information
 

package/dist/instance-config-impact.d.ts

@@ -0,0 +1,55 @@
+import type { InstanceConfig } from "./types.js";
+/** ⚡ applied to the running agent / 🔄 restart the agent / 🔄🔄 restart AgEnD. */
+export type ConfigImpact = "now" | "instance" | "fleet";
+/** Cheapest first. A batch of edits costs as much as its worst member. */
+export declare const IMPACT_ORDER: readonly ConfigImpact[];
+/**
+ * Instance settings a live daemon can take without a restart.
+ *
+ * Adding a key here is only half the change: `Daemon.applyConfigUpdate` has to
+ * learn it too, or the setting is written to disk, reported as applied, and
+ * silently ignored by the running agent. `tests/hot-cold-parity.test.ts` fails
+ * when the two drift.
+ */
+export declare const HOT_INSTANCE_CONFIG_KEYS: ReadonlySet<keyof InstanceConfig>;
+/**
+ * The hot keys a ClassicBot channel edit can use.
+ *
+ * Narrower than the fleet-wide set because a classic channel's hot path carries
+ * exactly what `FleetManager.classicBehaviorUpdate()` builds; a key that is hot
+ * for a fleet instance but absent from that payload (auto_pause_after) would be
+ * dropped on the way. Derived, not re-listed: dropping a key from the hot set
+ * drops it here too.
+ */
+export declare const CLASSIC_HOT_CONFIG_KEYS: ReadonlySet<string>;
+/** Split a config into what a live daemon can take and what needs a restart. */
+export declare function splitHotColdConfig(config: InstanceConfig): {
+    hot: Partial<InstanceConfig>;
+    cold: Partial<InstanceConfig>;
+};
+/** The complete hot snapshot sent over IPC; absent values are explicit nulls so
+ * the daemon removes them rather than keeping a stale override. */
+export declare function hotConfigUpdate(config: InstanceConfig): Record<string, unknown>;
+/**
+ * What applying `next` to a running instance costs.
+ *
+ * The one comparison `reconcileInstances` makes when it decides between an IPC
+ * hot update and a stop/start — shared so the apply job's plan says what the
+ * reconcile will actually do rather than holding a second opinion about it.
+ */
+export declare function classifyInstanceChange(runtime: InstanceConfig, next: InstanceConfig): "restart" | "hot" | "none";
+export declare function instanceFieldImpact(key: string): ConfigImpact;
+export declare function classicFieldImpact(key: string): ConfigImpact;
+/**
+ * Impact of one staged edit: hot only while every changed key is hot, since a
+ * single cold key in the batch forces the restart anyway.
+ */
+export declare function batchImpact(keys: readonly string[], impactOf: (key: string) => ConfigImpact): ConfigImpact;
+export interface SettingsImpactSchema {
+    /** field path → impact, e.g. `instance.tool_progress` → "now". */
+    impacts: Record<string, ConfigImpact>;
+    /** Escalation order, so the page can cost a batch without knowing the rule. */
+    order: readonly ConfigImpact[];
+}
+/** The payload behind `GET /api/settings/schema`. */
+export declare function buildSettingsImpactSchema(): SettingsImpactSchema;

package/dist/instance-config-impact.js

@@ -0,0 +1,152 @@
+/**
+ * One source of truth for "what does changing this setting cost?".
+ *
+ * `HOT_INSTANCE_CONFIG_KEYS` is the authority: a hot key is pushed into a live
+ * daemon over IPC (`Daemon.applyConfigUpdate`), anything else needs the CLI
+ * process restarted. That knowledge used to be spelled out in five places —
+ * the fleet manager, the settings API, twice in the settings page, and once per
+ * field as a hand-written badge — so the four copies could drift away from the
+ * one that decides what actually happens.
+ *
+ * Everything here is derived from the two sets below. The settings page reads
+ * it from `GET /api/settings/schema` instead of carrying its own copy.
+ */
+import { isDeepStrictEqual } from "node:util";
+/** Cheapest first. A batch of edits costs as much as its worst member. */
+export const IMPACT_ORDER = ["now", "instance", "fleet"];
+/**
+ * Instance settings a live daemon can take without a restart.
+ *
+ * Adding a key here is only half the change: `Daemon.applyConfigUpdate` has to
+ * learn it too, or the setting is written to disk, reported as applied, and
+ * silently ignored by the running agent. `tests/hot-cold-parity.test.ts` fails
+ * when the two drift.
+ */
+export const HOT_INSTANCE_CONFIG_KEYS = new Set([
+    "tool_progress",
+    "reply_completion_guard",
+    "mcp_proxy_reply",
+    "auto_pause_after",
+    "warm_cap",
+    "display_name",
+    "description",
+    "tags",
+    "log_level",
+]);
+/**
+ * The hot keys a ClassicBot channel edit can use.
+ *
+ * Narrower than the fleet-wide set because a classic channel's hot path carries
+ * exactly what `FleetManager.classicBehaviorUpdate()` builds; a key that is hot
+ * for a fleet instance but absent from that payload (auto_pause_after) would be
+ * dropped on the way. Derived, not re-listed: dropping a key from the hot set
+ * drops it here too.
+ */
+export const CLASSIC_HOT_CONFIG_KEYS = new Set(["tool_progress", "reply_completion_guard"]
+    .filter(key => HOT_INSTANCE_CONFIG_KEYS.has(key)));
+/**
+ * Instance keys that are not the instance's own business: they change how the
+ * fleet binds and routes the instance, so the fleet process has to restart.
+ */
+const FLEET_SCOPED_INSTANCE_KEYS = new Set([
+    "topic_id",
+    "channel_id",
+    "general_topic",
+]);
+/** Instance-scoped fields the settings page renders. */
+const INSTANCE_FIELDS = [
+    "display_name", "description", "backend", "model", "working_directory",
+    "auto_pause_after", "warm_cap", "topic_id", "channel_id", "general_topic",
+    "tool_progress", "reply_completion_guard", "mcp_proxy_reply", "log_level",
+    "systemPrompt", "tags", "hang_detector", "agent_mode", "tool_set",
+    "lightweight", "model_failover", "effort", "pre_task_command",
+];
+/** ClassicBot channel fields the settings page renders. */
+const CLASSIC_FIELDS = [
+    "backend", "model", "auto_pause_after", "tool_progress",
+    "reply_completion_guard", "collab", "context_lines", "pre_task_command",
+];
+/**
+ * Fleet-level fields, which no per-key rule can derive: they belong to the
+ * fleet process or the channel binding rather than to an instance's config.
+ */
+const FLEET_FIELD_IMPACTS = {
+    "defaults.locale": "now",
+    "fleet.channels": "fleet",
+    "fleet.channel.access.mode": "fleet",
+    "fleet.channel.access.allowed_users": "fleet",
+    "fleet.spawn_concurrency": "fleet",
+    "fleet.spawn_stagger_ms": "fleet",
+    "classic.admin_users": "fleet",
+    "classic.allowed_guilds": "fleet",
+    "instance.delete": "fleet",
+};
+/** Split a config into what a live daemon can take and what needs a restart. */
+export function splitHotColdConfig(config) {
+    const hot = {};
+    const cold = {};
+    for (const [key, value] of Object.entries(config)) {
+        (HOT_INSTANCE_CONFIG_KEYS.has(key) ? hot : cold)[key] = value;
+    }
+    return { hot, cold };
+}
+/** The complete hot snapshot sent over IPC; absent values are explicit nulls so
+ * the daemon removes them rather than keeping a stale override. */
+export function hotConfigUpdate(config) {
+    const update = {};
+    for (const key of HOT_INSTANCE_CONFIG_KEYS)
+        update[key] = config[key] ?? null;
+    return update;
+}
+/**
+ * What applying `next` to a running instance costs.
+ *
+ * The one comparison `reconcileInstances` makes when it decides between an IPC
+ * hot update and a stop/start — shared so the apply job's plan says what the
+ * reconcile will actually do rather than holding a second opinion about it.
+ */
+export function classifyInstanceChange(runtime, next) {
+    const before = splitHotColdConfig(runtime);
+    const after = splitHotColdConfig(next);
+    // Every field not explicitly classified hot is cold by default.
+    if (!isDeepStrictEqual(before.cold, after.cold))
+        return "restart";
+    if (!isDeepStrictEqual(before.hot, after.hot))
+        return "hot";
+    return "none";
+}
+export function instanceFieldImpact(key) {
+    if (FLEET_SCOPED_INSTANCE_KEYS.has(key))
+        return "fleet";
+    return HOT_INSTANCE_CONFIG_KEYS.has(key) ? "now" : "instance";
+}
+export function classicFieldImpact(key) {
+    return CLASSIC_HOT_CONFIG_KEYS.has(key) ? "now" : "instance";
+}
+/**
+ * Impact of one staged edit: hot only while every changed key is hot, since a
+ * single cold key in the batch forces the restart anyway.
+ */
+export function batchImpact(keys, impactOf) {
+    let worst = 0;
+    for (const key of keys)
+        worst = Math.max(worst, IMPACT_ORDER.indexOf(impactOf(key)));
+    return IMPACT_ORDER[worst];
+}
+/** The payload behind `GET /api/settings/schema`. */
+export function buildSettingsImpactSchema() {
+    const impacts = { ...FLEET_FIELD_IMPACTS };
+    for (const key of INSTANCE_FIELDS) {
+        impacts[`instance.${key}`] = instanceFieldImpact(key);
+        // Fleet defaults carry the same restart cost as the instance field they
+        // seed — except the fleet-scoped ones, which are not defaults at all.
+        if (!FLEET_SCOPED_INSTANCE_KEYS.has(key))
+            impacts[`defaults.${key}`] = instanceFieldImpact(key);
+    }
+    for (const key of CLASSIC_FIELDS) {
+        impacts[`classic.${key}`] = classicFieldImpact(key);
+        impacts[`classic_defaults.${key}`] = classicFieldImpact(key);
+    }
+    return { impacts, order: IMPACT_ORDER };
+}
+//# sourceMappingURL=instance-config-impact.js.map

package/dist/instance-config-impact.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"instance-config-impact.js","sourceRoot":"","sources":["../src/instance-config-impact.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AACH,OAAO,EAAE,iBAAiB,EAAE,MAAM,WAAW,CAAC;AAM9C,0EAA0E;AAC1E,MAAM,CAAC,MAAM,YAAY,GAA4B,CAAC,KAAK,EAAE,UAAU,EAAE,OAAO,CAAC,CAAC;AAElF;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,wBAAwB,GAAsC,IAAI,GAAG,CAAuB;IACvG,eAAe;IACf,wBAAwB;IACxB,iBAAiB;IACjB,kBAAkB;IAClB,UAAU;IACV,cAAc;IACd,aAAa;IACb,MAAM;IACN,WAAW;CACZ,CAAC,CAAC;AAEH;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,uBAAuB,GAAwB,IAAI,GAAG,CAChE,CAAC,eAAe,EAAE,wBAAwB,CAAW;KACnD,MAAM,CAAC,GAAG,CAAC,EAAE,CAAC,wBAAwB,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,CACpD,CAAC;AAEF;;;GAGG;AACH,MAAM,0BAA0B,GAAwB,IAAI,GAAG,CAAC;IAC9D,UAAU;IACV,YAAY;IACZ,eAAe;CAChB,CAAC,CAAC;AAEH,wDAAwD;AACxD,MAAM,eAAe,GAAG;IACtB,cAAc,EAAE,aAAa,EAAE,SAAS,EAAE,OAAO,EAAE,mBAAmB;IACtE,kBAAkB,EAAE,UAAU,EAAE,UAAU,EAAE,YAAY,EAAE,eAAe;IACzE,eAAe,EAAE,wBAAwB,EAAE,iBAAiB,EAAE,WAAW;IACzE,cAAc,EAAE,MAAM,EAAE,eAAe,EAAE,YAAY,EAAE,UAAU;IACjE,aAAa,EAAE,gBAAgB,EAAE,QAAQ,EAAE,kBAAkB;CACrD,CAAC;AAEX,2DAA2D;AAC3D,MAAM,cAAc,GAAG;IACrB,SAAS,EAAE,OAAO,EAAE,kBAAkB,EAAE,eAAe;IACvD,wBAAwB,EAAE,QAAQ,EAAE,eAAe,EAAE,kBAAkB;CAC/D,CAAC;AAEX;;;GAGG;AACH,MAAM,mBAAmB,GAA2C;IAClE,iBAAiB,EAAE,KAAK;IACxB,gBAAgB,EAAE,OAAO;IACzB,2BAA2B,EAAE,OAAO;IACpC,oCAAoC,EAAE,OAAO;IAC7C,yBAAyB,EAAE,OAAO;IAClC,wBAAwB,EAAE,OAAO;IACjC,qBAAqB,EAAE,OAAO;IAC9B,wBAAwB,EAAE,OAAO;IACjC,iBAAiB,EAAE,OAAO;CAC3B,CAAC;AAEF,gFAAgF;AAChF,MAAM,UAAU,kBAAkB,CAAC,MAAsB;IAIvD,MAAM,GAAG,GAA4B,EAAE,CAAC;IACxC,MAAM,IAAI,GAA4B,EAAE,CAAC;IACzC,KAAK,MAAM,CAAC,GAAG,EAAE,KAAK,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,MAAM,CAAwE,EAAE,CAAC;QACzH,CAAC,wBAAwB,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,GAAG,CAAC,GAAG,KAAc,CAAC;IACzE,CAAC;IACD,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,CAAC;AACvB,CAAC;AAED;mEACmE;AACnE,MAAM,UAAU,eAAe,CAAC,MAAsB;IACpD,MAAM,MAAM,GAA4B,EAAE,CAAC;IAC3C,KAAK,MAAM,GAAG,IAAI,wBAAwB;QAAE,MAAM,CAAC,GAAG,CAAC,GAAG,MAAM,CAAC,GAAG,CAAC,IAAI,IAAI,CAAC;IAC9E,OAAO,MAAM,CAAC;AAChB,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,sBAAsB,CACpC,OAAuB,EACvB,IAAoB;IAEpB,MAAM,MAAM,GAAG,kBAAkB,CAAC,OAAO,CAAC,CAAC;IAC3C,MAAM,KAAK,GAAG,kBAAkB,CAAC,IAAI,CAAC,CAAC;IACvC,gEAAgE;IAChE,IAAI,CAAC,iBAAiB,CAAC,MAAM,CAAC,IAAI,EAAE,KAAK,CAAC,IAAI,CAAC;QAAE,OAAO,SAAS,CAAC;IAClE,IAAI,CAAC,iBAAiB,CAAC,MAAM,CAAC,GAAG,EAAE,KAAK,CAAC,GAAG,CAAC;QAAE,OAAO,KAAK,CAAC;IAC5D,OAAO,MAAM,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,mBAAmB,CAAC,GAAW;IAC7C,IAAI,0BAA0B,CAAC,GAAG,CAAC,GAAG,CAAC;QAAE,OAAO,OAAO,CAAC;IACxD,OAAO,wBAAwB,CAAC,GAAG,CAAC,GAA2B,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,UAAU,CAAC;AACxF,CAAC;AAED,MAAM,UAAU,kBAAkB,CAAC,GAAW;IAC5C,OAAO,uBAAuB,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,UAAU,CAAC;AAC/D,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,WAAW,CAAC,IAAuB,EAAE,QAAuC;IAC1F,IAAI,KAAK,GAAG,CAAC,CAAC;IACd,KAAK,MAAM,GAAG,IAAI,IAAI;QAAE,KAAK,GAAG,IAAI,CAAC,GAAG,CAAC,KAAK,EAAE,YAAY,CAAC,OAAO,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC;IACrF,OAAO,YAAY,CAAC,KAAK,CAAE,CAAC;AAC9B,CAAC;AASD,qDAAqD;AACrD,MAAM,UAAU,yBAAyB;IACvC,MAAM,OAAO,GAAiC,EAAE,GAAG,mBAAmB,EAAE,CAAC;IACzE,KAAK,MAAM,GAAG,IAAI,eAAe,EAAE,CAAC;QAClC,OAAO,CAAC,YAAY,GAAG,EAAE,CAAC,GAAG,mBAAmB,CAAC,GAAG,CAAC,CAAC;QACtD,wEAAwE;QACxE,sEAAsE;QACtE,IAAI,CAAC,0BAA0B,CAAC,GAAG,CAAC,GAAG,CAAC;YAAE,OAAO,CAAC,YAAY,GAAG,EAAE,CAAC,GAAG,mBAAmB,CAAC,GAAG,CAAC,CAAC;IAClG,CAAC;IACD,KAAK,MAAM,GAAG,IAAI,cAAc,EAAE,CAAC;QACjC,OAAO,CAAC,WAAW,GAAG,EAAE,CAAC,GAAG,kBAAkB,CAAC,GAAG,CAAC,CAAC;QACpD,OAAO,CAAC,oBAAoB,GAAG,EAAE,CAAC,GAAG,kBAAkB,CAAC,GAAG,CAAC,CAAC;IAC/D,CAAC;IACD,OAAO,EAAE,OAAO,EAAE,KAAK,EAAE,YAAY,EAAE,CAAC;AAC1C,CAAC"}

package/dist/instance-lifecycle.js

@@ -27,6 +27,7 @@ export const BACKEND_INSTALLATION_INFO = {
     opencode: { binary: "opencode", install: "curl -fsSL https://opencode.ai/install | bash" },
     antigravity: { binary: "agy", install: "curl -fsSL https://antigravity.google/cli/install.sh | bash" },
     grok: { binary: "grok", install: "curl -fsSL https://x.ai/cli/install.sh | bash" },
+    muse: { binary: "muse", install: "curl -fsSL https://api.meta.ai/muse-launcher.sh | bash" },
 };
 /** Check one executable using the same PATH visible to the fleet process. */
 export function checkBinaryInstalled(binary) {
@@ -674,10 +675,13 @@ export class InstanceLifecycle {
                     this.ctx.logger.warn({ name, backend: "codex" }, "Codex quota verification failed or timed out — pausing conservatively");
                 }
             }
-            // Claude's credit-balance message also remains in pane scrollback. Only
-            // a fresh usage API row can prove it stale; provider fallback to a local
-            // statusline, timeout, or missing credentials remains fail-closed.
-            if (data.type === "quota" && data.action === "pause" && this.backendOf(name) === "claude-code") {
+            // Claude's credit-balance and hard usage-pause messages can remain in pane
+            // scrollback. Only a fresh usage API row can prove them stale; provider
+            // fallback to a local statusline, timeout, or missing credentials remains
+            // fail-closed. `verifyQuota` lets a notify-only pattern request the same
+            // second opinion without entering the destructive pause action below.
+            if (data.type === "quota" && this.backendOf(name) === "claude-code"
+                && (data.action === "pause" || data.verifyQuota)) {
                 const verdict = await this.verifyClaudeQuota();
                 if (verdict === "available") {
                     this.ctx.logger.debug({ name, backend: "claude-code" }, "quota pattern ignored — live usage has capacity (stale pane history)");