Context
The user-signup work introduces account-owned endpoints. Browser inspector/control APIs now require the owning Better Auth session for endpoints with ownerUserId.
The whlol CLI currently uses plain unauthenticated fetch calls, so it can only operate on anonymous endpoints. Account-owned endpoints created while signed in cannot currently be used from the CLI.
Affected commands
whlol tail <endpointId>whlol forward <endpointId> --to <url>whlol replay <endpointId> ...
These commands will appear anonymous to the server and fail for account-owned endpoints, typically as 404 Endpoint not found.
Desired outcome
Design and implement a CLI-compatible access model for account-owned endpoints. Possible directions:
- CLI auth/session flow
- Endpoint-scoped access tokens for CLI use
- Another explicit server-supported access mechanism for account-owned endpoint operations
Context
The user-signup work introduces account-owned endpoints. Browser inspector/control APIs now require the owning Better Auth session for endpoints with
ownerUserId.The
whlolCLI currently uses plain unauthenticatedfetchcalls, so it can only operate on anonymous endpoints. Account-owned endpoints created while signed in cannot currently be used from the CLI.Affected commands
whlol tail <endpointId>whlol forward <endpointId> --to <url>whlol replay <endpointId> ...These commands will appear anonymous to the server and fail for account-owned endpoints, typically as
404 Endpoint not found.Desired outcome
Design and implement a CLI-compatible access model for account-owned endpoints. Possible directions: