Edit real files
It reads, edits and writes plugin source and .cfg files inside the working folder.
Product
CS2 server plugins and configs, handled with real tools
01
CS2 server plugins run only on a dedicated server you control, and they are written as C# source files. Nocode Atelier opens that source in your project folder, edits it with file tools, runs your build command and shows the result as a card. You review the diff.
Run your build
Shell runs your build command and judges success by the real exit code.
Approve each step
Ask first pauses before every change, and Plan only changes nothing at all.
What the agent can do
- Filesread_file, write_file, edit_file, grep and glob work inside the chat's working folder, and a counter shows files created, edited and read.
- Shellruns terminal commands such as your plugin build command. Success is judged by the real exit code, and dangerous commands are blocked.
- Webweb_search and http_get read documentation pages, such as the Valve Developer Community wiki, so answers can point to a source.
- Screenshots and imagesocr reads text from a screenshot, such as an error dialog, and gen_image saves real image files into the project.
- Orchestrationtask runs parallel sub-agents, run_on_model sends a hard step to a bigger model, and skill stores reusable playbooks.
- Approval modesAuto-run acts at once, Ask first pauses before every change, and Plan only plans without changing anything. Plans survive restarts.
- Cronruns a prompt on a schedule, for example a daily read of your server logs with a summary for you to review.
- Modelsconnect a cloud AI provider, a model running locally on your PC, or the built-in model, and use the Test button to check it.
Where it fits in a CS2 project
The agent works on the files around your server: configs, plugin source, rotation lists and notes. Hammer stays your map editor. Two folders are enough to start, one for the server and one for your plugin source.
Add a round MVP message to my plugin and run the build.
- grep
"round" src/7 matches - read_file
src/RoundMessage.cs52 lines - edit_file
src/RoundMessage.cs+14 -1 - Shell
your build commandexit 0 - write_file
notes/test-plan.md+9
Waiting for your OK before the next stepRejectAccept
Two jobs, step by step
Add a round MVP message
You own a small plugin and want it to print the round MVP when a round ends. Nocode Atelier starts with grep to find the code that already handles rounds, then read_file opens the 52 line source file. edit_file adds the new lines, and Shell runs your build command so the real exit code decides whether the step passed. With Ask first on, each edit waits for your OK. Copy the built plugin to your test server, play one round and confirm the message before you keep the change.
Review CS2 plugins before match night
Before a league night you want to know what every installed plugin command does. Start in Plan only mode and ask the agent to read each source file with read_file. It uses grep to list the command names, then write_file saves a 1-page summary in your notes folder. Nothing in your plugins changes. If a command looks wrong, you fix it in a separate session with Ask first on. Read the summary against the source yourself, and test any change on a local server.
What Nocode Atelier does not do
Nocode Atelier is not a plugin for Hammer or the game, and it never touches the game client, servers you do not own, other players or their accounts. It cannot fix a CS2 map editor that is not working, but it can read the log text you save. Review the diff.
