Files
remorses__playwriter/.changeset
Tommy D. Rossi e9339a3ecc fix: send auth token on remote status check routes
When using `--token` with a remote `--host`, the CLI and executor
status check fetches (`/extensions/status`, `/extension/status`) were
not sending the bearer token. The host validation middleware rejects
non-localhost requests without a valid token, so remote `session new`
and `session list` would silently fail with "no connected browsers".

**cli.ts**: `fetchExtensionsStatus` now accepts `{ host, token }` and
passes auth headers via `buildAuthHeaders` to both status endpoints.

**executor.ts**: `checkExtensionStatus` reads `token` from
`this.cdpConfig` (falling back to `PLAYWRITER_TOKEN` env) and attaches
`Authorization: Bearer` header to all status fetch calls.

`relay-client.ts` left unchanged since those functions are hardcoded
to `127.0.0.1` (local-only, always passes host validation).

Closes #91
Fixes #85

Session: ses_1b4c572a4ffev2Dct63TjK77gJ
2026-05-21 17:53:18 +02:00
..

Changesets

This folder contains pending release notes for public packages. Each .md file describes one user-facing fix or feature that should appear in the next generated changelog.

What to put here

  • Add one descriptive kebab-case .md file per logical change, for example fix-auth-token-refresh.md.
  • Use patch for fixes and minor for new features.
  • Write in present tense, focused on what users see.
  • Check GitHub issues first. If the change fixes one, include Fixes #123 on its own line.

What not to put here

  • Do not add changesets for private packages or packages without a version field.
  • Do not edit CHANGELOG.md directly.
  • Do not run the interactive changeset CLI.
  • Do not add vague entries like "misc improvements" or "update internals".