From c40fe774ded9e1700f4c5ab3c43e7feeec5f4815 Mon Sep 17 00:00:00 2001 From: Dario Gabriel Lipicar Date: Sun, 27 Sep 2026 19:22:46 -0300 Subject: [PATCH] docs: the daemon listens on its local socket only MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit tcp and tcp_ssl were removed in logos-protocol 0.15. §6.1 says the daemon listens on its local socket only and points to §9.6 for another computer or runtime; the logoscore paragraph says its tcp and tcp_ssl flags are refused. Co-Authored-By: Claude Opus 5.5 --- logos-developer-guide.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/logos-developer-guide.md b/logos-developer-guide.md index e8bbd74..fb7f88e 100644 --- a/logos-developer-guide.md +++ b/logos-developer-guide.md @@ -1103,7 +1103,9 @@ continue to use the runtime paths embedded by the build and packaging tools. `logosctl`'s daemon and client are plain C++ and use the local `qt_remote_plain` transport. Modules built with `qt_remote` still interoperate unchanged, because their Qt plugin loading and Qt runtime stay inside the -separate `logos_host_qt` compatibility process. +separate `logos_host_qt` compatibility process. The daemon listens on its local +socket only: to operate it from another computer, or to call its modules from +another runtime, see [§9.6](#96-linking-runtimes-peering). The daemon finds `logos_runtime` beside its own executable (or at `LOGOS_RUNTIME_PATH`), and the runtime finds the host processes beside it, or in @@ -1234,7 +1236,7 @@ credential. #### `logoscore` -`logoscore` is the same runtime without package management or sessions: its daemon loads modules straight from a directory (`logoscore -D -m ./modules`) and keeps its state in `~/.logoscore`. It is no longer released. Build it from source with `nix build 'github:logos-co/logos-logoscore-cli#cli'` if you need it; its client commands are the old spellings of the ones above (`load-module`, `module-info`, `list-modules`, `status`, `stop`). Its daemon takes the placement policy and bundled directories as `--placement` and `--bundled-modules-dir`. +`logoscore` is the same runtime without package management or sessions: its daemon loads modules straight from a directory (`logoscore -D -m ./modules`) and keeps its state in `~/.logoscore`. It is no longer released. Build it from source with `nix build 'github:logos-co/logos-logoscore-cli#cli'` if you need it; its client commands are the old spellings of the ones above (`load-module`, `module-info`, `list-modules`, `status`, `stop`). Its daemon takes the placement policy and bundled directories as `--placement` and `--bundled-modules-dir`. Since logos-protocol 0.15 it too listens on its local socket only, and refuses the `tcp` and `tcp_ssl` flags it used to take. ---