switchroom 0.14.0 → 0.14.2

package/dist/host-control/main.js

@@ -21276,7 +21276,7 @@ class HostdServer {
     if (req.args.deep) {
       PROBES.push({
         name: "auth_live",
-        cmd: "timeout 25 claude -p ok >/dev/null 2>&1"
+        cmd: "python3 -c 'import json,sys,time,re;" + 'c=json.load(open("/state/agent/.claude/.credentials.json"));' + 'o=c.get("claudeAiOauth",{});' + 't=o.get("accessToken","");' + 'sys.exit(0 if re.match(r"sk-ant-oat\\d+-",t)' + ' and ("expiresAt" not in o or o["expiresAt"]>time.time()*1000)' + " else 1)'"
       });
     }
     if (!running) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "switchroom",
-  "version": "0.14.0",
+  "version": "0.14.2",
   "description": "Run Claude Code 24/7 on your Claude Pro/Max subscription over Telegram. Open-source alternative to OpenClaw and NanoClaw — no API keys.",
   "type": "module",
   "bin": {

package/profiles/_shared/telegram-style.md.hbs

@@ -17,7 +17,7 @@ The one thing to avoid is **spam**: a reply on every tool call, on a cadence, or
 - **`reply`** is the default. Use for acks, mid-turn updates, sub-agent handbacks, final answers. Pass `disable_notification: true` mid-turn.
 - **`stream_reply`** is for content whose final answer benefits from streaming character-by-character (long prose, code blocks). First call sends fresh; subsequent calls edit (no ping until `done=true`). Don't use it just to "show progress" — that's what `reply` is for.
 
-The 👀→🤔→🔥→👍 status reaction and the typing indicator are *ambient* liveness — they tell the user the agent is alive and working, automatically. They do **not** replace the five beats: ambient says "alive", your `reply` messages say "here's what's happening." Different layers; both run.
+The 👀→🤔→✍→👍 status reaction and the typing indicator are *ambient* liveness — they tell the user the agent is alive and working, automatically. They do **not** replace the five beats: ambient says "alive", your `reply` messages say "here's what's happening." Different layers; both run.
 
 **Reactions ON your replies.** Sometimes you'll receive a turn whose body is wrapped in `<channel source="reaction">`. That means the user reacted to one of your earlier messages and the gateway forwarded the reaction as a synthetic turn (the message preview is included so you know which reply they reacted to). 👎 / ❌ are stop signals — pause, reconsider the approach, ask what's off. 👍 / ✅ are acknowledgements — keep going if mid-task, no extra reply needed. A brief explicit acknowledgement is fine but not required; don't ceremonially reply to every reaction. The allowlist + per-hour cap are operator-tunable (default 10/hour); other emojis you might see don't trigger turns.
 

package/telegram-plugin/auth-snapshot-format.ts

@@ -19,7 +19,7 @@
  */
 
 import type { QuotaResult, QuotaUtilization } from './quota-check.js';
-import type { AccountState, ListStateData } from '../src/auth/broker/client.js';
+import type { AccountState, LastQuotaSnapshot, ListStateData } from '../src/auth/broker/client.js';
 
 // ── shared types ─────────────────────────────────────────────────────
 
@@ -610,3 +610,49 @@ export function buildSnapshotsFromState(
   }
   return out;
 }
+
+/**
+ * Convert a broker-side `LastQuotaSnapshot` (dates as ISO strings) into a
+ * `QuotaUtilization` (dates as `Date | null`). Returns null when the
+ * input snapshot is absent or null (no probe has run since broker start).
+ *
+ * Used by the quota-watch loop to build `AccountSnapshot[]` from cached
+ * broker state without triggering a live Anthropic network call.
+ */
+export function reviveLastQuota(snap: LastQuotaSnapshot | null | undefined): QuotaUtilization | null {
+  if (!snap) return null;
+  return {
+    fiveHourUtilizationPct: snap.fiveHourUtilizationPct,
+    sevenDayUtilizationPct: snap.sevenDayUtilizationPct,
+    fiveHourResetAt: snap.fiveHourResetAt ? new Date(snap.fiveHourResetAt) : null,
+    sevenDayResetAt: snap.sevenDayResetAt ? new Date(snap.sevenDayResetAt) : null,
+    representativeClaim: snap.representativeClaim,
+    overageStatus: snap.overageStatus,
+    overageDisabledReason: snap.overageDisabledReason,
+  };
+}
+
+/**
+ * Build AccountSnapshot[] from broker listState using only the
+ * broker's in-memory last_quota cache — no live Anthropic probe.
+ * Accounts with no cached snapshot will have `quota: null`, causing
+ * `classifyHealth` to return 'unknown' and the quota-watch loop to skip them.
+ *
+ * This is the cheap classification path for the 15-minute poll loop.
+ * The live probeQuota path (`buildSnapshotsFromState`) is reserved for
+ * user-initiated /auth commands and notification body enrichment.
+ */
+export function buildSnapshotsFromCachedState(
+  state: ListStateData,
+): AccountSnapshot[] {
+  return state.accounts.map((acc) => {
+    const lq = acc.last_quota ?? null;
+    return {
+      label: acc.label,
+      isActive: acc.label === state.active,
+      quota: reviveLastQuota(lq),
+      quotaError: lq ? undefined : 'no cached quota (no probe since broker start)',
+      expiresAtMs: acc.expiresAt,
+    };
+  });
+}