Free chat access comes with a browser dependency
ZeroScript-Free takes an unusual route into Roblox Studio. Its extension reads and writes inside supported AI chat pages, passes recognized commands to a local Python bridge, and lets that bridge talk to Studio's built-in MCP server. You can ask for script edits, Luau execution, tree inspection, asset work, or play-test control from the same chat box used for ordinary questions.
The supported list has 8 providers: DeepSeek, ChatGPT, Gemini, Kimi, GLM, Qwen, Arena, and Meta AI. There is no model API key and no ZeroScript account. That removes one cost and setup barrier, but it does not make the AI service local. Your prompts and replies still pass through whichever provider page you sign into, subject to that service's limits and policies.
The four-part path is simple to follow and easy to break
A working session has four moving pieces: the chat page, extension, bridge, and Roblox Studio. The README walks through loading the unpacked extension, enabling Studio's MCP server, starting the bridge, and clicking the ZeroScript session bar. A status dot distinguishes a ready Studio connection from a live bridge with no usable place and a bridge that is offline.
Version 1.5.5 supports Windows and macOS, Python 3.9 or newer, and Edge or Chrome. Linux and Firefox are absent from the requirements, and both have open requests. Mac users must approve a downloaded command file in Privacy & Security on first launch. Windows gets a batch launcher that handles Python setup, while macOS users may need to install Python themselves.
What happened when we ran it
Our sandbox installed commit 32dd846 in 7 seconds, pulling 35 packages and using 37 MB on disk. The build succeeded in 1 second. Pip-audit found 0 known vulnerabilities. This was a fresh Debian container with 3 CPUs, 8 GB of RAM, no secrets, and no elevated privileges. Those results cover repository setup only, not a live Roblox or provider session.
There was no test script or target, so the lab skipped tests. That is different from a passing suite. The 1.9 MB checkout contained 35 files and about 15,048 lines of source, but no tests directory, Dockerfile, or CI workflow. A maintainer can ship a provider adapter without any visible automated check proving that it still finds the right editor, reads a full command, or handles a changed page layout.
Chat page changes have already broken supported providers
The maintenance history reads like a record of moving browser targets. Release 1.5.5 changed the DeepSeek adapter after the site merged its model choices and removed the old picker. Version 1.5.4 had repaired ZeroScript's placement above a redesigned ChatGPT composer and fixed reading long code blocks. Those are useful fixes, and they show why this design needs frequent attention.
Open issue 85, filed October 1, reports that the ZeroScript bar disappeared again on ChatGPT v1.5.5 after another composer structure change. The reporter said the bridge and Studio connection were healthy while the page integration stalled. We did not reproduce that browser report in our container. It is still a concrete example of the extension's main failure mode: a healthy local stack can become unusable when someone else's HTML changes.
Provider behavior differs even when the bar appears
The README recommends DeepSeek, while documenting caveats elsewhere. Gemini may stop using Roblox tools in long sessions. Kimi may choose its native tools instead of ZeroScript commands. Arena only works in Direct mode, and ZeroScript blocks its other modes. ChatGPT screenshot input is intentionally disabled because the free tier applies a separate quota to files and images. One interface does not mean one consistent agent.
The v1.5.5 extension manifest requests access to the 8 provider families plus 127.0.0.1 over HTTP and WebSocket. That is understandable for its job, but it is meaningful access. Read the extension source, use the official repository release, and keep the browser profile separate if you do not want unrelated browsing mixed with an experimental development tool.
Account enforcement is reported, while causation is unknown
Issue 89 documents one user's DeepSeek suspension and ChatGPT warning while using ZeroScript. The report carefully says neither provider identified ZeroScript as the cause. Other issues also mention DeepSeek account restrictions, but user reports cannot establish why enforcement happened. Message frequency, automated page interaction, content, or an unrelated account event could all matter, and the available evidence does not choose among them.
That uncertainty changes the recommendation. Do not test a browser-driven agent on the only account you rely on for work. Keep sessions supervised, stop when tool calls loop, and review generated Luau before it runs. ZeroScript can execute commands in an open Studio place, so a mistaken edit has a larger consequence than a wrong chat answer. Project memory stored inside the place also deserves inspection before sharing the file.
Active fixes do not replace a release gate
GitHub listed 306 stars and 65 open issues and pull requests on October 5, 2026. Search separated that total into 63 issues and 2 pull requests. The default branch still points to the September 10 release commit, while issue discussion continued into October. Release v1.5.5 is recent, but the queue includes support requests, provider breakage, and many low-information posts.
ZeroScript-Free is best treated as a clever supervised convenience for Roblox hobby work. Its 7-second install is the easy part. The lasting cost is watching four integrations, trusting a wide-host browser extension, and recovering whenever a provider changes its page or behavior. If that trade saves enough friction, use a disposable place and an account you can afford to stop using.