@homie-rocks/studio 0.30.1 → 0.30.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -17,9 +17,44 @@ To bring a studio up to date, tell Claude: "Upgrade my studio to the newest Homi
17
17
  `npx -y @homie-rocks/studio@latest upgrade`, which shows what's new since the version your studio pins (from this
18
18
  file) and what the upgrade would change, and changes nothing until you agree.
19
19
 
20
+ ## [0.30.2] - 2026-10-04
21
+
22
+ **Plugin 0.31.2** · [#48](https://github.com/homie-rocks/homie/pull/48)
23
+
24
+ Fixes from first runs in Codex and Grok: a missing connector no longer stops a new studio, you are told when Homie's holds are off (in Grok they are), Grok has an install command, and a one-sentence studio gives you a Play link before it polishes.
25
+
26
+ ### Added
27
+
28
+ - `homie-studio setup status --client codex` (or `--client grok`) has a row, **Homie's holds**: on when the plugin's hooks ran in that app in the last ten minutes, off otherwise, with how to turn them on. Codex runs no plugin's hooks until you trust them in `/hooks`, and says nothing when it skips them, so a session where nothing was held looked the same as one where everything was. The hooks now leave a small dated mark each time they run (in `.cache/homie-studio/holds/` of your home folder: the app, the time and which hook, nothing else), and the status reads it. When the holds are off, your AI says so in its first reply and asks you itself before a deploy, a Cloudflare change, a paid call or a model download. When they are on, nothing changes. In Grok the row is off (see Fixed).
29
+ - The setup status says when another MCP server has taken the connector's name. The plugin's connector is the MCP server `homie`. If your Codex or Grok configuration already has a server of that name, that one keeps the name and the plugin's tools do not load. The connector row says so and gives the command that adds Homie's connector under its own name (`codex mcp add homie-rocks --url https://homie.rocks/mcp`), which your AI runs only with your yes. It reads only whether your entry is an address or a command, never the command itself.
30
+ - Grok Build has an install command in the README: `grok plugin install homie-rocks/homie#plugins/homie` (checked on Grok Build 1.0.41). Grok asks whether to trust the plugin, and loads its skills, its MCP server and its hooks once you do.
31
+ - A note you send to Homie from Grok says it came from Grok, not from "another app".
32
+
33
+ ### Changed
34
+
35
+ - **A missing connector no longer stops a new studio.** In Codex, "set up a game studio called X and make a multiplayer game" stopped after a minute with nothing made: the `studio-setup` skill said to stop when the Homie connector was not connected. A session that can run commands does not need it. Your AI now says in one line that the connector is not connected and what it would add, and makes the studio with the toolkit's own command (`npx -y @homie-rocks/studio@latest new <folder> --name "<Name>"`). It stops only when it has neither the connector nor a way to run a command, and then it says how to add the connector in that app. The setup status no longer calls the connector required.
36
+ - Other studios in the same folder are left alone. A new studio's `AGENTS.md` and the `studio-setup` and `game` skills say that a studio in a folder beside yours is somebody else's work: your AI does not read it or copy from it unless you ask. In a test, an AI read the game next door as a model for its own.
37
+ - **A Play link first.** Asked for everything at once, your AI now tells you the moment two browsers finish a round, with the link to play, and only then goes on to sound, art, the playtest's fixes and the landing page, saying what it is doing. The same sentence took 55 to 80 minutes to its first word in Claude Code, Codex and Grok, polishing all the way.
38
+ - Going online never lists a studio. The `studio-setup` and `publish` skills now say that listing in the homie.rocks directory is its own step, public, and yours to ask for: your AI lists a studio when you asked for it or said yes to its offer, never as part of a deploy.
39
+ - The skills no longer suggest a status line, a pane or a card in Codex or Grok, where Homie draws none.
40
+ - The README says what Claude Code means by "9 userConfig options not yet set" after an install: the Homie mod's nine switches, all optional and already at their defaults. Nothing is left to do.
41
+ - Shorter ways in, in the README. Claude Code: one line inside a session, `/plugin install homie --marketplace homie-rocks/homie` (2.1.275 or later). The Claude app: a link that opens "Add custom connector" with Homie filled in, so nobody types the address.
42
+
43
+ ### Fixed
44
+
45
+ - **Homie's holds do not run in Grok, and Homie no longer says they do.** 0.30.0 said Grok held the same calls as Claude Code and Codex. In a real run Grok deployed without asking. Grok Build 1.0.41 runs no plugin's hooks: its own log shows none registered in headless and agent sessions, for every installed plugin that ships hooks and for a test plugin holding nothing but a standard hooks file, so it is not Homie's layout. The README, the plugin's description and the skills now say that nothing is held in Grok and no secret is taken out of what Grok reads; the setup status says "Homie's holds: off"; and the `studio-setup` skill tells Grok to ask you before a deploy, a Cloudflare change, a paid call, a model download or an edit to a protected file. The hooks still ship, and the status turns on by itself with a Grok that runs them.
46
+ - "See a working game" where commands have no network (Codex runs them that way by default). `homie-studio demo` answered with the arcade's standing first pick, and your AI passed on that "the lookup couldn't reach the arcade". It now gives you the link as the live game it is: your browser opens it, not the session. The answer says `reached: false` and no longer blames the arcade for a network the session did not have.
47
+ - The setup status showed "List games in the homie.rocks directory" as not ready without the connector. Listing needs the directory, which `homie-studio publish` reaches by itself.
48
+
49
+ ### Upgrade notes
50
+
51
+ - Codex: if you have not yet, open `/hooks` and trust Homie's three hooks. `setup status --client codex` says whether they are on.
52
+ - Grok: nothing to install or switch on. Nothing holds a deploy or a paid call in Grok yet, so read what Grok is about to do when it asks; if it does not ask, tell it to.
53
+ - An existing studio: `upgrade --apply` brings the new lines into the Rules section of its `AGENTS.md` when you have not changed that section. Nothing else in a studio changes.
54
+
20
55
  ## [0.30.1] - 2026-10-04
21
56
 
22
- **Plugin 0.31.1** · [#47](https://github.com/homie-rocks/homie/pull/47)
57
+ **Plugin 0.31.1** · [#47](https://github.com/homie-rocks/homie/pull/47) · [release-2026-10-04-studio-0.30.1](https://github.com/homie-rocks/homie/releases/tag/release-2026-10-04-studio-0.30.1)
23
58
 
24
59
  Fixes from a filmed first run in the Claude desktop app: Claude tells you once to choose Always allow and what to do when a step sits on a spinner, the deploy plan's card fills in, and a starter is changed in a few large edits instead of twenty small ones.
25
60
 
package/README.md CHANGED
@@ -6,7 +6,7 @@ contract (every browser renders, strangers meet in public rooms, bots fill seats
6
6
  restart), and a site Worker with Table/Lobby Durable Objects and D1 that the studio deploys
7
7
  to its own Cloudflare account with Wrangler. The homie.rocks directory lists the games.
8
8
 
9
- Most people never run this by hand: the Homie plugin for Claude Code and Codex does,
9
+ Most people never run this by hand: the Homie plugin for Claude Code, Codex and Grok does,
10
10
  and the person approves Cloudflare once in their browser.
11
11
 
12
12
  ```sh
@@ -442,6 +442,23 @@ one token out: about 0.1 of the 10,000 free neurons a day; `lib/brain-probe.mjs`
442
442
  Workers Paid (error 5035) or retired (5007) is named, with what to do: pick another model, or, the person's money,
443
443
  Workers Paid. A spent daily allowance (3036) is said as that, not as a broken model.
444
444
 
445
+ A missing connector never blocks (0.30.2): a session that can run commands makes, deploys and lists a studio with
446
+ this toolkit alone (`new`, `deploy`, `publish`), and the connector row says so. With `--client codex` or
447
+ `--client grok` (in Codex the toolkit also reads the app from its environment) two things more:
448
+
449
+ - **The connector's name.** The Homie plugin's connector is the MCP server `homie`. When the app's own
450
+ configuration (`config.toml` in its home folder, or `.codex/` or `.grok/` in this folder) already has another
451
+ server of that name, the plugin's does not load. The row says so and gives the command that adds Homie's connector
452
+ under its own name (`codex mcp add homie-rocks --url https://homie.rocks/mcp`). It reads only whether that entry is
453
+ an address or a command; the command itself is never read out.
454
+ - **Homie's holds**: whether the plugin's hooks ran in this app in the last ten minutes, from the dated mark
455
+ they leave in `.cache/homie-studio/holds/` of the home folder. Off means nothing is held: Codex runs no plugin's hooks
456
+ until the person trusts them in `/hooks`, and the row says so; Grok Build 1.0.41 runs no plugin's hooks at all, so
457
+ there the row is off until a Grok that does.
458
+
459
+ `homie-studio demo` answers without a network too (0.30.2): where it cannot reach the arcade it names the arcade's
460
+ standing first pick, with `reached: false`.
461
+
445
462
  ## The Game Codex
446
463
 
447
464
  `games/<id>/CODEX.md` is a game's plan: Markdown with a small frontmatter for its look (palette, fonts, a
@@ -187,11 +187,15 @@
187
187
  * pages; the account id goes into studio.json, the token stays in Projects'
188
188
  * vault and its git-ignored .env, and Wrangler runs with it here. The usual
189
189
  * way, npx wrangler login, stays the default. lib/projects.mjs)
190
- * homie-studio setup status [--connector yes|no] (also: homie-studio doctor)
190
+ * homie-studio setup status [--connector yes|no] [--client claude|codex|grok] (also: homie-studio doctor)
191
191
  * what this computer and the person's accounts have for a studio: Node, the Homie
192
192
  * connector, Cloudflare (signed in, email verified), Chrome, ffmpeg, GitHub,
193
193
  * ElevenLabs, fal; green, missing or "do this now", what each unlocks and its
194
194
  * exact fix. Read-only and safe any time, inside a studio or before one exists.
195
+ * A missing connector never blocks: a session with a shell makes a studio with
196
+ * `new`. In Codex and Grok Build (--client, or the app's own environment) it
197
+ * also says whether Homie's holds are on (the plugin's hooks ran just now), and
198
+ * when another MCP server named homie has taken the connector's name there.
195
199
  *
196
200
  * homie-studio codex new <id> [--name "<Name>"]
197
201
  * games/<id>/CODEX.md: the Game Codex, every section, in the game's colours (a game
@@ -692,7 +696,7 @@ async function main() {
692
696
  if (cmd === 'port' && sub === 'plan') return planPort(positional[2] ?? '.');
693
697
  if (cmd === 'chrome' && sub === 'install') return installChrome({ log, fresh: flags.has('fresh') });
694
698
  if (cmd === 'chrome') { const chrome = findChrome(); return chrome ? { ok: true, command: 'chrome', chrome, args: chromeArgs() } : { ok: false, command: 'chrome', why: noChrome() }; }
695
- if ((cmd === 'setup' && sub === 'status') || cmd === 'doctor') return setupStatus({ connector: flags.get('connector') ?? null, homie: flags.get('homie') ?? null });
699
+ if ((cmd === 'setup' && sub === 'status') || cmd === 'doctor') return setupStatus({ connector: flags.get('connector') ?? null, homie: flags.get('homie') ?? null, client: flags.get('client') ?? null });
696
700
  if (cmd === 'statusline' && !flags.has('install') && !flags.has('remove')) {
697
701
  const line = statusLine({ columns: Number(process.env.COLUMNS) || 100, color: !process.env.NO_COLOR && !asJson && process.stdout.isTTY });
698
702
  if (asJson) return { ok: true, command: 'statusline', line };
package/lib/demo.mjs CHANGED
@@ -8,8 +8,12 @@
8
8
  * studio only when the person asks for one: `homie-studio game new <id> --from gem-rush`.
9
9
  *
10
10
  * It reads the arcade's own public manifest (/.well-known/homie-studio.json) and its live rooms (/api/rooms), so the
11
- * links are the ones live right now; when the arcade does not answer, it names its usual first pick. Read-only.
11
+ * links are the ones live right now. When this session cannot reach the arcade (a sandbox with no network, as Codex
12
+ * runs commands by default; a proxy; the arcade slow), it still answers, with the arcade's standing first pick
13
+ * (DEMO_FALLBACK, built in) and `reached: false`: the person's own browser opens that link, not this session, so it
14
+ * is still a live game to try. Read-only.
12
15
  */
16
+ import { whyFailed } from './net.mjs';
13
17
  import { STUDIO_VERSION } from './version.mjs';
14
18
 
15
19
  export const DEMO_STUDIO = 'https://arcade.homie.rocks';
@@ -34,13 +38,17 @@ async function getJson(fetchFn, url, ms) {
34
38
 
35
39
  export async function demoGames({ fetchFn = globalThis.fetch, studio = DEMO_STUDIO, timeoutMs = 6000 } = {}) {
36
40
  const site = String(studio).replace(/\/+$/, '');
37
- let manifest = null; let rooms = null; let why = null;
41
+ let manifest = null; let rooms = null; let why = null; let refused = false;
38
42
  try {
39
43
  [manifest, rooms] = await Promise.all([
40
44
  getJson(fetchFn, `${site}/.well-known/homie-studio.json`, timeoutMs),
41
45
  getJson(fetchFn, `${site}/api/rooms`, timeoutMs).catch(() => null),
42
46
  ]);
43
- } catch (error) { why = error?.message ?? String(error); }
47
+ } catch (error) {
48
+ // The arcade answered with an error, or this session never got to it (no network here, a proxy, a timeout).
49
+ refused = /answered \d{3}$/.test(String(error?.message));
50
+ why = refused ? error.message : whyFailed(error, site).why;
51
+ }
44
52
  const live = new Map();
45
53
  for (const r of Array.isArray(rooms?.rooms) ? rooms.rooms : []) {
46
54
  const id = text(r?.game, 40);
@@ -63,7 +71,11 @@ export async function demoGames({ fetchFn = globalThis.fetch, studio = DEMO_STUD
63
71
  ok: true, command: 'demo',
64
72
  studio: { name: text(manifest?.name, 60) || 'Homie Arcade', site },
65
73
  pick, games: games.length ? games : [pick],
66
- ...(why ? { note: `the arcade did not answer just now (${why}); this is its usual first pick` } : {}),
74
+ // Whether this session read the arcade just now. Not reached: the pick is the built-in one, and its link is as good.
75
+ reached: !why,
76
+ ...(why ? { note: refused
77
+ ? `the arcade did not give its list just now (${why}), so this is its standing first pick`
78
+ : `this session could not reach the arcade just now (${why}), so this is its standing first pick; the Play link opens in the person's own browser all the same` } : {}),
67
79
  how: HOW, copy: COPY,
68
80
  };
69
81
  }
package/lib/doctor.mjs CHANGED
@@ -4,8 +4,16 @@
4
4
  * unlocks, and the exact fix: one command the AI runs, or one page the person taps.
5
5
  *
6
6
  * Node.js required the toolkit runs on it
7
- * Homie connector required the directory, cards and the pinned toolkit's address (the AI says whether its
8
- * Homie tools are there: --connector yes|no)
7
+ * Homie connector recommended the directory's search and remixes, the cards and notes to Homie (the AI says
8
+ * whether its Homie tools are there: --connector yes|no). A session with a shell makes,
9
+ * deploys and lists a studio without it, so a missing connector never blocks. When
10
+ * the tools are missing and the app in use (Codex, Grok) has another MCP server named
11
+ * homie in its own config, the row says so: that name is the plugin's connector's
12
+ * Homie's holds in Codex and Grok Build only: whether the plugin's hooks ran just now (they leave a dated
13
+ * mark, hooks/codex.mjs), so a session where nothing is held says so, and how to turn
14
+ * them on (Codex: trust them in /hooks; Grok Build 1.0.41 runs no plugin's hooks, so
15
+ * there the row is off until a Grok that runs them). The app is the one the AI names
16
+ * (--client codex|grok) or its environment shows
9
17
  * Cloudflare to go online: signed in, and the account's email verified (Cloudflare checks that at the
10
18
  * first deploy; a deploy that went through proves it)
11
19
  * Workers AI for AI guides only when a server's guides think with Workers AI: the model they use
@@ -25,13 +33,16 @@
25
33
  * It is safe at any time, inside a studio or before one exists: it only reads (local files, `--version` of a few
26
34
  * tools, `wrangler whoami`, `gh auth status`, `elevenlabs auth status`, one GET to the directory and, when a fal key
27
35
  * is set, fal's free pricing API; when a server's AI guides use Workers AI, one read of the live database and one
28
- * one-word call to the model), never changes anything, and never prints a key, a token or an account's name or id.
36
+ * one-word call to the model; in Codex or Grok, the `[mcp_servers.homie]` table of that app's config.toml, of which
37
+ * it keeps only whether it is an address or a command, and the hooks' mark in this user's cache), never changes
38
+ * anything, and never prints a key, a token, a command line or an account's name or id.
29
39
  * Every check has a time limit, so it answers in seconds even with no network.
30
40
  */
31
41
  import { spawn } from 'node:child_process';
32
42
  import { existsSync, readFileSync } from 'node:fs';
33
43
  import { join } from 'node:path';
34
44
  import { workersAiRow } from './brain-probe.mjs';
45
+ import { studioClient } from './client.mjs';
35
46
  import { detectLocalAi } from './local-ai.mjs';
36
47
  import { findChrome } from './chrome.mjs';
37
48
  import { whyFailed } from './net.mjs';
@@ -72,14 +83,95 @@ async function reach(url, fetchFn, ms = 5000) {
72
83
  }
73
84
  }
74
85
 
86
+ /** The apps whose own configuration this status reads: where it is, and that app's own words for a fix. */
87
+ const APPS = {
88
+ codex: { name: 'Codex', home: (env, home) => env.CODEX_HOME || (home && join(home, '.codex')) || null, project: '.codex', add: (name, url) => `codex mcp add ${name} --url ${url}` },
89
+ grok: { name: 'Grok', home: (env, home) => env.GROK_HOME || (home && join(home, '.grok')) || null, project: '.grok', add: (name, url) => `grok mcp add ${name} ${url}` },
90
+ };
91
+ /** The name Homie's connector takes when another MCP server already has `homie`. No underscore: Grok's hooks match on it. */
92
+ export const CONNECTOR_NAME = 'homie-rocks';
93
+
94
+ /**
95
+ * Which app this session runs in, for the rows that differ by app: the one the AI named (`--client`, or HOMIE_CLIENT),
96
+ * else what the app's own environment shows (Claude Code and Codex set variables of their own on the commands they
97
+ * run). Null when neither says: never a guess.
98
+ */
99
+ export function sessionApp(client, env = process.env) {
100
+ const said = studioClient(client, env).id;
101
+ if (said !== 'chat') return said;
102
+ if (env.CLAUDECODE === '1') return 'claude';
103
+ if (env.CODEX_THREAD_ID || env.CODEX_SANDBOX || env.CODEX_SANDBOX_NETWORK_DISABLED || env.CODEX_CI) return 'codex';
104
+ return null;
105
+ }
106
+
107
+ /**
108
+ * Another MCP server under the name the Homie plugin's connector uses (`homie`), in the configuration of the app in
109
+ * use: its config.toml in the app's home folder, or the one in this folder (`.codex/`, `.grok/`). The person's own
110
+ * entry wins over a plugin's of the same name, so the plugin's tools never load. It reads only the
111
+ * `[mcp_servers.homie]` table's `url` and `command` keys, and returns only what kind of server it is and where it
112
+ * was found, never the command, its arguments, its environment or a header. Null when there is none, or it is
113
+ * Homie's own address.
114
+ */
115
+ export function connectorClash({ app, env = process.env, cwd = process.cwd(), root = null, directory = 'https://homie.rocks' } = {}) {
116
+ const a = APPS[app];
117
+ if (!a) return null;
118
+ const home = env.HOME || env.USERPROFILE || '';
119
+ const ours = new Set(['https://homie.rocks/mcp', `${String(directory).replace(/\/+$/, '')}/mcp`]);
120
+ const places = [
121
+ ...[...new Set([root, cwd].filter(Boolean))].map((dir) => ({ file: join(dir, a.project, 'config.toml'), where: `this folder's ${a.project}/config.toml` })),
122
+ { file: a.home(env, home) ? join(a.home(env, home), 'config.toml') : null, where: `config.toml in ${a.name}'s home folder` },
123
+ ];
124
+ for (const { file, where } of places) {
125
+ let text;
126
+ try { if (!file || !existsSync(file)) continue; text = readFileSync(file, 'utf8'); } catch { continue; }
127
+ if (text.length > 16 * 1024 * 1024) continue;
128
+ const lines = text.split(/\r?\n/);
129
+ const at = lines.findIndex((l) => /^\s*\[\s*mcp_servers\s*\.\s*(?:"homie"|'homie'|homie)\s*\]\s*(?:#.*)?$/.test(l));
130
+ if (at < 0) continue;
131
+ let url = null; let command = false;
132
+ for (let i = at + 1; i < lines.length && !/^\s*\[/.test(lines[i]); i += 1) {
133
+ const m = /^\s*(url|command)\s*=\s*(.*?)\s*$/.exec(lines[i]);
134
+ if (!m) continue;
135
+ if (m[1] === 'command') command = true;
136
+ else url = (/^(["'])(.*?)\1/.exec(m[2])?.[2] ?? m[2]).replace(/\/+$/, '');
137
+ }
138
+ if (url && !command && ours.has(url)) return null;
139
+ return { app, name: a.name, where, kind: command ? 'a local command' : url ? 'another address' : 'another server' };
140
+ }
141
+ return null;
142
+ }
143
+
144
+ /** How long a mark of Homie's hooks counts as "ran just now": they stamp it at every message and every tool call. */
145
+ export const HOLDS_FRESH_MS = 10 * 60_000;
146
+
147
+ /**
148
+ * The mark Homie's hooks leave each time they run in Codex or Grok Build (the plugin's hooks/codex.mjs `mark`): a
149
+ * small dated file in this user's cache, <app>.json, { v, app, at, event }. { at, event, ageMs } or null. HOMIE_HOLDS_MARKS
150
+ * names another folder (the tests use it).
151
+ */
152
+ export function holdsMark(app, { env = process.env, now = Date.now() } = {}) {
153
+ const home = env.HOME || env.USERPROFILE || '';
154
+ const dir = env.HOMIE_HOLDS_MARKS || (home && join(home, '.cache', 'homie-studio', 'holds'));
155
+ if (!dir || !/^[a-z]+$/.test(String(app ?? ''))) return null;
156
+ try {
157
+ const m = JSON.parse(readFileSync(join(dir, `${app}.json`), 'utf8'));
158
+ const at = Number(m?.at);
159
+ if (!Number.isFinite(at) || at <= 0) return null;
160
+ return { at, event: typeof m.event === 'string' ? m.event.slice(0, 20) : null, ageMs: Math.max(0, now - at) };
161
+ } catch { return null; }
162
+ }
163
+
164
+ const ago = (ms) => (ms < 90_000 ? `${Math.max(1, Math.round(ms / 1000))} s` : ms < 90 * 60_000 ? `${Math.round(ms / 60_000)} min` : ms < 36 * 3_600_000 ? `${Math.round(ms / 3_600_000)} h` : `${Math.round(ms / 86_400_000)} days`);
165
+
75
166
  /**
76
167
  * The checklist. `connector`: what the AI knows about its own tools ('yes' when the Homie MCP tools such as
77
- * studio_scaffold are in its tool list, 'no' when they are not, null when unsaid). `exec` and `fetchFn` are
168
+ * studio_scaffold are in its tool list, 'no' when they are not, null when unsaid). `client`: the app the AI says it
169
+ * is ('claude', 'codex', 'grok'; sessionApp reads the environment when it is unsaid). `exec`, `fetchFn` and `nowMs` are
78
170
  * replaceable for tests.
79
171
  */
80
172
  export async function setupStatus({
81
- cwd = process.cwd(), env = process.env, platform = process.platform, connector = null, homie = null,
82
- exec = defaultExec, fetchFn = globalThis.fetch, chrome = findChrome, node = process.versions.node,
173
+ cwd = process.cwd(), env = process.env, platform = process.platform, connector = null, homie = null, client = null,
174
+ exec = defaultExec, fetchFn = globalThis.fetch, chrome = findChrome, node = process.versions.node, nowMs = Date.now(),
83
175
  } = {}) {
84
176
  const root = findStudio(cwd);
85
177
  let studio = null;
@@ -148,24 +240,58 @@ export async function setupStatus({
148
240
  })(),
149
241
  ]);
150
242
 
151
- // The Homie connector.
243
+ // The Homie connector. A session with a shell makes, deploys and lists a studio without it, so it never blocks.
244
+ const app = sessionApp(client, env);
152
245
  {
246
+ const host = new URL(directory).host;
153
247
  const fixConnector = {
154
248
  who: 'person',
155
- say: 'Turn the Homie connector on. Claude Code: run /plugin, install or enable "homie" (marketplace homie-rocks/homie), then /mcp shows homie connected. Codex: install the Homie plugin from the same marketplace. Grok Build: the same plugin (.grok-plugin/plugin.json). The Claude app, or Grok: add the connector https://homie.rocks/mcp; its setup card (studio_setup) makes the studio on your own Cloudflare. Grok has no Cloudflare connector: you still approve Cloudflare in the browser. A Grok Bot on this computer runs the checklist and checks in with setup attach <hs_…> --client grok.',
249
+ say: `Turn the Homie connector on. Claude Code: run /plugin, install or enable "homie" (marketplace homie-rocks/homie), then /mcp shows homie connected. Codex: install the Homie plugin from the same marketplace (codex plugin marketplace add homie-rocks/homie, then codex plugin add homie@homie) and start a new session. Grok Build: grok plugin install homie-rocks/homie#plugins/homie (Grok asks whether to trust it), then a new session. The Claude app, or Grok chat: add the connector https://homie.rocks/mcp; its setup card (studio_setup) makes the studio on your own Cloudflare. Grok has no Cloudflare connector: you still approve Cloudflare in the browser. A Grok Bot on this computer runs the checklist and checks in with setup attach <hs_…> --client grok. Meanwhile a session with a shell goes on without it: ${cli} ${root ? '<command>' : 'new <folder> --name "<Name>"'} makes ${root ? 'everything in the studio' : 'the studio'}.`,
156
250
  };
251
+ // Another MCP server already called `homie` in this app's own config: the plugin's connector cannot load under it.
252
+ const clash = said !== 'yes' ? connectorClash({ app, env, cwd, root, directory }) : null;
253
+ const fixClash = clash ? {
254
+ who: 'ai', run: APPS[clash.app].add(CONNECTOR_NAME, `${directory}/mcp`),
255
+ say: `Another MCP server named homie is set up in ${clash.name} (${clash.where}). The Homie plugin's connector has the same name, and an app loads one server under a name, so the plugin's tools are missing while that one is there. This adds Homie's connector under its own name, ${CONNECTOR_NAME}, and leaves the other server as it is; you approve it, then start a new session. Until then your AI goes on with the studio's own commands.`,
256
+ } : null;
157
257
  let state; let detail;
158
- if (net.blocked) { state = 'act'; detail = `the network proxy of this machine refused ${new URL(directory).host}`; }
258
+ if (net.blocked) { state = 'act'; detail = `the network proxy of this machine refused ${host}`; }
159
259
  else if (said === 'yes') { state = 'ok'; detail = net.ok ? 'the Homie tools are here, and the directory answers' : `the Homie tools are here; this computer's request to the directory failed just now: ${net.why}`; }
160
- else if (said === 'no') { state = 'act'; detail = 'the Homie tools are not in this session'; }
260
+ else if (clash) { state = 'act'; detail = `${said === 'no' ? 'the Homie tools are not in this session' : 'your AI knows whether its Homie tools (studio_scaffold) are here'}; another MCP server named homie (${clash.kind}) is set up in ${clash.name}, in ${clash.where}, and it takes the name the Homie plugin's connector uses`; }
261
+ else if (said === 'no') { state = 'act'; detail = 'the Homie tools are not in this session; a studio is still made, checked, deployed and listed with the studio\'s own commands'; }
161
262
  // The directory not answering this computer says nothing about the connector: say what failed, as it is.
162
- else { state = 'unknown'; detail = net.ok ? `${new URL(directory).host} answers; your AI knows whether its Homie tools (studio_scaffold) are here` : `this computer's request to the directory failed: ${net.why}`; }
263
+ else { state = 'unknown'; detail = net.ok ? `${host} answers; your AI knows whether its Homie tools (studio_scaffold) are here` : `this computer's request to the directory failed: ${net.why}`; }
163
264
  rows.push({
164
- id: 'connector', label: 'Homie connector', need: 'required', state, detail,
165
- unlocks: 'making the studio with the right toolkit version, listing games in the homie.rocks directory, and the setup cards',
265
+ id: 'connector', label: 'Homie connector', need: 'recommended', state, detail,
266
+ unlocks: 'searching the homie.rocks directory and remixing a game from it, the cards where your app draws them, and notes to Homie; a session with a shell makes, deploys and lists a studio without it',
166
267
  fix: state === 'ok' ? null : net.blocked
167
- ? { who: 'person', say: `In claude.ai/code, open this environment's settings, set Network access to Custom, add ${new URL(directory).host} (keep the default package managers), and start a new session.` }
168
- : said === 'no' || net.ok ? fixConnector : null,
268
+ ? { who: 'person', say: `In claude.ai/code, open this environment's settings, set Network access to Custom, add ${host} (keep the default package managers), and start a new session.` }
269
+ : fixClash ?? (said === 'no' || net.ok ? fixConnector : null),
270
+ ...(clash && !net.blocked ? { clash: { app: clash.app, server: 'homie', kind: clash.kind, where: clash.where, as: CONNECTOR_NAME } } : {}),
271
+ });
272
+ }
273
+
274
+ // Homie's holds, in Codex and Grok Build: Codex runs the plugin's hooks only once the person has trusted them, Grok
275
+ // Build 1.0.41 was seen to run no plugin's hooks at all, and neither app says so. The hooks leave a dated mark at
276
+ // every message and tool call; a fresh one means they are on. Off in Grok is Grok's doing, so it is said as that.
277
+ if (app === 'codex' || app === 'grok') {
278
+ const name = APPS[app].name;
279
+ const seen = holdsMark(app, { env, now: nowMs });
280
+ const on = Boolean(seen && seen.ageMs <= HOLDS_FRESH_MS);
281
+ rows.push({
282
+ // Off in Codex is the person's to fix now (trust the hooks); off in Grok is nothing they can fix.
283
+ id: 'holds', label: 'Homie\'s holds', need: 'recommended', state: on ? 'ok' : app === 'codex' ? 'act' : 'optional', on, app,
284
+ detail: on ? `on: Homie's hooks ran in ${name} ${ago(seen.ageMs)} ago`
285
+ : seen ? `off: Homie's hooks last ran in ${name} ${ago(seen.ageMs)} ago, and not for this session's calls`
286
+ : app === 'grok' ? 'off: Grok Build runs no plugin\'s hooks yet (1.0.41), so nothing is held in Grok' : `off: Homie's hooks have not run in ${name} on this computer`,
287
+ ...(seen ? { seen: { at: new Date(seen.at).toISOString(), event: seen.event } } : {}),
288
+ unlocks: 'a wait for your own "proceed <code>" before a production deploy, an edit to a file the studio protects, a Cloudflare change outside the deploy, a paid call past the budget and a model download; and secrets taken out of what your AI reads',
289
+ fix: on ? null : {
290
+ who: 'person',
291
+ say: app === 'codex'
292
+ ? 'In Codex, open /hooks and trust Homie\'s three hooks: Codex runs no plugin\'s hooks until you do. Then run this again. Until then nothing is held, so your AI asks you before each of those itself.'
293
+ : 'Nothing to do on your side: Grok Build 1.0.41 runs no plugin\'s hooks (none are registered in its headless and agent sessions, from any plugin; checked 2026-10-04), so Homie\'s holds are off in Grok. Nothing is held and no secret is taken out of what your AI reads, so your AI asks you before each of those itself. This row turns on by itself when a Grok that runs them leaves the hooks\' mark.',
294
+ },
169
295
  });
170
296
  }
171
297
 
@@ -306,7 +432,8 @@ export async function setupStatus({
306
432
  { feature: 'Two-browser checks and playtests', state: ready(by.chrome.state), needs: ['chrome'] },
307
433
  { feature: 'Sound effects and a theme (free)', state: ready(by.ffmpeg.state), needs: ['ffmpeg'] },
308
434
  { feature: 'Put the studio online', state: ready(by.cloudflare.parts[0].state === 'ok' ? by.cloudflare.parts[1].state : by.cloudflare.parts[0].state), needs: ['cloudflare'] },
309
- { feature: 'List games in the homie.rocks directory', state: ready(by.connector.state), needs: ['connector'] },
435
+ // Listing needs the directory, not the connector: `homie-studio publish` reaches it from this computer.
436
+ { feature: 'List games in the homie.rocks directory', state: by.connector.state === 'ok' || net.ok ? 'ready' : 'not yet', needs: ['connector'] },
310
437
  { feature: 'Backup and pull requests', state: ready(by.github.state), needs: ['github'] },
311
438
  { feature: 'Songs and game scores', state: ready(by.elevenlabs.state), needs: ['elevenlabs'] },
312
439
  { feature: 'Painted art and generated video', state: ready(by.fal.state), needs: ['fal'] },
package/lib/feedback.mjs CHANGED
@@ -20,10 +20,10 @@
20
20
  import { redactText } from './redact.mjs';
21
21
 
22
22
  export const FEEDBACK_KINDS = Object.freeze(['stuck', 'confusing', 'idea', 'praise', 'bug']);
23
- export const FEEDBACK_APPS = Object.freeze(['claude-code', 'codex', 'claude-desktop', 'claude-ai', 'other']);
23
+ export const FEEDBACK_APPS = Object.freeze(['claude-code', 'codex', 'grok', 'claude-desktop', 'claude-ai', 'other']);
24
24
  export const FEEDBACK_LIMITS = Object.freeze({ text: 1500, raw: 6000, lines: 30, step: 80, email: 254, version: 32, perSession: 5, offers: 3 });
25
25
  export const KIND_LABEL = Object.freeze({ stuck: 'Stuck', confusing: 'Confusing', idea: 'Idea', praise: 'Praise', bug: 'Bug' });
26
- export const APP_LABEL = Object.freeze({ 'claude-code': 'Claude Code', codex: 'Codex', 'claude-desktop': 'the Claude desktop app', 'claude-ai': 'Claude on the web or a phone', other: 'another app' });
26
+ export const APP_LABEL = Object.freeze({ 'claude-code': 'Claude Code', codex: 'Codex', grok: 'Grok', 'claude-desktop': 'the Claude desktop app', 'claude-ai': 'Claude on the web or a phone', other: 'another app' });
27
27
 
28
28
  /** Where a note goes on a Homie directory (homie.rocks, or a local one for tests). */
29
29
  export const feedbackUrl = (directory = 'https://homie.rocks') => `${String(directory || 'https://homie.rocks').replace(/\/+$/, '')}/api/feedback/tell`;
@@ -175,6 +175,7 @@ export async function sendNote(note, { directory, source = 'plugin', consent = '
175
175
  export function appOf(clientInfo) {
176
176
  const name = String(clientInfo?.name ?? '').toLowerCase();
177
177
  if (/codex/.test(name)) return 'codex';
178
+ if (/grok/.test(name)) return 'grok';
178
179
  if (/claude[-_ ]?code/.test(name)) return 'claude-code';
179
180
  if (/claude/.test(name)) return 'claude-desktop';
180
181
  return 'other';
package/lib/scaffold.mjs CHANGED
@@ -422,11 +422,16 @@ chat's card follows the work from then on) and, for a studio still being set up,
422
422
  studio.json as \`cloudflare.domain\`.
423
423
  - A game's room size is its netplay manifest's \`maxPlayers\` (game.json \`netplay\`, or netplay.json), up to 32.
424
424
  - Nothing in this studio needs \`~/.homie\` or a Homie box.
425
+ - This studio is this folder. A studio in a folder beside it (another folder with its own \`studio.json\`) is
426
+ somebody else's work: never read it or copy from it unless the person asks.
425
427
  - Optional in studio.json: \`"protect"\` (globs of files the owner wants to look at before any change, such as
426
428
  \`"games/*/game.json"\`) and \`"budget"\` (\`{ "usd": <n>, "credits": <n> }\`: the most the studio's media jobs spend
427
429
  in all). In Claude Code, the Homie plugin's mod holds an edit to a protected file, a deploy, and a paid call past
428
- the budget until the person says Proceed, and takes keys out of command output. When it refuses a call, say what
429
- you meant to do and why; do not retry it unless the person asks.
430
+ the budget until the person says Proceed, and takes keys out of command output. In Codex the plugin's hooks hold
431
+ the same calls until the person's own \`proceed <code>\`, once the person has trusted them; in Grok Build nothing
432
+ holds them yet. \`npx --no-install homie-studio setup status --client codex\` (or \`grok\`) says whether Homie's
433
+ holds are on, and while they are off, ask before each of those yourself. When a call is refused, say what you
434
+ meant to do and why; do not retry it unless the person asks.
430
435
 
431
436
  ## Telling Homie
432
437
 
@@ -1511,6 +1511,46 @@
1511
1511
  }
1512
1512
  }
1513
1513
  }
1514
+ },
1515
+ "0.30.2": {
1516
+ "files": {
1517
+ "CLAUDE.md": "ddf2b2a0376202f6",
1518
+ "README.md": "684b3cca8001673c",
1519
+ "HANDOFF.md": "ce7a8fd91c6bbee2",
1520
+ "games/README.md": "5ad32fe80c61f117",
1521
+ "music/README.md": "a3dc042dadd39df8",
1522
+ "videos/README.md": "16babc3437d5545b",
1523
+ "posts/README.md": "37841aae476bd540",
1524
+ "site/README.md": "2928ca4f079ab76b",
1525
+ "site/src/worker.mjs": "ca3f1630f2420ad3"
1526
+ },
1527
+ "sections": {
1528
+ "AGENTS.md": {
1529
+ "(intro)": "214aa46eb3a895d5",
1530
+ "## Layout": "8baf49e4291e7e88",
1531
+ "## Commands (all through the pinned CLI in node_modules)": "d80ec56e4b4fc4c6",
1532
+ "## The site": "366ecce1a424837a",
1533
+ "## Making games": "abf2f0d59341512d",
1534
+ "## The Game Codex and progress": "0738ef719cef3a4c",
1535
+ "## Art direction and models": "aaea65236db52126",
1536
+ "## Running live games (the back office)": "4aa5f513a7cd2c3b",
1537
+ "## Servers and AI seats": "98d08705087a33ec",
1538
+ "## Selling things (the shop)": "b04b0a2b25f524f2",
1539
+ "## Continuing a build from the Claude app": "0d68081e924ca419",
1540
+ "## Rules": "13617a3dd1a66be6",
1541
+ "## Telling Homie": "80b46fdd9e578db8",
1542
+ "## Beta": "9d02638207a26e73"
1543
+ }
1544
+ },
1545
+ "named": {
1546
+ "Homie Arcade": {
1547
+ "sections": {
1548
+ "AGENTS.md": {
1549
+ "## Commands (all through the pinned CLI in node_modules)": "b35df2c19cd4b534"
1550
+ }
1551
+ }
1552
+ }
1553
+ }
1514
1554
  }
1515
1555
  }
1516
1556
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@homie-rocks/studio",
3
- "version": "0.30.1",
3
+ "version": "0.30.2",
4
4
  "description": "A studio for games, music and video on its own Cloudflare: scaffold, multiplayer starters on the netplay contract, a port toolkit that makes existing single-player web games multiplayer, the site Worker with public rooms (Table/Lobby Durable Objects and D1, all on the free Workers plan, no payment method), a site with the hub's sections (Home, Games, Music, Videos, Rooms, Posts with feeds) in the studio's own look, an epic landing page for every game, big songs and videos in the studio's own R2 once it has storage (uploaded, checked by SHA-256, served at the same addresses), deploy, and the homie.rocks directory.",
5
5
  "type": "module",
6
6
  "license": "Apache-2.0",
@@ -1,2 +1,2 @@
1
1
  /** The @homie-rocks/studio version this Worker code is (package.json's; a test keeps them equal). Cache-busts /_homie/site.js. */
2
- export const STUDIO_VERSION_TAG = '0.30.1';
2
+ export const STUDIO_VERSION_TAG = '0.30.2';