@tangle-network/agent-provider-cli-bridge 0.5.0 → 0.6.1

package/README.md

@@ -23,6 +23,7 @@ const reference = await environment.dispatch({
   sessionId: 'research-session',
   executionId: 'research-turn-1',
 })
+await saveControlRef(reference.controlRef)
 const session = environment.session(reference.id)
 
 for await (const event of session.events({ since: '0' })) {
@@ -35,6 +36,11 @@ await session.prompt({
 })
 ```
 
+Persist the returned `controlRef` before treating dispatch as accepted.
+It contains the exact provider, environment, session, execution, run, and request digest needed after a process restart.
+Reconstruct the environment with `provider.get(controlRef.environmentId)`, then call `environment.session(controlRef.sessionId, { controlRef })`.
+The provider rejects any coordinate or digest mismatch instead of attaching to a different run.
+
 The bridge model is selected from run data in this order: the turn, the provider default, or the profile's `harness` plus `model.default`.
 Execution fails before network use when none is present.
 
@@ -43,6 +49,8 @@ Passing the same `sessionId` on later turns continues the same CLI conversation.
 `dispatch()` starts a bridge-owned durable run and returns after detaching its HTTP reader.
 The returned `AgentSession` exposes status, cursor-based event replay, the terminal result, continuation, and cancellation.
 Cancellation returns only after cli-bridge confirms the run is terminal.
+Usage events and terminal result metadata include `modelRequests` only when the bridge measured an exact non-negative integer count.
+Missing, malformed, partial, or estimated request counts remain unknown.
 When `dispatch()` receives no `sessionId`, it creates one from that turn's stable run id and returns it.
 Replay and result reads fail loudly after cli-bridge's configured replay retention expires.
 Stopping a `session.events()` reader detaches only that replay observer.

package/dist/index.d.ts

@@ -1,33 +1,11 @@
 import type { AgentEnvironmentCapabilities, AgentEnvironmentProvider } from "@tangle-network/agent-interface/environment-provider";
 import { type HarnessType } from "@tangle-network/agent-interface";
-export interface CliBridgeProviderOptions {
-    baseUrl: string;
-    bearerToken?: string;
-    defaultModel?: string;
-    defaultMode?: "byob" | "hosted-safe" | "hosted-sandboxed";
-    defaultExecution?: {
-        kind: "host";
-    } | {
-        kind: "sandbox";
-        repoUrl?: string;
-        gitRef?: string;
-        capability?: string;
-        ttlSeconds?: number;
-    };
-    /** Maximum wait for response headers. Defaults to no timeout. */
-    headersTimeoutMs?: number;
-    /** Maximum idle time between response body chunks. Defaults to no timeout. */
-    bodyTimeoutMs?: number;
-    /** Maximum wait for cli-bridge to confirm cancellation. Defaults to 30 seconds. */
-    cancelWaitMs?: number;
-    fetch?: typeof fetch;
-    name?: string;
-    capabilities?: AgentEnvironmentCapabilities;
-}
+import { type CliBridgeProviderOptions } from "./provider-options.js";
+export type { CliBridgeProviderOptions } from "./provider-options.js";
 export declare function createCliBridgeProvider(options: CliBridgeProviderOptions): AgentEnvironmentProvider;
 /**
- * @param harness The bridge backend these capabilities describe. The prompt intents belong to that
- * harness, not to this adapter — the adapter only forwards `agent_profile`. Omit it and both intents
- * declare `false`: an adapter that cannot name its harness cannot promise either one.
+ * Describe the bridge backend, not this adapter.
+ *
+ * The adapter forwards an AgentProfile but does not own harness prompt controls.
  */
 export declare function defaultCliBridgeCapabilities(harness?: HarnessType): AgentEnvironmentCapabilities;