Documenting code, one commit at a time.
When working on the josedantearroyo/dyad project, we encountered a classic testing challenge: environment variable leakage. As our suite grew, global test configurations began interfering with one another, leading to brittle end-to-end (e2e) tests that were difficult to debug, particularly when working with Azure service integrations.
As we continue to build out Dyad, a core requirement is ensuring that our AI agents can communicate effectively with external tools and data sources. We needed a standardized way to bridge our internal services with external intelligence models without creating rigid, brittle coupling.
We decided to adopt the Model Context Protocol (MCP) to standardize how our
Managing multiple AI providers in a single application often leads to configuration friction. In our work on the Dyad project, we recently tackled the complexity of our Azure OpenAI integration, moving away from fragmented settings toward a robust, UI-driven configuration workflow.
Previously, Azure configuration relied heavily on a mix of environment
