fix(cli)!: remove browser fork, add adapter override to hosted mode - #361

Merged
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork
Aug 19, 2026
Merged

fix(cli)!: remove browser fork, add adapter override to hosted mode#361
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork

Conversation

@ankitranjan7

@ankitranjan7ankitranjan7 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

What

webcmd browser fork was an undocumented alias bound to the same handler as webcmd adapter override, and it leaked the alias in its own error message:

$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")

The caller is told the usage of a command they did not run. browser fork appears nowhere in docs/, skills/, README.md, or CHANGELOG.md — it was only ever reachable by guessing. It also sat in the browser namespace behind a require-existing session policy for what is a local file copy.

This removes it from the local CLI and from the hosted browser catalog.

adapter override in hosted mode (second commit)

browser fork turned out to be hosted's only fork path. adapter override was never routed in hosted mode — src/hosted/runner.ts matched only source, path, and help — and cloud's forkSystemAdapterCommand had exactly one caller: the fork browser action. Removing browser fork alone would have taken hosted's fork capability away with no replacement.

So the second commit routes adapter override <site>/<command> in hosted mode to a new POST /v1/adapters/override. After both commits the command means the same thing in either mode: fork an installed upstream command into a private copy you can edit, refusing commands that are not installed upstream and commands already forked.

Storage differs, so the output does:

localhosted
writes~/.webcmd/clis/<site>/<cmd>.js + .base copytenant-private adapter package
printsyours: / base: pathspackage: id + source: file
edit withthe path from adapter pathadapter source get|put
not upstream"not provided by an installed plugin"HOSTED_ADAPTER_FORK_SOURCE_INVALID
already forked"an override already exists at …"HOSTED_ADAPTER_FORK_ALREADY_EXISTS

Behaviour after

$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
# exit 2
$ webcmd browser click x
error: unknown command 'click'
# exit 2 (was 1)

Unknown browser subcommands now exit 2 (USAGE_ERROR) instead of 1.

Why fork stays in BROWSER_SUBCOMMAND_NAMES

rejectPositionalBrowserSessionArgv reads any unreserved token after browser as the retired positional-session grammar. Dropping fork from that set would answer webcmd browser fork hackernews with:

error: Browser sessions are root selectors. Use: webcmd --session fork browser hackernews

— worse than what we started with. Retired names stay listed so commander can report them properly. The set was already a superset of the declared subcommands (~40 names, 7 real); the comment now says that is deliberate instead of asking the next person to "keep in sync".

Also

Corrects the usage string in the adapter-shadow hint, which advertised adapter override <site> <command> (two positionals) for a command that takes one <site>/<command>.

Hosted impact

Hosted impact: C — webcmd-cloud change required
Trigger: 3.4 browser command surface (src/browser/command-catalog.ts)
Cloud files: src/default-adapters/source.ts:268, src/live-gates/cli-gates.ts:14
Why: cloud asserts the exact list ['bind','close','fork','init','run','snapshot','tabs','verify']
and the count browserCommands: 8. Removing fork throws BrowserRunProtocolMismatchError.
Sequencing: land the cloud PR before `npm run bump:webcmd`.

The cloud side is agentrhq/webcmd-cloud#50, which serves POST /v1/adapters/override, drops the fork action, and re-pins the parity digests. Without it the hosted adapter override here 404s.

Order: merge this → bump PINNED_WEBCMD_SHA in cloud → merge webcmd-cloud#50.

Known window: between this release and the cloud deploy, hosted mode has no fork command — browser fork is gone and adapter override 404s until webcmd-cloud#50 ships. Accepted deliberately rather than splitting the PRs; keep the two merges close together.

Verification

  • npm run typecheck — clean
  • npm test — 5682 passed, 1 failed: src/doctor.test.ts:218 (profile alias rendering), pre-existing on main, unrelated to this change
  • npm run check:hosted-contract — passes; regenerated hosted-contract.json now lists 7 browser commands
  • npm run check:codex-plugin — passes

Cross-repo, per §7 of .github/hosted-impact-review.md: packed this branch, installed it into webcmd-cloud, ran cloud's full suite against it — 1189 passed, 0 failed.

Follow-ups from the same audit (not in this PR)

  • runCli() has no error handler, so adapter path, adapter source get|put, site fixture get, and session close <bad-id> dump raw Node stack traces
  • webcmd adapter path <site>/<cmd> fails for every command that is not already a local override — the documented private-fork workflow
  • Adapter error envelopes are always YAML, even under -f json
  • --help -f yaml is missing on site, skills, session, external

🤖 Generated with Claude Code

`webcmd browser fork` was an undocumented alias bound to the same handler as
`webcmd adapter override`. It leaked the alias immediately:
$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")
The error names a command the caller did not run, and nothing in docs/, skills/,
README, or CHANGELOG ever referenced `browser fork`. It also sat in the browser
namespace behind a `require-existing` session policy for what is a local file
copy.
Remove the local registration and the hosted catalog entry, so `adapter
override` is the single fork path in both modes.
`browser <retired>` now reports the replacement instead of a bare unknown
command, and unknown browser subcommands exit 2 (USAGE_ERROR) rather than 1:
$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
`fork` stays in BROWSER_SUBCOMMAND_NAMES: the preprocessor reads an unreserved
token after `browser` as a retired positional session id, so dropping it would
answer with "Browser sessions are root selectors" instead. The comment there now
says retired names are kept on purpose — the set was already a superset of the
declared subcommands.
Also corrects the usage string in the adapter-shadow hint, which showed
`adapter override <site> <command>` for a command that takes one
`<site>/<command>` positional.
BREAKING CHANGE: `webcmd browser fork` is removed. Use `webcmd adapter override
<site>/<command>`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actionsBot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

Removing `browser fork` in the previous commit took away hosted mode's only
way to fork an adapter: `adapter override` was never routed in hosted mode
(runner.ts matched only `source`, `path`, and help), and cloud exposes no
override route — `forkSystemAdapterCommand` had exactly one caller, the
`fork` browser action.
Route `adapter override <site>/<command>` in hosted mode to the new
`POST /v1/adapters/override`, so the command means the same thing in both
modes: fork an installed upstream command into a private copy you can edit,
refusing commands that are not installed upstream and commands already
forked.
Storage differs, so the output does. Local prints the file it wrote and its
`.base` copy; hosted prints the private package id and the source file, and
points at `adapter source get|put` as the editing path — the hosted analogue
of editing the file at `adapter path`.
Requires the matching webcmd-cloud change; without it the route 404s.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ankitranjan7ankitranjan7 changed the title fix(cli)!: remove the duplicate browser fork subcommandfix(cli)!: remove browser fork, add adapter override to hosted modeAug 19, 2026
@ankitranjan7
ankitranjan7 merged commit 3919f6f into mainAug 19, 2026
37 checks passed
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
@ankitranjan7
ankitranjan7 deleted the fix/remove-browser-fork branch September 1, 2026 12:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

fix(cli)!: remove browser fork, add adapter override to hosted mode - #361

Merged
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork
Aug 19, 2026
Merged

fix(cli)!: remove browser fork, add adapter override to hosted mode#361
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork

Conversation

@ankitranjan7

@ankitranjan7ankitranjan7 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

What

webcmd browser fork was an undocumented alias bound to the same handler as webcmd adapter override, and it leaked the alias in its own error message:

$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")

The caller is told the usage of a command they did not run. browser fork appears nowhere in docs/, skills/, README.md, or CHANGELOG.md — it was only ever reachable by guessing. It also sat in the browser namespace behind a require-existing session policy for what is a local file copy.

This removes it from the local CLI and from the hosted browser catalog.

adapter override in hosted mode (second commit)

browser fork turned out to be hosted's only fork path. adapter override was never routed in hosted mode — src/hosted/runner.ts matched only source, path, and help — and cloud's forkSystemAdapterCommand had exactly one caller: the fork browser action. Removing browser fork alone would have taken hosted's fork capability away with no replacement.

So the second commit routes adapter override <site>/<command> in hosted mode to a new POST /v1/adapters/override. After both commits the command means the same thing in either mode: fork an installed upstream command into a private copy you can edit, refusing commands that are not installed upstream and commands already forked.

Storage differs, so the output does:

localhosted
writes~/.webcmd/clis/<site>/<cmd>.js + .base copytenant-private adapter package
printsyours: / base: pathspackage: id + source: file
edit withthe path from adapter pathadapter source get|put
not upstream"not provided by an installed plugin"HOSTED_ADAPTER_FORK_SOURCE_INVALID
already forked"an override already exists at …"HOSTED_ADAPTER_FORK_ALREADY_EXISTS

Behaviour after

$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
# exit 2
$ webcmd browser click x
error: unknown command 'click'
# exit 2 (was 1)

Unknown browser subcommands now exit 2 (USAGE_ERROR) instead of 1.

Why fork stays in BROWSER_SUBCOMMAND_NAMES

rejectPositionalBrowserSessionArgv reads any unreserved token after browser as the retired positional-session grammar. Dropping fork from that set would answer webcmd browser fork hackernews with:

error: Browser sessions are root selectors. Use: webcmd --session fork browser hackernews

— worse than what we started with. Retired names stay listed so commander can report them properly. The set was already a superset of the declared subcommands (~40 names, 7 real); the comment now says that is deliberate instead of asking the next person to "keep in sync".

Also

Corrects the usage string in the adapter-shadow hint, which advertised adapter override <site> <command> (two positionals) for a command that takes one <site>/<command>.

Hosted impact

Hosted impact: C — webcmd-cloud change required
Trigger: 3.4 browser command surface (src/browser/command-catalog.ts)
Cloud files: src/default-adapters/source.ts:268, src/live-gates/cli-gates.ts:14
Why: cloud asserts the exact list ['bind','close','fork','init','run','snapshot','tabs','verify']
and the count browserCommands: 8. Removing fork throws BrowserRunProtocolMismatchError.
Sequencing: land the cloud PR before `npm run bump:webcmd`.

The cloud side is agentrhq/webcmd-cloud#50, which serves POST /v1/adapters/override, drops the fork action, and re-pins the parity digests. Without it the hosted adapter override here 404s.

Order: merge this → bump PINNED_WEBCMD_SHA in cloud → merge webcmd-cloud#50.

Known window: between this release and the cloud deploy, hosted mode has no fork command — browser fork is gone and adapter override 404s until webcmd-cloud#50 ships. Accepted deliberately rather than splitting the PRs; keep the two merges close together.

Verification

  • npm run typecheck — clean
  • npm test — 5682 passed, 1 failed: src/doctor.test.ts:218 (profile alias rendering), pre-existing on main, unrelated to this change
  • npm run check:hosted-contract — passes; regenerated hosted-contract.json now lists 7 browser commands
  • npm run check:codex-plugin — passes

Cross-repo, per §7 of .github/hosted-impact-review.md: packed this branch, installed it into webcmd-cloud, ran cloud's full suite against it — 1189 passed, 0 failed.

Follow-ups from the same audit (not in this PR)

  • runCli() has no error handler, so adapter path, adapter source get|put, site fixture get, and session close <bad-id> dump raw Node stack traces
  • webcmd adapter path <site>/<cmd> fails for every command that is not already a local override — the documented private-fork workflow
  • Adapter error envelopes are always YAML, even under -f json
  • --help -f yaml is missing on site, skills, session, external

🤖 Generated with Claude Code

`webcmd browser fork` was an undocumented alias bound to the same handler as
`webcmd adapter override`. It leaked the alias immediately:
$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")
The error names a command the caller did not run, and nothing in docs/, skills/,
README, or CHANGELOG ever referenced `browser fork`. It also sat in the browser
namespace behind a `require-existing` session policy for what is a local file
copy.
Remove the local registration and the hosted catalog entry, so `adapter
override` is the single fork path in both modes.
`browser <retired>` now reports the replacement instead of a bare unknown
command, and unknown browser subcommands exit 2 (USAGE_ERROR) rather than 1:
$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
`fork` stays in BROWSER_SUBCOMMAND_NAMES: the preprocessor reads an unreserved
token after `browser` as a retired positional session id, so dropping it would
answer with "Browser sessions are root selectors" instead. The comment there now
says retired names are kept on purpose — the set was already a superset of the
declared subcommands.
Also corrects the usage string in the adapter-shadow hint, which showed
`adapter override <site> <command>` for a command that takes one
`<site>/<command>` positional.
BREAKING CHANGE: `webcmd browser fork` is removed. Use `webcmd adapter override
<site>/<command>`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actionsBot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

Removing `browser fork` in the previous commit took away hosted mode's only
way to fork an adapter: `adapter override` was never routed in hosted mode
(runner.ts matched only `source`, `path`, and help), and cloud exposes no
override route — `forkSystemAdapterCommand` had exactly one caller, the
`fork` browser action.
Route `adapter override <site>/<command>` in hosted mode to the new
`POST /v1/adapters/override`, so the command means the same thing in both
modes: fork an installed upstream command into a private copy you can edit,
refusing commands that are not installed upstream and commands already
forked.
Storage differs, so the output does. Local prints the file it wrote and its
`.base` copy; hosted prints the private package id and the source file, and
points at `adapter source get|put` as the editing path — the hosted analogue
of editing the file at `adapter path`.
Requires the matching webcmd-cloud change; without it the route 404s.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ankitranjan7ankitranjan7 changed the title fix(cli)!: remove the duplicate browser fork subcommandfix(cli)!: remove browser fork, add adapter override to hosted modeAug 19, 2026
@ankitranjan7
ankitranjan7 merged commit 3919f6f into mainAug 19, 2026
37 checks passed
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
@ankitranjan7
ankitranjan7 deleted the fix/remove-browser-fork branch September 1, 2026 12:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(cli)!: remove browser fork, add adapter override to hosted mode - #361

Merged
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork
Aug 19, 2026
Merged

fix(cli)!: remove browser fork, add adapter override to hosted mode#361
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork

Conversation

@ankitranjan7

@ankitranjan7ankitranjan7 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

What

webcmd browser fork was an undocumented alias bound to the same handler as webcmd adapter override, and it leaked the alias in its own error message:

$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")

The caller is told the usage of a command they did not run. browser fork appears nowhere in docs/, skills/, README.md, or CHANGELOG.md — it was only ever reachable by guessing. It also sat in the browser namespace behind a require-existing session policy for what is a local file copy.

This removes it from the local CLI and from the hosted browser catalog.

adapter override in hosted mode (second commit)

browser fork turned out to be hosted's only fork path. adapter override was never routed in hosted mode — src/hosted/runner.ts matched only source, path, and help — and cloud's forkSystemAdapterCommand had exactly one caller: the fork browser action. Removing browser fork alone would have taken hosted's fork capability away with no replacement.

So the second commit routes adapter override <site>/<command> in hosted mode to a new POST /v1/adapters/override. After both commits the command means the same thing in either mode: fork an installed upstream command into a private copy you can edit, refusing commands that are not installed upstream and commands already forked.

Storage differs, so the output does:

localhosted
writes~/.webcmd/clis/<site>/<cmd>.js + .base copytenant-private adapter package
printsyours: / base: pathspackage: id + source: file
edit withthe path from adapter pathadapter source get|put
not upstream"not provided by an installed plugin"HOSTED_ADAPTER_FORK_SOURCE_INVALID
already forked"an override already exists at …"HOSTED_ADAPTER_FORK_ALREADY_EXISTS

Behaviour after

$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
# exit 2
$ webcmd browser click x
error: unknown command 'click'
# exit 2 (was 1)

Unknown browser subcommands now exit 2 (USAGE_ERROR) instead of 1.

Why fork stays in BROWSER_SUBCOMMAND_NAMES

rejectPositionalBrowserSessionArgv reads any unreserved token after browser as the retired positional-session grammar. Dropping fork from that set would answer webcmd browser fork hackernews with:

error: Browser sessions are root selectors. Use: webcmd --session fork browser hackernews

— worse than what we started with. Retired names stay listed so commander can report them properly. The set was already a superset of the declared subcommands (~40 names, 7 real); the comment now says that is deliberate instead of asking the next person to "keep in sync".

Also

Corrects the usage string in the adapter-shadow hint, which advertised adapter override <site> <command> (two positionals) for a command that takes one <site>/<command>.

Hosted impact

Hosted impact: C — webcmd-cloud change required
Trigger: 3.4 browser command surface (src/browser/command-catalog.ts)
Cloud files: src/default-adapters/source.ts:268, src/live-gates/cli-gates.ts:14
Why: cloud asserts the exact list ['bind','close','fork','init','run','snapshot','tabs','verify']
and the count browserCommands: 8. Removing fork throws BrowserRunProtocolMismatchError.
Sequencing: land the cloud PR before `npm run bump:webcmd`.

The cloud side is agentrhq/webcmd-cloud#50, which serves POST /v1/adapters/override, drops the fork action, and re-pins the parity digests. Without it the hosted adapter override here 404s.

Order: merge this → bump PINNED_WEBCMD_SHA in cloud → merge webcmd-cloud#50.

Known window: between this release and the cloud deploy, hosted mode has no fork command — browser fork is gone and adapter override 404s until webcmd-cloud#50 ships. Accepted deliberately rather than splitting the PRs; keep the two merges close together.

Verification

  • npm run typecheck — clean
  • npm test — 5682 passed, 1 failed: src/doctor.test.ts:218 (profile alias rendering), pre-existing on main, unrelated to this change
  • npm run check:hosted-contract — passes; regenerated hosted-contract.json now lists 7 browser commands
  • npm run check:codex-plugin — passes

Cross-repo, per §7 of .github/hosted-impact-review.md: packed this branch, installed it into webcmd-cloud, ran cloud's full suite against it — 1189 passed, 0 failed.

Follow-ups from the same audit (not in this PR)

  • runCli() has no error handler, so adapter path, adapter source get|put, site fixture get, and session close <bad-id> dump raw Node stack traces
  • webcmd adapter path <site>/<cmd> fails for every command that is not already a local override — the documented private-fork workflow
  • Adapter error envelopes are always YAML, even under -f json
  • --help -f yaml is missing on site, skills, session, external

🤖 Generated with Claude Code

`webcmd browser fork` was an undocumented alias bound to the same handler as
`webcmd adapter override`. It leaked the alias immediately:
$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")
The error names a command the caller did not run, and nothing in docs/, skills/,
README, or CHANGELOG ever referenced `browser fork`. It also sat in the browser
namespace behind a `require-existing` session policy for what is a local file
copy.
Remove the local registration and the hosted catalog entry, so `adapter
override` is the single fork path in both modes.
`browser <retired>` now reports the replacement instead of a bare unknown
command, and unknown browser subcommands exit 2 (USAGE_ERROR) rather than 1:
$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
`fork` stays in BROWSER_SUBCOMMAND_NAMES: the preprocessor reads an unreserved
token after `browser` as a retired positional session id, so dropping it would
answer with "Browser sessions are root selectors" instead. The comment there now
says retired names are kept on purpose — the set was already a superset of the
declared subcommands.
Also corrects the usage string in the adapter-shadow hint, which showed
`adapter override <site> <command>` for a command that takes one
`<site>/<command>` positional.
BREAKING CHANGE: `webcmd browser fork` is removed. Use `webcmd adapter override
<site>/<command>`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actionsBot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

Removing `browser fork` in the previous commit took away hosted mode's only
way to fork an adapter: `adapter override` was never routed in hosted mode
(runner.ts matched only `source`, `path`, and help), and cloud exposes no
override route — `forkSystemAdapterCommand` had exactly one caller, the
`fork` browser action.
Route `adapter override <site>/<command>` in hosted mode to the new
`POST /v1/adapters/override`, so the command means the same thing in both
modes: fork an installed upstream command into a private copy you can edit,
refusing commands that are not installed upstream and commands already
forked.
Storage differs, so the output does. Local prints the file it wrote and its
`.base` copy; hosted prints the private package id and the source file, and
points at `adapter source get|put` as the editing path — the hosted analogue
of editing the file at `adapter path`.
Requires the matching webcmd-cloud change; without it the route 404s.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ankitranjan7ankitranjan7 changed the title fix(cli)!: remove the duplicate browser fork subcommandfix(cli)!: remove browser fork, add adapter override to hosted modeAug 19, 2026
@ankitranjan7
ankitranjan7 merged commit 3919f6f into mainAug 19, 2026
37 checks passed
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
@ankitranjan7
ankitranjan7 deleted the fix/remove-browser-fork branch September 1, 2026 12:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(cli)!: remove browser fork, add adapter override to hosted mode - #361

Merged
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork
Aug 19, 2026
Merged

fix(cli)!: remove browser fork, add adapter override to hosted mode#361
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork

Conversation

@ankitranjan7

@ankitranjan7ankitranjan7 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

What

webcmd browser fork was an undocumented alias bound to the same handler as webcmd adapter override, and it leaked the alias in its own error message:

$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")

The caller is told the usage of a command they did not run. browser fork appears nowhere in docs/, skills/, README.md, or CHANGELOG.md — it was only ever reachable by guessing. It also sat in the browser namespace behind a require-existing session policy for what is a local file copy.

This removes it from the local CLI and from the hosted browser catalog.

adapter override in hosted mode (second commit)

browser fork turned out to be hosted's only fork path. adapter override was never routed in hosted mode — src/hosted/runner.ts matched only source, path, and help — and cloud's forkSystemAdapterCommand had exactly one caller: the fork browser action. Removing browser fork alone would have taken hosted's fork capability away with no replacement.

So the second commit routes adapter override <site>/<command> in hosted mode to a new POST /v1/adapters/override. After both commits the command means the same thing in either mode: fork an installed upstream command into a private copy you can edit, refusing commands that are not installed upstream and commands already forked.

Storage differs, so the output does:

localhosted
writes~/.webcmd/clis/<site>/<cmd>.js + .base copytenant-private adapter package
printsyours: / base: pathspackage: id + source: file
edit withthe path from adapter pathadapter source get|put
not upstream"not provided by an installed plugin"HOSTED_ADAPTER_FORK_SOURCE_INVALID
already forked"an override already exists at …"HOSTED_ADAPTER_FORK_ALREADY_EXISTS

Behaviour after

$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
# exit 2
$ webcmd browser click x
error: unknown command 'click'
# exit 2 (was 1)

Unknown browser subcommands now exit 2 (USAGE_ERROR) instead of 1.

Why fork stays in BROWSER_SUBCOMMAND_NAMES

rejectPositionalBrowserSessionArgv reads any unreserved token after browser as the retired positional-session grammar. Dropping fork from that set would answer webcmd browser fork hackernews with:

error: Browser sessions are root selectors. Use: webcmd --session fork browser hackernews

— worse than what we started with. Retired names stay listed so commander can report them properly. The set was already a superset of the declared subcommands (~40 names, 7 real); the comment now says that is deliberate instead of asking the next person to "keep in sync".

Also

Corrects the usage string in the adapter-shadow hint, which advertised adapter override <site> <command> (two positionals) for a command that takes one <site>/<command>.

Hosted impact

Hosted impact: C — webcmd-cloud change required
Trigger: 3.4 browser command surface (src/browser/command-catalog.ts)
Cloud files: src/default-adapters/source.ts:268, src/live-gates/cli-gates.ts:14
Why: cloud asserts the exact list ['bind','close','fork','init','run','snapshot','tabs','verify']
and the count browserCommands: 8. Removing fork throws BrowserRunProtocolMismatchError.
Sequencing: land the cloud PR before `npm run bump:webcmd`.

The cloud side is agentrhq/webcmd-cloud#50, which serves POST /v1/adapters/override, drops the fork action, and re-pins the parity digests. Without it the hosted adapter override here 404s.

Order: merge this → bump PINNED_WEBCMD_SHA in cloud → merge webcmd-cloud#50.

Known window: between this release and the cloud deploy, hosted mode has no fork command — browser fork is gone and adapter override 404s until webcmd-cloud#50 ships. Accepted deliberately rather than splitting the PRs; keep the two merges close together.

Verification

  • npm run typecheck — clean
  • npm test — 5682 passed, 1 failed: src/doctor.test.ts:218 (profile alias rendering), pre-existing on main, unrelated to this change
  • npm run check:hosted-contract — passes; regenerated hosted-contract.json now lists 7 browser commands
  • npm run check:codex-plugin — passes

Cross-repo, per §7 of .github/hosted-impact-review.md: packed this branch, installed it into webcmd-cloud, ran cloud's full suite against it — 1189 passed, 0 failed.

Follow-ups from the same audit (not in this PR)

  • runCli() has no error handler, so adapter path, adapter source get|put, site fixture get, and session close <bad-id> dump raw Node stack traces
  • webcmd adapter path <site>/<cmd> fails for every command that is not already a local override — the documented private-fork workflow
  • Adapter error envelopes are always YAML, even under -f json
  • --help -f yaml is missing on site, skills, session, external

🤖 Generated with Claude Code

`webcmd browser fork` was an undocumented alias bound to the same handler as
`webcmd adapter override`. It leaked the alias immediately:
$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")
The error names a command the caller did not run, and nothing in docs/, skills/,
README, or CHANGELOG ever referenced `browser fork`. It also sat in the browser
namespace behind a `require-existing` session policy for what is a local file
copy.
Remove the local registration and the hosted catalog entry, so `adapter
override` is the single fork path in both modes.
`browser <retired>` now reports the replacement instead of a bare unknown
command, and unknown browser subcommands exit 2 (USAGE_ERROR) rather than 1:
$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
`fork` stays in BROWSER_SUBCOMMAND_NAMES: the preprocessor reads an unreserved
token after `browser` as a retired positional session id, so dropping it would
answer with "Browser sessions are root selectors" instead. The comment there now
says retired names are kept on purpose — the set was already a superset of the
declared subcommands.
Also corrects the usage string in the adapter-shadow hint, which showed
`adapter override <site> <command>` for a command that takes one
`<site>/<command>` positional.
BREAKING CHANGE: `webcmd browser fork` is removed. Use `webcmd adapter override
<site>/<command>`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actionsBot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

Removing `browser fork` in the previous commit took away hosted mode's only
way to fork an adapter: `adapter override` was never routed in hosted mode
(runner.ts matched only `source`, `path`, and help), and cloud exposes no
override route — `forkSystemAdapterCommand` had exactly one caller, the
`fork` browser action.
Route `adapter override <site>/<command>` in hosted mode to the new
`POST /v1/adapters/override`, so the command means the same thing in both
modes: fork an installed upstream command into a private copy you can edit,
refusing commands that are not installed upstream and commands already
forked.
Storage differs, so the output does. Local prints the file it wrote and its
`.base` copy; hosted prints the private package id and the source file, and
points at `adapter source get|put` as the editing path — the hosted analogue
of editing the file at `adapter path`.
Requires the matching webcmd-cloud change; without it the route 404s.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ankitranjan7ankitranjan7 changed the title fix(cli)!: remove the duplicate browser fork subcommandfix(cli)!: remove browser fork, add adapter override to hosted modeAug 19, 2026
@ankitranjan7
ankitranjan7 merged commit 3919f6f into mainAug 19, 2026
37 checks passed
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
@ankitranjan7
ankitranjan7 deleted the fix/remove-browser-fork branch September 1, 2026 12:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

fix(cli)!: remove browser fork, add adapter override to hosted mode - #361

Merged
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork
Aug 19, 2026
Merged

fix(cli)!: remove browser fork, add adapter override to hosted mode#361
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork

Conversation

@ankitranjan7

@ankitranjan7ankitranjan7 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

What

webcmd browser fork was an undocumented alias bound to the same handler as webcmd adapter override, and it leaked the alias in its own error message:

$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")

The caller is told the usage of a command they did not run. browser fork appears nowhere in docs/, skills/, README.md, or CHANGELOG.md — it was only ever reachable by guessing. It also sat in the browser namespace behind a require-existing session policy for what is a local file copy.

This removes it from the local CLI and from the hosted browser catalog.

adapter override in hosted mode (second commit)

browser fork turned out to be hosted's only fork path. adapter override was never routed in hosted mode — src/hosted/runner.ts matched only source, path, and help — and cloud's forkSystemAdapterCommand had exactly one caller: the fork browser action. Removing browser fork alone would have taken hosted's fork capability away with no replacement.

So the second commit routes adapter override <site>/<command> in hosted mode to a new POST /v1/adapters/override. After both commits the command means the same thing in either mode: fork an installed upstream command into a private copy you can edit, refusing commands that are not installed upstream and commands already forked.

Storage differs, so the output does:

localhosted
writes~/.webcmd/clis/<site>/<cmd>.js + .base copytenant-private adapter package
printsyours: / base: pathspackage: id + source: file
edit withthe path from adapter pathadapter source get|put
not upstream"not provided by an installed plugin"HOSTED_ADAPTER_FORK_SOURCE_INVALID
already forked"an override already exists at …"HOSTED_ADAPTER_FORK_ALREADY_EXISTS

Behaviour after

$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
# exit 2
$ webcmd browser click x
error: unknown command 'click'
# exit 2 (was 1)

Unknown browser subcommands now exit 2 (USAGE_ERROR) instead of 1.

Why fork stays in BROWSER_SUBCOMMAND_NAMES

rejectPositionalBrowserSessionArgv reads any unreserved token after browser as the retired positional-session grammar. Dropping fork from that set would answer webcmd browser fork hackernews with:

error: Browser sessions are root selectors. Use: webcmd --session fork browser hackernews

— worse than what we started with. Retired names stay listed so commander can report them properly. The set was already a superset of the declared subcommands (~40 names, 7 real); the comment now says that is deliberate instead of asking the next person to "keep in sync".

Also

Corrects the usage string in the adapter-shadow hint, which advertised adapter override <site> <command> (two positionals) for a command that takes one <site>/<command>.

Hosted impact

Hosted impact: C — webcmd-cloud change required
Trigger: 3.4 browser command surface (src/browser/command-catalog.ts)
Cloud files: src/default-adapters/source.ts:268, src/live-gates/cli-gates.ts:14
Why: cloud asserts the exact list ['bind','close','fork','init','run','snapshot','tabs','verify']
and the count browserCommands: 8. Removing fork throws BrowserRunProtocolMismatchError.
Sequencing: land the cloud PR before `npm run bump:webcmd`.

The cloud side is agentrhq/webcmd-cloud#50, which serves POST /v1/adapters/override, drops the fork action, and re-pins the parity digests. Without it the hosted adapter override here 404s.

Order: merge this → bump PINNED_WEBCMD_SHA in cloud → merge webcmd-cloud#50.

Known window: between this release and the cloud deploy, hosted mode has no fork command — browser fork is gone and adapter override 404s until webcmd-cloud#50 ships. Accepted deliberately rather than splitting the PRs; keep the two merges close together.

Verification

  • npm run typecheck — clean
  • npm test — 5682 passed, 1 failed: src/doctor.test.ts:218 (profile alias rendering), pre-existing on main, unrelated to this change
  • npm run check:hosted-contract — passes; regenerated hosted-contract.json now lists 7 browser commands
  • npm run check:codex-plugin — passes

Cross-repo, per §7 of .github/hosted-impact-review.md: packed this branch, installed it into webcmd-cloud, ran cloud's full suite against it — 1189 passed, 0 failed.

Follow-ups from the same audit (not in this PR)

  • runCli() has no error handler, so adapter path, adapter source get|put, site fixture get, and session close <bad-id> dump raw Node stack traces
  • webcmd adapter path <site>/<cmd> fails for every command that is not already a local override — the documented private-fork workflow
  • Adapter error envelopes are always YAML, even under -f json
  • --help -f yaml is missing on site, skills, session, external

🤖 Generated with Claude Code

`webcmd browser fork` was an undocumented alias bound to the same handler as
`webcmd adapter override`. It leaked the alias immediately:
$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")
The error names a command the caller did not run, and nothing in docs/, skills/,
README, or CHANGELOG ever referenced `browser fork`. It also sat in the browser
namespace behind a `require-existing` session policy for what is a local file
copy.
Remove the local registration and the hosted catalog entry, so `adapter
override` is the single fork path in both modes.
`browser <retired>` now reports the replacement instead of a bare unknown
command, and unknown browser subcommands exit 2 (USAGE_ERROR) rather than 1:
$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
`fork` stays in BROWSER_SUBCOMMAND_NAMES: the preprocessor reads an unreserved
token after `browser` as a retired positional session id, so dropping it would
answer with "Browser sessions are root selectors" instead. The comment there now
says retired names are kept on purpose — the set was already a superset of the
declared subcommands.
Also corrects the usage string in the adapter-shadow hint, which showed
`adapter override <site> <command>` for a command that takes one
`<site>/<command>` positional.
BREAKING CHANGE: `webcmd browser fork` is removed. Use `webcmd adapter override
<site>/<command>`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actionsBot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

Removing `browser fork` in the previous commit took away hosted mode's only
way to fork an adapter: `adapter override` was never routed in hosted mode
(runner.ts matched only `source`, `path`, and help), and cloud exposes no
override route — `forkSystemAdapterCommand` had exactly one caller, the
`fork` browser action.
Route `adapter override <site>/<command>` in hosted mode to the new
`POST /v1/adapters/override`, so the command means the same thing in both
modes: fork an installed upstream command into a private copy you can edit,
refusing commands that are not installed upstream and commands already
forked.
Storage differs, so the output does. Local prints the file it wrote and its
`.base` copy; hosted prints the private package id and the source file, and
points at `adapter source get|put` as the editing path — the hosted analogue
of editing the file at `adapter path`.
Requires the matching webcmd-cloud change; without it the route 404s.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ankitranjan7ankitranjan7 changed the title fix(cli)!: remove the duplicate browser fork subcommandfix(cli)!: remove browser fork, add adapter override to hosted modeAug 19, 2026
@ankitranjan7
ankitranjan7 merged commit 3919f6f into mainAug 19, 2026
37 checks passed
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
@ankitranjan7
ankitranjan7 deleted the fix/remove-browser-fork branch September 1, 2026 12:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(cli)!: remove browser fork, add adapter override to hosted mode - #361

Merged
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork
Aug 19, 2026
Merged

fix(cli)!: remove browser fork, add adapter override to hosted mode#361
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork

Conversation

@ankitranjan7

@ankitranjan7ankitranjan7 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

What

webcmd browser fork was an undocumented alias bound to the same handler as webcmd adapter override, and it leaked the alias in its own error message:

$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")

The caller is told the usage of a command they did not run. browser fork appears nowhere in docs/, skills/, README.md, or CHANGELOG.md — it was only ever reachable by guessing. It also sat in the browser namespace behind a require-existing session policy for what is a local file copy.

This removes it from the local CLI and from the hosted browser catalog.

adapter override in hosted mode (second commit)

browser fork turned out to be hosted's only fork path. adapter override was never routed in hosted mode — src/hosted/runner.ts matched only source, path, and help — and cloud's forkSystemAdapterCommand had exactly one caller: the fork browser action. Removing browser fork alone would have taken hosted's fork capability away with no replacement.

So the second commit routes adapter override <site>/<command> in hosted mode to a new POST /v1/adapters/override. After both commits the command means the same thing in either mode: fork an installed upstream command into a private copy you can edit, refusing commands that are not installed upstream and commands already forked.

Storage differs, so the output does:

localhosted
writes~/.webcmd/clis/<site>/<cmd>.js + .base copytenant-private adapter package
printsyours: / base: pathspackage: id + source: file
edit withthe path from adapter pathadapter source get|put
not upstream"not provided by an installed plugin"HOSTED_ADAPTER_FORK_SOURCE_INVALID
already forked"an override already exists at …"HOSTED_ADAPTER_FORK_ALREADY_EXISTS

Behaviour after

$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
# exit 2
$ webcmd browser click x
error: unknown command 'click'
# exit 2 (was 1)

Unknown browser subcommands now exit 2 (USAGE_ERROR) instead of 1.

Why fork stays in BROWSER_SUBCOMMAND_NAMES

rejectPositionalBrowserSessionArgv reads any unreserved token after browser as the retired positional-session grammar. Dropping fork from that set would answer webcmd browser fork hackernews with:

error: Browser sessions are root selectors. Use: webcmd --session fork browser hackernews

— worse than what we started with. Retired names stay listed so commander can report them properly. The set was already a superset of the declared subcommands (~40 names, 7 real); the comment now says that is deliberate instead of asking the next person to "keep in sync".

Also

Corrects the usage string in the adapter-shadow hint, which advertised adapter override <site> <command> (two positionals) for a command that takes one <site>/<command>.

Hosted impact

Hosted impact: C — webcmd-cloud change required
Trigger: 3.4 browser command surface (src/browser/command-catalog.ts)
Cloud files: src/default-adapters/source.ts:268, src/live-gates/cli-gates.ts:14
Why: cloud asserts the exact list ['bind','close','fork','init','run','snapshot','tabs','verify']
and the count browserCommands: 8. Removing fork throws BrowserRunProtocolMismatchError.
Sequencing: land the cloud PR before `npm run bump:webcmd`.

The cloud side is agentrhq/webcmd-cloud#50, which serves POST /v1/adapters/override, drops the fork action, and re-pins the parity digests. Without it the hosted adapter override here 404s.

Order: merge this → bump PINNED_WEBCMD_SHA in cloud → merge webcmd-cloud#50.

Known window: between this release and the cloud deploy, hosted mode has no fork command — browser fork is gone and adapter override 404s until webcmd-cloud#50 ships. Accepted deliberately rather than splitting the PRs; keep the two merges close together.

Verification

  • npm run typecheck — clean
  • npm test — 5682 passed, 1 failed: src/doctor.test.ts:218 (profile alias rendering), pre-existing on main, unrelated to this change
  • npm run check:hosted-contract — passes; regenerated hosted-contract.json now lists 7 browser commands
  • npm run check:codex-plugin — passes

Cross-repo, per §7 of .github/hosted-impact-review.md: packed this branch, installed it into webcmd-cloud, ran cloud's full suite against it — 1189 passed, 0 failed.

Follow-ups from the same audit (not in this PR)

  • runCli() has no error handler, so adapter path, adapter source get|put, site fixture get, and session close <bad-id> dump raw Node stack traces
  • webcmd adapter path <site>/<cmd> fails for every command that is not already a local override — the documented private-fork workflow
  • Adapter error envelopes are always YAML, even under -f json
  • --help -f yaml is missing on site, skills, session, external

🤖 Generated with Claude Code

`webcmd browser fork` was an undocumented alias bound to the same handler as
`webcmd adapter override`. It leaked the alias immediately:
$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")
The error names a command the caller did not run, and nothing in docs/, skills/,
README, or CHANGELOG ever referenced `browser fork`. It also sat in the browser
namespace behind a `require-existing` session policy for what is a local file
copy.
Remove the local registration and the hosted catalog entry, so `adapter
override` is the single fork path in both modes.
`browser <retired>` now reports the replacement instead of a bare unknown
command, and unknown browser subcommands exit 2 (USAGE_ERROR) rather than 1:
$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
`fork` stays in BROWSER_SUBCOMMAND_NAMES: the preprocessor reads an unreserved
token after `browser` as a retired positional session id, so dropping it would
answer with "Browser sessions are root selectors" instead. The comment there now
says retired names are kept on purpose — the set was already a superset of the
declared subcommands.
Also corrects the usage string in the adapter-shadow hint, which showed
`adapter override <site> <command>` for a command that takes one
`<site>/<command>` positional.
BREAKING CHANGE: `webcmd browser fork` is removed. Use `webcmd adapter override
<site>/<command>`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actionsBot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

Removing `browser fork` in the previous commit took away hosted mode's only
way to fork an adapter: `adapter override` was never routed in hosted mode
(runner.ts matched only `source`, `path`, and help), and cloud exposes no
override route — `forkSystemAdapterCommand` had exactly one caller, the
`fork` browser action.
Route `adapter override <site>/<command>` in hosted mode to the new
`POST /v1/adapters/override`, so the command means the same thing in both
modes: fork an installed upstream command into a private copy you can edit,
refusing commands that are not installed upstream and commands already
forked.
Storage differs, so the output does. Local prints the file it wrote and its
`.base` copy; hosted prints the private package id and the source file, and
points at `adapter source get|put` as the editing path — the hosted analogue
of editing the file at `adapter path`.
Requires the matching webcmd-cloud change; without it the route 404s.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ankitranjan7ankitranjan7 changed the title fix(cli)!: remove the duplicate browser fork subcommandfix(cli)!: remove browser fork, add adapter override to hosted modeAug 19, 2026
@ankitranjan7
ankitranjan7 merged commit 3919f6f into mainAug 19, 2026
37 checks passed
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
@ankitranjan7
ankitranjan7 deleted the fix/remove-browser-fork branch September 1, 2026 12:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(cli)!: remove browser fork, add adapter override to hosted mode - #361

Merged
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork
Aug 19, 2026
Merged

fix(cli)!: remove browser fork, add adapter override to hosted mode#361
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork

Conversation

@ankitranjan7

@ankitranjan7ankitranjan7 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

What

webcmd browser fork was an undocumented alias bound to the same handler as webcmd adapter override, and it leaked the alias in its own error message:

$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")

The caller is told the usage of a command they did not run. browser fork appears nowhere in docs/, skills/, README.md, or CHANGELOG.md — it was only ever reachable by guessing. It also sat in the browser namespace behind a require-existing session policy for what is a local file copy.

This removes it from the local CLI and from the hosted browser catalog.

adapter override in hosted mode (second commit)

browser fork turned out to be hosted's only fork path. adapter override was never routed in hosted mode — src/hosted/runner.ts matched only source, path, and help — and cloud's forkSystemAdapterCommand had exactly one caller: the fork browser action. Removing browser fork alone would have taken hosted's fork capability away with no replacement.

So the second commit routes adapter override <site>/<command> in hosted mode to a new POST /v1/adapters/override. After both commits the command means the same thing in either mode: fork an installed upstream command into a private copy you can edit, refusing commands that are not installed upstream and commands already forked.

Storage differs, so the output does:

localhosted
writes~/.webcmd/clis/<site>/<cmd>.js + .base copytenant-private adapter package
printsyours: / base: pathspackage: id + source: file
edit withthe path from adapter pathadapter source get|put
not upstream"not provided by an installed plugin"HOSTED_ADAPTER_FORK_SOURCE_INVALID
already forked"an override already exists at …"HOSTED_ADAPTER_FORK_ALREADY_EXISTS

Behaviour after

$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
# exit 2
$ webcmd browser click x
error: unknown command 'click'
# exit 2 (was 1)

Unknown browser subcommands now exit 2 (USAGE_ERROR) instead of 1.

Why fork stays in BROWSER_SUBCOMMAND_NAMES

rejectPositionalBrowserSessionArgv reads any unreserved token after browser as the retired positional-session grammar. Dropping fork from that set would answer webcmd browser fork hackernews with:

error: Browser sessions are root selectors. Use: webcmd --session fork browser hackernews

— worse than what we started with. Retired names stay listed so commander can report them properly. The set was already a superset of the declared subcommands (~40 names, 7 real); the comment now says that is deliberate instead of asking the next person to "keep in sync".

Also

Corrects the usage string in the adapter-shadow hint, which advertised adapter override <site> <command> (two positionals) for a command that takes one <site>/<command>.

Hosted impact

Hosted impact: C — webcmd-cloud change required
Trigger: 3.4 browser command surface (src/browser/command-catalog.ts)
Cloud files: src/default-adapters/source.ts:268, src/live-gates/cli-gates.ts:14
Why: cloud asserts the exact list ['bind','close','fork','init','run','snapshot','tabs','verify']
and the count browserCommands: 8. Removing fork throws BrowserRunProtocolMismatchError.
Sequencing: land the cloud PR before `npm run bump:webcmd`.

The cloud side is agentrhq/webcmd-cloud#50, which serves POST /v1/adapters/override, drops the fork action, and re-pins the parity digests. Without it the hosted adapter override here 404s.

Order: merge this → bump PINNED_WEBCMD_SHA in cloud → merge webcmd-cloud#50.

Known window: between this release and the cloud deploy, hosted mode has no fork command — browser fork is gone and adapter override 404s until webcmd-cloud#50 ships. Accepted deliberately rather than splitting the PRs; keep the two merges close together.

Verification

  • npm run typecheck — clean
  • npm test — 5682 passed, 1 failed: src/doctor.test.ts:218 (profile alias rendering), pre-existing on main, unrelated to this change
  • npm run check:hosted-contract — passes; regenerated hosted-contract.json now lists 7 browser commands
  • npm run check:codex-plugin — passes

Cross-repo, per §7 of .github/hosted-impact-review.md: packed this branch, installed it into webcmd-cloud, ran cloud's full suite against it — 1189 passed, 0 failed.

Follow-ups from the same audit (not in this PR)

  • runCli() has no error handler, so adapter path, adapter source get|put, site fixture get, and session close <bad-id> dump raw Node stack traces
  • webcmd adapter path <site>/<cmd> fails for every command that is not already a local override — the documented private-fork workflow
  • Adapter error envelopes are always YAML, even under -f json
  • --help -f yaml is missing on site, skills, session, external

🤖 Generated with Claude Code

`webcmd browser fork` was an undocumented alias bound to the same handler as
`webcmd adapter override`. It leaked the alias immediately:
$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")
The error names a command the caller did not run, and nothing in docs/, skills/,
README, or CHANGELOG ever referenced `browser fork`. It also sat in the browser
namespace behind a `require-existing` session policy for what is a local file
copy.
Remove the local registration and the hosted catalog entry, so `adapter
override` is the single fork path in both modes.
`browser <retired>` now reports the replacement instead of a bare unknown
command, and unknown browser subcommands exit 2 (USAGE_ERROR) rather than 1:
$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
`fork` stays in BROWSER_SUBCOMMAND_NAMES: the preprocessor reads an unreserved
token after `browser` as a retired positional session id, so dropping it would
answer with "Browser sessions are root selectors" instead. The comment there now
says retired names are kept on purpose — the set was already a superset of the
declared subcommands.
Also corrects the usage string in the adapter-shadow hint, which showed
`adapter override <site> <command>` for a command that takes one
`<site>/<command>` positional.
BREAKING CHANGE: `webcmd browser fork` is removed. Use `webcmd adapter override
<site>/<command>`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actionsBot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

Removing `browser fork` in the previous commit took away hosted mode's only
way to fork an adapter: `adapter override` was never routed in hosted mode
(runner.ts matched only `source`, `path`, and help), and cloud exposes no
override route — `forkSystemAdapterCommand` had exactly one caller, the
`fork` browser action.
Route `adapter override <site>/<command>` in hosted mode to the new
`POST /v1/adapters/override`, so the command means the same thing in both
modes: fork an installed upstream command into a private copy you can edit,
refusing commands that are not installed upstream and commands already
forked.
Storage differs, so the output does. Local prints the file it wrote and its
`.base` copy; hosted prints the private package id and the source file, and
points at `adapter source get|put` as the editing path — the hosted analogue
of editing the file at `adapter path`.
Requires the matching webcmd-cloud change; without it the route 404s.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ankitranjan7ankitranjan7 changed the title fix(cli)!: remove the duplicate browser fork subcommandfix(cli)!: remove browser fork, add adapter override to hosted modeAug 19, 2026
@ankitranjan7
ankitranjan7 merged commit 3919f6f into mainAug 19, 2026
37 checks passed
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
@ankitranjan7
ankitranjan7 deleted the fix/remove-browser-fork branch September 1, 2026 12:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

fix(cli)!: remove browser fork, add adapter override to hosted mode - #361

Merged
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork
Aug 19, 2026
Merged

fix(cli)!: remove browser fork, add adapter override to hosted mode#361
ankitranjan7 merged 2 commits into
mainfrom
fix/remove-browser-fork

Conversation

@ankitranjan7

@ankitranjan7ankitranjan7 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

What

webcmd browser fork was an undocumented alias bound to the same handler as webcmd adapter override, and it leaked the alias in its own error message:

$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")

The caller is told the usage of a command they did not run. browser fork appears nowhere in docs/, skills/, README.md, or CHANGELOG.md — it was only ever reachable by guessing. It also sat in the browser namespace behind a require-existing session policy for what is a local file copy.

This removes it from the local CLI and from the hosted browser catalog.

adapter override in hosted mode (second commit)

browser fork turned out to be hosted's only fork path. adapter override was never routed in hosted mode — src/hosted/runner.ts matched only source, path, and help — and cloud's forkSystemAdapterCommand had exactly one caller: the fork browser action. Removing browser fork alone would have taken hosted's fork capability away with no replacement.

So the second commit routes adapter override <site>/<command> in hosted mode to a new POST /v1/adapters/override. After both commits the command means the same thing in either mode: fork an installed upstream command into a private copy you can edit, refusing commands that are not installed upstream and commands already forked.

Storage differs, so the output does:

localhosted
writes~/.webcmd/clis/<site>/<cmd>.js + .base copytenant-private adapter package
printsyours: / base: pathspackage: id + source: file
edit withthe path from adapter pathadapter source get|put
not upstream"not provided by an installed plugin"HOSTED_ADAPTER_FORK_SOURCE_INVALID
already forked"an override already exists at …"HOSTED_ADAPTER_FORK_ALREADY_EXISTS

Behaviour after

$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
# exit 2
$ webcmd browser click x
error: unknown command 'click'
# exit 2 (was 1)

Unknown browser subcommands now exit 2 (USAGE_ERROR) instead of 1.

Why fork stays in BROWSER_SUBCOMMAND_NAMES

rejectPositionalBrowserSessionArgv reads any unreserved token after browser as the retired positional-session grammar. Dropping fork from that set would answer webcmd browser fork hackernews with:

error: Browser sessions are root selectors. Use: webcmd --session fork browser hackernews

— worse than what we started with. Retired names stay listed so commander can report them properly. The set was already a superset of the declared subcommands (~40 names, 7 real); the comment now says that is deliberate instead of asking the next person to "keep in sync".

Also

Corrects the usage string in the adapter-shadow hint, which advertised adapter override <site> <command> (two positionals) for a command that takes one <site>/<command>.

Hosted impact

Hosted impact: C — webcmd-cloud change required
Trigger: 3.4 browser command surface (src/browser/command-catalog.ts)
Cloud files: src/default-adapters/source.ts:268, src/live-gates/cli-gates.ts:14
Why: cloud asserts the exact list ['bind','close','fork','init','run','snapshot','tabs','verify']
and the count browserCommands: 8. Removing fork throws BrowserRunProtocolMismatchError.
Sequencing: land the cloud PR before `npm run bump:webcmd`.

The cloud side is agentrhq/webcmd-cloud#50, which serves POST /v1/adapters/override, drops the fork action, and re-pins the parity digests. Without it the hosted adapter override here 404s.

Order: merge this → bump PINNED_WEBCMD_SHA in cloud → merge webcmd-cloud#50.

Known window: between this release and the cloud deploy, hosted mode has no fork command — browser fork is gone and adapter override 404s until webcmd-cloud#50 ships. Accepted deliberately rather than splitting the PRs; keep the two merges close together.

Verification

  • npm run typecheck — clean
  • npm test — 5682 passed, 1 failed: src/doctor.test.ts:218 (profile alias rendering), pre-existing on main, unrelated to this change
  • npm run check:hosted-contract — passes; regenerated hosted-contract.json now lists 7 browser commands
  • npm run check:codex-plugin — passes

Cross-repo, per §7 of .github/hosted-impact-review.md: packed this branch, installed it into webcmd-cloud, ran cloud's full suite against it — 1189 passed, 0 failed.

Follow-ups from the same audit (not in this PR)

  • runCli() has no error handler, so adapter path, adapter source get|put, site fixture get, and session close <bad-id> dump raw Node stack traces
  • webcmd adapter path <site>/<cmd> fails for every command that is not already a local override — the documented private-fork workflow
  • Adapter error envelopes are always YAML, even under -f json
  • --help -f yaml is missing on site, skills, session, external

🤖 Generated with Claude Code

`webcmd browser fork` was an undocumented alias bound to the same handler as
`webcmd adapter override`. It leaked the alias immediately:
$ webcmd browser fork hackernews
Error: Usage: webcmd adapter override <site>/<command> (got "hackernews")
The error names a command the caller did not run, and nothing in docs/, skills/,
README, or CHANGELOG ever referenced `browser fork`. It also sat in the browser
namespace behind a `require-existing` session policy for what is a local file
copy.
Remove the local registration and the hosted catalog entry, so `adapter
override` is the single fork path in both modes.
`browser <retired>` now reports the replacement instead of a bare unknown
command, and unknown browser subcommands exit 2 (USAGE_ERROR) rather than 1:
$ webcmd browser fork hackernews
error: 'webcmd browser fork' was removed. Use: webcmd adapter override <site>/<command>
`fork` stays in BROWSER_SUBCOMMAND_NAMES: the preprocessor reads an unreserved
token after `browser` as a retired positional session id, so dropping it would
answer with "Browser sessions are root selectors" instead. The comment there now
says retired names are kept on purpose — the set was already a superset of the
declared subcommands.
Also corrects the usage string in the adapter-shadow hint, which showed
`adapter override <site> <command>` for a command that takes one
`<site>/<command>` positional.
BREAKING CHANGE: `webcmd browser fork` is removed. Use `webcmd adapter override
<site>/<command>`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actionsBot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

Removing `browser fork` in the previous commit took away hosted mode's only
way to fork an adapter: `adapter override` was never routed in hosted mode
(runner.ts matched only `source`, `path`, and help), and cloud exposes no
override route — `forkSystemAdapterCommand` had exactly one caller, the
`fork` browser action.
Route `adapter override <site>/<command>` in hosted mode to the new
`POST /v1/adapters/override`, so the command means the same thing in both
modes: fork an installed upstream command into a private copy you can edit,
refusing commands that are not installed upstream and commands already
forked.
Storage differs, so the output does. Local prints the file it wrote and its
`.base` copy; hosted prints the private package id and the source file, and
points at `adapter source get|put` as the editing path — the hosted analogue
of editing the file at `adapter path`.
Requires the matching webcmd-cloud change; without it the route 404s.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ankitranjan7ankitranjan7 changed the title fix(cli)!: remove the duplicate browser fork subcommandfix(cli)!: remove browser fork, add adapter override to hosted modeAug 19, 2026
@ankitranjan7
ankitranjan7 merged commit 3919f6f into mainAug 19, 2026
37 checks passed
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 20, 2026
…q#361agentrhq#361 landed on main after this branch was opened and already removed
`browser fork` for good (retirement redirect to `adapter override`).
Rebasing reintroduced this PR's now-stale fork re-registration, which
duplicated that removal and broke the retirement tests. Drop it and
update the grouping/tests/docs to match the current adapter authoring
surface (init, verify).
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
@ankitranjan7
ankitranjan7 deleted the fix/remove-browser-fork branch September 1, 2026 12:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@ankitranjan7