Struct CreateSessionInput 

pub struct CreateSessionInput {
    pub id: String,
    pub title: Option<String>,
    pub system_prompt: Option<String>,
    pub model: Option<String>,
    pub model_ref: Option<ProviderModelRef>,
    pub reasoning_effort: Option<ReasoningEffort>,
    pub gold_config_json: Option<String>,
    pub workspace_path: Option<String>,
}

Request-level input for session creation.

Fields

id: String

title: Option<String>

system_prompt: Option<String>

model: Option<String>

model_ref: Option<ProviderModelRef>

reasoning_effort: Option<ReasoningEffort>

gold_config_json: Option<String>

workspace_path: Option<String>

Optional workspace path, same semantics as ChatTurnInput::workspace_path (#480: connect bridge sets workspace at session-creation; an external connector using POST /sessions should be able to as well). Only the metadata write happens here — syncing the runtime workspace directory on disk (ensure_session_workspace) is a handler-layer concern, same split as the chat turn use case.