Group of 3 You'll notice
No documentation found
Artifact database reads can skip approval for recognized trusted sources, while writes outside the working folder are hard-denied with no approver present
What
read_dbcalls 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_dbcall is now allowed automatically with the message "Reading the database of ... needs no approval", skipping the usual prompt. - The equivalent
write_dbconsent 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.