Sicherheit
Credentials in tool output are blacked out before storage and before the model
A command like env could print a proxy password into the chat. Output of tools now passes a blackout step before it is stored or sent to a model provider.
On 27 October the command env printed a proxy address with a password inside into a chat. From there it went into the database and to the model provider. A blackout step now sits where a tool result turns into a chat message.
Text version
Tool output is checked before it becomes a chat message. Passwords inside addresses, proxy variables, values of names ending in secret or token, and unambiguous key formats are replaced. Chat history and the model provider only see the replacement.
This runs in normal chat turns and in background job runs. For vault entries there is a second net: the real values you saved, also as base64, hex or URL encoded text, are replaced in every request to a model provider.
It is pattern based. A secret in a format nobody could recognize, in a place the patterns do not cover, can still pass. Keep such values in the vault set to "use only", which keeps the real value out of the box altogether.
See the vault docs.