You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add a --report-dir option and config setting for report output #2071
BaseReporter writes reports to a relative file name, so they always land in Dev Proxy's current working directory. To control where reports go, all five agent-written CI scripts spawned Dev Proxy with cwd set to an output folder. That also changes how relative config paths and devproxyrc.json discovery resolve, so every script needed extra absolute-path handling.
Proposal
Add --report-dir <path> and an equivalent reportsFolder setting in devproxyrc.json, resolved relative to the config file. Every reporter honours it, and the default stays the working directory.
Found while evaluating how coding agents use Dev Proxy: VS Code + GitHub Copilot Chat with Claude Sonnet 5.5, Dev Proxy 4.0.0 on Windows, 5 runs of the task "add a CI script that starts Dev Proxy in the background, starts and stops recording through the API around npm start, and shuts Dev Proxy down through the API".
Activity