Claude Code First, specification version 0.1.0. The plain-language guide
Version 0.1.0. Grade R1/S2.
F400 Plugin hooks did not reach web sessions, so the guard was carried by a launcher committed to the repository
| Field | Value |
|---|---|
| Status | active |
| Topic | Environment, permissions, and agent-facing products |
| Grade | R1/S2 |
| Cases | Shio, roadkeep, freewilly, polyweave |
| Contrary | none |
| Harness facts | H10, H11; O3 (observed, contradicted by H10) |
Claim
In Claude Code on the web, a guard shipped inside a marketplace plugin did not load, so an agent could hand-edit the files the guard protects, and the remedy was a launcher committed to the repository and wired from the committed settings.
Mechanism
The guard that refuses a hand edit of the governed files ships in the roadkeep plugin. A web session read the repository's committed files and settings (H11) but, as the projects recorded it in August 2026, did not install marketplace plugins, so the plugin's hooks and MCP server never loaded there. A script committed under .claude/hooks/ and named in the committed settings.json and .mcp.json reaches that session because it is part of the checkout. The launcher then has to find an engine at run time and must decide whether an installed plugin already answers, which is where its own defects came from (see F403).
Observations
- shio. The failure was recorded from a web session, in a commit authored by Claude with
a session link, on 2026-08-08: the web harness "never installs marketplace plugins" [shio@c215718bb], so "the guard that denies a hand-edit of the roadkeep-owned docs is absent" [shio@c215718bb]. The same commit hand-wrote the first committed launcher. Shio worked from web sessions before and after: 55 commits are authored by Claude with a claude.ai session link, from [shio@c652a2cba] on 2026-04-11 to [shio@daecef641] on 2026-08-16 (git log 821f18d74 --author='^Claude' --format=%h | wc -l gives 55). At the pin the launcher runs on three hook events, "roadkeep-launch.py" [shio@821f18d74:.claude/settings.json#L61-L94].
- roadkeep. Four days later, on 2026-08-12, roadkeep made the launcher part of the tool,
for environments "which do not support plugin installations" [roadkeep@7243dc05]. Its ledger names where the idea came from: "so a project hand-writes the launcher that finds one" [roadkeep@91754240:docs/CHANGELOG.md#L1067]. The shipped launcher records a defect of that hand-written copy, which deferred to a plugin found on disk and not loaded: "A hand-written copy globbed" [roadkeep@91754240:hooks/roadkeep-launch.py#L43-L47].
- freewilly. The launcher arrived with the first commit, the afternoon roadkeep shipped
it [freewilly@acc7fc1]. The ignore file keeps hooks/ committed because "the plugin never installs on Claude Code on the web" [freewilly@c1c2eaf:.gitignore#L12]. Twelve commits authored by Claude on 2026-08-13 carry a session link, "Claude-Session: https://claude.ai/code/session_" [freewilly@915e22e]; that they came from a web session is an interpretation. No failure of the guard is recorded here.
- polyweave. The launcher was imported whole on the first day [polyweave@c45f7b3], with
the same reason, "Claude Code on the web has no" [polyweave@6d1c136:.claude/hooks/roadkeep-launch.py#L9] plugin command, and with roadkeep's task ids in its text. No failure is recorded here.
Independence
One origin. The failure is recorded once, in Shio, and the remedy was invented there by hand on 2026-08-08. roadkeep generalised it (RK1108, 2026-08-12), and freewilly and polyweave carry roadkeep's version, whose docstring cites RK1108. Neither of them records a web session in which the guard was absent. The register's observation O3 in ../harness.md says roadkeep built the launcher and it then spread to Shio; the dates at the pins and roadkeep's own ledger entry place the first launcher in Shio.
Counter-evidence
H10 contradicts the premise as the documentation stands on 2026-09-24: a plugin enabled for the claude.ai account loads in a cloud session as a synced plugin. The practice may have outlived its cause, or a synced plugin may not cover one installed from a project marketplace; no source at the pins tests either. winwright wires the guard to a sibling checkout, "/../roadkeep/scripts/roadkeep.py" [winwright@861b82e:.mcp.json#L6], and commits no launcher; it records no web session, so it neither supports nor contradicts the claim.
Grade
R1: one independent origin (Shio); the other three are copies of the remedy. S2: the failure is a commit that records what was absent and when, and nothing counted it or tested it. Because H10 now contradicts the premise, a rule drawn from this finding must be re-checked in a cloud session before it is written.