@haven_ai/connect 0.1.29-alpha.0 → 0.1.31-alpha.0

package/dist/index.d.cts

@@ -12,6 +12,11 @@ interface ConnectApiClient {
      * never any secret material.
      */
     getConnectorStatus(setupId: string, apiKey: string): Promise<ConnectorStatusResponse>;
+    /**
+     * #1700: the agent behind an API key. Used by the re-key flow on both sides
+     * of the dashboard hand-off — see {@link AgentIdentity}.
+     */
+    getAgentIdentity(apiKey: string): Promise<AgentIdentity>;
 }
 interface ConnectorStatusResponse {
     status: string;
@@ -33,6 +38,18 @@ interface RegisterSetupInput extends ResolveSetupInput {
     proofSignature: string;
     apiKeyHash: string;
     apiKeyPrefix: string;
+    /**
+     * #1878: the RESOLVED hosted MCP server name this agent is being wired as —
+     * `haven` for the bare pair, `haven-<slug>` for a named one. Sent so the
+     * dashboard can tell two agents in one harness apart; it is a display aid
+     * and Haven keys nothing off it.
+     *
+     * Always sent by a connector that supports it, bare pair included. Omitting
+     * it for the bare pair would make "absent" ambiguous between *this is the
+     * unnamed pair* and *an older connector said nothing*, and only the second
+     * of those may render as unknown.
+     */
+    mcpServerName?: string;
     connectorContext?: ConnectorContext;
     installCapabilities?: {
         canWriteRuntimeConfig?: boolean;
@@ -105,6 +122,25 @@ interface RegisterSetupResponse {
     hosted_mcp_url: string;
     next_action: string;
 }
+/**
+ * The agent identity behind an API key (#1700).
+ *
+ * Read from `GET /machine-payments/agent`, the same agent-authenticated
+ * endpoint the SDK's `getAgent()` uses. Re-key needs it twice and for two
+ * different questions: BEFORE, to refuse a legacy-rail account the way the
+ * backend would rather than let the owner discover it five signed steps later;
+ * and AFTER, to prove the API key the owner pasted really belongs to this
+ * agent and really names the key this machine just generated.
+ */
+interface AgentIdentity {
+    id: string;
+    name: string;
+    status: string;
+    safe_address: string | null;
+    delegate_address: string | null;
+    chain_id: number | null;
+    execution_rail: 'legacy' | 'delegation' | string;
+}
 declare function createConnectApiClient(baseUrl: string, fetchImpl?: typeof fetch): ConnectApiClient;
 
 interface LocalDelegateKey {
@@ -167,8 +203,8 @@ interface RuntimeProfile {
 }
 declare function runtimeProfile(runtime: string | undefined, env?: NodeJS.ProcessEnv): RuntimeProfile;
 declare function normalizeRuntime(runtime: string | undefined, env?: NodeJS.ProcessEnv): RuntimeId;
-/** The flag values a refusal message should offer. Mirrors RuntimeId. */
-declare const RUNTIME_FLAG_VALUES: "claude-code, codex-cli, codex-desktop, cursor, vscode, vscode-insiders, claude-desktop, hermes, other";
+/** The same values as refusal-message prose. */
+declare const RUNTIME_FLAG_VALUES: string;
 interface RuntimeSelection {
     runtime: RuntimeId | null;
     source: 'force' | 'detected' | 'explicit' | 'prompted' | 'none';
@@ -411,7 +447,7 @@ declare function runtimeInstallCapabilities(runtime: string | undefined, env?: N
     restartRequired: boolean;
 };
 
-declare const CONNECTOR_VERSION = "0.1.29-alpha.0";
+declare const CONNECTOR_VERSION = "0.1.31-alpha.0";
 interface ConnectOptions {
     setupToken: string;
     apiBaseUrl: string;
@@ -479,9 +515,19 @@ interface ConnectOutcome {
     };
     delegate_address?: string;
     setup_challenge_expires_at?: string;
+    /**
+     * #2091, additive within schema_version 1: `message` is the redacted human
+     * refusal (automation used to get code + next_action and nothing to act
+     * on), and `allowed_runtimes` carries the valid `--runtime` retry values on
+     * runtime-selection refusals — the list the backend's setup prompt requires
+     * a retry to be drawn from, which `--json` previously discarded with the
+     * prose.
+     */
     error?: {
         code: string;
         next_action: string;
+        message?: string;
+        allowed_runtimes?: readonly string[];
     };
 }
 interface ConnectDeps {
@@ -519,13 +565,18 @@ declare function completionOutcome(input: {
     approvalRequired: boolean;
 }): ConnectOutcome;
 /**
- * A deliberately terse failure record: error messages can contain server or
- * filesystem detail, while this public contract must remain safe to serialize.
+ * The failure record for the `--json` contract.
  *
  * #1719: a `ConnectError` carries its own code and next action, so it is read
  * rather than guessed. The regex ladder below survives only for the refusals
  * that are still plain `Error`s — every new failure mode joins the vocabulary
  * instead of joining that ladder.
+ *
+ * #2091: the record now carries the redacted message rather than omitting it.
+ * The old stance — terse because "messages can contain server or filesystem
+ * detail" — left automation with a code and nothing to act on; the field
+ * failure was a Codex agent staring at `connect_failed` with, in its own
+ * words, "no additional safe error detail". Sanitize, don't silence.
  */
 declare function failedConnectOutcome(runtimeHint: string | undefined, error: unknown): ConnectOutcome;
 /**
@@ -564,6 +615,16 @@ interface ParsedCli {
         reason?: string;
         replacedBy?: string;
     };
+    /**
+     * #1700: replace an agent's signing key on this machine. Two phases, because
+     * the dashboard sits between them — `start` generates the key and prints its
+     * address, `finish` writes the key the owner brings back. No setup token: the
+     * re-key API is owner-authenticated and this connector never calls it.
+     */
+    rekey?: {
+        phase: 'start' | 'finish';
+        newApiKey?: string;
+    };
 }
 declare function parseArgs(argv: string[], env?: NodeJS.ProcessEnv): ParsedCli;
 declare function helpText(): string;
@@ -588,10 +649,22 @@ declare function shortAddress(address: string): string;
  * Codes are additive and never renamed: a consumer pinned to an older
  * connector must keep recognising the ones it already knows.
  */
+interface ConnectErrorDetails {
+    /**
+     * The `--runtime` values a retry may use, when the refusal is about runtime
+     * selection (#2091). The values lived only in `message` prose, which the
+     * `--json` contract discards entirely — while the backend's setup prompt
+     * instructs an agent to retry only with "one of the values that refusal
+     * lists". Carrying them structurally is what makes that retry reachable
+     * from automation.
+     */
+    allowedRuntimes?: readonly string[];
+}
 declare class ConnectError extends Error {
     readonly code: string;
     readonly nextAction: string;
-    constructor(code: string, message: string, nextAction: string);
+    readonly details: ConnectErrorDetails;
+    constructor(code: string, message: string, nextAction: string, details?: ConnectErrorDetails);
 }
 declare function isConnectError(err: unknown): err is ConnectError;
 
@@ -651,11 +724,11 @@ declare function resolveRuntimeByInstalledClientPrompt(options?: ScanInstalledCl
 
 declare const MCP_RUNTIME_MANIFEST: {
     readonly mcpPackage: "@haven_ai/mcp";
-    readonly mcpVersion: "0.1.29-alpha.0";
+    readonly mcpVersion: "0.1.31-alpha.0";
     readonly sdkPackage: "@haven_ai/sdk";
-    readonly sdkVersion: "0.1.29-alpha.0";
+    readonly sdkVersion: "0.1.31-alpha.0";
     readonly signerPackage: "@haven_ai/signer";
-    readonly signerVersion: "0.1.29-alpha.0";
+    readonly signerVersion: "0.1.31-alpha.0";
     readonly minimumNodeVersion: "22.0.0";
     readonly supportedClients: readonly ["codex-cli", "codex-desktop", "claude-code"];
     readonly requiredTools: readonly string[];

package/dist/index.d.ts

@@ -12,6 +12,11 @@ interface ConnectApiClient {
      * never any secret material.
      */
     getConnectorStatus(setupId: string, apiKey: string): Promise<ConnectorStatusResponse>;
+    /**
+     * #1700: the agent behind an API key. Used by the re-key flow on both sides
+     * of the dashboard hand-off — see {@link AgentIdentity}.
+     */
+    getAgentIdentity(apiKey: string): Promise<AgentIdentity>;
 }
 interface ConnectorStatusResponse {
     status: string;
@@ -33,6 +38,18 @@ interface RegisterSetupInput extends ResolveSetupInput {
     proofSignature: string;
     apiKeyHash: string;
     apiKeyPrefix: string;
+    /**
+     * #1878: the RESOLVED hosted MCP server name this agent is being wired as —
+     * `haven` for the bare pair, `haven-<slug>` for a named one. Sent so the
+     * dashboard can tell two agents in one harness apart; it is a display aid
+     * and Haven keys nothing off it.
+     *
+     * Always sent by a connector that supports it, bare pair included. Omitting
+     * it for the bare pair would make "absent" ambiguous between *this is the
+     * unnamed pair* and *an older connector said nothing*, and only the second
+     * of those may render as unknown.
+     */
+    mcpServerName?: string;
     connectorContext?: ConnectorContext;
     installCapabilities?: {
         canWriteRuntimeConfig?: boolean;
@@ -105,6 +122,25 @@ interface RegisterSetupResponse {
     hosted_mcp_url: string;
     next_action: string;
 }
+/**
+ * The agent identity behind an API key (#1700).
+ *
+ * Read from `GET /machine-payments/agent`, the same agent-authenticated
+ * endpoint the SDK's `getAgent()` uses. Re-key needs it twice and for two
+ * different questions: BEFORE, to refuse a legacy-rail account the way the
+ * backend would rather than let the owner discover it five signed steps later;
+ * and AFTER, to prove the API key the owner pasted really belongs to this
+ * agent and really names the key this machine just generated.
+ */
+interface AgentIdentity {
+    id: string;
+    name: string;
+    status: string;
+    safe_address: string | null;
+    delegate_address: string | null;
+    chain_id: number | null;
+    execution_rail: 'legacy' | 'delegation' | string;
+}
 declare function createConnectApiClient(baseUrl: string, fetchImpl?: typeof fetch): ConnectApiClient;
 
 interface LocalDelegateKey {
@@ -167,8 +203,8 @@ interface RuntimeProfile {
 }
 declare function runtimeProfile(runtime: string | undefined, env?: NodeJS.ProcessEnv): RuntimeProfile;
 declare function normalizeRuntime(runtime: string | undefined, env?: NodeJS.ProcessEnv): RuntimeId;
-/** The flag values a refusal message should offer. Mirrors RuntimeId. */
-declare const RUNTIME_FLAG_VALUES: "claude-code, codex-cli, codex-desktop, cursor, vscode, vscode-insiders, claude-desktop, hermes, other";
+/** The same values as refusal-message prose. */
+declare const RUNTIME_FLAG_VALUES: string;
 interface RuntimeSelection {
     runtime: RuntimeId | null;
     source: 'force' | 'detected' | 'explicit' | 'prompted' | 'none';
@@ -411,7 +447,7 @@ declare function runtimeInstallCapabilities(runtime: string | undefined, env?: N
     restartRequired: boolean;
 };
 
-declare const CONNECTOR_VERSION = "0.1.29-alpha.0";
+declare const CONNECTOR_VERSION = "0.1.31-alpha.0";
 interface ConnectOptions {
     setupToken: string;
     apiBaseUrl: string;
@@ -479,9 +515,19 @@ interface ConnectOutcome {
     };
     delegate_address?: string;
     setup_challenge_expires_at?: string;
+    /**
+     * #2091, additive within schema_version 1: `message` is the redacted human
+     * refusal (automation used to get code + next_action and nothing to act
+     * on), and `allowed_runtimes` carries the valid `--runtime` retry values on
+     * runtime-selection refusals — the list the backend's setup prompt requires
+     * a retry to be drawn from, which `--json` previously discarded with the
+     * prose.
+     */
     error?: {
         code: string;
         next_action: string;
+        message?: string;
+        allowed_runtimes?: readonly string[];
     };
 }
 interface ConnectDeps {
@@ -519,13 +565,18 @@ declare function completionOutcome(input: {
     approvalRequired: boolean;
 }): ConnectOutcome;
 /**
- * A deliberately terse failure record: error messages can contain server or
- * filesystem detail, while this public contract must remain safe to serialize.
+ * The failure record for the `--json` contract.
  *
  * #1719: a `ConnectError` carries its own code and next action, so it is read
  * rather than guessed. The regex ladder below survives only for the refusals
  * that are still plain `Error`s — every new failure mode joins the vocabulary
  * instead of joining that ladder.
+ *
+ * #2091: the record now carries the redacted message rather than omitting it.
+ * The old stance — terse because "messages can contain server or filesystem
+ * detail" — left automation with a code and nothing to act on; the field
+ * failure was a Codex agent staring at `connect_failed` with, in its own
+ * words, "no additional safe error detail". Sanitize, don't silence.
  */
 declare function failedConnectOutcome(runtimeHint: string | undefined, error: unknown): ConnectOutcome;
 /**
@@ -564,6 +615,16 @@ interface ParsedCli {
         reason?: string;
         replacedBy?: string;
     };
+    /**
+     * #1700: replace an agent's signing key on this machine. Two phases, because
+     * the dashboard sits between them — `start` generates the key and prints its
+     * address, `finish` writes the key the owner brings back. No setup token: the
+     * re-key API is owner-authenticated and this connector never calls it.
+     */
+    rekey?: {
+        phase: 'start' | 'finish';
+        newApiKey?: string;
+    };
 }
 declare function parseArgs(argv: string[], env?: NodeJS.ProcessEnv): ParsedCli;
 declare function helpText(): string;
@@ -588,10 +649,22 @@ declare function shortAddress(address: string): string;
  * Codes are additive and never renamed: a consumer pinned to an older
  * connector must keep recognising the ones it already knows.
  */
+interface ConnectErrorDetails {
+    /**
+     * The `--runtime` values a retry may use, when the refusal is about runtime
+     * selection (#2091). The values lived only in `message` prose, which the
+     * `--json` contract discards entirely — while the backend's setup prompt
+     * instructs an agent to retry only with "one of the values that refusal
+     * lists". Carrying them structurally is what makes that retry reachable
+     * from automation.
+     */
+    allowedRuntimes?: readonly string[];
+}
 declare class ConnectError extends Error {
     readonly code: string;
     readonly nextAction: string;
-    constructor(code: string, message: string, nextAction: string);
+    readonly details: ConnectErrorDetails;
+    constructor(code: string, message: string, nextAction: string, details?: ConnectErrorDetails);
 }
 declare function isConnectError(err: unknown): err is ConnectError;
 
@@ -651,11 +724,11 @@ declare function resolveRuntimeByInstalledClientPrompt(options?: ScanInstalledCl
 
 declare const MCP_RUNTIME_MANIFEST: {
     readonly mcpPackage: "@haven_ai/mcp";
-    readonly mcpVersion: "0.1.29-alpha.0";
+    readonly mcpVersion: "0.1.31-alpha.0";
     readonly sdkPackage: "@haven_ai/sdk";
-    readonly sdkVersion: "0.1.29-alpha.0";
+    readonly sdkVersion: "0.1.31-alpha.0";
     readonly signerPackage: "@haven_ai/signer";
-    readonly signerVersion: "0.1.29-alpha.0";
+    readonly signerVersion: "0.1.31-alpha.0";
     readonly minimumNodeVersion: "22.0.0";
     readonly supportedClients: readonly ["codex-cli", "codex-desktop", "claude-code"];
     readonly requiredTools: readonly string[];