@pellux/goodvibes-agent 1.0.5 → 1.0.6

package/docs/connected-host.md

@@ -56,6 +56,8 @@ Agent does not own connected-host lifecycle. It does not provide commands to ins
 
 The model can inspect this boundary with `agent_harness` mode `connected_host`. That report includes the configured base URL, token presence, token path, allowed route families, first-class Agent tool capabilities, tool availability, and blocked capabilities. Allowed capabilities are limited to read-only operator briefing, explicit allowlisted approval/automation/schedule actions, isolated Agent Knowledge read/ingest, confirmed channel or notification delivery, confirmed reminder schedules, and configured media generation. Blocked capabilities include connected-host lifecycle, listener mutation, default or non-Agent knowledge fallback, hidden background Agent jobs, implicit delegated review, route/account creation, and arbitrary connected-host mutations.
 
+The model can inspect live connected-host readiness with `agent_harness` mode `connected_host_status`. That report uses the same read-only status probe as the CLI: it checks the connected-host status route, verifies the SDK version pin, checks the isolated Agent Knowledge status route when token and version posture allow it, reports endpoint bindings and token posture without printing token values, and returns actionable findings. It is diagnostic only and does not expose host start, stop, restart, install, listener, or account-management operations.
+
 Agent Knowledge is its own product segment. Agent uses `/api/goodvibes-agent/knowledge/*` only and must not fall back to default knowledge or other product-specific knowledge routes.
 
 Normal assistant chat uses companion chat. Build/fix/review work is delegated explicitly to GoodVibes TUI through public runtime/session contracts, and delegated review is requested only when explicitly asked for build/fix/review work.

package/docs/getting-started.md

@@ -44,7 +44,7 @@ After setup has been applied once, the TUI opens directly into the Agent operato
 
 Press `/` inside the Agent workspace to search every workspace action by name, category, command, or detail. Use that finder before reaching for shell commands; CLI subcommands are scriptable mirrors of these TUI workflows.
 
-The model can inspect and use the same harness surface through Agent-owned tools. `agent_harness` exposes workspace action discovery, built-in panel discovery/routing, modal/overlay/picker UI surface discovery/routing, top-level CLI mirror discovery, fixed shortcut and configurable keybinding discovery, keybinding mutation with confirmation, slash-command discovery, command policy metadata, command execution with confirmation, model tool discovery, settings inspection/mutation, and connected-host posture. CLI mirror modes are read-only catalog/parser inspection and point the model to the matching in-process tool, workspace action, setting mode, or slash-command mirror. Panel modes expose catalog/open state and route visible panel/workspace changes through the current Agent shell bridge with confirmation. UI surface modes expose help, shortcuts, context, bookmarks, model/provider pickers, session/profile pickers, settings, MCP workspace, onboarding, and Agent workspace entrypoints; `open_ui_surface` is confirmation-gated and only performs visible shell navigation. Shortcut modes expose the fixed runtime/editor shortcuts and the live keybindings table; confirmed keybinding edits write the same `keybindings.json` file the user edits and reload the runtime manager. Workspace action discovery can include editor field schemas with `includeParameters:true`, including starter-template defaults for profile creation and selected-routine defaults for routine schedule promotion when `recordId` is supplied. Selection-based local workspace actions accept a local `recordId`, so the model can use the same note promotion and local registry flows as the TUI. First-class model tools cover the main product workflows directly: Agent Knowledge, Agent Knowledge ingest, Agent-local memory/notes/personas/skills/routines, operator actions, notifications, channel sends, reminders, generated media, and work plans.
+The model can inspect and use the same harness surface through Agent-owned tools. `agent_harness` exposes workspace action discovery, built-in panel discovery/routing, modal/overlay/picker UI surface discovery/routing, top-level CLI mirror discovery, fixed shortcut and configurable keybinding discovery, keybinding mutation with confirmation, slash-command discovery, command policy metadata, command execution with confirmation, model tool discovery, settings inspection/mutation, connected-host capability inventory, and live connected-host readiness posture. CLI mirror modes are read-only catalog/parser inspection and point the model to the matching in-process tool, workspace action, setting mode, or slash-command mirror. Panel modes expose catalog/open state and route visible panel/workspace changes through the current Agent shell bridge with confirmation. UI surface modes expose help, shortcuts, context, bookmarks, model/provider pickers, session/profile pickers, settings, MCP workspace, onboarding, and Agent workspace entrypoints; `open_ui_surface` is confirmation-gated and only performs visible shell navigation. Shortcut modes expose the fixed runtime/editor shortcuts and the live keybindings table; confirmed keybinding edits write the same `keybindings.json` file the user edits and reload the runtime manager. Workspace action discovery can include editor field schemas with `includeParameters:true`, including starter-template defaults for profile creation and selected-routine defaults for routine schedule promotion when `recordId` is supplied. Selection-based local workspace actions accept a local `recordId`, so the model can use the same note promotion and local registry flows as the TUI. First-class model tools cover the main product workflows directly: Agent Knowledge, Agent Knowledge ingest, Agent-local memory/notes/personas/skills/routines, operator actions, notifications, channel sends, reminders, generated media, and work plans.
 
 Use the Artifacts area for concrete files and generated output: attach images to prompts, export conversations or saved sessions, ingest local source files and URL lists into Agent Knowledge, import bookmarks or browser history, inspect source records, and generate media artifacts from confirmed prompts.
 
@@ -138,7 +138,7 @@ If the GoodVibes API is not on `http://127.0.0.1:3421`, pass `--runtime-url http
 
 Agent Knowledge is an Agent-owned product segment. Agent commands must not fall back to default knowledge or other product-specific knowledge spaces.
 
-Host lifecycle commands are not part of GoodVibes Agent. Use Agent Workspace -> Home -> Host compatibility, Doctor diagnostics, and Review health for diagnostics. CLI status/doctor/compat commands are scriptable mirrors for install checks. The model-visible `connected_host` harness report lists usable Agent route families, first-class tool capabilities, and blocked lifecycle/non-Agent surfaces without exposing host start/stop/restart/install operations.
+Host lifecycle commands are not part of GoodVibes Agent. Use Agent Workspace -> Home -> Host compatibility, Doctor diagnostics, and Review health for diagnostics. CLI status/doctor/compat commands are scriptable mirrors for install checks. The model-visible `connected_host` harness report lists usable Agent route families, first-class tool capabilities, and blocked lifecycle/non-Agent surfaces. The model-visible `connected_host_status` report performs the live read-only connected-host status and isolated Agent Knowledge readiness checks, reports SDK compatibility, token posture, endpoint bindings, route readiness, and actionable findings, and still does not expose host start/stop/restart/install operations.
 
 ## Current Product Notes
 

package/docs/tools-and-commands.md

@@ -43,14 +43,14 @@ Host-management and coding-first commands that would imply connected-host lifecy
 
 The main Agent model has an Agent-owned harness bridge rather than generic SDK settings/context control. Use these model tools as the supported parity layer:
 
-- `agent_harness`: inspect workspace categories/actions, inspect built-in panels, inspect modal/overlay/picker UI surfaces, inspect top-level CLI mirrors, inspect fixed shortcuts and configurable keybindings, inspect slash commands and command policy metadata, run concrete workspace or slash-command mirrors with confirmation, inspect model tools, inspect or change Agent settings/keybindings, and inspect connected-host posture.
+- `agent_harness`: inspect workspace categories/actions, inspect built-in panels, inspect modal/overlay/picker UI surfaces, inspect top-level CLI mirrors, inspect fixed shortcuts and configurable keybindings, inspect slash commands and command policy metadata, run concrete workspace or slash-command mirrors with confirmation, inspect model tools, inspect or change Agent settings/keybindings, inspect connected-host capability boundaries, and inspect live connected-host readiness.
 - `agent_local_registry`: inspect and maintain Agent-local memory, notes, personas, skills, skill bundles, and routines. Deleting local records requires `confirm:true` and `explicitUserRequest`.
 - `agent_knowledge` and `agent_knowledge_ingest`: ask/search and ingest into the isolated Agent Knowledge segment.
 - `agent_operator_briefing` and `agent_operator_action`: inspect connected work/approval/automation posture, or run exact confirmed approval/automation actions.
 - `agent_work_plan`: keep the visible Agent-local work plan current from the conversation.
 - `agent_channel_send`, `agent_notify`, `agent_reminder_schedule`, and `agent_media_generate`: perform confirmed external delivery, notification, reminder, or media actions when the user explicitly asks.
 
-`agent_harness` discovery modes are read-only. `summary` reports the model access map; `panels` and `panel` return the built-in panel catalog, current open/focused state, and each panel's matching Agent workspace route; `ui_surfaces` and `ui_surface` return modal, overlay, picker, and workspace entrypoints with shell-opener availability and preferred model routes; `cli_commands` and `cli_command` return top-level package CLI mirror metadata, parser output, blocked command tokens, and preferred in-process model routes; `shortcuts` returns fixed runtime/editor shortcuts plus configurable keybindings; `keybindings` and `keybinding` return the live resolved keybinding table, default bindings, custom state, and config path; `commands` and `command` return slash-command descriptions plus effect/confirmation/preferred-tool/boundary policy metadata; `workspace_actions` lists Agent workspace actions and can inline editor field schemas with `includeParameters:true`; `workspace_action` returns one action with its editor schema; `tools` can inline model tool JSON schemas with `includeParameters:true`; `settings` returns setting descriptors plus setting policy; and `connected_host` returns the connected-host route families, allowed capabilities, blocked capabilities, and first-class tool availability.
+`agent_harness` discovery modes are read-only. `summary` reports the model access map; `panels` and `panel` return the built-in panel catalog, current open/focused state, and each panel's matching Agent workspace route; `ui_surfaces` and `ui_surface` return modal, overlay, picker, and workspace entrypoints with shell-opener availability and preferred model routes; `cli_commands` and `cli_command` return top-level package CLI mirror metadata, parser output, blocked command tokens, and preferred in-process model routes; `shortcuts` returns fixed runtime/editor shortcuts plus configurable keybindings; `keybindings` and `keybinding` return the live resolved keybinding table, default bindings, custom state, and config path; `commands` and `command` return slash-command descriptions plus effect/confirmation/preferred-tool/boundary policy metadata; `workspace_actions` lists Agent workspace actions and can inline editor field schemas with `includeParameters:true`; `workspace_action` returns one action with its editor schema; `tools` can inline model tool JSON schemas with `includeParameters:true`; `settings` returns setting descriptors plus setting policy; `connected_host` returns the connected-host route families, allowed capabilities, blocked capabilities, and first-class tool availability; and `connected_host_status` performs a live read-only check of the connected-host status and Agent Knowledge status routes and reports endpoint bindings, token posture, SDK compatibility, route readiness, and findings without printing token values.
 
 `open_ui_surface` is a confirmation-gated visible navigation mode for the same shell surfaces the user can open: Agent workspace, settings, MCP workspace, model/provider pickers, session/profile pickers, bookmarks, context inspector, help, shortcuts, and onboarding. It does not perform hidden operations; use first-class model tools, settings modes, workspace actions, or confirmed slash-command mirrors for actual state changes.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pellux/goodvibes-agent",
-  "version": "1.0.5",
+  "version": "1.0.6",
   "private": false,
   "description": "GoodVibes personal operator assistant TUI with a proactive Agent product brain, isolated Agent Knowledge, local profiles, routines, skills, personas, and explicit build delegation.",
   "type": "module",

package/src/tools/agent-harness-connected-host-status.ts

@@ -0,0 +1,146 @@
+import type { ToolRegistry } from '@pellux/goodvibes-sdk/platform/tools';
+import { resolveRuntimeEndpointBinding } from '../cli/endpoints.ts';
+import { inspectCliExternalRuntime, type CliExternalRuntimeSnapshot } from '../cli/external-runtime.ts';
+import type { CommandContext } from '../input/command-registry.ts';
+import { connectedHostOperatorTokenFingerprint, readConnectedHostOperatorToken } from '../runtime/connected-host-auth.ts';
+import {
+  blockedConnectedHostCapabilities,
+  connectedHostCapabilityMap,
+  connectedHostRouteFamilies,
+} from './agent-harness-metadata.ts';
+
+const CONNECTED_HOST_STATUS_TIMEOUT_MS = 1500;
+
+function resolveHomeDirectory(context: CommandContext): string {
+  return context.workspace.shellPaths?.homeDirectory
+    ?? context.platform.configManager.getHomeDirectory()
+    ?? '';
+}
+
+function resolveWorkingDirectory(context: CommandContext): string {
+  return context.workspace.shellPaths?.workingDirectory
+    ?? context.platform.configManager.getWorkingDirectory()
+    ?? '';
+}
+
+function connectedHostFindings(
+  runtime: CliExternalRuntimeSnapshot,
+  tokenUsable: boolean,
+): readonly Record<string, unknown>[] {
+  const findings: Record<string, unknown>[] = [];
+
+  if (!runtime.reachable) {
+    findings.push({
+      id: 'connected-host-unreachable',
+      severity: 'warning',
+      summary: 'Connected host is not reachable.',
+      cause: runtime.error ?? `No response from ${runtime.baseUrl}.`,
+      action: 'Start or repair the owning GoodVibes host outside Agent, then recheck connected-host status.',
+    });
+  } else if (!runtime.compatible) {
+    findings.push({
+      id: 'connected-host-version-mismatch',
+      severity: 'warning',
+      summary: 'Connected host SDK version does not match Agent.',
+      cause: `Connected host reports SDK ${runtime.version}; Agent expects ${runtime.expectedVersion}.`,
+      action: 'Update the owning GoodVibes host so its /status route reports the Agent SDK pin.',
+    });
+  }
+
+  if (!tokenUsable) {
+    findings.push({
+      id: 'connected-host-token-missing',
+      severity: 'warning',
+      summary: 'Connected-host operator token is missing or unreadable.',
+      cause: `No usable operator token was found at ${runtime.operatorToken.path}.`,
+      action: 'Provision or repair connected-host access through the owning GoodVibes host.',
+    });
+  }
+
+  if (runtime.reachable && tokenUsable && !runtime.agentKnowledge.ready) {
+    findings.push({
+      id: 'agent-knowledge-route-not-ready',
+      severity: 'warning',
+      summary: 'Isolated Agent Knowledge route is not ready.',
+      cause: `${runtime.agentKnowledge.route} returned ${runtime.agentKnowledge.kind}${runtime.agentKnowledge.statusCode === null ? '' : ` (${runtime.agentKnowledge.statusCode})`}.`,
+      action: 'Update or repair the connected host, then recheck Agent Knowledge compatibility.',
+    });
+  }
+
+  return findings;
+}
+
+export async function connectedHostStatusSummary(
+  context: CommandContext,
+  toolRegistry: ToolRegistry,
+): Promise<Record<string, unknown>> {
+  const homeDirectory = resolveHomeDirectory(context);
+  const workingDirectory = resolveWorkingDirectory(context);
+  const token = readConnectedHostOperatorToken(homeDirectory);
+  const runtime = await inspectCliExternalRuntime({
+    configManager: context.platform.configManager,
+    homeDirectory,
+    timeoutMs: CONNECTED_HOST_STATUS_TIMEOUT_MS,
+  });
+  const tokenUsable = Boolean(token.token);
+
+  return {
+    ownership: 'external-connected-host',
+    readOnly: true,
+    timeoutMs: CONNECTED_HOST_STATUS_TIMEOUT_MS,
+    lifecycle: 'GoodVibes Agent can inspect connected-host readiness and use public operator routes, but does not start, stop, restart, install, expose, or mutate the host listener.',
+    paths: {
+      workingDirectory,
+      homeDirectory,
+    },
+    endpoints: {
+      controlPlane: {
+        enabled: context.platform.configManager.get('controlPlane.enabled'),
+        ...resolveRuntimeEndpointBinding(context.platform.configManager, 'controlPlane'),
+      },
+      httpListener: {
+        enabled: context.platform.configManager.get('danger.httpListener'),
+        ...resolveRuntimeEndpointBinding(context.platform.configManager, 'httpListener'),
+      },
+      web: {
+        enabled: context.platform.configManager.get('web.enabled'),
+        ...resolveRuntimeEndpointBinding(context.platform.configManager, 'web'),
+      },
+    },
+    operatorToken: {
+      present: token.present,
+      usable: tokenUsable,
+      path: token.path,
+      fingerprint: token.token ? `sha256:${connectedHostOperatorTokenFingerprint(token.token)}` : null,
+      error: token.error ?? null,
+    },
+    liveStatus: runtime,
+    routeReadiness: [
+      {
+        id: 'status',
+        route: '/status',
+        reachable: runtime.reachable,
+        statusCode: runtime.statusCode,
+        sdkVersion: runtime.version,
+        expectedSdkVersion: runtime.expectedVersion,
+        compatible: runtime.compatible,
+      },
+      {
+        id: 'agent-knowledge',
+        route: runtime.agentKnowledge.route,
+        ready: runtime.agentKnowledge.ready,
+        kind: runtime.agentKnowledge.kind,
+        statusCode: runtime.agentKnowledge.statusCode,
+      },
+    ],
+    findings: connectedHostFindings(runtime, tokenUsable),
+    modelAccess: {
+      diagnostics: 'Use mode:"connected_host_status" for live read-only host readiness. Use mode:"connected_host" for capability and boundary inventory.',
+      cliMirrors: ['goodvibes-agent status --json', 'goodvibes-agent doctor', 'goodvibes-agent compat'],
+      tuiMirrors: ['Agent Workspace -> Home -> Host compatibility', 'Agent Workspace -> Home -> Doctor diagnostics', 'Agent Workspace -> Home -> Review health'],
+    },
+    routeFamilies: connectedHostRouteFamilies(),
+    capabilities: connectedHostCapabilityMap(toolRegistry),
+    blockedCapabilities: blockedConnectedHostCapabilities(),
+  };
+}

package/src/tools/agent-harness-metadata.ts

@@ -366,6 +366,7 @@ export function connectedHostSummary(context: CommandContext, toolRegistry: Tool
     tokenPath: connection.tokenPath,
     ownership: 'external-connected-host',
     lifecycle: 'GoodVibes Agent can use public connected-host operator routes, but does not start, stop, restart, install, expose, or mutate the host listener.',
+    statusMode: 'Use agent_harness mode:"connected_host_status" for live read-only reachability, SDK compatibility, token posture, and Agent Knowledge route readiness.',
     routeFamilies: connectedHostRouteFamilies(),
     capabilities: connectedHostCapabilityMap(toolRegistry),
     blockedCapabilities: blockedConnectedHostCapabilities(),

package/src/tools/agent-harness-tool-schema.ts

@@ -4,7 +4,7 @@ export const AGENT_HARNESS_MODES = [
   'shortcuts', 'keybindings', 'keybinding', 'set_keybinding', 'reset_keybinding',
   'commands', 'command', 'run_command', 'settings', 'get_setting', 'set_setting',
   'reset_setting', 'workspace', 'workspace_categories', 'workspace_actions',
-  'workspace_action', 'run_workspace_action', 'tools', 'connected_host',
+  'workspace_action', 'run_workspace_action', 'tools', 'connected_host', 'connected_host_status',
 ] as const;
 
 const KEY_COMBO_PARAMETER_SCHEMA = {

package/src/tools/agent-harness-tool.ts

@@ -20,6 +20,7 @@ import { parseSlashCommand } from '../input/slash-command-parser.ts';
 import { blockedHarnessCliCommandTokens, describeHarnessCliCommand, listHarnessCliCommands, totalHarnessCliCommands } from './agent-harness-cli-metadata.ts';
 import { describeHarnessKeybinding, listHarnessKeybindings, listHarnessShortcuts, resetHarnessKeybinding, setHarnessKeybinding, totalHarnessKeybindings, totalHarnessShortcuts } from './agent-harness-keybinding-metadata.ts';
 import { describeHarnessPanel, listHarnessPanels, openHarnessPanel, totalHarnessPanels } from './agent-harness-panel-metadata.ts';
+import { connectedHostStatusSummary } from './agent-harness-connected-host-status.ts';
 import { describeLocalWorkspaceModelExecution, runLocalWorkspaceAction } from './agent-harness-local-operations.ts';
 import { listHarnessModelTools } from './agent-harness-model-tool-catalog.ts';
 import { AGENT_HARNESS_MODES, AGENT_HARNESS_PARAMETER_PROPERTIES } from './agent-harness-tool-schema.ts';
@@ -543,6 +544,7 @@ export function createAgentHarnessTool(deps: AgentHarnessToolDeps): Tool {
               settings: 'Use mode:"settings", mode:"get_setting", mode:"set_setting", and mode:"reset_setting".',
               tools: 'Use mode:"tools" with includeParameters:true to inspect first-class model tool schemas.',
               connectedHost: 'Use mode:"connected_host" for the connected-host capability map and blocked boundaries.',
+              connectedHostStatus: 'Use mode:"connected_host_status" for live read-only host reachability, SDK compatibility, token posture, and Agent Knowledge route readiness.',
             },
             settingsPolicy: settingsPolicySummary(),
             connectedHost: connectedHostSummary(deps.commandContext, deps.toolRegistry),
@@ -680,6 +682,7 @@ export function createAgentHarnessTool(deps: AgentHarnessToolDeps): Tool {
           return output({ tools, returned: tools.length, total: deps.toolRegistry.getToolDefinitions().length });
         }
         if (args.mode === 'connected_host') return output(connectedHostSummary(deps.commandContext, deps.toolRegistry));
+        if (args.mode === 'connected_host_status') return output(await connectedHostStatusSummary(deps.commandContext, deps.toolRegistry));
         return error(`Unhandled agent_harness mode: ${args.mode}`);
       } catch (err) {
         return error(formatHarnessError(err));

package/src/version.ts

@@ -6,7 +6,7 @@ import { join } from 'node:path';
 // The prebuild script updates the fallback value before compilation.
 // Uses import.meta.dir (Bun) to locate package.json relative to this file,
 // which is correct regardless of the process working directory.
-let _version = '1.0.5';
+let _version = '1.0.6';
 let _sdkVersion = '0.33.35';
 try {
   const pkg = JSON.parse(readFileSync(join(import.meta.dir, '..', 'package.json'), 'utf-8')) as {