@rubytech/create-maxy-code 0.1.565 → 0.1.566

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy-code",
-  "version": "0.1.565",
+  "version": "0.1.566",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy-code": "./dist/index.js"

package/payload/platform/config/brand-registry.json

@@ -6,7 +6,7 @@
       "vncDisplay": 99,
       "rfbPort": 5900,
       "websockifyPort": 6080,
-      "cdpPort": 9222
+      "cdpPort": 9322
     },
     {
       "hostname": "property-administrators",

package/payload/platform/config/brand.json

@@ -12,7 +12,7 @@
   "vncDisplay": 99,
   "rfbPort": 5900,
   "websockifyPort": 6080,
-  "cdpPort": 9222,
+  "cdpPort": 9322,
   "claudeSessionManagerPort": 19400,
   "outlookClientId": "",
   "googleClientId": "",

package/payload/platform/plugins/admin/skills/whats-new/SKILL.md

@@ -9,6 +9,10 @@ Invoked by the admin agent directly.
 
 This is the platform's release timeline, newest first. Each entry shows the date it shipped and the version it shipped in, so you can tell the operator how current their install is. To compare, read the installed version from `capabilities-here` and match it against the versions below. Keep answers high level and in plain English; this is a summary, not a full commit log.
 
+## 2026-08-05 (0.1.566)
+
+- Installing or upgrading Maxy on a machine that also runs another Maxy-family product no longer fails because a browser is in the way. Maxy's browser-automation port was the one every browser tool picks by default when nothing tells it otherwise, so an assistant on the other product could take it and the install would stop rather than write over a port in use. Maxy now uses a port outside that range.
+
 ## 2026-08-05 (0.1.565)
 
 - Every channel now delivers the assistant's answer the same way the admin webchat does: the answer is taken from the conversation record and sent. Previously WhatsApp, Telegram and the public webchat asked the assistant to call a send tool, so an answer was suppressed when it called and lost entirely when it did not. Long answers arrive as ordered segments, and an answer meant for you fans out to every channel you have live, naming any that could not be reached.

package/payload/platform/scripts/vnc.sh

@@ -21,12 +21,21 @@
 # rfbport, websockify port, and CDP port are all brand-scoped so any number
 # of brands on the same device run their full VNC stacks concurrently
 # without sharing session cookies, extensions, local storage, or display
-# binding. Defaults: Maxy=:99/5900/6080/9222, Real Agent=:100/5901/6081/
+# binding. Defaults: Maxy=:99/5900/6080/9322, Real Agent=:100/5901/6081/
 # 9223, Maxy-2=:101/5902/6082/9224, Maxy-3=:102/5903/6083/9225,
 # Maxy-4=:103/5904/6084/9226. Each brand's port set is stamped in
 # brand.json at install time and re-read at runtime; missing fields are
 # derived from `vncDisplay` via the ordinal offset rule.
 #
+# Maxy's CDP port is the one deliberate break from that rule. The ordinal
+# value for display :99 is 9222, which is Chrome's own universal default,
+# so any agent-side browser tool that launches Chromium without being told
+# a port lands on it. On a box where Maxy co-resides with another brand,
+# that brand's account agents kept taking 9222 and the installer's
+# UNRELATED-holder preflight then refused to write Maxy's service files.
+# 9322 sits outside the 922x block, which the offset rule cannot reach
+# until display :199, so no future brand can derive onto it either.
+#
 # retired the admin-UI terminal surface entirely. This script
 # no longer spawns GUI terminal emulators of any kind; upgrades and
 # cloudflare-setup actions run via the detached action runner