@agfpd/iapeer 0.4.74 → 0.4.75

package/README.md

@@ -107,6 +107,8 @@ What this means for you:
 - You are trusting the model's judgment, and the doctrine you give each peer, the same way you would trust a developer with a shell on your account.
 - iapeer does **not** silently weaken your own interactive `claude` / `codex` setup. The bypass acceptance is recorded per peer, in that agent's own config; the project-MCP pre-approval is written **project-locally**, under the peer's folder — never to your global user settings.
 
+**Want a human in the loop for a given peer?** Set its approval mode to `gated` — `iapeer approval-mode <peer> gated`. That peer launches **without** the bypass flag, and every blocking approval its runtime would raise is routed to you — a Telegram button, a click in the tray, or `iapeer approve` on the CLI — before the tool runs; your `allow`/`deny` (with a reason) flows back and the tool proceeds or is refused. The default stays `yolo` (bypass) for every peer; `gated` is opt-in, per peer. See [docs/17 — Human approval](docs/17-approval.md).
+
 Run iapeer on a host you control, give each peer only the access it needs, and treat a peer's instructions as security-relevant. `iapeer onboard` states this at setup; it's repeated here so the trade-off is explicit before you create your first agent. Details on every first-run dialog: [docs/07 — Install & update](docs/07-install-and-update.md#first-run-dialogs-on-a-clean-machine).
 
 ## Documentation
@@ -121,8 +123,6 @@ Planned, not yet built:
 - **Linux support** — iapeer runs on macOS today; Linux is planned.
 - **More agent runtimes** — `opencode` and `antigravity`, two further CLI runtimes alongside Claude Code and Codex.
 - **Discord runtime** — a human-presence runtime for Discord, alongside Telegram.
-- **Permissions gate** — finer control over what an agent is allowed to do.
-- **Approve permissions over Telegram** — approve an agent's permission requests from the chat; today permissions are auto-allowed by flags.
 
 ## License
 

package/docs/16-tray.md

@@ -24,11 +24,16 @@ activation that also installs SwiftBar.app when it is absent.
   daemon any other way; the built-in TUI keeps its direct read path for that case, see
   [15](15-fleet-api.md)).
 - **Dropdown:** a host header (`iapeer <version> · up <uptime>`) and the memory/voice
-  provider heartbeats, then one row per peer:
+  provider heartbeats, then one row per peer, in **two groups**: the `🔒` **launchd block**
+  (the human channel + service infra — non-clickable status rows) is pulled to the **top as
+  one contiguous block, before the first working agent**, regardless of live/asleep — so the
+  bar separates "service, don't touch" from the working agents at a glance. Working agents
+  follow. Within **each** group the order is live → asleep → stopped, then alphabetical.
   - `<peer>  <runtime><glyph> …  <age>` with the same glyph semantics as the CLI —
     `●` live · `○` asleep · `✕` stopped — green when any runtime is live. Badges: `👤`
-    a human is attached, `🔒` launchd-managed (H4 read-only), `⏳N` an ephemeral peer's
-    queue depth.
+    a human is attached, `🔒` launchd-managed (H4 read-only), `🛡` the peer runs in **gated**
+    human-approval mode (docs/17; `yolo` is the fleet default and carries no badge — a bare
+    row reads as yolo), `⏳N` an ephemeral peer's queue depth.
   - **Click an agent peer → Terminal.app running `iapeer attach <peer>`.** The row itself is
     the attach action (no submenu, so a click attaches rather than merely expanding). The
     handoff goes through `iapeer tray attach-term`, which writes a per-peer `.command`

package/docs/ru/16-tray.md

@@ -22,11 +22,16 @@ SwiftBar.app, если его нет.
   покажет сломанный демон — встроенный TUI держит прямой путь чтения для этого случая, см.
   [15](15-fleet-api.md)).
 - **Выпадашка:** шапка хоста (`iapeer <версия> · up <аптайм>`) и хартбиты провайдеров памяти
-  и голоса, затем строка на пира:
+  и голоса, затем строка на пира, **двумя группами**: блок `🔒` **под launchd** (человеческий
+  канал + служебная инфра — некликабельные статус-строки) вынесен **наверх единым непрерывным
+  блоком, перед первым рабочим агентом**, независимо от live/asleep — так бар с одного взгляда
+  отделяет «служебное, не трогать» от рабочих агентов. Рабочие агенты идут следом. Внутри
+  **каждой** группы порядок: живой → спит → остановлен, затем по алфавиту.
   - `<peer>  <рантайм><глиф> …  <возраст>` с той же семантикой глифов, что в CLI —
     `●` живой · `○` спит · `✕` остановлен — зелёный, если хоть один рантайм живой. Бейджи:
-    `👤` подключён человек, `🔒` под launchd (H4 read-only), `⏳N` глубина очереди эфемерного
-    пира.
+    `👤` подключён человек, `🔒` под launchd (H4 read-only), `🛡` пир в режиме **gated**
+    human-approval (docs/17; `yolo` — дефолт флота, без бейджа: голая строка читается как yolo),
+    `⏳N` глубина очереди эфемерного пира.
   - **Клик по агент-пиру → Terminal.app с `iapeer attach <peer>`.** Строка сама и есть действие
     attach (без подменю — клик аттачит, а не раскрывает). Передача идёт через `iapeer tray
     attach-term`: пишет per-peer `.command`-лаунчер и `open`'ит его — `open <файл>.command`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agfpd/iapeer",
-  "version": "0.4.74",
+  "version": "0.4.75",
   "description": "Run Claude Code and Codex CLI as local background agents that message each other, wake on demand, and share one memory.",
   "license": "Apache-2.0",
   "author": "agfpd",

package/src/launch/index.ts

@@ -122,6 +122,24 @@ export function exitLogPath(exitLogDir: string): string {
 // launch — bring up ONE session (runtime-agnostic via the adapter)
 // ─────────────────────────────────────────────────────────────────────────────
 
+/**
+ * The intelligence gate — launch step (0), extracted as a PURE predicate so it is
+ * unit-testable in isolation (no bring-up, never touches the pty host). A channel
+ * adapter that declares `allowedIntelligences` (telegram/voicetalk → ['natural',
+ * 'absent']) refuses a peer whose nature is NOT in the set — and refuses too when
+ * the nature is unknown (cannot confirm). Returns the fail-loud reason string, or
+ * `null` when the gate PASSES (the peer may proceed to bring-up).
+ */
+export function intelligenceGateReason(adapter: RuntimeAdapter, spec: LaunchSpec): string | null {
+  if (adapter.allowedIntelligences && (spec.intelligence == null || !adapter.allowedIntelligences.includes(spec.intelligence))) {
+    return (
+      `runtime "${spec.runtime}" requires intelligence ∈ {${adapter.allowedIntelligences.join(', ')}}, ` +
+      `peer "${spec.personality}" is ${spec.intelligence ?? 'unknown'} — refusing to launch`
+    )
+  }
+  return null
+}
+
 export const launch: LaunchFn = async (
   spec: LaunchSpec,
   adapter: RuntimeAdapter,
@@ -137,13 +155,8 @@ export const launch: LaunchFn = async (
   //     A channel runtime carries a human (natural) OR a faceless service bot (absent), never an
   //     LLM agent (artificial). Ports the persistent-peer FATAL human-channel guard, relaxed to
   //     first-class faceless service bots (docs/Рантайм-адаптеры).
-  if (adapter.allowedIntelligences && (spec.intelligence == null || !adapter.allowedIntelligences.includes(spec.intelligence))) {
-    return fail(
-      identity,
-      `runtime "${spec.runtime}" requires intelligence ∈ {${adapter.allowedIntelligences.join(', ')}}, ` +
-        `peer "${spec.personality}" is ${spec.intelligence ?? 'unknown'} — refusing to launch`,
-    )
-  }
+  const gateReason = intelligenceGateReason(adapter, spec)
+  if (gateReason) return fail(identity, gateReason)
 
   // (0.5) Ensure the socket's PARENT dir exists before `tmux new-session -S <sock>` —
   //       tmux does NOT create it and fails SILENTLY (the session "dies immediately")

package/src/tray/render.ts

@@ -43,6 +43,8 @@ export interface TrayPeer {
   last_active_ms?: number
   attached?: boolean
   launchd_managed?: boolean
+  /** Human-approval mode (docs/17). ABSENT ⇒ `yolo` (client obligation — a pre-approval daemon omits it). */
+  approval_mode?: 'yolo' | 'gated'
   wake_policy?: 'warm' | 'ephemeral'
   queue_depth?: number
 }
@@ -133,6 +135,12 @@ function aggregate(p: TrayPeer): 'live' | 'asleep' | 'stopped' {
 
 const RANK: Record<'live' | 'asleep' | 'stopped', number> = { live: 0, asleep: 1, stopped: 2 }
 
+// 🔒 launchd-managed peers (the human channel + service infra — arthur/timer/watcher) are
+// NON-clickable status rows. They form ONE contiguous block at the very TOP, before the first
+// working agent, regardless of live/asleep — so the bar separates "service, don't touch" from the
+// working agents at a glance (owner UX). `attachable` (= !launchd_managed) is the same predicate.
+const lockRank = (p: TrayPeer): number => (p.launchd_managed ? 0 : 1)
+
 // ── renderers ─────────────────────────────────────────────────────────────────
 
 const MANAGE_COMMANDS: Array<{ cmd: string; label: string }> = [
@@ -150,6 +158,10 @@ export function renderSwiftBar(snapshot: TraySnapshot, opts: RenderOptions): str
   const now = opts.now ?? Date.now()
   const bin = opts.binPath
   const peers = [...snapshot.peers].sort((a, b) => {
+    // primary: the 🔒 lock block first (service/human infra), working agents below
+    const l = lockRank(a) - lockRank(b)
+    if (l !== 0) return l
+    // secondary (within EACH block): the existing live→asleep→stopped, then alpha
     const r = RANK[aggregate(a)] - RANK[aggregate(b)]
     return r !== 0 ? r : a.personality.localeCompare(b.personality)
   })
@@ -241,9 +253,14 @@ function attachable(p: TrayPeer): boolean {
 function renderPeerRow(p: TrayPeer, bin: string, now: number, pendingCount = 0): string {
   const agg = aggregate(p)
   const detail = p.runtimes.map(r => `${r.runtime}${GLYPH[r.status]}`).join(' ')
+  // approval mode (docs/17): the whole fleet defaults to `yolo`, so showing it on every row is
+  // noise — mark ONLY the exception, `gated` (this peer's blocking approvals go to a human), with a
+  // 🛡 shield. No badge ⇒ yolo (the default; also how a pre-approval snapshot with the field absent
+  // renders). So the row reads the mode: 🛡 = gated, bare = yolo.
   const badges =
     (p.attached ? ' 👤' : '') +
     (p.launchd_managed ? ' 🔒' : '') +
+    (p.approval_mode === 'gated' ? ' 🛡' : '') +
     (p.wake_policy === 'ephemeral' && (p.queue_depth ?? 0) > 0 ? ` ⏳${p.queue_depth}` : '')
   const ageStr = p.last_active_ms ? `  ${fmtAge(p.last_active_ms, now)}` : ''
   // HIGHLIGHT a peer with a pending approval: a ⚠ prefix + a red count badge + the row painted red