Create or reconnect to a PTY session.

Looks up the PTY session identified by the path session_name and either reconnects to the existing session or creates it if it does not yet exist. The session_name is a client-chosen session identifier, not an opaque server-issued ID. It must be non-empty and use only ASCII letters, digits, ’-’ and ’_’. Bootstrap parameters such as terminal dimensions may be supplied on the initial connect request. A newly created PTY session starts an interactive bash shell on the Devbox. If a client is already attached to the named session, a new concurrent connect request is rejected rather than attaching a second live client. If the active client disconnects, the PTY session is preserved for a bounded idle TTL so a later request using the same session_name can reconnect to the same shell state. After that TTL expires, or after the underlying Devbox lifecycle replaces the PTY process such as through suspend/resume, a later request with the same session_name creates a fresh PTY session without the previous shell state. The response returns the information needed to attach to the PTY data plane, but the interactive byte stream itself is intentionally not modeled in OpenAPI.

Documentation note: this operation is published from mux strictly as an OpenAPI contract stub for the PTY service control plane. It is not evidence that mux itself serves the interactive PTY transport.