Desktop simulators are powerful, stateful, and often difficult to automate safely. Reflux adapters keep the native simulator in charge while exposing controlled actions the agent can plan, run, and explain.
The adapter surface separates discovery from mutation: reading blocks, streams, and paths is ordinary context gathering; writing to a live case stays behind an explicit review boundary.
- Exposes simulator-specific reads, runs, and output parsing through a narrow API.
- Keeps adapter context visible in the Reflux UI and generated artifacts.
- Records supported commands and limits so reviewers know what happened.