Skip to main content
By default, SoloEnt asks you to approve every action it takes—reading files, saving content, browsing the web. Auto-approve lets you skip those confirmation prompts for actions you trust. Auto-approve settings panel showing checkboxes for Read project files, Edit project files, Execute safe commands, Execute all commands, Use the browser, Use MCP servers, and Enable notifications Most writers do well with this baseline:

Always enable

Read project files — lets SoloEnt read your chapters, outlines, and character sheets without asking each time

Enable if you want SoloEnt to save

Edit project files — lets SoloEnt write content directly to your files, so nothing gets lost

Enable for workflows

Execute safe commands — workflows rely on commands to run and save their reports automatically

Enable for research

Use the browser — lets SoloEnt look up facts, names, or references while you write
Execute all commands and Use MCP servers are not needed for writing work — leave them off.

What each permission does

PermissionWhat it means for writers
Read project filesSoloEnt can read your chapters, outlines, and character sheets as context
Read all filesSoloEnt can read files outside your project folder
Edit project filesSoloEnt saves generated content directly to your files
Edit all filesSoloEnt can edit files outside your project folder
Execute safe commandsPowers workflows — reads project files, runs the workflow, and saves reports to the required location
Execute all commandsRuns any system command — not needed for writing
Use the browserSoloEnt can look up information online while helping you write
Use MCP serversAdvanced tool integrations — not needed for most writers
Enable notificationsSends an alert when a long-running task finishes
“Read all files” and “Edit all files” only extend access outside your project folder. If the base toggle is off, these sub-options have no effect.

Common writing scenarios

Enable Execute safe commands. SoloEnt’s built-in workflows (like /review for chapter quality checks and /marketing for publishing strategy) need this permission to read your project files, run the workflow, and save reports to the notes/ folder. Without it, every step pauses for manual confirmation.
Enable Edit project files. SoloEnt saves content directly to your files as it generates—you won’t lose work if you close the window or something interrupts the session.
With edit access enabled, SoloEnt can overwrite existing content. Review changes carefully, and use the chat history to recover anything unexpected.
Enable Use the browser. SoloEnt can look up historical facts, place names, terminology, or any reference material without you having to switch tabs.
Leave everything off. SoloEnt can still talk through ideas, suggest plot directions, and help you think—it just won’t read or touch your files unless you paste content directly into the chat.
Enable Enable notifications. You’ll get an alert when the task finishes, so you don’t have to keep checking back.

Next steps

Interface overview

Learn the three-panel workspace

API configuration

Set up your API keys