Vintage Story server config edits you can review

What the agent can use

• Filesread_file, write_file, edit_file, copy_file, list_dir, grep and glob work in the chat's working folder, such as your server's data folder. A counter shows files read and edited.
• Shellruns your start and backup scripts and other terminal commands, and judges success by the real exit code. Dangerous commands are blocked.
• Webweb_search and http_get read the official documentation pages, for example to check the spelling of an admin command before you type it into the console.
• Screenshots and imagesocr reads text from a saved screenshot of an error window that a player sent you, and gen_image saves real image files.
• Orchestrationtask runs parallel sub-agents on separate files, 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 actions that change something, and Plan only writes a plan and runs nothing.
• Cronruns a prompt on a schedule, for example a request to read the latest server log and list every line that mentions a failed mod.
• Modelsconnect a cloud AI provider, a model on your PC or the built-in model, and use the Test button to check an endpoint.

Four jobs, step by step

Vintage Story server setup on a new PC

You want a folder for a world that friends will join. You download and unpack the server package yourself, then choose the data folder as the working folder of the chat. The agent uses web_search and http_get to read the official server documentation, write_file to save the start options into a start script, and read_file to check serverconfig.json. Shell runs the script and the card shows the real exit code. Watch every card. In Ask first mode you also see a diff before any file is written, and you accept or reject it, so nothing on the machine changes behind your back. When the script has finished, you open the game, choose multiplayer and test the connection yourself.

Change name, player limit and password

You want to rename the server, set MaxClients to 10 and put a password on it. The agent opens serverconfig.json with read_file, and copy_file stores a copy beside it before any change. Then edit_file changes ServerName, MaxClients and Password, and the card shows the diff line by line. Stop the server before you accept the diff, because the file should not change while the server runs. Afterwards grep checks that the three keys hold the new values and Shell starts the server with your script. Then ask a friend to join and look at the log together. Port 42420 (TCP) stays the same unless you change Port yourself, and if players come from the internet you forward only the port you use on your router.

Match mods on the server and the clients

You want to add a content mod, which is a set of JSON asset files, and later a code mod written in C#. Mods go into the Mods folder of the data folder as .zip files or folders, and each one describes itself in a modinfo.json. The agent uses list_dir to show what is installed, read_file to read each modinfo.json and write_file to save a mod list that you can send to your players, because server and players need the same mods and versions. You can make a translation as a mod, since translations are JSON asset files. Before you add worldgen mods, ask whether they will affect previous saves, and test the answer on a copy of the Saves folder. Plan only shows the steps first.

Find out why a player cannot join

A player reports an error while joining. When a friend cannot get into your server, the first suspects are the port, the password and a mod mismatch. The agent uses grep to search the server log for the line where the player was disconnected or a mod failed to load, and read_file opens serverconfig.json so that you can compare Port and Password with what the player typed. glob lists the log files and list_dir shows the Mods folder. Change one thing. Ask first stops before anything is edited, you read each match, and you test again after every change. If a mod is the cause, you move that single file out of the Mods folder yourself, restart the server and read the log once more, so that you know which change fixed the problem.