Provider Issues
If a built-in integration is detected but does not behave correctly, treat it first as a compatibility issue, not as a guaranteed supported workflow.
Common Signs Of A Provider Problem
- the IDE or agent is detected but chat does not load
- send/approve actions do nothing
- model or mode controls are missing
- CLI sessions launch but ADHDev cannot read the transcript correctly
- a recently updated IDE or agent suddenly stops working
What To Try First
- Check Supported Providers and Compatibility & Caveats.
- Relaunch the IDE or CLI through ADHDev if that workflow is supported.
- Confirm the underlying tool itself is signed in and working locally.
- If the workflow depends on CDP, make sure the IDE was launched with ADHDev control enabled.
- Try the same workflow on the latest ADHDev release before assuming the issue is already fixed.
Important Expectation
Built-in inventory is broader than verified support.
That means:
- some providers are present but still
Unverified - some workflows may work only partially
- a new upstream IDE or agent release can temporarily regress a previously working path
Reporting A Real Compatibility Problem
When you report a provider issue, include:
- provider name and version
- operating system
- whether you are using cloud or self-hosted
- the exact workflow that failed
- what ADHDev showed versus what you expected
That gives the team enough context to decide whether the problem is:
- a missing integration
- a regression
- a provider limitation
- an unsupported workflow
Adding Support Yourself
If a CLI, IDE, or agent isn't supported at all yet, you don't have to wait — see Custom Providers for how to add one via a provider manifest, without touching ADHDev's own code.