logo

Changelog 71: AI development with Replay and OpenHands

We show our prototype integration with OpenHands for reliable AI development
profile photo
Brian Hackett
We’ve developed a prototype tool for making frontend changes with an autonomous AI developer.  We are using OpenHands as our AI developer, and using Replay to provide the context needed to make changes reliably and validate the problem was fixed.
This flow greatly streamlines the process of frontend development. AI developers can make straightforward bug fixes and improvements, but have trouble understanding how large applications work, as we described in an earlier post. Using Replay to get over this hurdle allows the AI to handle even a complex new feature, by breaking it down into discrete tasks to solve with minimal guidance.
Image without caption
Configuration requires a couple new GitHub workflows in a project: one to ask OpenHands to generate a PR on issues containing Replay links when it gets tagged, and one to rerecord the provided Replay once the PR is created, to show the impact the PR has.
With these workflows in place, fixing a bug or making an improvement requires the following steps:
  1. Use the Replay browser to record the behavior which needs to change.
  1. Comment on the resulting recording to describe the change to make.
  1. File an issue with a link to the recording.
  1. Tag OpenHands in the issue.
  1. OpenHands uses Replay to get the additional context and generates a PR soon after.
  1. When a preview deployment is available for the PR, a new recording is generated of the same interactions to show the new behavior.
  1. The rerecording action comments on the PR with before/after screenshots showing the changes in the new recording.
This GitHub issue shows these steps for performing the same fix we studied in the earlier post.  We asked OpenHands three times to fix the issue and each time it produced a PR which the rerecording clearly shows is a suitable fix [1] [2] [3].
This video walks through the steps above for this issue.
We’ll continue to use this to develop Replay’s frontend and will have more to share soon.  If you’d like to try this out we’d love to hear from you, email us at hi@replay.io or fill out our contact form and we’ll be in touch.
Related posts
We share our plans on helping AIs resolve issues fully automatically
Over the past couple of years, JS frameworks like Next.js and Remix have gone full stack. We believe it’s time for DevTools to join the party!
We discuss a project for automatically fixing test failures
Powered by Notaku