Hosting and extensions
Run the summary-agent lesson’s interview and check its saved result before trying an extension. Keep a copy of the completed checkpoint for comparison.
To start a different application, use build your own agent. It separates the model connection and agent from the supplied workshop infrastructure.
Consider a different place to run the agents
Section titled “Consider a different place to run the agents”Use optional deployment to host the existing .NET services in Container Apps. Moving agent execution into a managed agent service is a separate implementation project; hosting architecture lists the decisions to make about runtime, identity, networking, and state.
Make record updates harder to misuse
Section titled “Make record updates harder to misuse”Try splitting document-field replacement from transcript append. Start with the existing update behavior and extension checklist, including repeated-call behavior. Change the repository, MCP schema, instructions, and tests together.
Add a tool before adding another specialist
Section titled “Add a tool before adding another specialist”A read-only competency catalog could give the technical interviewer more useful context. Give it a typed query and an authoritative data source, then inspect discovery and a real call.
Add a specialist when its responsibility needs separate instructions or tool access and you can define a clear route to it. Review service-boundary access controls for any tool that reads user records.