read_db/write_db approval logic gains a trusted-source shortcut and a hard deny for unapproved out-of-folder writes
Artifact database reads can skip approval for recognized trusted sources, while writes outside the working folder are hard-denied with no approver present
Group of 3You'll noticeNo documentation foundImprovements
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Artifacts DBArea: what it touches
ImprovementsKind: in v2.1.268,
ImprovementsSection of the release
What
read_db calls now hard-deny outright when they would save documents outside the session's working folders and there's no human present in the session to approve it, returning a dedicated safety-check reason instead of prompting.
A new helper can recognize an artifact's slug as coming from a pre-trusted, known source; when it does, a read_db call is now allowed automatically with the message "Reading the database of ... needs no approval", skipping the usual prompt.
The equivalent write_db consent check was extended to treat the same trusted-source signal as already-consented, in addition to the existing per-session consent flags.
Why
This reduces unnecessary approval prompts for artifact database reads/writes that Claude Code already knows are safe, while closing a gap where a write outside the session's own folders could otherwise proceed unapproved when nobody is around to confirm it.
