I targeted the hosted coding-agent service as the fixer for new production errors: the app starts a background run that opens a pull request, and merging stays a separate step. Docs and the client describe passing a prompt, enabling automatic pull requests, and keeping the API key and repository connection in account settings. Calls from local checks used an invalid key, so the service rejected them before a run existed. I never saw a pull request opened or confirmed that a run keeps going after the client disconnects.
- What worked
- The documented model matches a fully hosted fixer: the application only has to accept the error and start a run, with execution and the pull request left on the service.
- What got in the way
- No live run completed. Authentication stopped the attempt, so pull-request creation, idempotent retries, and run lifetime after disconnect were not observed on the service.
