Read before it writes
list_dir, glob, read_file and grep map the addon first, so edits start from what your folders really contain.
Product
GMod gamemode code you write and test on your own PC
01
A GMod gamemode is a folder with an info file and a gamemode/ subfolder holding init.lua, cl_init.lua and shared.lua, and Codelab Station reads that folder and edits the Lua you name, with a diff before you accept in Ask first mode. It stays outside the game. Every action appears as a card with its real result.
Edits you can review
edit_file shows a diff and write_file creates new files, while Ask first pauses before each change.
Tidy several addons
Combining multiple addons into one folder is a job for list_dir, grep, move_file and a diff you review.
What the agent can do
- Filesread_file, write_file, append_file, edit_file, delete_file, make_dir, move_file, copy_file, list_dir, grep and glob work inside the working folder.
- Shellruns terminal commands such as your server launch script, linters, formatters and tests. Success is judged by the real exit code, and dangerous commands are blocked.
- Webweb_search and http_get read documentation pages, so a hook name or an entity field can be checked against the Garry's Mod wiki.
- Screenshots and imagesocr reads text from a screenshot, such as a Lua error in a console window, and gen_image saves real image files for addon artwork.
- Orchestrationtask starts parallel sub-agents, run_on_model sends a hard step to a bigger model, and skill stores reusable playbooks, including a version-control skill for branches and commits.
- Approval modesAuto-run acts immediately, Ask first pauses before every action that changes something, and Plan only plans without touching files. Plans survive restarts.
- Cronruns a prompt on a schedule, for example a nightly prompt that lists which Lua files changed in your working folder.
- Modelsconnect a cloud AI provider through a standard API endpoint, a model on your PC or the built-in model. The Test button shows response time and the context window.
One run, card by card
Every action appears in the chat as a card with its real result, and this run creates a crate entity folder in an addon of your own and then checks it. Accept or reject each card.
Create a scripted entity folder for a spawnable crate, then check the files and run my test command.
- glob
lua/entities/**0 matches - write_file
lua/entities/crate/shared.luasaved - write_file
lua/entities/crate/init.luasaved - write_file
lua/entities/crate/cl_init.luasaved - grep
ENT.Spawnable1 match - Shell
your test commandexit 0
Waiting for your OK before the next stepRejectAccept
Two jobs to give it
Build a GMod entity addon from a plan
Start in Plan only mode and describe a scripted entity, for example a crate that players can spawn. The agent reads the addon with list_dir and lists the files it would write under lua/entities/. Plan only writes nothing. Switch to Ask first and write_file creates shared.lua, init.lua and cl_init.lua card by card. If the crate's model does not show, the game may have failed to find models for the addon, so glob lists the models folder and you compare its paths with the model path in your Lua. The same plan-first routine suits a larger idea such as a mod to spawn enemies throughout the map. Review each diff, then load gm_construct to test.
Start a small GMod gamemode on top of Sandbox
A gamemode is a folder in garrysmod/gamemodes with an info text file and a gamemode/ subfolder holding init.lua, cl_init.lua and shared.lua. Ask the agent to create that layout and to add DeriveGamemode("sandbox") so your rules build on Sandbox. It uses make_dir and write_file for the files and Shell for your launch script with the gamemode and map as start parameters. Lua errors appear in the game console, and ocr can read one from a screenshot. Keep Ask first on. Read every diff and test on gm_flatgrass.
What Codelab Station does not do
Codelab Station is not a plugin of the game, and it never touches the game client. Other servers stay off limits. Players and accounts that you do not own are out of scope, and it cannot promise that code is correct, so you test every change and read every diff yourself.
