ad hoc playwright code exec API

[rgarcia]

• add node, playwright, and tsx to the images
• add an endpoint that takes in code and executes it within a shim that provides a page Playwright object

---

Note

Adds /playwright/execute API to run TypeScript/Playwright code against the running Chromium via a tsx-based executor, and installs Node.js 22 + Playwright tooling in images.

• API/Backend:
  • Introduces POST /playwright/execute to run arbitrary TS/Playwright code with timeout; serializes runs via ApiService.playwrightMu.
  • Implements handler ExecutePlaywrightCode executing tsx /usr/local/lib/playwright-executor.ts <tmp.ts> and returning JSON {success,result|error,stdout,stderr}.
  • Updates generated OAPI types/clients/routers for new request/response models (ExecutePlaywrightRequest/Result).
• Runtime:
  • Adds server/runtime/playwright-executor.ts connecting to ws://127.0.0.1:9222 via playwright-core, exposing page/context/browser, returning JSON.
• Images:
  • Installs Node.js 22.x, recreates npm/npx/corepack links; globally installs typescript, playwright-core, tsx in both chromium-headful and chromium-headless images.
  • Copies playwright-executor.ts into /usr/local/lib/.
• Tests:
  • Adds E2E test TestPlaywrightExecuteAPI validating navigation to example.com and returned title.
• Spec:
  • Extends openapi.yaml and embedded swagger; regenerates server/lib/oapi.

^{Written by Cursor Bugbot for commit aaccaeb. This will update automatically on new commits. Configure here.}

[mesa-dot-dev]

Mesa Description

• add node, playwright, and tsx to the images
• add an endpoint that takes in code and executes it within a shim that provides a page Playwright object

---

Note

Adds POST /playwright/execute to run user TypeScript/Playwright code via tsx against Chromium, updates images with Node.js 22 + Playwright, and includes an e2e test.

• API:
  • New Endpoint: POST /playwright/execute to run Playwright/TypeScript code with timeout; returns {success,result,error,stdout,stderr} (server/cmd/api/api/playwright.go).
  • OpenAPI + Generated Client/Server: Spec and codegen updated to expose request/response types and routing (server/openapi.yaml, server/lib/oapi/oapi.go).
• Runtime:
  • Executor: Add server/runtime/playwright-executor.ts invoked via tsx, connecting to ws://127.0.0.1:9222 and evaluating provided code.
• Containers:
  • Install Node.js 22, typescript, playwright-core, and tsx; copy executor into image (images/chromium-headful/Dockerfile, images/chromium-headless/image/Dockerfile).
• Tests:
  • Add e2e test executing a simple Playwright script and asserting result (server/e2e/e2e_chromium_test.go).

^{Written by Cursor Bugbot for commit 8251b07. This will update automatically on new commits. Configure here.}

^{Description generated by Mesa. Update settings}

[mesa-dot-dev]

Performed full review of 174e365...e809a85

Tip

Help

Configure your agents

Mesa Docs

Slash Commands:

• /review - Request a full code review
• /review latest - Review only changes since the last review
• /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
• /help - Get help with Mesa commands and configuration options

^{7 files reviewed | 0 comments | Edit Agent Settings}

[hiroTamada]

Is the point of this making the playwright code and chrome physically close to each other to avoid network connectivity issue and latency?

[hiroTamada]

Just curious, does it make the image bigger?

[rgarcia]

yes by 200-300 MB

[hiroTamada]

I actually wonder if this endpoint is thread safe or not. Would concurrent script executions break chrome?

[rgarcia]

Is the point of this making the playwright code and chrome physically close to each other to avoid network connectivity issue and latency?

yes, exactly!