Saeta is in development and has no public release yet. This page describes the current development build and our plans.
Folders outside your project
In safe auto mode, a call that reads, edits or names a place outside the project asks you. Agents often need a few such places: the temporary folder for a screenshot, their own working folders, a build cache. You can let safe auto mode count those folders as inside the project.
An allowed folder answers nothing on its own. It only stops "outside the project" from being a reason to ask. Every other question still applies there: deleting files, a push, an agent's hook settings, secrets, Saeta's own files. Saeta's blocks still block. Outside safe auto mode, an allowed folder changes nothing.
Built-in groups
Saeta ships three groups of folders. You switch them on or off, everywhere or for one project. You can't edit what's in them; a new version of Saeta can change them, and the release notes say so.
| Group | At first | What it covers |
|---|---|---|
| Temporary folders | On | The system's temporary folders |
| Agent working folders | Off | Each agent's data folders, for every agent at once |
| Build and package caches | Off | Package downloads, to read only |
Temporary folders
| Linux | macOS | Windows |
|---|---|---|
$TMPDIR, /tmp, /var/tmp | the same, plus /private/tmp, /private/var/folders | %TEMP%, %TMP%, %LOCALAPPDATA%\Temp |
Agent working folders
The same folders on every system, under your home folder (~, or %USERPROFILE% on Windows):
| Agent | Folders |
|---|---|
| Claude Code | ~/.claude/projects, ~/.claude/todos, ~/.claude/plans |
| Codex | ~/.codex/sessions, ~/.codex/worktrees, ~/.codex/log |
| Cursor | ~/.cursor/projects/*/agent-transcripts, ~/.cursor/projects/*/terminals |
| Gemini CLI | ~/.gemini/tmp, ~/.gemini/history |
| Qwen Code | ~/.qwen/tmp, ~/.qwen/history |
| Pi | ~/.pi/agent/sessions |
| OpenCode | ~/.local/share/opencode/log, storage and tool-output in the same folder |
It deliberately leaves out everything that configures an agent or runs later: settings, hooks, plugins, extensions, skills, commands, rules, tools and config files, Claude Code's shell snapshots (which it runs before each command), and OpenCode's ~/.config/opencode, its sign-ins (auth.json) and its snapshots (git folders). In Cursor it leaves out canvases, which are code Cursor renders, and MCP instructions, which steer it. Writing into any of those still asks, in the home folder and in a project.
Codex's worktrees are working copies of your repositories. Their build files and scripts run when you build there, as in any project.
Build and package caches
These are read only: an agent may look in them without asking, but writing to them still asks, because what's there runs in your next build.
| Folder | Systems |
|---|---|
~/.cargo/registry, ~/.cargo/git | All |
~/.gradle/caches, ~/.m2/repository | All |
~/.npm/_cacache, ~/go/pkg/mod | All |
Your cache folder: $XDG_CACHE_HOME or ~/.cache on Linux, ~/Library/Caches on macOS | Linux, macOS |
Not in the group at all, even to read: ~/.rustup and ~/.gradle/wrapper (the tools that run your builds), ~/.npm/_npx (what npx runs) and ~/.pnpm-store (linked into projects). On Windows the cache folder would be %LOCALAPPDATA%, which also holds installed programs, so it is left out.
When a variable a folder needs isn't set, that folder counts for nothing. A missing variable never widens a group.
This session, this project, everywhere
Besides the groups, you can allow a folder of your own, with one of three reaches:
- This session: for one agent session. Kept in memory only, never saved. It ends when Saeta restarts, or after 24 hours.
- This project: for requests from that project. Saved as the project's group in the Trust List.
- Everywhere: for every project. Saved in the "Outside folders" group.
Built-in groups have the same choice of everywhere or one project. What a project says wins for that project, so a group can be on everywhere and off for one project.
The setup question
When you turn safe auto mode on for a project, in the desktop app or with saeta auto on, Saeta asks which folders outside it the project may use. Temporary folders is checked, Agent working folders is checked when an agent is connected, Build and package caches is not. A group that is already on everywhere stays checked. If the project has an earlier answer, the boxes show that instead. Add your own folders too, then save or skip; you can change it later in the Trust List or with saeta groups. Saving records every box for this project, so a later change everywhere doesn't reach it. Skipping changes nothing.
In a terminal, a number switches an item, a path adds a folder, Enter saves and s skips. saeta auto on only asks when a person is there, with a terminal for both input and output. From a script or an agent it asks nothing, changes no folders and prints how to choose. It doesn't ask when safe auto mode was already on for the project. Groups your organisation has set are shown and can't be changed, and if that is all of them there is no question. Turning off folder grants locks all of them.
Allow a folder from a request
When safe auto mode asks because a call leaves the project for one folder, Allow can also allow that folder: for this session, in this project, or everywhere. If the folder is in a built-in group that is off, it also offers to turn that group on for this project. The folder offered is the git top-level of the place, or else its nearest folder.
From a terminal
saeta groups # every group and its folders
saeta groups on builtin.build-caches # everywhere
saeta groups off builtin.temp --project ~/Code/app # one project
saeta folders allow ~/Pictures/shots --project ~/Code/app
saeta folders allow /data/fixtures --everywhere
saeta folders allow /tmp/run-42 --session <session-id>
--project takes a folder in the project. saeta status lists the agent sessions of the last day with their ids. When an agent runs these commands, Saeta asks you first.
What can't be allowed
- Your home folder, the filesystem root, or a folder above your home.
- A whole folder that holds an agent's hook settings or Saeta's files, or a folder above one:
~/.claude,~/.codex,~/.cursor,~/.gemini,~/.qwen,~/.pi,~/.config/opencode,~/.saeta, so not~/.configeither. That holds through symbolic links too: if~/.claudelinks into~/dotfiles,~/dotfilescan't be allowed. Otherwise copying a file into the folder could replace the settings that make the agent ask Saeta.
On a managed computer, an organisation can turn off your folder grants and set the built-in groups itself; see For administrators.