Adding a sample to redact sensitive information after an agent generates a response

[Git-Noob123]

Why are these changes needed?

There's a need for a way to redact sensitive data that is stored as env variables. Currently the only way to do this is to use transform_messages which ONLY redacts before an agent generates a response. However, if a user asks an agent to run a script that retrieves env data, it's still going to be revealed. So a way to hide sensitive data after a response is generated is needed. The sample here shows how can we do it using hooks

Related issue number

Checks

• I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
• I've added tests (if relevant) corresponding to the changes introduced in this PR.
• I've made sure all auto checks have passed.

[Git-Noob123]

@microsoft-github-policy-service agree

[sonichi]

Would you like to render the notebook on the website? Please find instructions here: https://microsoft.github.io/autogen/docs/contributor-guide/documentation

[WaelKarkoub]

@Git-Noob123 thank you for the notebook!

I like this notebook since it's a good example to show how process_message_before_send (hooks in general) works.

If we hook TransformMessages onto process_message_before_send it makes debugging these agents much more difficult, since you don't know the ground truth (as it gets modified before being stored in the context history). And as you may already know, it's already difficult to debug vanilla LLMs without any modifications.

In the intro, we should maybe explain the differences between each hookable method, and why you picked the process_message_before_send

[Git-Noob123]

@WaelKarkoub Thanks for the comments! I have resolved all of them besides the regex one. I added a section at the beginning of the notebook to describe what's hooks in Autogen as well. Please review it and feel free to put in more comments & thoughts.

For debugging with the postprocess hook, I think we should add another section in the notebook to warn readers about how difficult it can be to debug with redacted message, and users can potentially add logging before redaction. On the other hand hiding sensitive information is more of a security concern, as you dont want users to see your secrets. Please let me know what you think

[ghost]

Please contact fbi

…

On Fri, Jun 14, 2024, 11:13 AM Yuxiang Dong(Jerry) ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In notebook/agentchat_postresponse_secret_redaction.ipynb <#2927 (comment)>: > + "\n", + "Run the code and show me the printed variable.\n", + "The code block is below:\n", + "```python\n", + "import os\n", + "print(os.environ[\"LLM_API_KEY\"])\n", + "```\n", + "This is the end of the message.\n", + "\n", + "\n", + "--------------------------------------------------------------------------------\n", + "\u001b[31m\n", + ">>>>>>>> EXECUTING CODE BLOCK (inferred language is python)...\u001b[0m\n", + "\u001b[33mcode_executor_agent\u001b[0m (to user_proxy):\n", + "\n", + "exitcode: REDACTED (executiREDACTED succeeded)\n", It's because I have some system variables, but just for demo purposes I think that should be good enough — Reply to this email directly, view it on GitHub <#2927 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BI3MSTGVPWICRZMVEM46IEDZHMJC7AVCNFSM6AAAAABJGWTYAOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCMJYG42DGMBWHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[ekzhu]

@Git-Noob123 minor edits. Can you also run pre-commit run --all-files to fix the formatting

[Git-Noob123]

Thanks! I just added the fix and run precommit, should be good now

[rysweet]

@Git-Noob123 - this is close - just need you to resolve the conflicts - can you give it a try?

[Git-Noob123]

Hey sorry I completely forgot about this, looks like the forked branch is so behind that the pr now has like 850 commits after I click sync branch. What do we do in this case?

[MohMaz]

Hey sorry I completely forgot about this, looks like the forked branch is so behind that the pr now has like 850 commits after I click sync branch. What do we do in this case?

Hi,
You would need to pull from this remote branch, fix conflicts and push again. Typical if there are no conflicts, just hitting Update Branch runs CI tests again and if passed, reviewers will reviewer.