Redbird workshop

Keep building in code

If someone on your team can run a coding agent (e.g., Claude Code or Codex), you can download your fix as a folder of code and keep changing it for as many rounds as it takes.

The panel's AI writes a first version from one description, but getting a fix to work for a person usually takes several rounds. With the folder, you can ask the agent for one change at a time, look at the code, and run the tests after each change.

Get the folder

  1. Build a first version in the Build your adapter tab, the way Build your own says.
  2. Under your fix, open More and press Download the folder. The folder has the code of your last version, who it's for, and the conversation so far.
  3. Unzip it, open the folder in Claude Code or Codex, and say: "Read AGENTS.md and start the store."
  4. The agent gives you a link to the store on your computer, like http://localhost:5179/search?q=charger&try=local. Open it in Chrome. It's the same store and panel, but it runs the adapter from your folder, and the page runs it again each time the agent saves it.

To start from nothing instead, download a blank folder:

Note

The folder needs Node.js 18 or newer. If the agent says it can't find node, ask it to install Node.js.

Try it on a real website

With the folder running, install the Redbird panel extension, open a site in Chrome and click the extension's button (or press Alt+Shift+R). The page loads again with the panel and runs your adapter. Each time the file is saved, the page runs it again. Please stay signed out of the sites you try.

Chat with opencode in the panel

With opencode, you can chat with a coding agent right in the panel, on a real website or on the store on your computer. It runs inside the panel, so there's no other window to open and no key to add.

  1. Install Node.js 18 or newer, if you don't have it.
  2. In a terminal, run npm install -g opencode-ai. You only do this once.
  3. Get a folder, the way Get the folder says. You don't need Claude Code or Codex for this.
  4. In a terminal, go to that folder and run npm run dev. Leave it running. It starts opencode for you.
  5. Open a site with the panel on. If the site is already open, reload it, since the panel looks for your folder when a page loads.
  6. Open Build your adapter and say what should change. If you see Your folder with a chat box, you're using opencode.

Opencode reads the page and changes the adapter, then the page runs the new version. The first message usually takes a minute or two, and later ones under a minute. An adapter can look right to a test and still be wrong, so have someone check each change with their own tools.

Who does what

If someone on your team has the access need you're designing for, they should be the one testing each version. If not, one person on the team uses the store with the same tools the person would use (e.g., VoiceOver or only the keyboard).

  • The tester uses the store with their own tools (e.g., their screen reader) and says what's wrong, without needing to read any code.
  • The coder asks the agent for changes, and reads its answers out loud if the tester can't see the screen.

Each round

  1. The tester tries the page the way they would, and finds what's still wrong.
  2. The tester writes it under Your folder in the panel's Build your adapter tab and presses Add note for the coding agent (Point at it on the page adds the part of the page they mean). The note goes at the bottom of feedback.md in the folder, with the page's address.
  3. The coder tells the agent: "Read the new feedback and change the adapter."
  4. The agent changes adapter.js, runs the tests and says what to try next, and the page runs the new version by itself.

Tip

Ask the agent for one change at a time, using the tester's own words, for example "VoiceOver reads the rating twice" or "Tab never reaches Add to cart".

Test it

The agent runs npm test after each change. It opens the store's pages in Chrome in the background and writes test-report.md, which you can ask the agent to read to you. For each page, it says:

  • whether the adapter stopped with an error
  • which planted problems it fixes, using the same checks as the red and green badges
  • what it changed, and what a screen reader hears there with and without it
  • whether turning it off puts the page back

These tests check the store's planted problems, but not what your tester needs (e.g., whether they can Tab to Add to cart). For that, give the agent each check from your verification plan, like "VoiceOver reads each price as one number", and ask it to write the check in the checks folder so that npm test runs it on every page too.

Share it

In the panel, under Your folder, press Share it. The link opens your adapter on the live store, and you can paste it in the workshop chat the way Test it and share it says.