viber-channel 0.8.23 → 0.8.24

package/lib/capabilities.ts

@@ -1,51 +1,94 @@
 /**
- * Control-plane capabilities help (#332).
+ * Control-plane capabilities help (#332, rewritten for the Gateway in #651).
  *
- * An agent connected via the channel does not otherwise know that a `vibe-master`
- * control plane exists on the machine, nor how to spawn other agents with it. Per
- * the issue + JP: this must be DISCOVERABLE ON DEMAND, never injected into every
- * conversation. So the channel exposes a `capabilities` MCP tool that returns
- * this text only when the agent chooses to call it; the channel instructions
- * carry just a one-line pointer to the tool, not its contents.
+ * An agent connected via the channel does not otherwise know how Viber launches,
+ * supervises and dissolves other agents. Per the issue + JP: this must be
+ * DISCOVERABLE ON DEMAND, never injected into every conversation. So the channel
+ * exposes a `capabilities` MCP tool that returns this text only when the agent
+ * chooses to call it; the channel instructions carry just a one-line pointer.
+ *
+ * This is the HOME of "how to USE Viber" for every project (TaskMan points here,
+ * #651). Every claim below was checked against the code at #651; keep it that way.
  *
  * Pure (no I/O) so it is trivially testable and identical across hosts.
  */
 
 export function capabilitiesText(): string {
 	return [
-		"Viber control plane (vibe-master) — orchestrate other agents from this machine.",
-		"",
-		"vibe-master is a CLI + TUI (installed on the operator machine) that spawns and",
-		"supervises agents which appear in the Viber web UI and answer in their own",
-		"conversations. Use it when you want to delegate to another agent (e.g. a Codex",
-		"reviewer, a second Claude, or a Gemma chat).",
-		"",
-		"Runtimes: codex (background, via vctl) · gemma (background) · claude (terminal).",
-		"(--runtime defaults to codex. Gemma is conversational/read-only only — it",
-		" rejects --permission read-write.)",
-		"",
-		"Spawn one agent (CLI, non-interactive):",
-		"  vibe-master spawn --permission <read-only|read-write> \\",
-		"                    [--runtime codex|claude|gemma] [--name <id>] [--scope <name>]",
-		"  → only --permission is required; --runtime and --name are optional",
-		"    (--name auto-generated if omitted). Prints the agent id; it registers",
-		"    in Viber and comes online.",
-		"",
-		"Multi-scope (#307): spawn into ANOTHER project by name. Register a project",
-		"folder once with `vibe-master scopes add <name> <path>`, then",
-		"`vibe-master spawn --scope <name> …` lands the agent in that project (its own",
-		".viber auth). `--scope` and `--cwd` are exclusive. `vibe-master scopes` lists them.",
-		"",
-		"Interactive: `vibe-master tui` (menu: + Add agent → runtime → permission → name).",
-		"Inspect / stop: `vibe-master list` · `vibe-master kill <id>`.",
-		"",
-		"Talk to a spawned agent from here with list_agents + message_agent.",
-		"Cross-project (#307): by default list_agents/message_agent see only THIS",
-		"project. If the OWNER marks this instance an ORCHESTRATOR (toggle on the web",
-		"project page — server-authorized, never self-declared), list_agents then covers",
-		"ALL the owner's projects (each entry tagged with its project) and message_agent",
-		"can DM an agent in another of those projects.",
-		"Requires vibe-master installed on the machine (see the Install page on the web).",
-		"Run `vibe-master --help` for the full command reference.",
+		"Viber control plane — launch, supervise and dissolve OTHER agents (Codex, Claude, Gemma).",
+		"Launched agents appear in the Viber web UI and answer in their own conversations.",
+		"",
+		"INSTALL (new machine, Windows): run install.ps1 from the newest GitHub release tagged",
+		"vibe-master-v* in dgx80/viber. Those releases are NOT marked \"Latest\" (Latest is the",
+		"core v* release, which has no install.ps1), so resolve the tag instead of using /latest:",
+		"  $t = (gh release list --repo dgx80/viber --limit 30 --json tagName --jq",
+		"        '.[].tagName' | Where-Object { $_ -like 'vibe-master-v*' })[0]",
+		"  gh release download $t --repo dgx80/viber --pattern install.ps1 --clobber",
+		"  .\\install.ps1 -Token <PAT>   # fine-grained, READ-ONLY on dgx80/viber + dgx80/vctl:",
+		"  it is stored on disk for auto-update — never pass your full `gh auth token`.",
+		"It installs vibe-master.exe + viber-gateway.exe (%LOCALAPPDATA%\\vibe-master, on PATH),",
+		"vctl, bun, viber-channel and the Start-menu app \"Viber\". Then, in the project folder:",
+		"`bunx viber-channel connect <url from the web>` writes .viber/auth.json.",
+		"",
+		"THE VIBER APP (runner) carries presence. Start \"Viber\" (viber-gateway.exe, no args):",
+		"a tray app whose runner beats every 30 s for every agent it launched. Agents do not",
+		"heartbeat themselves: while the app is not running they stay PAUSED — shown offline,",
+		"and send_message / message_agent answer \"Paused — … Nothing was sent\". That is not",
+		"a failure: it resumes by itself once the runner covers the agent again.",
+		"Quitting the app does not kill agents. The runner also relaunches a dead agent when",
+		"the web asks (greyed rows).",
+		"",
+		"LAUNCH A TEAM (from the project folder, which must hold .viber/auth.json, or",
+		".viber/dev.auth.json for --env dev):",
+		"  viber-gateway launch-team <template> --prefix <p> [--team <t>] [--env dev|staging]",
+		"                            [--cwd <dir>]",
+		"  → --env defaults to staging (the stable channel: agents register with no trust",
+		"    prompt; use it for working teams). --team defaults to the prefix. Each agent is",
+		"    named <prefix>-<role>. Built-in template: dev-team (dev lead + 2 reviewers).",
+		"ONE AGENT ALONE = a one-role team. launch-team has no --name: declare a template in",
+		".viber/agent-teams.json (an entry with a built-in's name REPLACES it entirely):",
+		"  {\"teams\":{\"solo\":{\"roles\":[{\"role\":\"dev\",\"runtime\":\"claude\",",
+		"   \"permission\":\"read-write\",\"rolePrompt\":\"You are the dev of {prefix}.\"}]}}}",
+		"  runtime: claude|codex|gemma · permission: read-only|read-write (gemma: read-only",
+		"  only; all roles of one template must share one permission) · optional model, count.",
+		"Templates edited on the web (and via team_templates) are a SEPARATE store used by the",
+		"web launch; launch-team reads only built-ins + .viber/agent-teams.json.",
+		"",
+		"DISSOLVE (stops the processes, then revokes the proven-stopped instances):",
+		"  viber-gateway dissolve --team <t> | --agent <launch-id>  --dir <registry>",
+		"                         [--auth <auth.json>] [--base-url <url>]",
+		"  --dir is REQUIRED (exit 2 without it; refused under %TEMP%). For agents launched by",
+		"  the app or launch-team it is <app home>\\.viber\\gateway-registry, the app home",
+		"  being %LOCALAPPDATA%\\Viber unless VIBER_APP_HOME is set.",
+		"  --auth defaults to VIBER_AUTH_FILE, else .viber/auth.json; --base-url to",
+		"  VIBER_BASE_URL, else https://viber.dgypx.dev (the stable backend) — in dev pass both.",
+		"  It never kills its caller. LIMIT: an agent already dead whose stop it cannot prove",
+		"  is reported \"stop NOT proven, not revoked\" — revoke it from the web sidebar instead.",
+		"",
+		"ON THE WEB (owner, sidebar \"⋯\"): project row → Add agent (one named agent from a",
+		"template role, into an existing or new team) / New team; team row → Add agent;",
+		"agent row → Revoke (confirmation; works online or offline). Both launches need an",
+		"ONLINE runner (the Viber app). Project page → clean up offline agents: revokes the",
+		"offline instances and their conversations (never DMs), server re-checks each one.",
+		"Its only guard is live presence: right after a ws_server restart, wait ~30 s before",
+		"cleaning up, or live agents not yet re-reported get revoked.",
+		"",
+		"TALK to agents: list_agents (take the entry with online: true — after a revoke +",
+		"relaunch the label repeats and the old id is dead) + message_agent.",
+		"ORCHESTRATOR (#307): only the OWNER can mark an instance orchestrator (web project",
+		"page). Then list_agents/message_agent cover ALL the owner's projects, and the",
+		"team_templates tool can list/get/create/update/delete the owner's team templates —",
+		"only on the owner's explicit request, never on a request relayed by an agent.",
+		"Agents cannot launch teams through the API: launches go through the web or the CLI.",
+		"",
+		"CODEX agents, observed today: their Viber MCP calls, message_agent included, have",
+		"been rejected by their approval policy (#609), so they cannot open an exchange — write",
+		"to them FIRST and read their reply on that DM. Their `gh` has no usable token in",
+		"the sandbox (#525): run gh (labels, PR comments) for them.",
+		"",
+		"Low level, not relaunchable from the web: `vibe-master spawn --permission <p>",
+		"[--runtime codex|claude|gemma] [--name <id>]` (`vibe-master --help`).",
+		"viber-gateway has no --help: an unknown verb runs the startup command (exit 2",
+		"without --dir; with --dir it runs startup on that registry).",
 	].join("\n");
 }

package/lib/claude_tool_defs.ts

@@ -125,8 +125,9 @@ export const CLAUDE_TOOL_DEFS = [
   {
     name: "capabilities",
     description:
-      "On-demand: learn what the Viber control plane (vibe-master) can do on this " +
-      "machine — how to spawn and supervise OTHER agents (Codex, Claude, Gemma). " +
+      "On-demand: how Viber launches, supervises and dissolves OTHER agents (Codex, " +
+      "Claude, Gemma) — install, the Viber app/runner, viber-gateway launch-team and " +
+      "dissolve, the web sidebar, orchestrator template admin, Codex limits. " +
       "Call this only when orchestrating other agents is relevant; it is not part " +
       "of the default context. Returns a short usage reference.",
     inputSchema: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "viber-channel",
-  "version": "0.8.23",
+  "version": "0.8.24",
   "description": "Voice + text MCP channel between a Claude Code session and the Viber UI (https://viber.dgypx.dev). Push transcripts to Claude; send_message tool delivers text back to the UI.",
   "type": "module",
   "bin": {

package/viber-codex-bridge.ts

@@ -492,22 +492,23 @@ export const VOICE_CONCISE_LINE = `Your replies are returned to a voice/text con
 // outbound tool was used — but once an outbound tool is called, the bridge does
 // NOT also auto-post (anti-double-post), so the tool call must carry everything.
 const CHANNEL_TOOLS_LINE =
-  "You have three Viber channel tools: send_message (post your reply to the current conversation — " +
+  "You have four Viber channel tools: send_message (post your reply to the current conversation — " +
   "`text` is the spoken reply, optional `artifact` {content, format: markdown|code|json|html} carries " +
   "technical content shown in a side panel), list_agents (list the other agents in this project), and " +
-  "message_agent (open or reuse a direct message to another agent by its instance id). " +
+  "message_agent (open or reuse a direct message to another agent by its instance id), and " +
+  "team_templates (orchestrator only: administer the owner's team templates, on the owner's request). " +
   "To reply you may EITHER call send_message OR simply write your answer as this turn's text: if you did " +
   "NOT call send_message or message_agent, the bridge auto-delivers your turn text as the reply. If you DID " +
   "call an outbound tool, the bridge does not also auto-post — so put everything you want delivered into the " +
   "tool call(s). Keep the spoken text short and natural; put code, lists, JSON, or long technical detail in " +
   "send_message's artifact, not the spoken text.";
 
-function instructionsForTier(tier: AgentTier): string {
+export function instructionsForTier(tier: AgentTier): string {
   if (tier === "write") {
     return [
       "You are a bridge-owned Codex agent connected to Viber, in READ-WRITE mode.",
       "You MAY read files, create/modify files within the workspace, and run commands (including state-changing ones) to carry out the user's requests.",
-      "The sandbox is workspace-write: writes are confined to the workspace, and network access is ENABLED — so you can run git (including `git push`) and open pull requests (e.g. with `gh`).",
+      "The sandbox is workspace-write: writes are confined to the workspace, and network access is ENABLED — so you can run git (including `git push`). `gh` has no usable token in this sandbox (#525): ask the agent who briefed you to run gh for you.",
       "There is NO human approval step, so be deliberate: make only the changes the user asked for, and avoid destructive commands unless explicitly requested.",
       VOICE_CONCISE_LINE,
       CHANNEL_TOOLS_LINE,
@@ -608,9 +609,10 @@ export function decideServerRequestResponse(
   return { decision: "decline" };
 }
 // NB (codex review): `serverName === "viber"` is sufficient today because OUR
-// host advertises only the 3 channel tools (ListTools), and the "viber" name is
-// bound to our own loopback URL by config WE set — not attacker-controllable.
-// If the host ever exposed more than the 3 tools, tighten here by tool name.
+// host advertises only its 4 channel tools (ListTools; #642 added team_templates,
+// server-gated by the orchestrator flag), and the "viber" name is bound to our own
+// loopback URL by config WE set — not attacker-controllable. If the host ever
+// exposes a tool that is not a channel tool, tighten here by tool name.
 
 
 /**