I just stumbled upon a recent repo for playwright via the CLI. I use OpenCode w/ Opus 4.6. After installing the skill in my repo Claude navigated my local running frontend and has grasped some UI/UX refactors I was struggling to convey.
Thought I would share this for anyone running a similar set up doing frontend/full-stack work. I know playwright MCP is nothing new, but the CLI + skill is much lighter on token usage. So far so good.
What are some good alternatives to Firefox? I have loved the browser for years, but the future isn’t looking bright. Waterfox is on my radar. Any others I should be aware/you guys are using?
Wow, these numbers are insanse! I tried it yesterday and it worked beautifully well. It also responded the way I wanted every time, I didn't have to spend time prompting it on how to respond properly (unlike Grok 4 expert, which tends to yap a lot), it just knew.
Todays models have gotten so good that at this point, whatever I run, just works and helps me in whatever. Maybe I should start noting down prompts that some models fails at.
- Simple online verification: the easiest way is to use the public POST /v1/verify endpoint. Any of your services can call this with the agent's credential. It's a stateless check that returns a JSON object confirming if the token is valid and crucially what scopes and user_identifier it was issued for.
- Decentralized/offline verification: for more advanced use cases or high-throughput services that want to avoid a network call you can also verify the credentials offline. The tokens are standard JWTs signed with RS256, and I expose the public keys via a standard /.well-known/jwks.json endpoint on the main domain. You can fetch the keys, cache them and then verify the token signatures locally.
The goal is to make it easy for a developer to get started with the online endpoint, while still providing the standard, scalable method for more mature systems. Thanks for checking it out!
reply