thangchung/agent-engineering-experiment

Repository Shape and Entry Points

This is a workspace of independent samples/prototypes, not one deployable application; the root README is empty and there is no root solution. Each top-level project owns its runtime and deployment model. Primary .NET entry points include DotNetClaw/DotNetClaw/Program.cs, foundry-agentfx/apphost.cs, loop-runtime/src/LoopRuntime.AppHost/Program.cs, mcp-experiments/src/AppHost/Program.cs, and context-engineering-dotnet/src/ContextEngineering.Api/Program.cs. A separate Next.js storefront starts from myshop-claude-code/app/page.tsx.

Agent Runtime and Channel Pattern

DotNetClaw is a compact agent host: a runtime loads agent “mind” instructions and exposes Slack and web channels. Its core control path is host startup → runtime → tools/memory/skills → channel response.

• Runtime and telemetry: DotNetClaw/DotNetClaw/ClawRuntime.cs, DotNetClaw/DotNetClaw/ClawTelemetry.cs

• Input/output boundaries: DotNetClaw/DotNetClaw/SlackChannel.cs, DotNetClaw/DotNetClaw/WebChannel.cs

• Agent state/prompt assets: DotNetClaw/DotNetClaw/mind/SOUL.md, DotNetClaw/DotNetClaw/mind/.working-memory/memory.md

Foundry Coffeeshop Distributed Agent

foundry-agentfx decomposes the same broad pattern into services: channels route requests to an agent; the agent invokes a coffeeshop workflow and discovers tools through a gateway; an MCP service implements coffeeshop operations.

• Agent execution: foundry-agentfx/src/Claw.Agent/Program.cs, foundry-agentfx/src/Claw.Agent/Agents/CoffeeshopWorkflow.cs

• Channel-to-agent client boundary, including local versus Foundry-backed clients: foundry-agentfx/src/Claw.Channels/Program.cs, foundry-agentfx/src/Claw.Channels/FoundryAgentClient.cs

• Tool search/registration: foundry-agentfx/src/ToolSearch.Gateway/Program.cs, foundry-agentfx/src/ToolSearch.Gateway/Registry/ToolRegistry.cs

• MCP business tools: foundry-agentfx/src/Coffeeshop.Mcp/Program.cs, foundry-agentfx/src/Coffeeshop.Mcp/Tools/OrderTools.cs

Azure Foundry, Azure AI Search, Storage, Application Insights, Log Analytics, Container Apps, and container registry are provisioned through foundry-agentfx/infra/main.bicep.

Agent Gateway with OBO Identity

agentgateway-entraid-obo is a Todo-oriented reference architecture for delegated identity across API, agent, MCP server, and gateway. The Todo API accepts client requests and delegates through an IAgentGateway; the agent uses an LLM description generator and an MCP todo sink; the MCP service persists todos via EF Core.

• Public API/gateway adapters: agentgateway-entraid-obo/src/AgenticTodo.TodoApi/Program.cs, agentgateway-entraid-obo/src/AgenticTodo.TodoApi/Adapters/OboAgentGateway.cs

• Agent domain and feature orchestration: agentgateway-entraid-obo/src/AgenticTodo.TodoAgent/Features/CreateTodo/CreateTodoHandler.cs, agentgateway-entraid-obo/src/AgenticTodo.TodoAgent/Adapters/Mcp/McpTodoSink.cs

• MCP persistence boundary: agentgateway-entraid-obo/src/AgenticTodo.TodoMcpServer/Adapters/TodoDbContext.cs, agentgateway-entraid-obo/src/AgenticTodo.TodoMcpServer/Tools/TodoTools.cs

• Gateway policy/configuration: agentgateway-entraid-obo/gateway.yaml

Iterative Executor–Checker Runtime

loop-runtime implements an agent loop: an executor agent works with local/remote MCP tools and a code sandbox; a checker service evaluates output over A2A; shared contracts carry feedback, verdicts, and run results.

• Agent loop state and roles: loop-runtime/src/LoopRuntime.Agents/ExecutorAgent.cs, loop-runtime/src/LoopRuntime.Agents/CheckerAgent.cs, loop-runtime/src/LoopRuntime.Agents/SessionState.cs

• Checker service/A2A boundary: loop-runtime/src/LoopRuntime.Checker/CheckerA2AEndpoint.cs, loop-runtime/src/LoopRuntime.Checker/CheckerAIAgent.cs

• Tool and execution isolation: loop-runtime/src/LoopRuntime.Mcp/Program.cs, loop-runtime/src/LoopRuntime.Sandbox/DockerSandbox.cs

• Cross-service types: loop-runtime/src/LoopRuntime.Contracts/ICodeSandbox.cs, loop-runtime/src/LoopRuntime.Contracts/Verdict.cs

It uses Docker for sandboxing and includes Entra agent-identity/OBO setup scripts.

MCP and Context Infrastructure Experiments

Two projects supply reusable patterns around MCP.

• mcp-experiments turns OpenAPI operations into registered/searchable tools and can execute generated code through local, Hyperlight, or OpenSandbox runners: mcp-experiments/src/McpServer/Program.cs, mcp-experiments/src/McpServer/OpenApi/OpenApiToolCatalogBuilder.cs, mcp-experiments/src/McpServer/CodeMode/SandboxRunnerFactory.cs.

• context-engineering-dotnet provides conversation/scratchpad persistence, token counting, and context reduction behind API and MCP-server hosts: context-engineering-dotnet/src/ContextEngineering.Infrastructure/Data/AppDbContext.cs, context-engineering-dotnet/src/ContextEngineering.Infrastructure/Services/SummarizingChatReducer.cs, context-engineering-dotnet/src/ContextEngineering.McpServer/Program.cs.

Most .NET distributed projects use Aspire AppHosts and shared ServiceDefaults for local orchestration, service discovery, resilience, and telemetry.