madarx 2.24.0 → 2.24.1

package/CHANGELOG.md

@@ -6,25 +6,31 @@ All notable changes to Madarx OS. Newest first.
 
 _No unreleased changes._
 
+## [2.24.1] - 2026-06-07
+
+### Changed
+
+- **Friendlier release notes for operators.** The in-app “What’s new” card now explains the latest MadarX updates in plain language, focusing on what changed for the owner instead of listing internal files, tests, and engineering details.
+
 ## [2.24.0] - 2026-06-07
 
 ### Added
 
-- **R2 channel adapter foundation.** Added `lib/channels/` as a transport-only adapter framework: frozen adapter contracts (`connect` / `disconnect` / `send`), canonical inbound normalization, an isolated/default registry, deterministic most-specific routing, allowlist/rate-limit hooks, reply-to-origin dispatch, and a WhatsApp adapter seam over the existing bridge without cutting over or breaking current WhatsApp behavior. The slice includes 17 dependency-free tests that prove inbound normalization, unknown-sender blocking, route specificity, reply-to-origin, and registration-only channel addition. Telegram / Slack / Discord / iMessage / Signal remain explicit follow-on adapters before full R2 acceptance.
+- **madarX is getting ready for more messaging channels.** This update adds the groundwork for safer, more reliable conversations beyond the current WhatsApp bridge. Messages are prepared in a consistent way, unknown senders can be blocked, and replies are designed to go back to the place the message came from. WhatsApp keeps working as it does today; Telegram, Slack, Discord, iMessage, and Signal are planned follow-ups.
 
-- **Agent model & reasoning-effort selection + live "what the agent is doing".** Model picker fixed so the Anthropic engine lists its full lineup (was collapsing to Sonnet-only); `agent-config` curates the latest models (Opus 4.8/4.7, Sonnet 4.6, Haiku 4.5) and augments them with a cached best-effort `models.list` fetch (falls back offline). The Claude Code CLI now exposes selectable models (sonnet/opus/haiku) and a reasoning-effort dial (low/medium/high) — per-agent (persisted in `metadata_json`) and for the main agent (persisted in config), mapped to an extended-thinking token budget in both the CLI (`MAX_THINKING_TOKENS`) and the Anthropic loop. The chat model pill is now compact/low-emphasis with effort + context surfaced in its dropdown. The `/agents/[id]` tool picker is redesigned as icon + plain-English cards with non-technical status (Ready / Asks first / Needs setup). Background CLI agents stream throttled, ephemeral `agent_thinking`/`agent_narration` events so the toolbar and agent activity feed show reasoning and the composed answer, not just tool names. Config modal open latency fixed by decoupling its four fetches and warming `/api/config` on mount. Files: `lib/agent-config.js`, `lib/agent-engines.js`, `app/agents/**`, `app/components/dashboard/**`, `app/api/{config,orchestrator/stream}/route.js`. Tests: `tests/{agent-engines,bg-agent-reducer,config}.test.js`.
+- **You can choose how each agent thinks.** The model menu now shows the full Claude lineup instead of hiding most options, and agents can be set to think lightly, normally, or deeply depending on the job. The chat header is cleaner, and the activity feed now explains what an agent is doing in plain language rather than only showing internal tool names.
 
-- **`generate_ui` enforces the madarX brand template and in-artifact action buttons.** The `generate_ui` design system prompt (`lib/tools/adapters/generate-ui.js`) now mandates, for every artifact produced by any agent: (1) the madarX brand system from `/settings/brand` is the **template**, not optional reference — palette/typography/logo/voice applied verbatim, never a generic or off-brand page; the brand block is framed as "madarX BRAND TEMPLATE — apply (mandatory)"; and (2) whenever the page proposes an action the owner should confirm or trigger (create/schedule/run/approve/publish/send), the page must include a brand-styled `<button data-madarx-action="prompt" data-prompt="…">` that re-enters the main agent chat with a complete, actionable confirmation sentence — no `<a href="#">` actions, no emoji-gated actions. Applies to the main agent and every sub-agent that calls `generate_ui`. Files: `lib/tools/adapters/generate-ui.js`. Tests: `tests/generate-ui-brand.test.js`.
+- **Agent-made pages now follow your brand and include real action buttons.** When an agent creates a page, proposal, or mini-interface, it now uses the MadarX brand settings as the required design template. If the page asks you to approve, run, schedule, publish, or send something, the button sends a clear confirmation back into chat instead of using a dead link.
 
-- **Any agent can put a designed, on-brand UI artifact on a space (`generate_ui` for sub-agents).** `generate_ui` was a main-agent-only core tool — sub-agents (e.g. a UI Designer) couldn't produce a designed page, only a plain markdown-rendered document. It is now a real registry tool (`lib/tools/adapters/generate-ui.js` + `MARKETPLACE_TOOLS` entry) flagged `agent_default: true`, so **every tool-running agent has it by default** without an explicit grant (the owner can still opt a specific agent out with a `disabled` permission row). The design pass is identity-free (Anthropic call with `DESIGN_RULES` + active style + brand); the adapter threads `agent_id`/`space_id`, and `createArtifact` resolves the target space as explicit `space_id` > the calling agent's `default_space_id` > `default`, so a sub-agent's UI lands on its own space with no extra wiring. Removed from `CORE_TOOLS` to avoid a duplicate name (the main agent now receives it via the marketplace path; its behaviour is unchanged — `risk_level:'low'`, non-`approval_required`, so it still executes ungated). Permission model extended minimally: `getEnabledToolSchemasForAgent` surfaces, and `enforceAgentToolPermission` allows, `agent_default` tools without a row. **Designer agents are auto-created on the `anthropic` engine** (`createAgentWithFocusedPrompt`): the madarX design tools only execute on the anthropic tool-running tick, so a design-oriented agent (by name/mission/role, or one explicitly granted `generate_ui`) is flipped to anthropic unless the caller pinned a different engine. Files: `lib/tools/adapters/generate-ui.js`, `lib/tools/registry.js`, `lib/orchestrator-tools.js`. Tests: `tests/generate-ui-tool.test.js`.
+- **Specialist agents can now place polished UI directly on their spaces.** Design-focused agents are no longer limited to plain text documents. They can create branded, visual artifacts in the right workspace so their work is easier to review and use.
 
-- **Main agent can edit an existing agent's deliverable contract (`update_agent`).** Previously the orchestrator could set `expected_output` / `mission` only at creation (`create_agent`) — there was no tool to change them afterward, so "update the expected output of X" had no effect. New `update_agent` core tool (`lib/orchestrator-tools.js`) resolves an agent by `agent_id` or fuzzy `agent_name` and patches `expected_output`, `mission`, and/or `system_prompt` via the existing `updateAgent` runtime writer (empty string clears a field; non-string values are ignored; unknown/ambiguous names get a helpful error). The change persists onto the agent row, so it applies to every future run — unlike `run_agent`'s per-call `expected_output`, which overrides one run only. `create_agent`'s schema now also shows `expected_output`, and the CLI system prompt documents both create-with-deliverable and edit-existing flows. Schedule / WhatsApp / toolset keep their dedicated tools and are intentionally out of scope here. Files: `lib/orchestrator-tools.js`, `app/api/orchestrator/stream/route.js`. Tests: `tests/update-agent-tool.test.js`.
+- **You can update an existing agent's mission or expected deliverable.** If an agent's role or output needs to change, the main agent can now edit it directly instead of making you recreate the agent from scratch.
 
 ### Fixed
 
-- **`EmptyState` no longer triggers a nested-`<p>` hydration error.** `/agents/[id]?view=details` (and any admin page whose `EmptyState` is given block children) logged `In HTML, <p> cannot be a descendant of <p>` — `EmptyState` wrapped its `children` in a `<p>`, and call sites like `AgentConnectionsList` pass `<p>`/`<a>`/button children. The wrapper is now a `<div className="admin-empty-body">` (with matching typography in `app/globals.css`), legal for arbitrary block children, fixing every call site at the source. Files: `app/components/admin/admin-page.jsx`, `app/globals.css`.
-- **CLI-engine turn no longer dead-ends after `request_capability`, `list_agents`, or any read tool.** The CLI engines (claude-code / codex) execute `madarx-action` blocks post-hoc and never feed the result back into the subprocess, so a turn whose only actions are non-terminal — `route_goal`, the read tools (`list_agents`, `get_state`, `find_artifacts`, `disk_*`, …), or the fire-and-forget `request_capability` dispatch — stalled: the model said "now I'll act on what I found" and there was no second turn. The owner saw the agent stop after `request_capability` (no "Tool Smith is building it" confirmation) and after `list_agents` (never proceeds to create/run the agent). The route_goal-only continuation is generalised into `needsResultContinuation` (`lib/cli-action-flow.js`): any non-terminal-only, no-HTML turn now triggers ONE re-invoke with the executed tool results injected (`buildResultContinuationPrompt`), so the agent takes its follow-up action or answers directly in the next pass; a single terminal action (`run_agent`, `create_artifact`, `generate_ui`, `web_search`, …) leaves it untouched. The retry is accepted when it yields an action, an HTML artifact, **or** substantive prose (a read turned into a direct answer). Files: `lib/cli-action-flow.js`, `app/api/orchestrator/stream/route.js`. Tests: `tests/cli-action-flow.test.js`.
-- **CLI-engine proposal HTML no longer dropped off the canvas.** On a CLI engine (claude-code), a turn that created an agent **and** designed a `` ```html `` proposal (e.g. "stand up the full product-dev team" → CPO agent + org-chart proposal) was misclassified as a Codex misroute: `cliOnlyCreatedAgent` (`actions.every(create_agent)`) forced `wouldFallback`, routing into the plain-text branch that never calls `processCliOutput` and gates `autoArtifact` behind `!cliHasHtml`. The proposal artifact — and its in-artifact `data-madarx-action` confirm buttons — was silently dropped; the canvas stayed empty even though the agent was created. The fallback decision and HTML extraction are extracted into two pure, unit-tested helpers in `lib/cli-action-flow.js`: `shouldFallbackFromCli` only treats a lone `create_agent` as a misroute when no HTML was produced (`&& !hasHtml`), so a create-and-design turn now flows through `processCliOutput` + the agent-created-card loop; `extractHtmlArtifacts` accepts a full document **or** a substantial fragment (the model occasionally omits `<!doctype html>`, which the old doctype-anchored regex silently dropped) while still ignoring one-line inline snippets. Buttons render automatically once the artifact exists (iframe bridge in `artifact-utils.js`). Also tightens the `build_capability` prompt guidance (system + route-continuation) to force the `request_capability` action block instead of a narrated promise. Files: `lib/cli-action-flow.js`, `app/api/orchestrator/stream/route.js`. Tests: `tests/cli-action-flow.test.js`.
+- **Cleaner agent detail pages.** Empty sections on agent pages now render correctly, avoiding a noisy page-layout error that could appear in the browser.
+- **Agents keep going after they look something up.** When an agent checks available teammates, reads the current workspace, or asks for a missing capability, madarX now gives it the result and lets it continue instead of stopping halfway.
+- **Agent proposals now appear on the canvas.** If an agent creates a new teammate and also drafts a visual proposal, org chart, or plan page, that artifact now lands on the canvas instead of disappearing behind the scenes.
 
 ## [2.23.0] - 2026-06-06
 

package/ai-docs/api-surface.md

@@ -49,9 +49,13 @@ Reference for every `app/api/**/route.js` route. Read this when you need to find
 |-------|-------------|
 | `GET /api/whatsapp/status` | Bridge health + inbound allowlist. |
 | `GET /api/whatsapp/qr` | Current QR pairing string, or `{ paired: true }`. |
-| `POST /api/whatsapp/send` | Send manually. `{ chat_id, text }`. Logs + audit row. |
-| `GET /api/whatsapp/messages` | Recent messages. `?limit=` up to 200. |
+| `GET /api/whatsapp/messages?limit=50` | Recent inbound/outbound log. |
+| `POST /api/whatsapp/send` | Manual outbound send. Body `{ chat_id, text }`. |
 | `GET/POST/DELETE /api/whatsapp/allowlist` | Manage senders. `POST { chat_id, label?, kind? }`; `DELETE ?chat_id=`. |
+| `GET /api/connectivity/status` | Multi-channel setup status, allowlist counts, and live-smoke readiness for WhatsApp/Telegram/Slack/Discord/iMessage/Signal/Webhook; never returns secret values. |
+| `GET/POST/DELETE /api/connectivity/allowlist` | Shared inbound sender/address allowlist. `POST { channel, address, label?, kind? }`; `DELETE ?channel=&address=`. WhatsApp entries reuse the existing WhatsApp allowlist normalization/table. |
+| `GET /api/connectivity/smoke` | V-REACH dry/live smoke matrix for all channels. |
+| `POST /api/connectivity/smoke` | Dry-run by default, or opt-in live channel smoke. Body `{ channel, address, text?, dry_run? }`. |
 
 ## Voice (Jarvis)
 

package/ai-docs/key-constraints.md

@@ -56,7 +56,7 @@ Provider abstraction lives in `lib/voice/providers.js`. Lanes: `realtime` (prima
 
 ## WhatsApp gateway
 
-`scripts/whatsapp-bridge/` is a Baileys-based sub-package with its own `node_modules`. The daemon at `scripts/whatsapp-daemon.mjs` spawns the bridge on `127.0.0.1:3210` and runs the inbound poller from `lib/whatsapp-router.js`. Pair via `npm run whatsapp:bridge` → open `/whatsapp` → scan QR with WhatsApp → Linked Devices. **Pair only a dedicated WhatsApp number**, not your personal account — Baileys is an unofficial Web client and WhatsApp can ban the paired number. The router enforces an allowlist (`whatsapp_allowlist` table) and a 5-msg/minute per-sender rate limit. Inbound WhatsApp messages route to `lib/whatsapp-agent.js::runWhatsAppOrchestrator()` — a Claude tool loop (max 6 turns, 1536 tokens) with a WhatsApp-specific system prompt (plain text only, artifacts land in the dashboard not in the reply). Replies are sent through `POST /send` on the bridge; if the orchestrator takes >5s, an interim "Working on it…" reply goes out automatically. The main agent can also message proactively via the `whatsapp_send` tool. Session lives at `data/whatsapp/session/`; wipe with `npm run whatsapp:reset` to force re-pairing.
+`scripts/whatsapp-bridge/` is a Baileys-based sub-package with its own `node_modules`. The daemon at `scripts/whatsapp-daemon.mjs` spawns the bridge on `127.0.0.1:3210` and runs the inbound poller from `lib/whatsapp-router.js`. Pair via `npm run whatsapp:bridge` → open `/whatsapp` or the main-agent **Connectivity** tab → scan QR with WhatsApp → Linked Devices. **Pair only a dedicated WhatsApp number**, not your personal account — Baileys is an unofficial Web client and WhatsApp can ban the paired number. The router enforces an allowlist (`whatsapp_allowlist` table) and a 5-msg/minute per-sender rate limit. Inbound WhatsApp messages route to `lib/whatsapp-agent.js::runWhatsAppOrchestrator()` — a Claude tool loop (max 6 turns, 1536 tokens) with a WhatsApp-specific system prompt (plain text only, artifacts land in the dashboard not in the reply). Replies are sent through `POST /send` on the bridge; if the orchestrator takes >5s, an interim "Working on it…" reply goes out automatically. The main agent can also message proactively via the `whatsapp_send` tool. Session lives at `data/whatsapp/session/`; wipe with `npm run whatsapp:reset` to force re-pairing.
 
 ## Process / Workflow engine
 

package/app/api/connectivity/allowlist/route.js

@@ -0,0 +1,72 @@
+import { requireSession } from '@/lib/auth.js';
+import { appendAudit } from '@/lib/runtime.js';
+import {
+  addChannelAllowlistEntry,
+  listChannelAllowlist,
+  normalizeAddress,
+  normalizeChannel,
+  removeChannelAllowlistEntry,
+} from '@/lib/channel-allowlist.js';
+
+export const runtime = 'nodejs';
+export const dynamic = 'force-dynamic';
+
+function catchAuth(err) {
+  if (err && typeof err === 'object' && err.status) {
+    return Response.json({ error: err.error || 'unauthorized' }, { status: err.status });
+  }
+  return null;
+}
+
+export async function GET(req) {
+  try {
+    await requireSession(req);
+    const { searchParams } = new URL(req.url);
+    const channel = searchParams.get('channel');
+    return Response.json({ ok: true, allowlist: listChannelAllowlist(channel || null) });
+  } catch (err) {
+    return catchAuth(err) ?? Response.json({ ok: false, error: err?.message || String(err) }, { status: 500 });
+  }
+}
+
+export async function POST(req) {
+  let body;
+  try { body = await req.json(); }
+  catch { return new Response('Invalid JSON', { status: 400 }); }
+  try {
+    await requireSession(req);
+    const channel = normalizeChannel(body?.channel || 'whatsapp');
+    const address = normalizeAddress(channel, body?.address || body?.chat_id);
+    if (!address) return Response.json({ ok: false, error: 'address is required' }, { status: 400 });
+    const entry = addChannelAllowlistEntry({ channel, address, kind: body?.kind || null, label: body?.label || null });
+    appendAudit({
+      type: 'connectivity.allowlist.add',
+      summary: `Added ${channel} address to connectivity allowlist`,
+      status: 'added',
+      meta: { channel, address, label: body?.label || null },
+    });
+    return Response.json({ ok: true, entry }, { status: 201 });
+  } catch (err) {
+    return catchAuth(err) ?? Response.json({ ok: false, error: err?.message || String(err) }, { status: 500 });
+  }
+}
+
+export async function DELETE(req) {
+  try {
+    await requireSession(req);
+    const { searchParams } = new URL(req.url);
+    const channel = normalizeChannel(searchParams.get('channel') || 'whatsapp');
+    const address = normalizeAddress(channel, searchParams.get('address') || searchParams.get('chat_id'));
+    if (!address) return Response.json({ ok: false, error: 'address query param is required' }, { status: 400 });
+    const removed = removeChannelAllowlistEntry(channel, address);
+    appendAudit({
+      type: 'connectivity.allowlist.remove',
+      summary: `Removed ${channel} address from connectivity allowlist`,
+      status: 'removed',
+      meta: { channel, address, removed },
+    });
+    return Response.json({ ok: true, removed });
+  } catch (err) {
+    return catchAuth(err) ?? Response.json({ ok: false, error: err?.message || String(err) }, { status: 500 });
+  }
+}

package/app/api/connectivity/smoke/route.js

@@ -0,0 +1,40 @@
+import { requireSession } from '@/lib/auth.js';
+import { getVReachSmokeMatrix, runChannelSmoke } from '@/lib/channels/smoke.js';
+
+export const runtime = 'nodejs';
+export const dynamic = 'force-dynamic';
+
+function catchAuth(err) {
+  if (err && typeof err === 'object' && err.status) {
+    return Response.json({ error: err.error || 'unauthorized' }, { status: err.status });
+  }
+  return null;
+}
+
+export async function GET(req) {
+  try {
+    await requireSession(req);
+    const matrix = await getVReachSmokeMatrix({ includeHealth: true });
+    return Response.json(matrix);
+  } catch (err) {
+    return catchAuth(err) ?? Response.json({ ok: false, error: err?.message || String(err) }, { status: 500 });
+  }
+}
+
+export async function POST(req) {
+  let body;
+  try { body = await req.json(); }
+  catch { return new Response('Invalid JSON', { status: 400 }); }
+  try {
+    await requireSession(req);
+    const result = await runChannelSmoke({
+      channel: body?.channel,
+      address: body?.address || body?.chat_id,
+      text: body?.text,
+      dryRun: body?.dry_run !== false,
+    });
+    return Response.json({ ok: true, smoke: result });
+  } catch (err) {
+    return catchAuth(err) ?? Response.json({ ok: false, error: err?.message || String(err) }, { status: 500 });
+  }
+}

package/app/api/connectivity/status/route.js

@@ -0,0 +1,18 @@
+import { requireSession } from '@/lib/auth.js';
+import { getConnectivityStatus } from '@/lib/connectivity-status.js';
+
+export const runtime = 'nodejs';
+export const dynamic = 'force-dynamic';
+
+export async function GET(req) {
+  try {
+    await requireSession(req);
+    const status = await getConnectivityStatus();
+    return Response.json(status);
+  } catch (err) {
+    if (err && typeof err === 'object' && err.status) {
+      return Response.json({ error: err.error || 'unauthorized' }, { status: err.status });
+    }
+    return Response.json({ ok: false, error: err?.message || String(err) }, { status: 500 });
+  }
+}

package/app/components/app-topbar.jsx

@@ -12,6 +12,20 @@ import { reduceAgentEvent } from './dashboard/bg-agent-reducer.js';
 const LINGER_MS = 20000;     // keep a finished agent visible long enough to notice
 const ORPHAN_TTL_MS = 120000; // drop a "running" agent with no activity for 2m
 
+// Plain-language source for who kicked off a run — the raw values
+// (main_agent / cron / heartbeat / manual / whatsapp) are internal jargon.
+const TRIGGER_LABELS = {
+  main_agent: 'Main Agent',
+  cron: 'Scheduled',
+  heartbeat: 'Scheduled',
+  manual: 'You',
+  whatsapp: 'WhatsApp',
+};
+function triggerLabel(t) {
+  if (!t) return null;
+  return TRIGGER_LABELS[t] || t.replace(/_/g, ' ');
+}
+
 export default function AppTopbar() {
   const pathname = usePathname();
 
@@ -189,20 +203,15 @@ export default function AppTopbar() {
               style={coords ? { top: coords.top, right: coords.right } : { visibility: 'hidden' }}
             >
               <div className="bg-activity-head">
-                <b>Background agents</b>
-                <small>
-                  {runningCount
-                    ? `${runningCount} working now`
-                    : list.length
-                      ? 'Recently finished'
-                      : 'Live view of agents the Main Agent spawns'}
-                </small>
+                <b>Activity</b>
+                {(runningCount || list.length) ? (
+                  <small>{runningCount ? `${runningCount} working now` : 'Recently finished'}</small>
+                ) : null}
               </div>
               {list.length === 0 && (
                 <div className="bg-activity-empty">
                   <Activity size={18} aria-hidden />
-                  <span>No background agents active right now.</span>
-                  <small>When the Main Agent calls a sub-agent, it shows here live.</small>
+                  <span>Nothing running right now</span>
                 </div>
               )}
               <div className="bg-activity-list">
@@ -215,8 +224,8 @@ export default function AppTopbar() {
                         {a.status === 'failed' && <StepXIcon />}
                       </span>
                       <span className="bg-activity-agent-name">{a.agent_name}</span>
-                      {a.triggered_by && (
-                        <span className="bg-activity-agent-by">via {a.triggered_by}</span>
+                      {triggerLabel(a.triggered_by) && (
+                        <span className="bg-activity-agent-by">{triggerLabel(a.triggered_by)}</span>
                       )}
                       <span className="bg-activity-agent-status">
                         {a.status === 'running'
@@ -254,7 +263,7 @@ export default function AppTopbar() {
                   </div>
                 ))}
               </div>
-              <a className="bg-activity-foot" href="/activity">Open activity log →</a>
+              <a className="bg-activity-foot" href="/activity">View all activity →</a>
             </div>,
             document.body,
           )}

package/app/components/dashboard/config-panel.jsx

@@ -1,7 +1,7 @@
 "use client";
 import { memo } from 'react';
 import AdminModal from '@/app/components/admin/admin-modal.jsx';
-import WhatsAppSection from './whatsapp-section.jsx';
+import ConnectivitySection from './whatsapp-section.jsx';
 import { useDashboard } from './dashboard-context';
 import InstructionsTab from './config-tabs/instructions-tab.jsx';
 import ToolsTab from './config-tabs/tools-tab.jsx';
@@ -31,7 +31,7 @@ function ConfigPanel() {
           ['design', 'Design', 'Artifact style'],
           ['voice', 'Voice', 'Jarvis console'],
           ['tools', 'Tools', 'Keys and access'],
-          ['whatsapp', 'WhatsApp', 'Bridge + chats'],
+          ['connectivity', 'Connectivity', 'Channels + pairing'],
         ].map(([id, label, desc]) => (
           <button key={id} className={'config-tab' + (configTab === id ? ' on' : '')} onClick={() => setConfigTab(id)}>
             <span>{label}</span>
@@ -76,13 +76,13 @@ function ConfigPanel() {
     )}
     {configTab === 'voice' && <VoiceTab />}
     {configTab === 'tools' && <ToolsTab />}
-    {configTab === 'whatsapp' && (
+    {configTab === 'connectivity' && (
       <div className="config-body">
         <div className="config-page-head">
-          <span>WhatsApp</span>
-          <p>Bridge pairing, allowed senders, and message history for this agent&apos;s WhatsApp number.</p>
+          <span>Connectivity</span>
+          <p>Pairing, allowed senders, status, and live-smoke readiness for every main-agent channel.</p>
         </div>
-        <WhatsAppSection />
+        <ConnectivitySection />
       </div>
     )}
       </div>

package/app/components/dashboard/whatsapp-section.jsx

@@ -4,6 +4,7 @@ import { useCallback, useEffect, useMemo, useState } from 'react';
 import QRCode from 'qrcode';
 
 const WA_SUBTABS = [
+  ['status', 'Status', 'All channels'],
   ['pairing', 'Pairing', 'Bridge status + QR'],
   ['allowlist', 'Allowlist', 'Permitted senders'],
   ['messages', 'Messages', 'Inbound + outbound'],
@@ -33,7 +34,7 @@ async function fetchJson(url, opts) {
 }
 
 export default function WhatsAppSection() {
-  const [waSub, setWaSub] = useState('pairing');
+  const [waSub, setWaSub] = useState('status');
   const [status, setStatus] = useState(null);
   const [qr, setQr] = useState(null);
   const [qrDataUrl, setQrDataUrl] = useState('');
@@ -41,6 +42,7 @@ export default function WhatsAppSection() {
   const [err, setErr] = useState(null);
 
   // Allowlist add form state
+  const [addChannel, setAddChannel] = useState('whatsapp');
   const [addChatId, setAddChatId] = useState('');
   const [addLabel, setAddLabel] = useState('');
   const [addBusy, setAddBusy] = useState(false);
@@ -61,7 +63,7 @@ export default function WhatsAppSection() {
   const refreshAll = useCallback(async () => {
     try {
       const [s, q, m] = await Promise.all([
-        fetchJson('/api/whatsapp/status'),
+        fetchJson('/api/connectivity/status'),
         fetchJson('/api/whatsapp/qr'),
         fetchJson('/api/whatsapp/messages?limit=50'),
       ]);
@@ -95,9 +97,20 @@ export default function WhatsAppSection() {
     return () => { cancelled = true; };
   }, [qr]);
 
-  const health = status?.health || {};
+  const channels = status?.channels || [];
+  const whatsAppChannel = channels.find(c => c.channel === 'whatsapp');
+  const health = whatsAppChannel?.health || status?.health || {};
   const allowlist = status?.allowlist || [];
-  const pairingState = health.pairing_state || (health.ok === false ? 'offline' : 'unknown');
+  const channelOptions = channels.length ? channels : [
+    { channel: 'whatsapp', label: 'WhatsApp' },
+    { channel: 'telegram', label: 'Telegram' },
+    { channel: 'slack', label: 'Slack' },
+    { channel: 'discord', label: 'Discord' },
+    { channel: 'imessage', label: 'iMessage' },
+    { channel: 'signal', label: 'Signal' },
+    { channel: 'webhook', label: 'Webhook/API' },
+  ];
+  const pairingState = whatsAppChannel?.state || health.pairing_state || (health.ok === false ? 'offline' : 'unknown');
   const showQrCard = pairingState !== 'paired';
   const lastConnected = health.last_connected_at
     ? new Date(health.last_connected_at).toLocaleTimeString()
@@ -114,10 +127,10 @@ export default function WhatsAppSection() {
     if (!addChatId.trim()) return;
     setAddBusy(true);
     setAddError('');
-    const r = await fetchJson('/api/whatsapp/allowlist', {
+    const r = await fetchJson('/api/connectivity/allowlist', {
       method: 'POST',
       headers: { 'Content-Type': 'application/json' },
-      body: JSON.stringify({ chat_id: addChatId.trim(), label: addLabel.trim() || null }),
+      body: JSON.stringify({ channel: addChannel, address: addChatId.trim(), label: addLabel.trim() || null }),
     });
     setAddBusy(false);
     if (!r.ok) {
@@ -129,9 +142,9 @@ export default function WhatsAppSection() {
     refreshAll();
   }
 
-  async function handleRemoveAllow(chatId) {
-    setRemovingId(chatId);
-    const r = await fetchJson(`/api/whatsapp/allowlist?chat_id=${encodeURIComponent(chatId)}`, { method: 'DELETE' });
+  async function handleRemoveAllow(channel, address) {
+    setRemovingId(`${channel}:${address}`);
+    const r = await fetchJson(`/api/connectivity/allowlist?channel=${encodeURIComponent(channel)}&address=${encodeURIComponent(address)}`, { method: 'DELETE' });
     setRemovingId(null);
     if (!r.ok) setErr(r.json?.error || 'Failed to remove');
     else refreshAll();
@@ -188,7 +201,7 @@ export default function WhatsAppSection() {
       )}
 
       {/* Subnav — same pattern as tools-subnav in config-panel */}
-      <nav className="tools-subnav" role="tablist" aria-label="WhatsApp sections">
+      <nav className="tools-subnav" role="tablist" aria-label="Connectivity sections">
         {WA_SUBTABS.map(([id, label, desc]) => (
           <button
             key={id}
@@ -204,6 +217,40 @@ export default function WhatsAppSection() {
         ))}
       </nav>
 
+      {waSub === 'status' && (
+        <div className="tools-pane">
+          <div className="config-secrets-panel">
+            <div className="config-secrets-head">
+              <div>
+                <span className="config-section-title">Channel readiness</span>
+                <p>Shared pairing + allowlist status for V-REACH channels. Secrets are never displayed.</p>
+              </div>
+            </div>
+            <div className="config-tools-list">
+              {channels.map(row => (
+                <div key={row.channel} className={'config-tool-row' + (row.ready_for_live_smoke ? ' on' : '')}>
+                  <div className="secrets-row-inner">
+                    <div className="secrets-row-meta">
+                      <div className="config-tool-titleline">
+                        <span className="config-tool-name" style={{ textTransform: 'none' }}>{row.label}</span>
+                        <span className={`admin-pill ${row.ready_for_live_smoke ? 'ready' : row.configured ? 'warn' : 'neutral'}`}>
+                          {row.ready_for_live_smoke ? 'Ready for smoke' : row.configured ? 'Needs allowlist' : 'Needs setup'}
+                        </span>
+                      </div>
+                      <div className="config-tool-status">
+                        <span>{row.kind}</span>
+                        <span>{row.allowlist_count || 0} allowlisted</span>
+                        {row.missing?.length ? <span>Missing: {row.missing.join(', ')}</span> : null}
+                      </div>
+                    </div>
+                  </div>
+                </div>
+              ))}
+            </div>
+          </div>
+        </div>
+      )}
+
       {/* ── Pairing tab ── */}
       {waSub === 'pairing' && (
         <div className="tools-pane">
@@ -335,7 +382,7 @@ export default function WhatsAppSection() {
             <div className="config-secrets-head">
               <div>
                 <span className="config-section-title">Allowed senders</span>
-                <p>Only chats on this list can message the agent. Add new entries below.</p>
+                <p>Only addresses on this list can message the agent. WhatsApp uses the same allowlist behavior, now shared across channels.</p>
               </div>
             </div>
 
@@ -343,11 +390,19 @@ export default function WhatsAppSection() {
             <form className="secrets-add-form" onSubmit={handleAddAllow}>
               <div className="secrets-add-fields">
                 <label className="config-env-field">
-                  <span className="config-env-field-top"><b>Chat id</b></span>
+                  <span className="config-env-field-top"><b>Channel</b></span>
+                  <select value={addChannel} onChange={e => setAddChannel(e.target.value)}>
+                    {channelOptions.map(row => (
+                      <option key={row.channel} value={row.channel}>{row.label || row.channel}</option>
+                    ))}
+                  </select>
+                </label>
+                <label className="config-env-field">
+                  <span className="config-env-field-top"><b>Address</b></span>
                   <input
                     type="text"
                     autoComplete="off"
-                    placeholder="9715XXXXXXXX or full JID"
+                    placeholder="Chat/channel/user id or webhook address"
                     value={addChatId}
                     onChange={e => setAddChatId(e.target.value)}
                     required
@@ -387,12 +442,13 @@ export default function WhatsAppSection() {
             ) : (
               <div className="config-tools-list">
                 {allowlist.map(row => (
-                  <div key={row.chat_id} className="config-tool-row on">
+                  <div key={`${row.channel}:${row.address || row.chat_id}`} className="config-tool-row on">
                     <div className="secrets-row-inner">
                       <div className="secrets-row-meta">
                         <div className="config-tool-titleline">
                           <span className="config-tool-name" style={{ textTransform: 'none' }}>
-                            <code className="whatsapp-mono">{row.chat_id}</code>
+                            <span className="config-tool-risk">{row.channel}</span>
+                            <code className="whatsapp-mono">{row.address || row.chat_id}</code>
                           </span>
                           {row.kind && <span className="config-tool-risk">{row.kind}</span>}
                         </div>
@@ -407,10 +463,10 @@ export default function WhatsAppSection() {
                         <button
                           type="button"
                           className="secrets-action-btn danger"
-                          disabled={removingId === row.chat_id}
-                          onClick={() => handleRemoveAllow(row.chat_id)}
+                          disabled={removingId === `${row.channel}:${row.address || row.chat_id}`}
+                          onClick={() => handleRemoveAllow(row.channel, row.address || row.chat_id)}
                         >
-                          {removingId === row.chat_id ? '...' : 'Remove'}
+                          {removingId === `${row.channel}:${row.address || row.chat_id}` ? '...' : 'Remove'}
                         </button>
                       </div>
                     </div>
@@ -455,7 +511,8 @@ export default function WhatsAppSection() {
                             {row.direction}
                           </span>
                         </td>
-                        <td><code className="whatsapp-mono">{row.chat_id}</code></td>
+                        <td><span className="config-tool-risk">{row.channel}</span>
+                            <code className="whatsapp-mono">{row.address || row.chat_id}</code></td>
                         <td><code className="whatsapp-mono">{row.sender || '—'}</code></td>
                         <td style={{ maxWidth: 260, overflow: 'hidden', textOverflow: 'ellipsis', whiteSpace: 'nowrap' }}>
                           {row.text}
@@ -483,7 +540,15 @@ export default function WhatsAppSection() {
             <form className="secrets-add-form" onSubmit={handleSend}>
               <div className="secrets-add-fields">
                 <label className="config-env-field">
-                  <span className="config-env-field-top"><b>Chat id</b></span>
+                  <span className="config-env-field-top"><b>Channel</b></span>
+                  <select value={addChannel} onChange={e => setAddChannel(e.target.value)}>
+                    {channelOptions.map(row => (
+                      <option key={row.channel} value={row.channel}>{row.label || row.channel}</option>
+                    ))}
+                  </select>
+                </label>
+                <label className="config-env-field">
+                  <span className="config-env-field-top"><b>Address</b></span>
                   <input
                     type="text"
                     autoComplete="off"

package/app/whatsapp/page.js

@@ -6,12 +6,12 @@ import WhatsAppSection from '@/app/components/dashboard/whatsapp-section.jsx';
 export default function WhatsAppPage() {
   return (
     <AdminShell
-      kicker="madarX OS · WhatsApp"
-      title="WhatsApp gateway"
+      kicker="madarX OS · Connectivity"
+      title="Connectivity gateway"
       description={
         <>
-          Text the main agent like you text Hermes. The bridge pairs as a WhatsApp Web client over Baileys
-          and runs as a separate daemon (npm run whatsapp:bridge).{' '}
+          Pair and allowlist the main agent across WhatsApp, Telegram, Slack, Discord, iMessage, Signal, and webhooks.
+          WhatsApp still uses the Baileys bridge daemon (npm run whatsapp:bridge).{' '}
           <a className="admin-link" href="/marketplace?kind=connection">Configured in Marketplace →</a>
         </>
       }