Module forge_sdk_bridge 

ForgeSdkBridge - in-process driver around a forge_sdk::Client.

Drives a forge_sdk::Client directly - no Node.js subprocess, no NDJSON, no command queue. The bridge holds the spawned Arc<Client> and dispatches each method as a direct call (or a tokio::spawn’d async task when the method is fire-and-forget). Synthesized events (Connected, PermissionRequest, McpSnapshot, …) flow back through an mpsc::UnboundedSender<AgentEvent> the bridge owns; consumers grab the matching receiver once via ForgeSdkBridge::take_events.

    view                    ForgeSdkBridge                  forge_sdk::Client
     | trait method            |                                    |
     |------------------------>|  client.method().await             |
     |                         |----------------------------------->|
     |                         |                                    |
     |       AgentEvent        |  reader_loop / callbacks           |
     |<------ event_tx --------+<-----------------------------------|

Re-exports

use std::collections::HashMap; 🔒

use std::path::Path; 🔒

use std::path::PathBuf; 🔒

use std::sync::Arc; 🔒

use std::time::Instant; 🔒

use forge_sdk::Client; 🔒

use parking_lot::Mutex; 🔒

use serde_json::Value; 🔒

use tokio::sync::mpsc; 🔒

use tokio::sync::oneshot; 🔒

use tracing::Instrument; 🔒

use crate::client::AgentEvent; 🔒

use crate::client::SessionLaunchSettings; 🔒

use crate::client::SpawnFailureKind; 🔒

use crate::forge_sdk_worker; 🔒

use crate::forge_sdk_worker::SessionId; 🔒

use forge_primitives::PermissionMode; 🔒

use forge_primitives::PermissionOutcome; 🔒

use forge_primitives::QuestionOutcome; 🔒

Structs

BridgeInner 🔒

ForgeSdkBridge

In-process bridge wrapping a single forge_sdk::Client.

ProbeInFlight 🔒

Holds a seat’s probe mark while its probe is out, and releases it however the probe ends: an answer, an error, a timeout, or a dispatch that never reached a client at all.

Constants

TESTING_STUB_CONFIG_DIR 🔒

Sentinel config_dir for ForgeSdkBridge test stubs that never exercise the path. Production code constructs the bridge with a real account config_dir; tests that don’t drive a session use this path so the typed field stays non-optional.

Functions

spawn_failure_kind 🔒

Name the class of a spawn failure from the SDK error itself, so a consumer never has to infer it from the rendered message.

turn_error 🔒

The turn-error event for a failure forge hit itself, classified where the message is built: a reader branching on the class gets it without searching the prose.

Type Aliases

PendingQuestions 🔒

Pending question outcomes keyed by tool_use_id. The AskUserQuestion driver in the can_use_tool callback parks a fresh oneshot per question, emits a QuestionRequest, and awaits the matching question_response.

PendingResponses 🔒

Pending permission responses keyed by tool_use_id. The can_use_tool callback parks a oneshot here when the CLI asks; dispatch drains it when the matching permission_response arrives from a view.