[Antriksh Jain (antriksh30)]

Summary

• migrate the BYO Activity echo and github-copilot hosted runtimes from requirements.txt to pyproject.toml, uv.lock, and uv.toml
• update both Python 3.13 containers and local debugging guidance to use frozen uv environments while preserving every original direct dependency
• keep Starlette transitively managed by AgentServer and avoid a global prerelease policy; the explicit Activity beta pin resolves without it
• preserve the Copilot sample's intentional runtime pip capability for model-generated Office and PDF files

Validation

• uv lock --check and frozen production export for both projects
• built both container images and verified their /app/user_agent/.venv/bin/python commands
• imported the Activity host in both images and the Copilot SDK stack in the assistant image
• verified runtime pip remains available in the Copilot image
• Python source compilation and dependency declaration parity checks
• hosted-agent dependency policy with --resolve
• hosted-agent contract policy
• git diff --check

[Copilot]

🟢 Approval recommended

The migration follows the repository’s uv dependency policy, with only minor capitalization corrections noted.

2 open findings

• Capitalize Microsoft product name “Foundry” · New
• Capitalize Microsoft product name “Foundry” · New

What changed in this PR

Migrates both BYO Activity samples to reproducible uv-managed Python 3.13 environments.

Changes:

• Replaces requirements.txt with pyproject.toml, uv.lock, and uv.toml.
• Updates containers to install and run from frozen uv environments.
• Refreshes local-development documentation and prerequisites.

File	Description
github-copilot/​AGENTS.md	Documents uv workflow and project files.
github-copilot/​README.md	Updates prerequisites and debugging steps.
github-copilot/​src/​github-copilot-activity/​.env.example	Updates the local-run command.
github-copilot/​src/​github-copilot-activity/​Dockerfile	Builds and runs from the uv environment.
github-copilot/​src/​github-copilot-activity/​pyproject.toml	Declares project dependencies.
github-copilot/​src/​github-copilot-activity/​requirements.txt	Removes the legacy dependency manifest.
github-copilot/​src/​github-copilot-activity/​uv.lock	Locks the resolved dependency graph.
github-copilot/​src/​github-copilot-activity/​uv.toml	Enables system certificates for uv.
echo/​AGENTS.md	Documents uv workflow and project files.
echo/​README.md	Updates prerequisites and debugging steps.
echo/​src/​echo-activity/​Dockerfile	Builds and runs from the uv environment.
echo/​src/​echo-activity/​pyproject.toml	Declares project dependencies.
echo/​src/​echo-activity/​requirements.txt	Removes the legacy dependency manifest.
echo/​src/​echo-activity/​uv.lock	Locks the resolved dependency graph.
echo/​src/​echo-activity/​uv.toml	Enables system certificates for uv.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🔵 Needs a closer look

Both READMEs describe F5 workflows backed by VS Code configuration files that are not present.

0 open findings

2 resolved since last review

• Capitalize Microsoft product name “Foundry”
• Capitalize Microsoft product name “Foundry”

Previously missed (2)

In code that hasn't changed since last review

Missing VS Code launch and task configurations

samples/​python/​hosted-agents/​bring-your-own/​activity/​echo/​README.md:101

The repository contains no src/echo-activity/.vscode/launch.json or tasks.json, so pressing F5 cannot start the agent with this uv environment or launch/clean up Agents Playground as described. Please either commit those configurations with the .venv interpreter or replace this section with the actual manual launch workflow.

Missing VS Code debug configurations

samples/​python/​hosted-agents/​bring-your-own/​activity/​github-copilot/​README.md:169

src/github-copilot-activity has no committed .vscode/launch.json or tasks.json, so this directory will not show the promised configuration and the later F5/pre- and post-debug behavior cannot occur. Please add the referenced configurations with the uv interpreter or document a manual launch workflow instead.

🧠 Review effort: Balanced