devflow-connect

Diagnose DevFlow agent connectivity failures between the maui CLI and .NET MAUI apps.

209|27|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dotnet/maui-labs --skill devflow-connect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devflow-connect
Source: https://github.com/dotnet/maui-labs/tree/main/plugins/dotnet-maui/skills/devflow-connect
Command: npx skills add https://github.com/dotnet/maui-labs --skill devflow-connect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It diagnoses why the DevFlow agent inside a running .NET MAUI app is not reachable from the maui CLI, preventing commands like listing agents or fetching the visual tree.

Core Features & Use Cases

  • Broker and agent reachability checks: validates broker status, discovers connected agents, and tests agent connectivity with a shallow tree request.
  • Platform-specific troubleshooting: handles Android emulator networking via adb forwarding/reverse, while using direct localhost checks for iOS/macOS/Windows/Linux.
  • Common failure recovery paths: guides users through resolving missing agent integration, broker not running, port conflicts, and “connection refused/cannot connect to agent” scenarios.

Quick Start

Run maui devflow list to confirm whether any DevFlow agents are visible before applying connectivity fixes.

Frequently Asked Questions about devflow-connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does the maui CLI show a "Cannot connect to agent" error?

The "Cannot connect to agent" error occurs when the DevFlow agent inside a running .NET MAUI app is unreachable from the maui CLI. This usually stems from a missing DevFlow agent NuGet integration, the broker not running, or blocked ports.

How do I fix Android emulator connectivity issues with the maui CLI?

Fix Android emulator connectivity by verifying and reconfiguring adb forwarding or adb reverse settings. The troubleshooting process diagnoses misconfigured emulator networking and applies platform-specific port tests to restore access to the DevFlow agent.

What should I check if my DevFlow agents are missing from the maui CLI?

If DevFlow agents are missing, first run the command "maui devflow list" to confirm visibility. You should then validate the broker status, verify the DevFlow agent NuGet initialization, and check for port conflicts blocking broker discovery.

How do I test broker reachability for a .NET MAUI app?

Test broker reachability by validating the broker status, discovering connected agents, and sending a shallow visual tree request. This verifies agent connectivity and helps isolate whether the failure is a network port block or an initialization issue.

Does fixing DevFlow connectivity require different steps on iOS and Windows?

Yes, troubleshooting adapts to the platform. Android requires adb forwarding and reverse configurations for emulator networking, while iOS, macOS, Windows, and Linux rely on direct localhost checks to resolve agent connection issues.

What is the best way to resolve port 9223 conflicts during DevFlow agent discovery?

Resolving port 9223 conflicts involves running platform-specific port and connectivity tests to identify the blockage. The recovery process guides you through clearing the port conflict and restarting broker discovery to restore interactive tooling access.