@Saccc_c: https://x.com/Saccc_c/status/2055259378174042388

X AI KOLs Following Tools

Summary

Go-Live.skill allows users to remotely Vibe Code via Codex on mobile devices and automatically deploy local websites online, solving the problem of not being able to open local web pages on mobile phones.

https://t.co/n2rFXEDpqV
Original Article
View Cached Full Text

Cached at: 05/15/26, 01:03 PM

This SKILL truly enables remote Vibe Coding with your Codex

Codex remote operation is officially launched — now you can smoothly control your computer from your phone.

I tried it immediately, but found a critical issue with Vibe Coding on mobile: you can’t open a local website from your phone.

That means after modifying the code, there’s no way to see the results directly on your phone. But if you could automatically deploy the site online, you’d be able to open it from your phone.

So I created a skill that lets you open local websites on your phone, and named it: Go-Live.skill

GitHub repo: https://github.com/Sac-Y/go-live

1. Skill Demonstration

Without this skill installed, you’ll run into this problem:

With this skill installed, you can open the deployed website directly on your phone (I used my phone to make a GitHub info aggregation site):

2. Installation Method

1. Run the command in your terminal:

2. Enter the following instruction in the Codex input box:

Please install this skill for me: https://github.com/Sac-Y/go-live

3. Actual Test Results

It works like a charm — perfectly solves the problem of not being able to open local web pages during remote Vibe Coding. Install it now and you can Vibe Code from anywhere.

Similar Articles

@GoSailGlobal: https://x.com/GoSailGlobal/status/2052573500800700560

X AI KOLs Timeline

SWE-WebDev Bench is a paper on arXiv that evaluated 6 mainstream vibe coding platforms (Lovable, Replit Agent3, Vercel v0-Max, Base44, Emergent E1-OPUS, QwikBuild). It found that all platforms scored below 60% on engineering composite metrics — their front-end UIs look great but back-end, security, and production readiness all collectively fail, requiring 12-60 hours of manual fixes before going live.