mirror of
https://github.com/cypress-io/cypress.git
synced 2026-05-25 01:49:06 -05:00
4931cf06ff
* chore: bootstrap AI agent context files (AGENTS.md + CLAUDE.md)
Adds a three-tier set of AI context files across the monorepo:
- Root AGENTS.md / CLAUDE.md — project overview, workspaces, common
commands, architecture map, code conventions, and CI/CD summary
- Workspace-level pairs for cli/, packages/, npm/, tooling/,
system-tests/, and scripts/
- Package-level pairs for all 33 packages/, 15 npm/, 3 tooling/
packages, and the cli workspace (117 files total)
CLAUDE.md files are thin wrappers (@AGENTS.md import + workflow rules)
so Claude Code picks them up walking upward from cwd. AGENTS.md files
carry the substantive content and are also read natively by Codex CLI
and Cursor.
Command conventions applied throughout:
- No watch / file-watcher commands (agents run once and read results)
- No bare full-suite test runs for large packages; always target a
specific file (<path-to-spec>) or glob ("<glob-pattern>")
- No cypress:open (interactive mode); use cypress:run with --spec
- Test runner syntax varies by package: vitest (test --),
mocha (test-unit/test-integration --), jest (--testPathPattern),
Cypress CT (cypress:run:ct -- --spec)
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* gitignore
* clarify AI internal docs and contribution guidelines
* update TOC
* tweak nvm wording
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Extension
This is the WebExtension responsible for automating the browser
Developing
Watching
Kicks off the gulp watcher that rebuilds the app/lib directories on change.
yarn workspace @packages/extension watch
Building
@packages/extension has a few different build processes occurring that are all driven by the gulpfile.
app- The web extension piece of the code, has two separate bundles:v2: Version 2 of the web extension which uses webpack to bundle theapp/v2directory and output it asbackground.jsv3: Version 3 of the web extension, which doesn't have any external dependencies so we are able to compile down to `ESM to run in the browser natively.
lib- the@packages/extensionmainentry that has utility methods on how to find/load the extension. This is transpiled to CommonJS as it is consumed in the Node context.
yarn workspace @packages/extension build
Testing
yarn workspace @packages/extension test
yarn workspace @packages/extension test-watch
yarn workspace @packages/extension test-debug
Debugging
In Chrome
- Open Chrome
- Go into Extensions (
chrome://extensions) - Check Developer Mode (top right of screen)
- Click Load unpacked extension... (top left of screen)
- Choose packages/extension/dist directory (v2)
- Click background page to debug
background.js(inspect viewsbackground page) - Click Reload (⌘R) to pull in changes to
manifest.json
In Firefox
- Launch Firefox via
cypress open. - Once Firefox is open, open an new tab and navigate to
about:debugging. - Click the
This Firefoxnavigation item on the left hand navigation pane and locate theCypressextension underTemporary Extensions. - Click
inspect. A console window should now appear in a separate window. - Close the
about:debuggingtab. - In the newly spawned console window, you should be able to see
background.jsin theDebuggertab. - Set breakpoints as needed to inspect what code you are trying to debug. Happy debugging!