this should by and large already be possible with playwright interactive no? anything you’d like to add/ change? https://
github.com/openai/skills/
tree/main/skills/.curated/playwright-interactive
…
TOOLS
-
Playwright Interactive Skills Implementation Discussion
By
–
-
What Tools Should Integrate With Codex Next?
By
–
We are expanding Codex’s toolkit – what tools would you love to see work with codex the most?
-
AI on the Assembly Line: Instant Potato Counting with Minimal Training
By
–
#AI on the Assembly Line: Instant Potato Counting with Minimal Training
— Ronald van Loon (@Ronald_vanLoon) 26 mars 2026
by @IlirAliu_
#ArtificialIntelligence #MachineLearning #ML #MI pic.twitter.com/voofupOVbE#AI on the Assembly Line: Instant Potato Counting with Minimal Training
by @IlirAliu_ #ArtificialIntelligence #MachineLearning #ML #MI -

Claude Code on Mobile: A Game-Changing Productivity Tool
By
–
I don’t think you all understand how powerful Claude Code is from a phone. Telegram, iMessage, remote control, mobile command, dispatch, whatever you have to do. Just get this thing on your phone. My team is going to hold a no-laptop hack day soon, where everyone is forced to leave their desk and just be on a walk or at a restaurant or in a park with their phone (and dictation, I’m sure). Whoever is most productive wins.
→ View original post on X — @alliekmiller, 2026-03-26 03:45 UTC
-

MCP Security: Avoid Local Servers, Run Remote Containers
By
–
PSA: Stop running local MCP servers. The folks at futuresearch were pwned when a local MCP server pulled in an impacted package. Always run your MCP servers remotely. The blast radius should be limited to the container that it runs in. If you're impacted by the LiteLLM
-

MCP Server Security: Avoid Local Deployment After LiteLLM Breach
By
–
PSA: Stop running local MCP servers. The folks at futuresearch were pwned when a local MCP server pulled in an impacted package. Always run your MCP servers remotely. The blast radius should be limited to the container that it runs in. If you're impacted by the LiteLLM
-

MCP Server Security: Avoid Local Deployment Risks
By
–
PSA: Stop running local MCP servers. The folks at futuresearch were pwned when a local MCP server pulled in an impacted package. Always run your MCP servers remotely. The blast radius should be limited to the container that it runs in. If you're impacted by the LiteLLM
-

Stop Running Local MCP Servers Security Warning
By
–
PSA: Stop running local MCP servers. The folks at futuresearch were pwned when a local MCP server pulled in an impacted package. Always run your MCP servers remotely. The blast radius should be limited to the container that it runs in. If you're impacted by the LiteLLM
-

Stop Running Local MCP Servers Security Advisory
By
–
PSA: Stop running local MCP servers. The folks at futuresearch were pwned when a local MCP server pulled in an impacted package. Always run your MCP servers remotely. The blast radius should be limited to the container that it runs in. If you're impacted by the LiteLLM
-

Stop Running Local MCP Servers Security Vulnerability Warning
By
–
PSA: Stop running local MCP servers. The folks at futuresearch were pwned when a local MCP server pulled in an impacted package. Always run your MCP servers remotely. The blast radius should be limited to the container that it runs in. If you're impacted by the LiteLLM