Codex efc35f7e2d [packages/cli]revert: remove --auto-connect (rollback of #545) ...

The --auto-connect feature's probing logic targets Chrome's legacy
/json/version endpoint. Chrome's new native "Allow remote debugging"
toggle (chrome://inspect) uses a different protocol, so --auto-connect
cannot attach to a user's daily Chrome profile — the only way to make
it work is to launch a dedicated Chrome with --remote-debugging-port
and an isolated user-data-dir, which is equivalent to `browser start`.

Rolling back so 1.5.0 ships without a misleading feature. Will revisit
once the native-toggle protocol is supported.

- Revert source changes from 9401bbee (feat: browser start --auto-connect)
- Remove --auto-connect from CLI help text (main.rs)
- Remove --auto-connect from 1.5.0 CHANGELOG entry
- Remove --auto-connect docs: docs/guides/browser.mdx, docs/api-reference/cli.mdx
- Remove --auto-connect examples from skills SKILL.md + command-reference.md

Also incorporates earlier CHANGELOG cleanups:
- Drop "ACT-" JIRA prefixes from release notes
- Drop mention of "browser send removed" (was never in a released version)

2026-04-18 00:30:25 +08:00

..

cli.mdx

[packages/cli]revert: remove --auto-connect (rollback of #545)

2026-04-18 00:30:25 +08:00

evaluate-api.mdx

[root]docs: restore deleted evaluate-api.mdx

2026-04-03 08:35:02 +08:00

mcp-tools.mdx

docs: make website CLI-first and demote MCP/SDK paths (#119)

2026-02-12 10:43:34 +08:00