RagLeapShort answer: v0.12.0 adds three things: optional folder auto-ingest (off by default), four roles with personal keys, and an audit log of who made each state-changing request. It is still single-tenant, has no single sign-on or multi-factor sign-in, and is not independently security reviewed. The channel and integration items are listed from merged pull requests and were not separately tested for this release.
Folder auto-ingest (off by default)
You grant a folder with a command run on the machine, for example ragleap files add /path --name docs --purpose knowledge. The sandbox copies the allowed documents (the 28 supported formats; no symlinks, no .env or keys, 25 MB per file) into a read-only staging volume, and the app reads new, changed and deleted files every 15 minutes. The first read of a folder waits for the owner’s approval, because embeddings can cost money; the Documents tab has a Folders card with an Approve button.
It needs COMPUTER_CONTROL=true, FOLDER_INGEST_ENABLED=true, a rebuilt sandbox image and db/schema.sql applied. Computer control is the part our roadmap page lists as experimental and off by default. Per the release notes, folder ingest was tested on one server with a small folder; Docker Desktop, rootless Docker and macOS are untested.
People, roles and audit
- Four roles: viewer, operator, admin and owner. Personal keys are shown once and stored as a hash, and every route has a role.
- The shared
RAGLEAP_API_KEYkeeps working and counts as the owner. - A person is recorded in every approval and in the activity log.
audit_eventsandGET /auditrecord who made each state-changing request. - The dashboard has tabs by role, a Users tab and an Audit tab.
What it does not do, per the release notes: the audit record says who called a route, not what they changed, and there is no single sign-on or multi-factor sign-in. It is still single-tenant: one deployment, one business.
Channels and integrations
The release lists a Meta WhatsApp Cloud API provider, Google Calendar event scheduling as an outbound action and HubSpot CRM record updates. The release notes say these items are listed from merged pull requests and were not separately tested for this release, so test them before relying on them.
Fixes and dependencies
The webhook, Slack and email senders no longer log exception detail. Pillow is 13.0.0 and pypdf is 6.21.1.
Upgrading
Apply db/schema.sql to existing databases (it is idempotent; back up first). Rebuild the sandbox image to use folder ingest. The documentation is built from this release.
Known limits
- Single-tenant. No single sign-on or multi-factor sign-in.
- The audit record says who called a route, not what they changed.
- Folder ingest was tested on one server with a small folder; Docker Desktop, rootless Docker and macOS are untested.
- The channel and integration items were not separately tested for this release.
- Not independently security reviewed. Pre-1.0: features may change.
Thanks
The release notes thank everyone who contributed since v0.11.1: @Nitjsefnie (Meta WhatsApp Cloud API provider, Google Calendar scheduling, HubSpot record updates, no exception detail in sender logs, Deepgram and ElevenLabs voice providers, Twilio-compatible audio, a Telegram webhook secret fix), @ahmet-izgi (voice number normalization for Turkish, Spanish, German and Italian, and the German README) and Yunare Maia (test coverage for the /chat role wiring). Full notes: v0.12.0 release notes.