@reticlehq/init 3.5.0 → 3.7.0

package/dist/plan/plan.js

@@ -6,11 +6,13 @@
 import { Framework, UiLibrary, installCommand, installCommandParts } from '../detect/detect.js';
 import { installFailureHint } from '../diagnose/install-hint.js';
 import { installRetries } from '../diagnose/install-retries.js';
-import { claudeAddCommand, claudeProjectMcpJson, mcpManual } from '../register/mcp.js';
+import { claudeAddCommand, claudeProjectMcpJson, codexAddCommand, mcpManual, } from '../register/mcp.js';
+import { codexNamesOurServer } from '../register/codex-toml.js';
 import { mergeClientConfig, ClientMergeStatus, clientSnippet, clientSpec, CLAUDE_PROJECT_CONFIG, CLAUDE_PROJECT_SPEC, McpClient, } from '../register/mcp-clients.js';
 import { CLAUDE_COMMAND_PATH, CURSOR_COMMAND_PATH, SLASH_COMMAND_BODY, SLASH_COMMAND_SIGNATURE, } from '../register/slash-command.js';
 import { mergeMarkedInstruction, reticleMdFile, cursorRuleFile, AgentRuleStatus, CLAUDE_MD_PATH, markedBlock, AGENTS_MD_PATH, RETICLE_MD_PATH, CURSOR_RULE_PATH, } from '../project/agent-rules.js';
 import { cspStep } from '../diagnose/csp-step.js';
+import { HTML_INDEX_PATH } from '../patch/static-page.js';
 import { frameworkSteps } from './framework-adapter.js';
 import { FRAMEWORK_ADAPTERS, RETICLE_BROWSER_SDK, RETICLE_REACT_KIT } from './framework-adapter.js';
 import { MCP_TARGET, StepStatus } from './plan-types.js';
@@ -21,7 +23,7 @@ import { configWithInstallSource } from '../project/install-source-config.js';
 import { portMoveDetail, retargetConfigPort } from './port-steps.js';
 import { containerisedStep, uiLibraryStep, webGlCanvasStep, windowsMcpNoteStep, } from './notices.js';
 import { existingConfigProblem, projectIdOf, RETICLE_CONFIG_FILE, } from '../detect/existing-config.js';
-import { CLAUDE_SETTINGS_PATH, stopHookStep } from './stop-hook-step.js';
+import { CLAUDE_SETTINGS_PATH, claudeSettingsSteps } from './stop-hook-step.js';
 // Re-exported: it moved to the module that reads it, and every existing importer says `plan.js`.
 export { RETICLE_CONFIG_FILE };
 /**
@@ -92,7 +94,34 @@ function claudeMcpStep(input) {
  * parse is reported with a paste-able block rather than overwritten, and everything else is written.
  */
 function otherClientSteps(input) {
-    return (input.detectedClients ?? []).map((detected) => clientStep(clientSpec(detected.id), detected.configPath, detected.existing));
+    return (input.detectedClients ?? []).map((detected) => {
+        const spec = clientSpec(detected.id);
+        return (codexCliStep(spec, detected.configPath, detected.existing, input) ??
+            clientStep(spec, detected.configPath, detected.existing));
+    });
+}
+/**
+ * Codex, registered through its own CLI instead of a printed block (#1238).
+ *
+ * `mergeClientConfig` answers MANUAL for TOML, since we never edit it blind. `codex mcp add` does
+ * the editing, so with the binary on PATH nothing is left for a human. It REPLACES an entry of the
+ * same name and exits 0, so this answers only when the config names no `reticle` server at all, in
+ * any shape. An entry somebody wrote — a local build, a `url` — falls through to `clientStep`, which
+ * leaves it alone (ALREADY) or hands over the block (MANUAL), exactly as before.
+ */
+function codexCliStep(spec, configPath, existing, input) {
+    if (McpClient.CODEX !== spec.id || true !== input.codexCli)
+        return null;
+    if (codexNamesOurServer(existing, spec.serversKey))
+        return null;
+    const cmd = codexAddCommand();
+    return {
+        title: `MCP server (${spec.label})`,
+        target: configPath,
+        status: StepStatus.APPLY,
+        detail: `register reticle with ${spec.label} (${cmd.display})`,
+        exec: { command: cmd.command, args: cmd.args, fallback: cmd.display },
+    };
 }
 /** One client's step: already-correct is left alone, an unparseable file gets a paste-able block. */
 function clientStep(spec, configPath, existing) {
@@ -488,12 +517,22 @@ function installStep(input) {
             detail: `${names.join(', ')} already declared${version === undefined || 0 === version.length ? '' : ` at ${version}`}`,
         };
     }
+    // Never install into a linked tree: the package manager replaces the link (a workspace's tree).
+    if (true === input.nodeModulesLinked) {
+        return {
+            title: 'Install dependencies',
+            target: 'package.json',
+            status: StepStatus.SKIP,
+            detail: `skipped: node_modules is a link to another tree, which an install here would replace; install them where it points: ${command}`,
+        };
+    }
+    // The person said `--no-install`: a choice, not a step left undone, so not a ⚠.
     if (!input.options.install) {
         return {
             title: 'Install dependencies',
             target: 'package.json',
-            status: StepStatus.MANUAL,
-            detail: command,
+            status: StepStatus.SKIP,
+            detail: `skipped (--no-install); install them yourself: ${command}`,
         };
     }
     const parts = installCommandParts(pm, packages, [], pmCommand);
@@ -561,6 +600,19 @@ function agentRootConfigStep(input, content) {
             },
         ];
     }
+    // Several apps: a root config names one and is wrong for the rest. Not written; an agent at the
+    // root is served whichever app's daemon is live, and one started in an app reads that app's.
+    if (true === input.agentRootSeveralApps && existingProject === undefined) {
+        return [
+            {
+                title: AGENT_ROOT_CONFIG_TITLE,
+                target: path,
+                status: StepStatus.NOTICE,
+                detail: 'not written: this workspace has several apps and the root can name only one. Run the ' +
+                    "agent from an app's directory to pin it to that app.",
+            },
+        ];
+    }
     if (input.agentRootConfigSource === content) {
         return [
             {
@@ -652,20 +704,26 @@ function reticleConfigSteps(input) {
     ];
 }
 export function buildPlan(input) {
+    const cspSteps = cspStep(input);
     const steps = [
-        ...cspStep(input),
+        ...cspSteps,
         ...mcpSteps(input),
         ...agentRuleSteps(input),
         ...slashCommandSteps(input),
-        ...(true === input.hooks
-            ? [stopHookStep(agentFile(input, CLAUDE_SETTINGS_PATH), input.claudeSettingsContent)]
-            : []),
+        ...claudeSettingsSteps(agentFile(input, CLAUDE_SETTINGS_PATH), input.claudeSettingsContent, {
+            stop: true === input.hooks,
+            // Beside the CLAUDE.md rule: the same agent, the same consent to write its instruction files.
+            compact: input.options.mcp && input.claudeCli,
+        }),
         ...uiLibraryStep(input),
         ...webGlCanvasStep(input),
         installStep(input),
         ...reticleConfigSteps(input),
     ];
-    steps.push(...frameworkSteps(input));
+    // Both steps can patch index.html: the connect write must keep the CSP edit that runs first.
+    const patchedIndex = cspSteps.find((step) => step.write?.path === HTML_INDEX_PATH)?.write
+        ?.content;
+    steps.push(...frameworkSteps(patchedIndex === undefined ? input : { ...input, htmlIndexSource: patchedIndex }));
     // LAST, and a notice rather than an action: it is a statement about this machine's shape, and it
     // only matters once every file above has been written. See containerised-dev-server.ts.
     const container = containerisedStep(input);

package/dist/plan/stop-hook-step.d.ts

@@ -2,3 +2,22 @@ import { type Step } from './plan-types.js';
 export declare const CLAUDE_SETTINGS_PATH = ".claude/settings.json";
 export declare const STOP_HOOK_COMMAND = "npx @reticlehq/server report --hook";
 export declare function stopHookStep(path: string, existing: string | null | undefined): Step;
+/**
+ * The Claude Code `SessionStart` hook with matcher `compact`: right after a compaction it prints
+ * `reticle context --compact` — what this session proved, what failed, what is still owed — back
+ * into the agent's fresh context. Reticle holds the memory; this is how it is handed back without
+ * the agent having to remember to ask.
+ *
+ * Written by default wherever the CLAUDE.md rule is (it only reads the project's own `.reticle/`, and
+ * prints nothing where there is none). Removable like any hook: delete the entry.
+ */
+export declare const COMPACT_HOOK_COMMAND = "npx @reticlehq/server context --compact";
+export declare function compactHookStep(path: string, existing: string | null | undefined): Step;
+/**
+ * Every hook this run writes into `.claude/settings.json`, each merged on top of the one before, so
+ * two steps writing the same file cannot undo each other.
+ */
+export declare function claudeSettingsSteps(path: string, existing: string | null | undefined, options: {
+    stop: boolean;
+    compact: boolean;
+}): Step[];

package/dist/plan/stop-hook-step.js

@@ -36,7 +36,12 @@ export function stopHookStep(path, existing) {
     const hooks = isObject(settings['hooks']) ? settings['hooks'] : {};
     const stop = Array.isArray(hooks[STOP_EVENT]) ? hooks[STOP_EVENT] : [];
     if (JSON.stringify(stop).includes(STOP_HOOK_COMMAND)) {
-        return { title: TITLE, target: path, status: StepStatus.ALREADY, detail: 'hook already installed' };
+        return {
+            title: TITLE,
+            target: path,
+            status: StepStatus.ALREADY,
+            detail: 'hook already installed',
+        };
     }
     const merged = { ...settings, hooks: { ...hooks, [STOP_EVENT]: [...stop, HOOK_ENTRY] } };
     return {
@@ -47,3 +52,71 @@ export function stopHookStep(path, existing) {
         write: { path, content: `${JSON.stringify(merged, null, 2)}\n`, expect: [STOP_HOOK_COMMAND] },
     };
 }
+/**
+ * The Claude Code `SessionStart` hook with matcher `compact`: right after a compaction it prints
+ * `reticle context --compact` — what this session proved, what failed, what is still owed — back
+ * into the agent's fresh context. Reticle holds the memory; this is how it is handed back without
+ * the agent having to remember to ask.
+ *
+ * Written by default wherever the CLAUDE.md rule is (it only reads the project's own `.reticle/`, and
+ * prints nothing where there is none). Removable like any hook: delete the entry.
+ */
+export const COMPACT_HOOK_COMMAND = `npx ${RETICLE_NPM_PACKAGE} context --compact`;
+const COMPACT_TITLE = 'Claude Code resume-after-compaction hook';
+const SESSION_START_EVENT = 'SessionStart';
+const COMPACT_MATCHER = 'compact';
+export function compactHookStep(path, existing) {
+    const settings = null === existing || undefined === existing ? {} : parseSettings(existing);
+    if (settings === undefined) {
+        return {
+            title: COMPACT_TITLE,
+            target: path,
+            status: StepStatus.MANUAL,
+            detail: `${CLAUDE_SETTINGS_PATH} is not a JSON object, so it was left alone. Add a SessionStart hook (matcher "${COMPACT_MATCHER}") running \`${COMPACT_HOOK_COMMAND}\``,
+        };
+    }
+    const hooks = isObject(settings['hooks']) ? settings['hooks'] : {};
+    const start = Array.isArray(hooks[SESSION_START_EVENT])
+        ? hooks[SESSION_START_EVENT]
+        : [];
+    if (JSON.stringify(start).includes(COMPACT_HOOK_COMMAND)) {
+        return {
+            title: COMPACT_TITLE,
+            target: path,
+            status: StepStatus.ALREADY,
+            detail: 'hook already installed',
+        };
+    }
+    const entry = {
+        matcher: COMPACT_MATCHER,
+        hooks: [{ type: 'command', command: COMPACT_HOOK_COMMAND }],
+    };
+    const merged = { ...settings, hooks: { ...hooks, [SESSION_START_EVENT]: [...start, entry] } };
+    return {
+        title: COMPACT_TITLE,
+        target: path,
+        status: StepStatus.APPLY,
+        detail: 'after a context compaction, hand the agent back what this session proved and still owes',
+        write: {
+            path,
+            content: `${JSON.stringify(merged, null, 2)}\n`,
+            expect: [COMPACT_HOOK_COMMAND],
+        },
+    };
+}
+/**
+ * Every hook this run writes into `.claude/settings.json`, each merged on top of the one before, so
+ * two steps writing the same file cannot undo each other.
+ */
+export function claudeSettingsSteps(path, existing, options) {
+    const steps = [];
+    let current = existing;
+    if (options.stop) {
+        const stop = stopHookStep(path, current);
+        steps.push(stop);
+        current = stop.write?.content ?? current;
+    }
+    if (options.compact)
+        steps.push(compactHookStep(path, current));
+    return steps;
+}

package/dist/project/agent-rules.d.ts

@@ -90,7 +90,7 @@ export declare const DEV_SERVER_POLICY = "**A dev server already running when `r
  * NOT to, how, and the guards against calling something proven when it is not. Everything an agent
  * needs only at the moment it hits a specific situation lives in RETICLE.md, named at the end.
  */
-export declare const RULE_BODY = "## Verifying with Reticle\n\nThis app is instrumented by **Reticle**, an in-app verification layer exposed as `reticle_*` MCP tools and the `npx @reticlehq/server` CLI (always through npx: Reticle's server is not installed into this project). Verifying is part of \"done\", not an optional extra.\n\n**Verify when you have changed something a user can see or do.** A component, a form, a route, a request, a piece of state that reaches the screen. Do it BEFORE telling the user it is complete. Reading the diff proves nothing and unit tests do not run the app.\n\n**Do not reach for Reticle when the change cannot show up in the running app.** It costs tool calls and the user's patience, and a verdict over an unrelated flow proves nothing about what you changed. Skip it for: documentation, comments, tests, build config, CI, dependency bumps with no user-facing effect, backend or CLI work with no UI surface, and any change to a project that is not a running web app. Say in one line that you skipped verification and why, rather than silently not doing it.\n\n**How to verify:**\n\n- Drive the flow with `reticle_act_and_wait({ ref, action, until })`. It names the consequence you expect BEFORE the action, which is the difference between a check and a rationalisation.\n- Batch a multi-step journey (a login, a form) into one `reticle_act { steps: [...] }` rather than one round trip per field.\n- Read the surrounding evidence with `reticle_look { action: \"page\" | \"state\" }` and `reticle_observe { action: \"network\" | \"console\" }`.\n- **Only `reticle_act_and_wait` and `reticle_assert` produce a verdict.** `reticle_act` and everything else move or read the app and prove nothing, so a session ending without one of those two has no result however many tools it used.\n- Covered flows: `npx @reticlehq/server gate` reports which recorded flows the changed files affect and whether they still pass.\n\n**Setting Reticle up? You are mid-sequence \u2014 do not stop until a verdict exists.** The whole of it\nis: instrument the app \u2192 get a dev server running \u2192 open the app in a browser \u2192 drive one flow \u2192\nreport the verdict. Every step is yours to do, and none of them needs the user. Stopping short leaves an app that\nlooks installed and can verify nothing, which is the commonest way this goes wrong. `/reticle`\ncarries the recovery ladder; never report the install as finished without a verdict to point at.\n\n**Nothing connected? Get the app running.**\n\n**A dev server already running when `reticle init` ran does not have Reticle in its bundle.** It read the build config at boot; `init` edited it afterwards. It serves the old bundle and no session appears. In order:\n\n1. **A dev server was already running?** Restart it, then hard-reload the tab. \"Something is listening\" does not mean the right bundle is served.\n2. **Nothing was running?** Start it in the BACKGROUND and say so in one line. `reticle_session { action: \"list\" }` gives you this project's own dev command in `next_action`; use that, never compose one. Started after `init`, it needs no restart.\n\nStopping to ask is how a verification turn ends with nothing verified.\n\nFour guards, none optional:\n\n1. **Never run two at once.** One dev server on the app's port. Restarting a stale one means stopping it first, not starting a second alongside it.\n2. **Never guess the command.** It comes from `package.json` scripts. No recognisable dev script means say so and stop, not invent one.\n3. **Never kill anything you did not start**, and never a daemon or a port holder. The one exception is the restart above, and say in one line that you did it.\n4. **The permission prompt belongs to your host.** Never bypass, suppress or auto-approve it, and take a refusal as the answer.\n\nA dev server that is already running does not pick up an edited build config or a newly created plugin file \u2014 restart it and hard-reload the tab. And if a server IS listening and still nothing connects, the cause is the SDK not loading in the page, not a missing dev server; do not tell the user to start one they are already running.\n\n**Finish `src/reticle-dev.ts` before you claim setup is done.** `init` writes it and cannot always fill it in: a store that needs an argument only reading the code supplies (Jotai atoms, an XState actor, a TanStack `queryClient`) is left as a commented `registerStore` line. A file that registers nothing looks exactly like a finished one, and `reticle_look { action: \"state\" }` then returns empty forever \u2014 which is indistinguishable from an app that has nothing to report, so it reads as success. Uncomment the line, complete it, and prove it by driving one flow and seeing your keys come back. If `init` told you to restart your client, this is the job waiting for you on the other side of that restart.\n\n**Verify each feature as you finish it, not all of them at the end.** Asked for four, build one, drive it, get a verdict, then start the second. A red verdict after four builds has four suspects; after one it has none.\n\n**Capture what a change is FOR while you are building it, not afterwards.** The business outcome a change is meant to produce is known only while the change is being made. Pass `intent` when a flow is saved, so the saved flow carries the reason it exists. A flow without one replays for months and then reports \"step 3 failed\" instead of what stopped being true for a user.\n\n**Honesty, which is the whole point:**\n\n- **`verified: \"unknown\"` is not a pass.** It means Reticle drove the app and could not tell what happened; `verifiedReason` says which clause decided that. Report it as unknown, never as working.\n- **`verified: \"no-fault\"` is not a pass either.** It means nothing was DECLARED to prove: the page settled and no channel complained, but you asserted nothing, so there is no verification. You get it whenever `until` is omitted. Name a consequence the action changes \u2014 a signal, a request, a route, or store state \u2014 and call again.\n- **Never weaken a check to make it green.** Downgrading, skipping or deleting an assertion is a finding, not a fix.\n- **If Reticle cannot run** (no daemon, or this is not a running web app), say so. Do not skip verification silently.\n- **Setup is not finished until one real flow has been driven and produced a verdict.** `init` exiting 0, the tools appearing, and a session being listed are all things that happen before anything has been verified.\n\n**The `/reticle` skill runs this whole loop for you** \u2014 detect, connect, drive one flow, report. If your client does not have it, install it once: `/plugin marketplace add reticlehq/reticle` then `/plugin install reticle@reticlehq` in Claude Code, or `npx skills add reticlehq/reticle` anywhere the skills CLI works.\n\n**A tool you need is missing?** Call `reticle_tools` before assuming it: this surface merges several families behind an `action`, so what looks absent is usually one argument away. It is the verify loop and nothing else on purpose, and a daemon started with `RETICLE_ADVERTISE_ALL_TOOLS=1` advertises the wider set \u2014 it reads that at startup, so it takes effect on the next one.\n\n**Report Reticle's own defects with `reticle_session { action: \"feedback\" }` the moment you notice**, then carry on with your task. You are the user Reticle is built for and the only one who can say what it cost you, and that knowledge is gone when your context is.\n\n\uD83D\uDCC4 **The rest is in [RETICLE.md](./RETICLE.md): what to do when the tools are missing, when a result carries `version_skew` or `update_available`, when `reticle_look { action: \"state\" }` comes back empty, and how to write a feedback report that can be acted on. Read it when you hit one of those, not before.**";
+export declare const RULE_BODY = "## Verifying with Reticle\n\nThis app is instrumented by **Reticle**, an in-app verification layer exposed as `reticle_*` MCP tools and the `npx @reticlehq/server` CLI (always through npx: Reticle's server is not installed into this project). Verifying is part of \"done\", not an optional extra.\n\n**Verify when you have changed something a user can see or do.** A component, a form, a route, a request, a piece of state that reaches the screen. Do it BEFORE telling the user it is complete. Reading the diff proves nothing and unit tests do not run the app.\n\n**Do not reach for Reticle when the change cannot show up in the running app.** It costs tool calls and the user's patience, and a verdict over an unrelated flow proves nothing about what you changed. Skip it for: documentation, comments, tests, build config, CI, dependency bumps with no user-facing effect, backend or CLI work with no UI surface, and any change to a project that is not a running web app. Say in one line that you skipped verification and why, rather than silently not doing it.\n\n**How to verify \u2014 the rules to keep in mind on every call:**\n\n1. **Only `verified: \"yes\"` is a pass.** `\"no-fault\"` (nothing was declared \u2014 you omitted `until`) and `\"unknown\"` (Reticle could not tell; `verifiedReason` says why) are not a pass: report them as not proved, never as working.\n2. **Name the consequence BEFORE acting:** `reticle_act_and_wait({ target, action, until })` (add `durable: true` if it must survive a reload). Only it, `reticle_assert` and `reticle_act { steps }` produce a verdict; everything else proves nothing.\n3. **A journey is one call:** `reticle_act { steps: [{ target, action, expect }] }` runs every step and stops at the first `expect` that fails. The last step's `expect` is the end state you were asked to deliver.\n4. **Text checks are exact-case.** Add `ignoreCase: true` only when case truly does not matter.\n5. **Target by `{ testid }` or `{ role, name }`.** An ambiguous target is refused, never guessed.\n6. **On a failure, read `expected` / `observed` / the nearest candidates before retrying.** Never weaken a check to make it green.\n7. **Open `screenshot.path` only when the look matters;** `reticle_observe { since }` has the rest.\n8. **Predicates:** `{ kind: \"signal\", name }` \u00B7 `{ kind: \"net\", method, urlContains, status }` \u00B7 `{ kind: \"route\", pathname }` \u00B7 `{ kind: \"state\", path, equals }` \u00B7 `{ kind: \"element\", query: { role, name } }` \u00B7 `{ kind: \"text\", contains }` \u00B7 `allOf` / `anyOf` / `not`.\n9. **No session?** `reticle_session { action: \"list\" }` and do its `next_action`. **No app connected at all?** Run `npx @reticlehq/server init` in the app's own folder yourself. **A version-skew warning?** `npx @reticlehq/server stop`, then retry.\n10. **End with the Reticle result block the server gives you**, verbatim.\n11. **If your context was compacted or you lost track, run `npx @reticlehq/server context --compact` first.** It is the daemon's own record of what was proved, what failed and what is still owed.\n\nCovered flows: `npx @reticlehq/server gate` reports which recorded flows the changed files affect and whether they still pass.\n\n**Setting Reticle up? You are mid-sequence \u2014 do not stop until a verdict exists.** The whole of it\nis: instrument the app \u2192 get a dev server running \u2192 open the app in a browser \u2192 drive one flow \u2192\nreport the verdict. Every step is yours to do, and none of them needs the user. Stopping short leaves an app that\nlooks installed and can verify nothing, which is the commonest way this goes wrong. `/reticle`\ncarries the recovery ladder; never report the install as finished without a verdict to point at.\n\n**Nothing connected? Get the app running.**\n\n**A dev server already running when `reticle init` ran does not have Reticle in its bundle.** It read the build config at boot; `init` edited it afterwards. It serves the old bundle and no session appears. In order:\n\n1. **A dev server was already running?** Restart it, then hard-reload the tab. \"Something is listening\" does not mean the right bundle is served.\n2. **Nothing was running?** Start it in the BACKGROUND and say so in one line. `reticle_session { action: \"list\" }` gives you this project's own dev command in `next_action`; use that, never compose one. Started after `init`, it needs no restart.\n\nStopping to ask is how a verification turn ends with nothing verified.\n\nFour guards, none optional:\n\n1. **Never run two at once.** One dev server on the app's port. Restarting a stale one means stopping it first, not starting a second alongside it.\n2. **Never guess the command.** It comes from `package.json` scripts. No recognisable dev script means say so and stop, not invent one.\n3. **Never kill anything you did not start**, and never a daemon or a port holder. The one exception is the restart above, and say in one line that you did it.\n4. **The permission prompt belongs to your host.** Never bypass, suppress or auto-approve it, and take a refusal as the answer.\n\nIf a server IS listening and still nothing connects, the cause is the SDK not loading in the page, not a missing dev server; do not tell the user to start one they are already running.\n\n**Finish `src/reticle-dev.ts` before you claim setup is done.** `init` writes it and cannot always fill it in: a store that needs an argument only reading the code supplies (Jotai atoms, an XState actor, a TanStack `queryClient`) is left as a commented `registerStore` line. A file that registers nothing looks exactly like a finished one, and `reticle_look { action: \"state\" }` then returns empty forever \u2014 which is indistinguishable from an app that has nothing to report, so it reads as success. Uncomment the line, complete it, and prove it by driving one flow and seeing your keys come back. If `init` told you to restart your client, this is the job waiting for you on the other side of that restart.\n\n**Verify each feature as you finish it, not all of them at the end.** Asked for four, build one, drive it, get a verdict, then start the second. A red verdict after four builds has four suspects; after one it has none.\n\n**Capture what a change is FOR while you are building it, not afterwards.** The business outcome a change is meant to produce is known only while the change is being made. Pass `intent` when a flow is saved, so the saved flow carries the reason it exists. A flow without one replays for months and then reports \"step 3 failed\" instead of what stopped being true for a user.\n\n**Honesty, which is the whole point:**\n\n- **If Reticle cannot run** (no daemon, or this is not a running web app), say so. Do not skip verification silently.\n- **Setup is not finished until one real flow has been driven and produced a verdict.** `init` exiting 0, the tools appearing, and a session being listed are all things that happen before anything has been verified.\n\n**The `/reticle` skill runs this whole loop for you** \u2014 detect, connect, drive one flow, report. If your client does not have it, install it once: `/plugin marketplace add reticlehq/reticle` then `/plugin install reticle@reticlehq` in Claude Code, or `npx skills add reticlehq/reticle` anywhere the skills CLI works.\n\n**A tool you need is missing?** Call `reticle_tools` before assuming it: this surface merges several families behind an `action`, so what looks absent is usually one argument away. It is the verify loop and nothing else on purpose, and a daemon started with `RETICLE_ADVERTISE_ALL_TOOLS=1` advertises the wider set \u2014 it reads that at startup, so it takes effect on the next one.\n\n**Report Reticle's own defects with `reticle_session { action: \"feedback\" }` the moment you notice**, then carry on with your task. You are the user Reticle is built for and the only one who can say what it cost you, and that knowledge is gone when your context is.\n\n\uD83D\uDCC4 **The rest is in [RETICLE.md](./RETICLE.md): what to do when the tools are missing, when a result carries `version_skew` or `update_available`, when `reticle_look { action: \"state\" }` comes back empty, and how to write a feedback report that can be acted on. Read it when you hit one of those, not before.**";
 /** The full-rules file, written verbatim (no markers: `init` owns this file entirely). */
 export declare function reticleMdFile(): string;
 export declare const AgentRuleStatus: {

package/dist/project/agent-rules.js

@@ -118,13 +118,21 @@ This app is instrumented by **Reticle**, an in-app verification layer exposed as
 
 **Do not reach for Reticle when the change cannot show up in the running app.** It costs tool calls and the user's patience, and a verdict over an unrelated flow proves nothing about what you changed. Skip it for: documentation, comments, tests, build config, CI, dependency bumps with no user-facing effect, backend or CLI work with no UI surface, and any change to a project that is not a running web app. Say in one line that you skipped verification and why, rather than silently not doing it.
 
-**How to verify:**
-
-- Drive the flow with \`reticle_act_and_wait({ ref, action, until })\`. It names the consequence you expect BEFORE the action, which is the difference between a check and a rationalisation.
-- Batch a multi-step journey (a login, a form) into one \`reticle_act { steps: [...] }\` rather than one round trip per field.
-- Read the surrounding evidence with \`reticle_look { action: "page" | "state" }\` and \`reticle_observe { action: "network" | "console" }\`.
-- **Only \`reticle_act_and_wait\` and \`reticle_assert\` produce a verdict.** \`reticle_act\` and everything else move or read the app and prove nothing, so a session ending without one of those two has no result however many tools it used.
-- Covered flows: \`${CLI} gate\` reports which recorded flows the changed files affect and whether they still pass.
+**How to verify — the rules to keep in mind on every call:**
+
+1. **Only \`verified: "yes"\` is a pass.** \`"no-fault"\` (nothing was declared — you omitted \`until\`) and \`"unknown"\` (Reticle could not tell; \`verifiedReason\` says why) are not a pass: report them as not proved, never as working.
+2. **Name the consequence BEFORE acting:** \`reticle_act_and_wait({ target, action, until })\` (add \`durable: true\` if it must survive a reload). Only it, \`reticle_assert\` and \`reticle_act { steps }\` produce a verdict; everything else proves nothing.
+3. **A journey is one call:** \`reticle_act { steps: [{ target, action, expect }] }\` runs every step and stops at the first \`expect\` that fails. The last step's \`expect\` is the end state you were asked to deliver.
+4. **Text checks are exact-case.** Add \`ignoreCase: true\` only when case truly does not matter.
+5. **Target by \`{ testid }\` or \`{ role, name }\`.** An ambiguous target is refused, never guessed.
+6. **On a failure, read \`expected\` / \`observed\` / the nearest candidates before retrying.** Never weaken a check to make it green.
+7. **Open \`screenshot.path\` only when the look matters;** \`reticle_observe { since }\` has the rest.
+8. **Predicates:** \`{ kind: "signal", name }\` · \`{ kind: "net", method, urlContains, status }\` · \`{ kind: "route", pathname }\` · \`{ kind: "state", path, equals }\` · \`{ kind: "element", query: { role, name } }\` · \`{ kind: "text", contains }\` · \`allOf\` / \`anyOf\` / \`not\`.
+9. **No session?** \`reticle_session { action: "list" }\` and do its \`next_action\`. **No app connected at all?** Run \`${CLI} init\` in the app's own folder yourself. **A version-skew warning?** \`${CLI} stop\`, then retry.
+10. **End with the Reticle result block the server gives you**, verbatim.
+11. **If your context was compacted or you lost track, run \`${CLI} context --compact\` first.** It is the daemon's own record of what was proved, what failed and what is still owed.
+
+Covered flows: \`${CLI} gate\` reports which recorded flows the changed files affect and whether they still pass.
 
 **Setting Reticle up? You are mid-sequence — do not stop until a verdict exists.** The whole of it
 is: instrument the app → get a dev server running → open the app in a browser → drive one flow →
@@ -136,7 +144,7 @@ carries the recovery ladder; never report the install as finished without a verd
 
 ${DEV_SERVER_POLICY}
 
-A dev server that is already running does not pick up an edited build config or a newly created plugin file — restart it and hard-reload the tab. And if a server IS listening and still nothing connects, the cause is the SDK not loading in the page, not a missing dev server; do not tell the user to start one they are already running.
+If a server IS listening and still nothing connects, the cause is the SDK not loading in the page, not a missing dev server; do not tell the user to start one they are already running.
 
 **Finish \`src/reticle-dev.ts\` before you claim setup is done.** \`init\` writes it and cannot always fill it in: a store that needs an argument only reading the code supplies (Jotai atoms, an XState actor, a TanStack \`queryClient\`) is left as a commented \`registerStore\` line. A file that registers nothing looks exactly like a finished one, and \`reticle_look { action: "state" }\` then returns empty forever — which is indistinguishable from an app that has nothing to report, so it reads as success. Uncomment the line, complete it, and prove it by driving one flow and seeing your keys come back. If \`init\` told you to restart your client, this is the job waiting for you on the other side of that restart.
 
@@ -146,9 +154,6 @@ A dev server that is already running does not pick up an edited build config or
 
 **Honesty, which is the whole point:**
 
-- **\`verified: "unknown"\` is not a pass.** It means Reticle drove the app and could not tell what happened; \`verifiedReason\` says which clause decided that. Report it as unknown, never as working.
-- **\`verified: "no-fault"\` is not a pass either.** It means nothing was DECLARED to prove: the page settled and no channel complained, but you asserted nothing, so there is no verification. You get it whenever \`until\` is omitted. Name a consequence the action changes — a signal, a request, a route, or store state — and call again.
-- **Never weaken a check to make it green.** Downgrading, skipping or deleting an assertion is a finding, not a fix.
 - **If Reticle cannot run** (no daemon, or this is not a running web app), say so. Do not skip verification silently.
 - **Setup is not finished until one real flow has been driven and produced a verdict.** \`init\` exiting 0, the tools appearing, and a session being listed are all things that happen before anything has been verified.
 

package/dist/register/codex-toml.d.ts

@@ -8,3 +8,15 @@
 export declare function codexServerTokens(existing: string | null, serversKey: string): string[];
 /** Does this config already declare a Reticle server under our name? */
 export declare function codexDeclaresOurServer(existing: string | null, serversKey: string): boolean;
+/**
+ * Does this config NAME a Reticle server at all, in any shape?
+ *
+ * Wider than {@link codexDeclaresOurServer}, which asks whether the entry holds a command we can
+ * read. A `url` entry, one that only has an `env` table, or an inline `mcp_servers = { … }` has no
+ * command and args, so it reads as absent there. `codex mcp add reticle` REPLACES such an entry
+ * without a word and exits 0, so anything that registers through that command has to ask this.
+ *
+ * Structural rather than a substring match: a project called `reticle`, under
+ * `[projects."/home/u/reticle"]`, does not name a server.
+ */
+export declare function codexNamesOurServer(existing: string | null, serversKey: string): boolean;

package/dist/register/codex-toml.js

@@ -142,3 +142,47 @@ export function codexServerTokens(existing, serversKey) {
 export function codexDeclaresOurServer(existing, serversKey) {
     return 0 < codexServerTokens(existing, serversKey).length;
 }
+/**
+ * Our key, as a KEY, inside an inline table's text: `reticle = …`, `"reticle" = …`, or the dotted
+ * `reticle.command = …`. A key follows the `{` or a `,`, and its quotes match, so a value that merely
+ * starts with the name (`command = "reticle.js"`) is not one.
+ */
+const OUR_KEY_INLINE = new RegExp(`(?:^|[{,])\\s*(?:${MCP_SERVER_NAME}|"${MCP_SERVER_NAME}"|'${MCP_SERVER_NAME}')\\s*[.=]`);
+/**
+ * Does this config NAME a Reticle server at all, in any shape?
+ *
+ * Wider than {@link codexDeclaresOurServer}, which asks whether the entry holds a command we can
+ * read. A `url` entry, one that only has an `env` table, or an inline `mcp_servers = { … }` has no
+ * command and args, so it reads as absent there. `codex mcp add reticle` REPLACES such an entry
+ * without a word and exits 0, so anything that registers through that command has to ask this.
+ *
+ * Structural rather than a substring match: a project called `reticle`, under
+ * `[projects."/home/u/reticle"]`, does not name a server.
+ */
+export function codexNamesOurServer(existing, serversKey) {
+    if (null === existing)
+        return false;
+    const want = ourTablePath(serversKey);
+    const isOurs = (path) => want.every((segment, i) => path[i] === segment);
+    let table = [];
+    for (const rawLine of existing.split(/\r?\n/)) {
+        const line = withoutComment(rawLine).trim();
+        const header = /^\[{1,2}([^\]]+)\]{1,2}$/.exec(line);
+        if (null !== header) {
+            table = keyPath(header[1] ?? '');
+            if (isOurs(table))
+                return true;
+            continue;
+        }
+        const assignment = /^([^=]+)=(.*)$/.exec(line);
+        if (null === assignment)
+            continue;
+        const path = [...table, ...keyPath(assignment[1] ?? '')];
+        if (isOurs(path))
+            return true;
+        // `mcp_servers = { reticle = { … } }`: the whole table is one inline value, our key inside it.
+        if (samePath(path, [serversKey]) && OUR_KEY_INLINE.test(assignment[2] ?? ''))
+            return true;
+    }
+    return false;
+}

package/dist/register/mcp.d.ts

@@ -58,14 +58,14 @@ export declare function npxServerArgs(): string[];
  * @param tokens every string in the entry's command + args, in any of the client shapes.
  */
 export declare function isReticleRegistration(tokens: readonly string[]): boolean;
-interface ClaudeAddCommand {
+interface CliAddCommand {
     command: string;
     args: string[];
     /** Human-readable form of the same command, for reports and manual fallback. */
     display: string;
 }
 /** `claude mcp add reticle -s user -- npx @reticlehq/server mcp` — registers globally for all projects (portless). */
-export declare function claudeAddCommand(): ClaudeAddCommand;
+export declare function claudeAddCommand(): CliAddCommand;
 /**
  * Is a `reticle` server already registered with Claude Code, in any scope this project sees?
  *
@@ -89,6 +89,19 @@ export declare function claudeAvailableProbe(): {
     command: string;
     args: string[];
 };
+/**
+ * `codex mcp add reticle -- npx @reticlehq/server mcp` — Codex keeps the entry in its own
+ * `~/.codex/config.toml`, shared by the desktop app and the CLI, so one registration covers both.
+ *
+ * It REPLACES an existing entry of the same name and still exits 0, so callers run it only when the
+ * config names no `reticle` server at all (see `codexNamesOurServer`).
+ */
+export declare function codexAddCommand(): CliAddCommand;
+/** Probe args for whether the `codex` CLI is installed at all. */
+export declare function codexAvailableProbe(): {
+    command: string;
+    args: string[];
+};
 /**
  * The Windows `cmd /c npx` registration. Printed on every Windows init, not only when the `claude`
  * CLI is missing — a successful `claude mcp add` of bare `npx` is exactly the failure that reported

package/dist/register/mcp.js

@@ -36,6 +36,7 @@ export const NPX = 'npx';
 const RETICLE_PACKAGE = RETICLE_NPM_PACKAGE;
 const MCP_SUBCOMMAND = 'mcp';
 const CLAUDE_CLI = 'claude';
+const CODEX_CLI = 'codex';
 /** Windows `cmd /c` — the spawn that PowerShell's execution policy does not gate. */
 const WINDOWS_SHELL = 'cmd';
 const WINDOWS_SHELL_C = '/c';
@@ -140,6 +141,21 @@ export function claudeHasReticle(io, projectDir, configDir = process.env['CLAUDE
 export function claudeAvailableProbe() {
     return { command: CLAUDE_CLI, args: ['--version'] };
 }
+/**
+ * `codex mcp add reticle -- npx @reticlehq/server mcp` — Codex keeps the entry in its own
+ * `~/.codex/config.toml`, shared by the desktop app and the CLI, so one registration covers both.
+ *
+ * It REPLACES an existing entry of the same name and still exits 0, so callers run it only when the
+ * config names no `reticle` server at all (see `codexNamesOurServer`).
+ */
+export function codexAddCommand() {
+    const args = [MCP_SUBCOMMAND, 'add', MCP_SERVER_NAME, '--', ...serverInvocation()];
+    return { command: CODEX_CLI, args, display: `${CODEX_CLI} ${args.join(' ')}` };
+}
+/** Probe args for whether the `codex` CLI is installed at all. */
+export function codexAvailableProbe() {
+    return { command: CODEX_CLI, args: ['--version'] };
+}
 /**
  * The Windows `cmd /c npx` registration. Printed on every Windows init, not only when the `claude`
  * CLI is missing — a successful `claude mcp add` of bare `npx` is exactly the failure that reported

package/dist/run-types.d.ts

@@ -41,6 +41,8 @@ export interface InitOptions {
      * at `src/admin` ended up with no `/reticle` at all (#318).
      */
     agentRoot?: string;
+    /** The agent root is a workspace with several apps: it is pinned to none of them. */
+    severalApps?: boolean;
     /**
      * Hand the telemetry outcome back rather than emitting it here.
      *
@@ -74,6 +76,8 @@ export interface InitIo {
     listDirs(relPath: string): readonly string[];
     /** File (non-directory) basenames inside a project-relative directory, including dotfiles. */
     listFiles(relPath: string): readonly string[];
+    /** Whether a project-relative path is a symbolic link. Optional: an IO without it reads none. */
+    isSymlink?(relPath: string): boolean;
     /** The same IO re-rooted at a project-relative subdirectory (used for the workspace redirect). */
     scoped(relPath: string): InitIo;
     /** Runs a subprocess to completion (inherits stdio); returns true on exit code 0. */
@@ -138,4 +142,6 @@ export interface InitResult {
      * `deferOutcome` is set. Absent on a dry run and on the exits that report for themselves.
      */
     outcome?: InitOutcome;
+    /** No app where init ran; it listed the apps below instead. Reported as `no_package_json`. */
+    listedAppsBelow?: true;
 }

package/dist/run.d.ts

@@ -1,5 +1,5 @@
 import type { InitOptions, InitIo, InitResult } from './run-types.js';
-export type { InitOptions, InitIo, InitResult } from './run-types.js';
 import { resolveLockfiles } from './detect/lockfiles.js';
+export type { InitOptions, InitIo, InitResult } from './run-types.js';
 export { resolveLockfiles };
 export declare function runInit(options: InitOptions, io: InitIo): InitResult;