Under the hood
Artifact "always allow" consent checks now use a different lookup depending on whether a person or something else answered
What
When Claude Code checks whether a previous "remember: always allow" decision covers a new artifact write or store request, it now looks at who gave that original consent. If a person answered, it uses one lookup helper; if the answer came from something else, such as an automated classifier, it uses a different one.
Why
Separating the two paths means consent given directly by a person is tracked separately from consent inferred automatically, which matters for making sure "always allow" only kicks in where it's actually safe to skip asking again.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It's unclear what practical difference the two lookup helpers produce beyond using separate storage.