Read before editing
read_file and grep open your config and logs, so the agent works from the real text of your files.
Product
Palworld server mods and files, handled with your approval
01
GeekCrest helps you keep Palworld server mods, settings and saves organized on a server you own. It reads before it writes. It lists folders, reads files and logs, edits one entry at a time with a diff and runs your own scripts, then shows every result as a card you can expand.
Edit with a diff
edit_file changes one setting and shows a diff; in Ask first you accept or reject it.
Run your own scripts
Shell runs your start or backup script and reports the real exit code.
What GeekCrest can do for a server admin
- Filesread_file, write_file, edit_file, grep, glob and list_dir work inside the chat's working folder, and a counter shows files created, edited and read.
- Shellruns your own terminal commands, such as a start or backup script, and judges success by the real exit code. Dangerous commands are blocked.
- Webweb_search and http_get read the Palworld server documentation and patch notes, so you can compare your files with the current text.
- Screenshots and imagesocr reads the text of a screenshot, such as an error window, and gen_image saves real image files.
- Orchestrationtask starts parallel sub-agents on separate logs, run_on_model sends a hard step to a bigger model, and skill reuses a playbook.
- 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 newest log; choose the approval mode before you leave it unattended.
- Modelsa cloud AI provider, a model on your PC or the built-in model, with a Test button that shows response time and the context window.
A server setup task as the agent runs it
The example below is a Palworld server setup check: the agent finds the settings file, reads it and backs up the saves, with every result visible as a card. Read each card.
Find my PalWorldSettings.ini, back up the save folder and show me the player limit entry.
- glob
**/PalWorldSettings.ini1 match - read_file
PalWorldSettings.iniread - grep
ServerPlayerMaxNum1 match - write_file
backup-saves.cmdsaved - Shell
backup-saves.cmdexit 0 - list_dir
C:\PalBackupslisted
Waiting for your OK before the next stepRejectAccept
Two tasks for a server admin
Keep a list of installed mods
Mods are community-made and their compatibility changes with game updates, so expect Palworld server mods to break after a patch. Ask GeekCrest to run list_dir on the server folder and use write_file to create mods-list.txt, then fill in the name, version and date of each mod you install. Install only mods you trust, on your own server. One mod at a time. After an update, grep searches that list for the entries you still need to check. If the server is running an incompatible version after an update, compare the versions in your list before you blame anything else. Read the new file in its card first, and use Plan only if you want to see the steps before any file is written.
Verify the first start and the settings file
After the first start, PalWorldSettings.ini appears in the Pal\Saved\Config\WindowsServer folder. GeekCrest finds it with glob, opens it with read_file and lists the entries to check: ServerName, ServerPassword, AdminPassword, PublicPort and ServerPlayerMaxNum. Mask the two password values first, or use a local model for this file, because a cloud model receives the file text the agent reads. Stop the server before any edit. If a change in a dedicated server ini file is not applying, check whether you edited the template DefaultPalWorldSettings.ini instead of PalWorldSettings.ini. Before you import a save from a dedicated server into a solo game, back up both saves, because player data is tied to player IDs. In Ask first mode every edit_file change shows a diff; accept it, restart and join to test.
What GeekCrest does not do
GeekCrest is not a plugin for Palworld and never touches the game client. File tools work in the chat's working folder, but Shell, web and SSH are not folder-bound, so you keep every task to a server you own or may manage. Nothing it writes is promised to be correct. Test every change.
