qaa-agent 1.6.3 → 1.7.1

package/commands/qa-fix.md

@@ -0,0 +1,395 @@
+# QA Fix & Validate
+
+Validate, diagnose, and fix test files — all in one command. Runs 4-layer static validation (syntax, structure, dependencies, logic), classifies failures, and auto-fixes TEST CODE ERRORS. Uses Playwright MCP to reproduce E2E failures and verify locators against the live app when available. Never touches application code.
+
+## Usage
+
+```
+/qa-fix [<test-files-or-directory>] [options]
+```
+
+### Options
+
+- `<test-files-or-directory>` — one or more test file paths or a directory (auto-detects if omitted)
+- `--check` — **final check mode**: full quality verification against company preferences, codebase conventions, and execution
+- `--validate-only` — run 4-layer static validation only, no test execution or classification
+- `--classify` — run tests and classify failures, but do NOT auto-fix
+- `--run --app-url <url>` — also execute E2E tests against live app after static validation
+- `--app-url <url>` — URL of running application (auto-detects if not provided)
+- `[error output]` — paste test runner output directly (skips running tests, classifies the pasted output)
+
+### Mode Detection
+
+```
+if --check:
+  MODE = "check"           → full quality check + execution + QA_CHECK_REPORT.md
+elif --validate-only:
+  MODE = "validate"        → 4-layer static validation + VALIDATION_REPORT.md
+elif --classify:
+  MODE = "classify"        → run tests + classify failures (no auto-fix)
+else:
+  MODE = "fix"             → run tests + classify + auto-fix TEST CODE ERRORS (default)
+```
+
+## What It Produces
+
+| Mode | Artifacts |
+|------|-----------|
+| check | QA_CHECK_REPORT.md (full quality verification with pass/fail per test file) |
+| check --ticket | QA_CHECK_REPORT.md + UAT_VERIFICATION.md (step-by-step screenshots vs ticket acceptance criteria) |
+| validate | VALIDATION_REPORT.md (syntax, structure, dependencies, logic per file) |
+| classify | FAILURE_CLASSIFICATION_REPORT.md (per-failure evidence, no fixes) |
+| fix | FAILURE_CLASSIFICATION_REPORT.md + auto-fixed test files |
+
+## Instructions
+
+### Step 1: Detect Mode and Test Directory
+
+Parse `$ARGUMENTS` for mode flags and test directory path.
+
+If no test directory provided, auto-detect:
+- Check for `tests/`, `cypress/`, `__tests__/`, `e2e/`, `spec/` directories
+- Check test config files for `testDir` setting
+
+Print banner:
+```
+=== QA Fix & Validate ===
+Mode: {validate | classify | fix}
+Test Directory: {path}
+App URL: {url or "auto-detect"}
+==========================
+```
+
+---
+
+### CHECK MODE (`--check`) — Final Quality Verification
+
+Full quality check for specific test files. Reads ALL context sources, verifies every aspect of the tests, runs them, and produces a pass/fail report. Use this as a final gate before delivering tests.
+
+**Accepts specific files:**
+```
+/qa-fix --check tests/e2e/login.e2e.spec.ts tests/e2e/checkout.e2e.spec.ts
+/qa-fix --check tests/unit/auth.unit.spec.ts
+/qa-fix --check tests/e2e/ --app-url http://localhost:3000
+```
+
+**Step 1: Read ALL context sources**
+
+Read every available context source — this is not optional, all must be read:
+
+1. **CLAUDE.md** — QA standards, POM rules, locator tiers, assertion rules, naming conventions, quality gates
+2. **~/.claude/qaa/MY_PREFERENCES.md** — company/user preferences that OVERRIDE CLAUDE.md rules
+3. **Codebase map** (`.qa-output/codebase/`):
+   - `CODE_PATTERNS.md` — naming conventions, import style, file organization (are tests matching the project's style?)
+   - `API_CONTRACTS.md` — real API shapes (are API test payloads correct?)
+   - `TEST_SURFACE.md` — function signatures (are test targets real?)
+   - `TESTABILITY.md` — mock boundaries (are mocks set up correctly?)
+4. **Locator Registry** (`.qa-output/locators/`) — real locators from the app (are POM locators accurate?)
+5. **Existing test patterns** — read 2-3 existing test files in the same repo to understand current conventions (describe block style, import patterns, assertion patterns, fixture usage)
+
+If codebase map is missing, STOP and tell the user to run `/qa-map` first.
+
+**Step 2: Verify each test file across 7 dimensions**
+
+For EACH selected test file, check:
+
+| # | Dimension | What to check | Source |
+|---|-----------|---------------|--------|
+| 1 | **Naming** | File name, test IDs, describe/it names follow conventions | CLAUDE.md + CODE_PATTERNS.md + MY_PREFERENCES.md |
+| 2 | **Structure** | Correct directory, imports resolve, follows repo patterns | CODE_PATTERNS.md + existing tests in repo |
+| 3 | **Locators** | POM locators match registry, Tier 1 preferred, no stale selectors | LOCATOR_REGISTRY.md |
+| 4 | **Assertions** | Concrete values (no toBeTruthy alone), match API contracts | CLAUDE.md + API_CONTRACTS.md |
+| 5 | **POM compliance** | No assertions in POMs, locators as properties, extends BasePage | CLAUDE.md |
+| 6 | **Code quality** | No redundant code, no dead code, no hardcoded credentials, no copy-paste | Code review |
+| 7 | **Company conventions** | Matches all rules in MY_PREFERENCES.md | MY_PREFERENCES.md |
+
+**Step 3: Run the tests**
+
+Execute the selected test files:
+
+```bash
+# Detect test runner from project config
+npx playwright test {files} --reporter=json 2>&1    # if Playwright
+npx cypress run --spec {files} 2>&1                  # if Cypress
+npx jest {files} --json 2>&1                         # if Jest
+npx vitest run {files} --reporter=json 2>&1          # if Vitest
+```
+
+If E2E tests and app URL available, also verify with Playwright MCP:
+- Navigate to each page referenced in the tests
+- `browser_snapshot()` to verify elements exist in DOM
+- Cross-reference locators against real page
+
+**Step 4: Fix issues found**
+
+For each issue found:
+- **AUTO-FIX** (HIGH confidence): naming, imports, locator mismatches, missing await, Tier 4→Tier 1 upgrade when registry has the value
+- **FLAG for review** (MEDIUM/LOW): logic changes, assertion value changes, structural refactors
+- Re-run tests after fixes (max 5 loops)
+
+**Step 5: Produce QA_CHECK_REPORT.md**
+
+```markdown
+# QA Check Report
+
+## Summary
+
+| Metric | Value |
+|--------|-------|
+| Files checked | {N} |
+| Dimensions checked | 7 |
+| Issues found | {N} |
+| Auto-fixed | {N} |
+| Flagged for review | {N} |
+| Tests passed | {N}/{total} |
+| Overall | PASS / PASS WITH WARNINGS / FAIL |
+
+## Per-File Results
+
+### {file_path}
+
+| Dimension | Status | Details |
+|-----------|--------|---------|
+| Naming | PASS/FAIL | {specific details} |
+| Structure | PASS/FAIL | {specific details} |
+| Locators | PASS/FAIL | {specific details} |
+| Assertions | PASS/FAIL | {specific details} |
+| POM compliance | PASS/FAIL | {specific details} |
+| Code quality | PASS/FAIL | {specific details} |
+| Company conventions | PASS/FAIL | {specific details} |
+
+**Test execution:** PASS / FAIL ({error if failed})
+**Fixes applied:** {list of auto-fixes}
+**Flagged for review:** {list of items needing human review}
+
+[... repeat per file ...]
+
+## Flagged Items (Needs Human Review)
+
+| File | Dimension | Issue | Suggested Fix |
+|------|-----------|-------|---------------|
+| ... | ... | ... | ... |
+```
+
+Write to `.qa-output/QA_CHECK_REPORT.md`.
+
+Present results to user with clear PASS/FAIL per file and overall status.
+
+**Step 6 (optional): Ticket Verification (`--ticket <source>`)**
+
+If `--ticket` flag is provided, perform UAT verification — walk through the test flow step-by-step in the browser, take screenshots at each step, and compare against the ticket's acceptance criteria.
+
+**Usage:**
+```
+/qa-fix --check --ticket #123 tests/e2e/login.e2e.spec.ts --app-url http://localhost:3000
+/qa-fix --check --ticket https://company.atlassian.net/browse/PROJ-456 tests/e2e/checkout.e2e.spec.ts
+/qa-fix --check --ticket "User logs in, sees dashboard with welcome message, clicks profile" tests/e2e/login.e2e.spec.ts
+```
+
+**Requires:** `--app-url` or auto-detected running app. Cannot do ticket verification without a live app.
+
+**Step 6a: Fetch and parse the ticket**
+
+Same ticket parsing as `/qa-create-test` from-ticket mode:
+- GitHub Issue: `gh issue view` → extract title, body, ACs
+- Jira/Linear URL: `WebFetch` → extract content
+- Plain text: use directly as acceptance criteria
+- File path: read file content
+
+Extract:
+- Acceptance criteria (AC-1, AC-2, ...)
+- Expected user flow (step-by-step)
+- Expected outcomes per step
+
+**Step 6b: Walk through the flow with Playwright MCP**
+
+For each E2E test file being checked, replay the user journey manually in the browser step-by-step:
+
+```
+For each step in the ticket's user flow:
+
+  1. Execute the action described in the step:
+     - Navigate: mcp__playwright__browser_navigate({ url: "{page}" })
+     - Fill form: mcp__playwright__browser_fill_form({ ... })
+     - Click: mcp__playwright__browser_click({ element: "..." })
+     - Wait: mcp__playwright__browser_wait_for({ text: "..." })
+
+  2. Take screenshot AFTER the action:
+     mcp__playwright__browser_take_screenshot()
+     → Save to .qa-output/uat-screenshots/{test-name}-step-{N}.png
+
+  3. Take accessibility snapshot to read page state:
+     mcp__playwright__browser_snapshot()
+
+  4. Record what the page shows:
+     - URL after action
+     - Visible text/headings
+     - Form state
+     - Error messages (if any)
+     - Elements visible/hidden
+```
+
+**Step 6c: Compare actual vs ticket**
+
+For each acceptance criterion from the ticket:
+
+| AC | Expected (from ticket) | Actual (from browser) | Screenshot | Verdict |
+|----|----------------------|---------------------|------------|---------|
+| AC-1 | User sees login form | Login form visible with email/password fields | step-1.png | MATCH |
+| AC-2 | After login, redirect to dashboard | Redirected to /dashboard, "Welcome" visible | step-3.png | MATCH |
+| AC-3 | Error message for wrong password | "Invalid credentials" alert shown | step-5.png | MATCH |
+| AC-4 | Remember me keeps session | Session persists after browser close | step-7.png | MISMATCH — session expired |
+
+Verdicts:
+- **MATCH** — actual behavior matches what the ticket describes
+- **MISMATCH** — actual behavior differs from ticket (could be app bug OR test not covering this AC)
+- **NOT TESTED** — ticket has an AC but no test step covers it
+- **EXTRA** — test covers something not in the ticket (informational, not a failure)
+
+**Step 6d: Produce UAT_VERIFICATION.md**
+
+```markdown
+# UAT Verification Report
+
+## Ticket Info
+
+| Field | Value |
+|-------|-------|
+| Source | {ticket URL or text} |
+| Title | {ticket title} |
+| ACs extracted | {count} |
+| Test files verified | {count} |
+
+## Step-by-Step Walkthrough
+
+### Step 1: {action description}
+- **Action:** Navigate to /login
+- **Screenshot:** [step-1.png](.qa-output/uat-screenshots/{test}-step-1.png)
+- **Page state:** Login form visible, email and password fields empty, "Log in" button enabled
+- **Matches AC:** AC-1 ✓
+
+### Step 2: {action description}
+- **Action:** Fill email "test@example.com", password "SecureP@ss123!"
+- **Screenshot:** [step-2.png]
+- **Page state:** Fields filled, button still enabled
+- **Matches AC:** (intermediate step, no AC)
+
+[... repeat per step ...]
+
+## AC Coverage Matrix
+
+| AC | Description | Tested | Verdict | Evidence |
+|----|-------------|--------|---------|----------|
+| AC-1 | Login form visible | Yes | MATCH | step-1.png |
+| AC-2 | Redirect to dashboard | Yes | MATCH | step-3.png |
+| AC-3 | Error on wrong password | Yes | MATCH | step-5.png |
+| AC-4 | Remember me session | No | NOT TESTED | — |
+
+## Summary
+
+| Metric | Value |
+|--------|-------|
+| ACs from ticket | {N} |
+| ACs matched | {N} |
+| ACs mismatched | {N} |
+| ACs not tested | {N} |
+| Screenshots captured | {N} |
+| Overall | PASS / PARTIAL / FAIL |
+```
+
+Write to `.qa-output/UAT_VERIFICATION.md`.
+
+If any AC is MISMATCH or NOT TESTED, present to user with recommendation:
+- MISMATCH → "AC-4 says X but the app does Y — either the app has a bug or the test needs updating"
+- NOT TESTED → "AC-4 is not covered by any test step — consider adding a test case"
+
+---
+
+### VALIDATE MODE (`--validate-only`)
+
+1. Read `CLAUDE.md` — quality gates, locator tiers, assertion rules.
+2. Execute static validation workflow:
+
+Follow the workflow defined in `@workflows/qa-validate.md` end-to-end.
+Preserve all workflow gates (fix loops, layer checks).
+
+The validator runs 4 layers per file:
+1. **Syntax** — code compiles without errors
+2. **Structure** — naming, folders, POM compliance
+3. **Dependencies** — all imports resolve
+4. **Logic** — concrete assertions, Tier 1-2 locators, no assertions in POMs
+
+**Optional Layer 5 (if Playwright MCP connected + app URL available):**
+- Navigate to each page referenced in E2E tests via `mcp__playwright__browser_navigate`
+- Take accessibility snapshot via `mcp__playwright__browser_snapshot`
+- Cross-reference test locators against real DOM elements
+- Flag locators that don't match, auto-fix mismatches
+
+Max 3 fix loop iterations. Produces VALIDATION_REPORT.md.
+
+If `--run` flag is also present and E2E test files exist, invoke E2E runner after static validation:
+
+Task(
+  prompt="
+    <objective>Run E2E tests against live application, capture real locators, fix mismatches, loop until pass</objective>
+    <execution_context>@agents/qaa-e2e-runner.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    - {E2E test files from validated directory}
+    - {POM files from validated directory}
+    </files_to_read>
+    <parameters>
+    app_url: {from --app-url flag or auto-detect}
+    output_dir: .qa-output
+    </parameters>
+  "
+)
+
+---
+
+### CLASSIFY MODE (`--classify`)
+
+Same as fix mode below but skip Step 4 (auto-fix). Only classify and report.
+
+---
+
+### FIX MODE (default)
+
+1. Read `CLAUDE.md` — classification rules, locator tiers, assertion quality.
+2. Invoke bug-detective agent:
+
+Task(
+  prompt="
+    <objective>Run tests, classify failures, and auto-fix TEST CODE ERRORS. Use Playwright MCP to reproduce E2E failures in the browser when available — navigate to failing pages, snapshot DOM, reproduce actions, and screenshot failure state for evidence.</objective>
+    <execution_context>@agents/qaa-bug-detective.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    </files_to_read>
+    <parameters>
+    user_input: $ARGUMENTS
+    app_url: {auto-detect from test config baseURL, or ask user}
+    </parameters>
+  "
+)
+
+**Classification categories:**
+- **APPLICATION BUG** — error in production code → Report only, NEVER auto-fix
+- **TEST CODE ERROR** — error in test code → Auto-fix if HIGH confidence
+- **ENVIRONMENT ISSUE** — missing env, connection refused → Report with resolution steps
+- **INCONCLUSIVE** — ambiguous → Report what's known, ask for more info
+
+**Auto-fix rules:**
+- Only TEST CODE ERROR at HIGH confidence
+- Allowed fixes: import paths, selectors, assertion values, config, missing await, fixture paths
+- Every fix verified by re-running the specific test
+- Never modify application code (src/, app/, lib/)
+
+**Browser reproduction (when Playwright MCP connected):**
+- Navigate to failing page → snapshot DOM → reproduce action → screenshot
+- Element not in DOM → TEST CODE ERROR (HIGH confidence)
+- Element exists, wrong behavior → APPLICATION BUG
+- Page doesn't load → ENVIRONMENT ISSUE
+
+3. Present results. APPLICATION BUGs are reported for developer action, not auto-fixed.
+
+$ARGUMENTS

package/commands/qa-map.md

@@ -0,0 +1,137 @@
+# QA Codebase Map & Analysis
+
+Deep-scan a codebase for QA-relevant information, produce a complete analysis, and generate test inventory. Runs codebase mapping (4 parallel agents) followed by full repository analysis. One command to fully understand a codebase before writing tests.
+
+## Usage
+
+```
+/qa-map [options]
+```
+
+### Options
+
+- No arguments — runs full map + analysis on current directory
+- `--focus <area>` — run a single map area only, skip analysis (testability, risk, patterns, existing-tests)
+- `--dev-repo <path>` — explicit path to developer repository
+- `--qa-repo <path>` — path to existing QA repository (produces gap analysis instead of blueprint)
+- `--skip-map` — skip codebase mapping, only run analysis (lighter, faster)
+
+## What It Produces
+
+### Stage 1: Codebase Map (4 parallel agents)
+
+| Focus Area | Documents Produced |
+|------------|-------------------|
+| **testability** | TESTABILITY.md + TEST_SURFACE.md — what's testable, entry points, mocking needs |
+| **risk** | RISK_MAP.md + CRITICAL_PATHS.md — business-critical paths, error handling gaps |
+| **patterns** | CODE_PATTERNS.md + API_CONTRACTS.md — naming conventions, API shapes, auth patterns |
+| **existing-tests** | TEST_ASSESSMENT.md + COVERAGE_GAPS.md — existing test quality, what's missing |
+
+All documents written to `.qa-output/codebase/`.
+
+### Stage 2: Repository Analysis
+
+| Document | Description |
+|----------|-------------|
+| SCAN_MANIFEST.md | File tree, framework detection, testable surfaces |
+| QA_ANALYSIS.md | Architecture overview, risk assessment, top 10 unit targets, testing pyramid |
+| TEST_INVENTORY.md | Every test case with ID, target, inputs, expected outcome, priority |
+| QA_REPO_BLUEPRINT.md | If no QA repo — full repo structure, configs, CI/CD strategy |
+| GAP_ANALYSIS.md | If QA repo provided — coverage map, missing tests, broken tests, quality assessment |
+
+## Instructions
+
+1. Read `CLAUDE.md` — QA standards.
+
+2. Create output directories:
+```bash
+mkdir -p .qa-output/codebase
+```
+
+3. **Stage 1: Codebase Mapping**
+
+If `--skip-map` was NOT passed and `--focus` was NOT specified, spawn 4 agents in parallel (one per focus area):
+
+```
+Agent(
+  prompt="Analyze this codebase for QA purposes. Focus area: testability. Write TESTABILITY.md and TEST_SURFACE.md to .qa-output/codebase/. Follow your agent definition process.",
+  subagent_type="general-purpose",
+  execution_context="@agents/qaa-codebase-mapper.md"
+)
+
+Agent(
+  prompt="Analyze this codebase for QA purposes. Focus area: risk. Write RISK_MAP.md and CRITICAL_PATHS.md to .qa-output/codebase/. Follow your agent definition process.",
+  subagent_type="general-purpose",
+  execution_context="@agents/qaa-codebase-mapper.md"
+)
+
+Agent(
+  prompt="Analyze this codebase for QA purposes. Focus area: patterns. Write CODE_PATTERNS.md and API_CONTRACTS.md to .qa-output/codebase/. Follow your agent definition process.",
+  subagent_type="general-purpose",
+  execution_context="@agents/qaa-codebase-mapper.md"
+)
+
+Agent(
+  prompt="Analyze this codebase for QA purposes. Focus area: existing-tests. Write TEST_ASSESSMENT.md and COVERAGE_GAPS.md to .qa-output/codebase/. Follow your agent definition process.",
+  subagent_type="general-purpose",
+  execution_context="@agents/qaa-codebase-mapper.md"
+)
+```
+
+If `--focus <area>` was provided, spawn only that one agent and STOP after it completes (skip Stage 2).
+
+If `--skip-map` was passed, skip Stage 1 entirely and go to Stage 2.
+
+4. When all map agents complete, print summary of documents produced.
+
+5. **Stage 2: Repository Analysis**
+
+Initialize pipeline context:
+```bash
+node bin/qaa-tools.cjs init qa-start 2>/dev/null || true
+```
+
+Invoke scanner agent:
+
+Task(
+  prompt="
+    <objective>Scan repository and produce SCAN_MANIFEST.md</objective>
+    <execution_context>@agents/qaa-scanner.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    </files_to_read>
+    <parameters>
+    user_input: $ARGUMENTS
+    </parameters>
+  "
+)
+
+Invoke analyzer agent:
+
+Task(
+  prompt="
+    <objective>Analyze repository and produce QA_ANALYSIS.md, TEST_INVENTORY.md, and blueprint or gap analysis. Use codebase map documents from .qa-output/codebase/ if they exist for deeper, more accurate analysis.</objective>
+    <execution_context>@agents/qaa-analyzer.md</execution_context>
+    <files_to_read>
+    - CLAUDE.md
+    - .qa-output/SCAN_MANIFEST.md
+    - .qa-output/codebase/TESTABILITY.md (if exists)
+    - .qa-output/codebase/RISK_MAP.md (if exists)
+    - .qa-output/codebase/CODE_PATTERNS.md (if exists)
+    - .qa-output/codebase/TEST_ASSESSMENT.md (if exists)
+    - .qa-output/codebase/TEST_SURFACE.md (if exists)
+    - .qa-output/codebase/CRITICAL_PATHS.md (if exists)
+    - .qa-output/codebase/API_CONTRACTS.md (if exists)
+    - .qa-output/codebase/COVERAGE_GAPS.md (if exists)
+    </files_to_read>
+    <parameters>
+    user_input: $ARGUMENTS
+    </parameters>
+  "
+)
+
+6. Print final summary: all documents produced across both stages.
+   No git operations. No test generation.
+   Suggest `/qa-create-test` to generate tests from the analysis.
+
+$ARGUMENTS

package/package.json

@@ -1,41 +1,40 @@
-{
-  "name": "qaa-agent",
-  "version": "1.6.3",
-  "description": "QA Automation Agent for Claude Code — multi-agent pipeline that analyzes repos, generates tests, validates, and creates PRs",
-  "bin": {
-    "qaa-agent": "./bin/install.cjs"
-  },
-  "keywords": [
-    "qa",
-    "automation",
-    "testing",
-    "claude-code",
-    "playwright",
-    "jest",
-    "pytest",
-    "ai-agent"
-  ],
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/Backhaus7997/qaa-agent.git"
-  },
-  "author": "Backhaus7997",
-  "license": "MIT",
-  "dependencies": {
-    "@playwright/mcp": "latest"
-  },
-  "files": [
-    "bin/",
-    "agents/",
-    "workflows/",
-    "templates/",
-    "docs/",
-    ".claude/commands/",
-    ".claude/skills/",
-    ".claude/settings.json",
-    ".mcp.json",
-    "CLAUDE.md",
-    "CHANGELOG.md",
-    "README.md"
-  ]
-}
+{
+  "name": "qaa-agent",
+  "version": "1.7.1",
+  "description": "QA Automation Agent for Claude Code — multi-agent pipeline that analyzes repos, generates tests, validates, and creates PRs",
+  "bin": {
+    "qaa-agent": "./bin/install.cjs"
+  },
+  "keywords": [
+    "qa",
+    "automation",
+    "testing",
+    "claude-code",
+    "playwright",
+    "jest",
+    "pytest",
+    "ai-agent"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/capmation/qaa-testing.git"
+  },
+  "author": "Backhaus7997",
+  "license": "MIT",
+  "dependencies": {
+    "@playwright/mcp": "latest"
+  },
+  "files": [
+    "bin/",
+    "agents/",
+    "workflows/",
+    "templates/",
+    "docs/",
+    "commands/",
+    "skills/",
+    "settings.json",
+    ".mcp.json",
+    "CLAUDE.md",
+    "CHANGELOG.md"
+  ]
+}

package/{.claude/settings.json → settings.json}

@@ -1,20 +1,19 @@
-{
-  "permissions": {
-    "allow": [
-      "Bash(*)",
-      "Read",
-      "Write",
-      "Edit",
-      "Glob",
-      "Grep",
-      "Agent",
-      "WebFetch",
-      "WebSearch",
-      "NotebookEdit",
-      "mcp__playwright__*"
-    ]
-  },
-  "env": {
-    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
-  }
-}
+{
+  "permissions": {
+    "allow": [
+      "Bash(*)",
+      "Read",
+      "Write",
+      "Edit",
+      "Glob",
+      "Grep",
+      "Agent",
+      "WebFetch",
+      "WebSearch",
+      "NotebookEdit"
+    ]
+  },
+  "env": {
+    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
+  }
+}