From a45bcf7f01e26549efae588b3301d489b393d50a Mon Sep 17 00:00:00 2001
From: SirKentut <81878031+SirKentut@users.noreply.github.com>
Date: Thu, 18 Jun 2026 02:36:32 -0700
Subject: [PATCH] [pierre] docs: note OPENSWARM_APP bridge works in lightweight
 app builder mode

---
 backend/apps/outputs/app_builder_skill.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/backend/apps/outputs/app_builder_skill.md b/backend/apps/outputs/app_builder_skill.md
index 8c3b86bf..66a5e8ec 100644
--- a/backend/apps/outputs/app_builder_skill.md
+++ b/backend/apps/outputs/app_builder_skill.md
@@ -56,6 +56,13 @@ fast.
 3. Leave `frontend/package.json`, `frontend/vite.config.ts`, `run.sh`,
    `.env`, `meta.json` alone — vite still needs them.
 4. Don't run `bash backend_init.sh` — lightweight mode has no backend.
+5. Agent control still works without the template: `window.OPENSWARM_APP` is
+   injected by the app shell, so even here you can make the app agent-operable
+   by calling `window.OPENSWARM_APP.register({ rules, controls, getState,
+   invoke })` from your inline `<script>` (see the bridge section below). This is
+   optional, the agent can also play any app via native keyboard/mouse, but for
+   a game/canvas a registered `getState` (e.g. score, alive) makes it far more
+   reliable. Don't wire up the bridge object yourself; it already exists.
 
 The rest of this document covers **workspace mode**. If you picked
 lightweight, only the "Debugging" section (frontend console logs in the