Reads your project
Open the folder with your .verse files and SentryEdit reads, searches and edits them.
Product
UEFN Verse Assistant That Acts on Your Files
01
Verse code for your island lives in .verse files, and SentryEdit can read, search and edit those files on your Windows PC. It is a separate app, not a plugin of the editor, so you still build and test in Epic's editor as usual. Every action shows up as a card with its real result.
Runs its own tools
File tools, Shell, web lookups and screenshots appear as cards with real results.
You stay in charge
Ask first pauses before each change. Plan only changes nothing at all.
What the agent can do
- Filesread_file, write_file, edit_file, move_file, grep and glob work inside the chat's working folder, and a counter shows files created, edited and read.
- Shellruns terminal commands on your PC, such as scripts you already use. Success is judged by the real exit code, and dangerous commands are blocked.
- Webweb_search and http_get read documentation pages, so the agent can check Epic's own documentation for Verse and your devices before it edits.
- Screenshots and imagesocr reads text from screenshots, such as a build error from the editor, and gen_image saves real image files into your project folder.
- Orchestrationtask runs parallel sub-agents, run_on_model sends a hard step to a bigger model, and skill stores reusable playbooks, including a version-control skill.
- Approval modesAuto-run, Ask first and Plan only. Ask first pauses before every action that changes something; Plan only plans and changes nothing.
- Cronruns a prompt on a schedule, for example a weekly scan of your Verse files for leftover Print lines. Plans survive restarts.
- Modelsconnect a cloud AI provider, a model running locally on your PC, or the built-in model. The Test button shows response time and context window.
From a request to a reviewed diff
You type a request in plain words. The agent works through its tools, and each step appears as a card. The last card is a diff that you accept or reject.
Read build_error.png and fix the Verse error it shows.
- ocr
build_error.png1 error - read_file
reward_button.verse18 lines - grep
Granter3 matches - edit_file
reward_button.verse+1 -1 - grep
GrantItem1 match - read_file
reward_button.versediff ready
Waiting for your OK before the next stepRejectAccept
Two ways to use it
Learn Verse programming one device at a time
Open a .verse file you copied from a tutorial and ask SentryEdit what each line does. It uses read_file to see the whole class, explains creative_device, @editable fields and Subscribe in plain words, and can web_search Epic's documentation for the device you use. Ask for one small change, such as a second Print line, and watch the edit_file card. The app lists 1 file changed, so the effect stays small. Run Ask first, read the diff, build from the Verse menu and test in a live edit session.
Plan a storm device for one part of the map
A common question in Fortnite Creative is how to place a storm device so the storm covers only one part of the map. In Plan only mode SentryEdit reads your project folder, lists which devices and settings you would check in the editor and writes the steps into a checklist, without changing a thing. You then work through the 5 items inside the editor yourself. The agent can later read your Verse files and point out where the round logic touches that device. Review the checklist and test each step in the game.
What SentryEdit does not do
SentryEdit is a separate Windows app, not a plugin of Epic's editor. It never touches the Fortnite game client, servers it does not own, other players or their accounts. It cannot guarantee that code is correct, so review each diff and test in your project before you publish.
