Every artifact database write in a Cowork session asks you; automatic approval cannot cover it.
What's wrong with this entry?
Writing to the artifact database from a Cowork session is now a safety check that the automatic permission classifier is not allowed to approve on your behalf. Previously only the first write in a session, and a stricter prompt in plan mode, needed confirmation.
- Applies only when the session is a Cowork session; other sessions keep the existing first-write confirmation.
- The reason given is that these writes are durable changes to shared state.
Artifact database writes from a Cowork session are durable shared-state changes
Strings lifted out of the shipped bundle, so the claim above can be checked against them.