SDK and stream-json startup output can report the messaging socket path when the inbox is running.
messaging_socket_path only appears when the default-off cross-session inbox has started.
What's wrong with this entry?
The system/init message sent to SDK and stream-json consumers now carries messaging_socket_path, read from the running cross-session messaging module rather than from the environment. It is only set when that messaging inbox started, which is itself gated off by default.
messaging_socket_path
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.232
Clearer failures when the messaging socket path is unusable
Both mention socket path
-
v2.1.247
--messaging-socket-pathnow errors instead of silently doing nothingBoth mention socket path
-
v2.1.248
Peer address row in the info panel
Both mention socket cross