KeelenAnswer · Roblox
Can AI build my Roblox game and keep updating it?
Updated 11 September 2026
A Roblox project is software. It needs version control, a test runner, and a release process you can check. Keelen can work on a GitHub repository with Rojo and Luau. It can use Lune when the project has a verified test command. Asset work requires the project to opt in explicitly. It also requires creator details. The account owner keeps publishing.
Start with a bounded Request. Review its pull request and the test evidence you have. Then use Studio and your release process to decide what reaches players.
What to do, in order
Get the game into version control
Rojo maps a Roblox place to files in a Git repository. This is the step that makes everything else possible. That gives you history and rollback. It also lets more than one person change the game safely.
Add a test runner
Lune runs Luau tests outside Studio. So a change can be checked without loading the place. Without it, unattended changes cannot be trusted.
Decide your update rhythm
Live games are retained by consistent updates. Pick a cadence you can actually sustain, then work out who does the shipping to sustain it.
Treat assets as part of the work
Art, audio, meshes, and characters are usually the slowest part of a small Roblox team's week. Declare what you need alongside the code change that needs it.
Keep a human on game feel
Balance, pacing and fun are judgement calls. Automate the shipping, and keep a person on design taste.
One-shot generation and continuous development are different problems
A playable prototype still leaves work to do. That means bugs, content changes, and release decisions. Put that work into version control. Write bounded Requests, and check test evidence and Studio behavior before you ship.
How the Roblox lane works
Keelen works on GitHub with Rojo and Luau. A verified Lune command gives test evidence outside Studio. Project review and merge settings still apply. Asset work needs you to turn it on for the project, plus creator details. A Request's manifest can drive asset generation. It can also drive the upload to Roblox Open Cloud. Check the assets in Studio.
Verification, on a game
A separate adversarial reviewer reads the diff. It does not see the conversation that wrote the code. The review model comes from your project settings. Red first proof and clean checkout tests need a verified project test command. Gated auto-merge needs the repository checks and a review window you set up. Plan review, manual merge, and branch-only mode each pick where a person must decide. Check the real evidence before you accept the result.
What it costs to run
Keelen runs on credentials you connect. Anthropic Claude works with a Claude Code subscription login or an API key. No Max plan is required. You can also connect OpenAI Codex, GLM, Kimi, or xAI Grok. Coding-engine token use bills to your own provider account at cost. Keelen charges one flat monthly fee and adds no markup.
When Keelen is not the answer
- Your game only exists inside Studio. You do not want it in a Git repository. Rojo is required here.
- You want a game generated from one prompt and then left alone. This is built for the opposite case, which is continuous updates.
- You need game design judgement rather than shipping capacity.
Hand the work to a loop
Connect a repository and write what you want in plain language. Review the tested pull requests that come back.
FAQ
Can AI write Luau scripts?
Keelen can work on Luau files with a supported engine. Check the change and the evidence from your test command. Tests outside Studio do not replace playtesting. They also do not replace your release decision.
Does it work inside Roblox Studio?
No. It works on the GitHub repository your place is synced to with Rojo. You keep using Studio; the loop works on the files.
Can it generate art and sound for my game?
Yes. Written requests can generate art, audio, meshes, skyboxes, and animated characters. The change that needs them declares them in a manifest. They upload through Roblox Open Cloud. You turn this on per project and supply your creator details first. The assets publish under your own account.
Will it publish updates to my live game automatically?
You stay in control of publishing. The loop ships changes as reviewed pull requests to your repository. You decide what your release process does with them.