Context
The cloud cold walk for neomjs/neo#20114 (2026-10-26, a fresh container, npx neo-app@13.3.2, the published neo-neural-link@1.0.0) loaded the app twice with the Bridge already running. Both times healthcheck and get_window_topology listed no windows, so simulate_event, which needs a windowId, could only be routed by copying an id out of query_component's output. Connections made after the app started (a focus retry, a reconnect after the Bridge was killed) did register the window.
The Problem
This is the normal agent flow: the harness starts the Neural Link first, then the dev server and page. With the Bridge already up, the socket opens about 0.5 s into the load, before Neo.app() has registered the application, and the window is never announced afterwards.
The Architectural Reality
src/ai/Client.mjs onSocketOpen (:304-356) announces windows once, at open time: from WindowManager.items, and for a non-SharedWorker app from the Neo.apps registry (:347-356).
onAppWorkerWindowConnect (:217) runs only for SharedWorker connect events.
src/controller/Application.mjs:82 registers Neo.apps[me.windowId] = me later, and nothing notifies the client. A grep of src finds only those three window_connected sends.
The Fix
When a non-SharedWorker application registers while the Neural Link socket is open, announce its window once (appName, windowId), through the same window_connected notification onSocketOpen sends. Keep the open-time rehydration for windows that already exist, and never announce a windowId twice.
Acceptance Criteria
Out of Scope
- The client's deliberate stop after five reconnect attempts (
onSocketReconnectFailed / redial, "never on a timer"). That trade-off is documented for agents in the create-app and skills leaves of #20114.
Related
Parent: neomjs/neo#20114 · cloud-walk receipt on #20114
Sweeps (2026-10-26T15:52Z): live latest-open, the 20 newest neomjs/neo issues, no equivalent; keyword window_connected / "announce its window" / "No active App Worker sessions", none open; A2A, latest 30 messages, no claim; own-assignment, #20114, #20128, #19919 and #15000, none overlapping.
Origin Session ID: 9853627c-2129-4d41-b905-0c74bec35a48
Retrieval Hint: "Neo.ai.Client onSocketOpen window_connected Neo.apps registers after socket open get_window_topology empty simulate_event windowId"
Context
The cloud cold walk for neomjs/neo#20114 (2026-10-26, a fresh container,
npx neo-app@13.3.2, the publishedneo-neural-link@1.0.0) loaded the app twice with the Bridge already running. Both timeshealthcheckandget_window_topologylisted no windows, sosimulate_event, which needs awindowId, could only be routed by copying an id out ofquery_component's output. Connections made after the app started (a focus retry, a reconnect after the Bridge was killed) did register the window.The Problem
This is the normal agent flow: the harness starts the Neural Link first, then the dev server and page. With the Bridge already up, the socket opens about 0.5 s into the load, before
Neo.app()has registered the application, and the window is never announced afterwards.The Architectural Reality
src/ai/Client.mjsonSocketOpen(:304-356) announces windows once, at open time: fromWindowManager.items, and for a non-SharedWorker app from theNeo.appsregistry (:347-356).onAppWorkerWindowConnect(:217) runs only for SharedWorkerconnectevents.src/controller/Application.mjs:82registersNeo.apps[me.windowId] = melater, and nothing notifies the client. A grep ofsrcfinds only those threewindow_connectedsends.The Fix
When a non-SharedWorker application registers while the Neural Link socket is open, announce its window once (
appName,windowId), through the samewindow_connectednotificationonSocketOpensends. Keep the open-time rehydration for windows that already exist, and never announce awindowIdtwice.Acceptance Criteria
window_connectedcarrying the app'sappNameandwindowIdis sent once the app registers (unit, red-first ondev).get_window_topologylists the window andsimulate_eventroutes with thatwindowId.Out of Scope
onSocketReconnectFailed/redial, "never on a timer"). That trade-off is documented for agents in the create-app and skills leaves of #20114.Related
Parent: neomjs/neo#20114 · cloud-walk receipt on #20114
Sweeps (2026-10-26T15:52Z): live latest-open, the 20 newest
neomjs/neoissues, no equivalent; keywordwindow_connected/ "announce its window" / "No active App Worker sessions", none open; A2A, latest 30 messages, no claim; own-assignment, #20114, #20128, #19919 and #15000, none overlapping.Origin Session ID: 9853627c-2129-4d41-b905-0c74bec35a48 Retrieval Hint: "Neo.ai.Client onSocketOpen window_connected Neo.apps registers after socket open get_window_topology empty simulate_event windowId"