KeelenAnswer — Roblox
Can AI build my Roblox game and keep updating it?
Updated 20 August 2026
Generating a first version is largely solved: Roblox's own in-Studio assistant and several prompt-to-game tools will produce something playable. Keeping a live game improving week after week is the harder half, and it needs the things software teams use rather than the things prompt tools provide: the game in version control, a test runner, and someone shipping changes on a rhythm. Keelen treats a Roblox game as a software project. It works on a GitHub repository with Rojo and Luau, runs tests with Lune, ships changes as reviewed pull requests, and can generate art, audio, meshes, skyboxes, and animated characters from written requests.
The practical consequence is that your game stops depending on one person opening Studio. Requests go in, tested changes come back, and the update cadence that retains players becomes possible without a full-time team.
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: history, review, rollback, and anyone other than one person changing the game safely.
Add a test runner
Lune runs Luau tests outside Studio, which means changes can be verified automatically rather than by loading the place and hoping. Without this, 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 whether something is fun are judgement calls. Automate the shipping, not the design taste.
One-shot generation and continuous development are different problems
Prompt-to-game tools optimise for the first playable build, and they are good at it. What they do not address is the second month: a live game with players, a bug list, and a need for new content on a schedule. That is ordinary software maintenance wearing a different hat, and it responds to the same remedies, which are version control, tests, and steady shipping.
How the Roblox lane works
Keelen detects a Rojo and Luau project, uses Lune as the test runner, and ships changes as pull requests through the same gates as any other stack. Asset generation is request-driven: a change declares the art or audio it needs in a manifest, and the pipeline generates and uploads it rather than leaving a placeholder.
Verification, on a game
Five gates stand between the loop and your main branch. New tests are applied without the implementation first and must fail, so tests born green are rejected. An independent reviewer that shares no context with the run that wrote the code reviews the diff. Your own test suite runs on a clean checkout. Nothing merges over a red required CI check. And a review window stands before gated auto-merge, which you can replace with plan-review sign-off, manual merge, or branch-only mode.
What it costs to run
Keelen runs on credentials you connect: Anthropic Claude (a Claude Code subscription login or an API key, no Max plan required), OpenAI Codex, Zhipu GLM, or Moonshot Kimi. Token usage bills to your own provider account at cost. Keelen charges a flat monthly tier and never marks tokens up.
When Keelen is not the answer
- Your game only exists inside Studio and you do not want it in a Git repository. Rojo is a prerequisite, not an optional extra.
- 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, write what you want in plain language, and review the tested pull requests that come back.
FAQ
Can AI write Luau scripts?
Yes. Luau is well supported by current coding models, and Keelen runs Claude, Codex, GLM, or Kimi on your own credentials. The difference from a chat window is that the change arrives as a tested pull request against your repository.
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. Art, audio, meshes, skyboxes, and animated characters can be generated from written requests, declared in a manifest by the change that needs them, and uploaded through Roblox Open Cloud. You turn this on per project and supply your creator details first, because the assets publish under your own account.
Will it publish updates to my live game automatically?
Publishing stays under your control. The loop ships changes as reviewed pull requests to your repository, and you decide what your release process does with them.