ragleap-core v0.13.3
File permissions for agents (behind switches, all off by default), a signed and attested image, and dependency fixes. Upgrading switches nothing new on.
What changed in the app
- Agents can propose writing and deleting files, always with your approval. New tools
write_file(#1390) anddelete_file(#1397) work 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. Old versions are kept in.ragleap-trashinside the folder; you list, restore or empty them on the machine withragleap files trash list|restore|empty(#1396). The agent cannot reach the trash. Approval is needed also infullautonomy mode, and the file text never goes into the action log. - Everything above is off by default. It needs the runner switch
COMPUTER_CONTROL,ragleap files writing onon the machine,FILE_TOOLS_ENABLEDandFILE_WRITE_ENABLEDin the app (andFILE_DELETE_ENABLEDfor deleting), and a write grant.ragleap files add --mode writestill refuses write grants on purpose. - Broad folders, short and read-only (#1398). A home folder,
/opt,/mnt,/srvor/mediacan be granted withragleap files add PATH --name N --broad --for 2h(1 minute to 24 hours, read-only). Names that start with a dot or look like secrets are hidden. This is a check on names, not on content. - Runner and preview groundwork: #1357 and #1378.
Supply chain and dependencies
- Core image publishing (#1405). 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. See
docs/supply-chain.md. Honest status: this workflow had one manual test run; this is the first run on a real release tag. - Fixed versions in
requirements.lockafter the first image scan:soupsieve4.0.1 (#1404),certifi2026.10.18,oauthlib4.0.1,pyasn10.6.5,pypdf6.21.4 (#1406) andsetuptools81.0.0 (#1407, its bundled copies ofjaraco.contextandwheelwere flagged).
Documentation
New guides: docs/file-access.md and docs/supply-chain.md.
Upgrade notes
- No schema change, 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, so the system library fixes in it are included.
- The sandbox runner changed. Rebuild the sandbox image only if you want to use file writing, deleting or broad folders.
- 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, and a signature says who built the image, not that it has no vulnerabilities.
Thanks
Thanks to everyone who tested and reported, and to Paige Ortiz (CerTova AI) for the technical review that prompted the supply-chain work. Contributors are credited by name; tell us if you prefer not to be.