Struct AttachOpts 

pub struct AttachOpts {
    pub profile: Option<String>,
    pub id: Option<String>,
    pub continue_session: Option<Option<String>>,
    pub system: Option<String>,
    pub prompt_manifest: Option<PathBuf>,
    pub mode: AttachMode,
    pub no_confirm_answers: bool,
    pub keep_warm: bool,
    pub new_session: bool,
    pub name: Option<String>,
    pub client_name: Option<String>,
    pub adopted: bool,
}

What to attach to.

Fields

profile: Option<String>

id: Option<String>

Session id (prefix ok); None = the only live session, else create.

continue_session: Option<Option<String>>

Create by continuing a saved session (name or id). --continue [NAME_OR_ID]: Some(None) = most recent journal (bare --continue), Some(Some(x)) = that one. Must stay two-level: the attach path used to flatten it, which turned a bare --continue into a fresh session under adopt / --new (soak F21).

system: Option<String>

prompt_manifest: Option<PathBuf>

mode: AttachMode

no_confirm_answers: bool

--no-confirm-answers: never answer confirm prompts (tool-call and tool-activation approvals) from this TUI, whatever keys reach it; they are only listed as waiting for another client. Secret prompts are still typed here.

keep_warm: bool

new_session: bool

--new/--create: always create a fresh session even if one is live. Rejected together with an explicit id.

name: Option<String>

--name: name the created session (synaps send --session <name> resolves it at once).

client_name: Option<String>

--as: what this client is called in the session; None = SYNAPS_CLIENT_NAME, else the daemon’s default (tui, tui-2, …).

adopted: bool

A plain synaps adopted a running daemon (no explicit --attach): after attaching, show what else lives in this daemon so parked work stays discoverable (F1).