Offline agent eval

[jluey1]

Why are these changes needed?

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.

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
10404662	Triggered	Generic CLI Secret	9a6ecfa2d0d2bb8189be8887ef29a71010f6dbfb	.github/workflows/dotnet-release.yml	View secret
10404662	Triggered	Generic CLI Secret	0e26a9ebd2b42dd4fbda5c279bad7726a7adc141	.github/workflows/dotnet-release.yml	View secret
10404662	Triggered	Generic CLI Secret	5a3969a855e006a36f0bfd96686d747f724fb7e5	.github/workflows/dotnet-release.yml	View secret
10404662	Triggered	Generic CLI Secret	7e64a96e131f34a3f2556bc4f2d52164627ca3f5	.github/workflows/dotnet-release.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 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.}

[WaelKarkoub]

Hi @jluey1! Do you have an issue that you are tracking or trying to resolve? If not and if you have time, do you mind updating the PR description, just to give us more context