@technomoron/agent-run 0.99.33 → 0.99.34

package/CHANGES

@@ -1,6 +1,13 @@
 CHANGES
 =======
 
+Version 0.99.34 (2026-09-07)
+----------------------------
+* Keep the agent-brain socket under the configured root so the service and
+  MCP clients connect regardless of their environment. Restart the service
+  and agent sessions after upgrading.
+* Remove the runtime-directory environment variable from the service helper.
+
 Version 0.99.33 (2026-09-06)
 ----------------------------
 * Run the agent-brain MCP server as `agent-brain` from `PATH` and choose its

package/README.md

@@ -865,8 +865,9 @@ agent-brain serve
 ```
 
 The service hosts SDK Streamable HTTP at `/mcp` using apicore's Fastify instance.
-It listens on `$XDG_RUNTIME_DIR/agent-brain.sock`, or
-`~/.agent-run/runtime/agent-brain.sock` when that variable is absent. The socket
+It listens on `<config-root>/runtime/agent-brain.sock`, which defaults to
+`~/.agent-run/runtime/agent-brain.sock`. Both the service and clients use the
+configured root regardless of their environment. The socket
 directory must belong to the current user and have mode `0700`; the socket has
 mode `0600`. No TCP listener or application user database is created.
 
@@ -874,7 +875,9 @@ Generated native-agent configurations run `agent-brain mcp` through `PATH`, so
 `agent-brain` must be installed and available there. The bridge selects the socket
 when it starts; generated files do not depend on the installation or runtime
 directory used to render them. Re-render existing profiles with `agent-run update`
-to replace older commands that contain absolute installation paths.
+to replace older commands that contain absolute installation paths. After
+upgrading from a version that used a different socket location, restart the service and
+agent sessions so they use the socket under the configuration root.
 
 `agent-run mcp` also bridges native-agent stdio to this socket. Use `--socket PATH`
 for a particular service. The bridge verifies the socket's ownership and private
@@ -888,8 +891,9 @@ stopped. Starting a second service on an existing socket fails without replacing
 the first service's socket.
 
 For a user service, copy `ops/systemd/agent-brain.service` to
-`~/.config/systemd/user/`, adjust `ExecStart` if your executable is elsewhere, and
-run `systemctl --user daemon-reload` followed by
+`~/.config/systemd/user/` and adjust `ExecStart` if your executable is elsewhere.
+Add `--configdir PATH` to `ExecStart` if you use a custom configuration root.
+Run `systemctl --user daemon-reload` followed by
 `systemctl --user enable --now agent-brain`. Installation is explicit.
 
 The supplied service uses `serve --pull`. On startup this pulls the configuration

package/dist/brain/config.js

@@ -14,7 +14,7 @@ const yaml_1 = require("yaml");
 const zod_1 = require("zod");
 const utils_1 = require("../utils");
 function defaultSocketPath(configRoot) {
-    return path.join(process.env.XDG_RUNTIME_DIR ?? path.join(configRoot, 'runtime'), 'agent-brain.sock');
+    return path.join(configRoot, 'runtime', 'agent-brain.sock');
 }
 exports.brainConfigSchema = zod_1.z.object({
     enabled: zod_1.z.boolean().default(true),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@technomoron/agent-run",
-  "version": "0.99.33",
+  "version": "0.99.34",
   "packageManager": "pnpm@10.34.5",
   "bin": {
     "agent-run": "dist/agent-run.js",

package/scripts/ensure-agent-brain.sh

@@ -17,7 +17,7 @@ for account in "$@"; do
 	loginctl enable-linger "$username"
 	systemctl start "user@$uid.service"
 	user_systemctl() {
-		runuser -u "$username" -- env "XDG_RUNTIME_DIR=/run/user/$uid" "DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$uid/bus" systemctl --user "$@"
+		runuser -u "$username" -- env "DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$uid/bus" systemctl --user "$@"
 	}
 	user_systemctl daemon-reload
 	user_systemctl enable agent-brain.service