ragleap-core v0.13.3 was published on 2026-11-14. Agents can now propose writing and deleting files, always with your approval and behind switches that are all off by default. The release also adds a signed core image and dependency fixes. Upgrading switches nothing new on. Source: the v0.13.3 release notes.
Can agents write and delete files now?
They can propose it. The new tools write_file (#1390) and delete_file (#1397) work only inside folders you grant with write access. The approval message and the dashboard show the real change (a diff, or the file's name, size and start). After approval exactly that change is made, and only if the file still matches what was previewed. Approval is needed also in full autonomy mode, and the file text never goes into the action log.
What happens to the old version of a file?
Old versions are kept in .ragleap-trash inside the folder. You list, restore or empty them on the machine with ragleap files trash list|restore|empty (#1396). The agent cannot reach the trash.
What do I have to switch on?
Everything is off by default. It needs the runner switch COMPUTER_CONTROL, ragleap files writing on on the machine, FILE_TOOLS_ENABLED and FILE_WRITE_ENABLED in the app (and FILE_DELETE_ENABLED for deleting), and a write grant. ragleap files add --mode write still refuses write grants on purpose.
Can I share a broad folder for a short time?
Yes, read-only (#1398). A home folder, /opt, /mnt, /srv or /media can be granted with ragleap files add PATH --name N --broad --for 2h (1 minute to 24 hours). Names that start with a dot or look like secrets are hidden. This is a check on names, not on content.
What changed in the core image and the dependencies?
A release tag now builds the image with provenance and SBOM attestations, signs it by digest with cosign (keyless), runs a Trivy scan in report-only mode and attaches a CycloneDX SBOM of the pinned Python packages to the release (#1405; see docs/supply-chain.md). Honest status: this workflow had one manual test run, and this is its first run on a real release tag. A signature says who built the image, not that it has no vulnerabilities. After the first image scan, requirements.lock got fixed versions of soupsieve, certifi, oauthlib, pyasn1, pypdf and setuptools (#1404, #1406, #1407).
What should I know before upgrading?
- No schema change and no new setting you must set. Rebuild and restart the app; the lock file changed, so the dependency layer is rebuilt (about 1 GB more free disk during the build). Pull a fresh base image when you build.
- The sandbox runner changed. Rebuild the sandbox image only if you want file writing, deleting or broad folders.
What is not covered yet?
- The outside security review (#800) has not happened. Keep file writing off in production until you have reviewed it yourself.
- Nothing here makes an installation compliant with any law or standard.
New guides: docs/file-access.md and docs/supply-chain.md. The release notes thank Paige Ortiz (CerTova AI) for the technical review that prompted the supply-chain work, and everyone who tested and reported. More: our release page and the roadmap.