Windows 10/11
x64 only, no account needed
Inthis Studio is a Windows 10/11 desktop agent for Fallout 4 modders. It reads your Papyrus scripts, INI files and Plugins.txt, runs your own commands and shows each result as a card. Version 2.9.22.
Data13 filesPlugins.txt11 lines.esm3 matchesplugin-check.txtsavedPlugins.txtdiff shownx64 only, no account needed
Released 28 October 2026
Portable .exe is about 25 MB
Interface languages in the app
Auto-run, Ask first, Plan only
No telemetry, chats stay on your PC
Fallout 4 mods are plugin files (.esp, .esm and light .esl), often with .ba2 archives or loose files, that go into the game's Data folder. Plugins load top to bottom. When two plugins change the same record, the one loaded later wins, so a written list of what you installed is the first thing to check when something breaks, and the agent can keep that list for you.
Plugins.txt lists the active plugins of Fallout 4, one per line. Copy it and the plugin files you want checked into your working folder first, because the file tools work only in that folder. Then list_dir maps the Data files, read_file opens Plugins.txt and grep finds the .esm lines, since master files load before ordinary plugins. The agent saves plugin-check.txt with write_file and lists the plugins it finds without a matching file. You read the report. In Ask first mode, edit_file shows a diff of any proposed change before you accept it.
list_dir Data → 13 files
read_file Plugins.txt → 11 lines
grep .esm → 3 matches
write_file plugin-check.txt → savedA short Papyrus script for Fallout 4 can show a message when the player activates an object. Describe that task in one sentence, and the agent saves InthisWelcome.psc with write_file, using an OnActivate event and Debug.Notification. Shell then runs your own compile command and reports the real exit code, so a non-zero code sends you to the error in the expanded card. Attaching the compiled script to the object in the Creation Kit stays your job. Test it in the game.
write_file scripts/InthisWelcome.psc → saved
read_file scripts/InthisWelcome.psc → 12 lines
Shell your compile command → exit 0Script errors leave lines in the Papyrus log. Switch logging on with bEnableLogging=1 and bEnableTrace=1 in the [Papyrus] section of your INI file, play until the error, then copy the log from Documents\My Games\Fallout4 into your working folder. read_file opens it, and grep finds the script name and the word error. The agent then reads that .psc file and proposes a fix with edit_file as a diff. You decide. Test again and read the new log.
Settlement building mods in Fallout 4 add workshop objects. Those objects are made in the Creation Kit as workshop recipes, and Plan only is the place to start because it changes nothing. Ask for a step list for one new buildable item. The agent writes the steps in the chat from your prompt, runs nothing and touches no file. Nothing is saved. Open the Creation Kit wiki yourself, or switch to Ask first so http_get can fetch a page and write_file can keep the list as a text file.
Version 2.9.22 acts on files. A typical chat assistant explains in text and leaves the typing, running and checking to you, while the agent runs the tools and shows each real result.
| Typical chat assistant | Inthis Studio | |
|---|---|---|
| Files | Shows a script in the chat for you to copy | Reads and edits files in the working folder, with a diff |
| Checks | Usually cannot run your compile command | Runs your command in Shell and shows the real exit code |
| Control | Replies with text only | Auto-run, Ask first or Plan only, your choice |
| Privacy | Prompts often go to a hosted service | Runs locally; prompts go only to the model you pick |
First-time modders and long-time players who search for 'best Fallout 4 mods' often end up with a pile of names and no record of what they installed. It does not rank mods. It writes your own list, with plugin names, load positions and one note per plugin, which also shows which mods and patches to restore when you are reinstalling Fallout 4.
Script writers who know a little Papyrus use it for small jobs, such as a welcome message, a fix after a compile error or a helper for a workshop object. It edits the .psc file. You attach the compiled script in the Fallout 4 Creation Kit and test in the game.
Settlement builders and players planning a larger workshop build use it to keep the plan in one place. Planning comes first. Fallout 4 settlement mods add buildable objects, and settlement-heavy mods raise script and object load, so the agent lists what you installed and leaves the choice with you.
A mod is a plugin file (.esp, .esm or light .esl) that adds or changes game records, usually with archives or loose files in the Data folder. Consoles work differently. Players there install mods only through the in-game Mods menu, while this app works with files on a Windows PC.
Yes, inthiscode.com is the official Inthis Studio website. Download the original build here and compare its SHA-256 checksum with the published manifest before you run the setup program. Inthis Studio is not affiliated with Bethesda Softworks. For support, press Send feedback.
The agent reads Plugins.txt with read_file, lists your Data folder with list_dir and writes a report of duplicate lines and plugins without a file. You decide the order. In Ask first mode you see a diff before any edit.
No. It writes scripts, notes and step lists, but you create workshop objects and recipes yourself in the Creation Kit, because the agent cannot click in that window. Large settlements slow a save down, so test with a backup of your saves.
When PC mods are crashing Fallout 4 on startup, four checks come first: a missing master file, a plugin in the wrong place in the load order, a plugin listed in Plugins.txt without a file in Data, and the Papyrus log. Back up your saves first. The agent reads those files with read_file and grep, and you decide what to change.
No. The model can write Papyrus that fails to compile or does nothing in the game, so you test every change. Shell shows the real exit code of your compile command, and the Papyrus log shows what happened at run time. Testing stays with you.
The answer depends on the model you pick. A cloud provider receives the prompt text, including any file text the agent reads, while a local model keeps everything on your PC. Keys stay local. Chats and working folders also stay on the PC, and secrets in tool output are redacted before they reach the model.
Install version 2.9.22, pick a project folder and try one small job, such as reading a Papyrus log or checking a copy of Plugins.txt. No account is needed.
Download Inthis Studio for Windows ↗Every page is available in 20 languages.
What the agent does for mod authors ↗ Connect a cloud, local or built-in model ↗ Step by step: write your first mod script ↗ Download, checksum and install steps ↗ Answers about add-ons, scripts and privacy ↗ What the site and the app record ↗