Skip to content
WorklettoHelp

Change Workletto with an AI coding assistant

Applies to Workletto 1.x.

You can change anything in your copy of Workletto. You don’t need to be a developer: an AI coding assistant can make the change in your private GitHub repository and propose it as a pull request, a change you can check before it goes live.

Two ways to ask, both in the browser:

  • Claude Code on the web (claude.ai/code), from Anthropic.
  • Codex (chatgpt.com/codex), from OpenAI.

Both need their own account, which you pay for with the company that makes it. Workletto doesn’t charge for them.

Before you start

Section titled “Before you start”
  • Take a backup. Open Manage, then Security & data, and under Backup click Download backup. See Back up and restore.
  • Know where your copy is: the private GitHub repository you made with Use this template when you installed Workletto.

Make a change

Section titled “Make a change”

  1. In the assistant, connect your GitHub account and choose your Workletto repository.

  2. Describe the change in plain words. For example: “Add a phone number to clients, shown on the client page and in the client export.”

  3. The assistant reads the code, makes the change and opens a pull request. Your copy includes instructions just for AI assistants (the AGENTS.md file): how the app is built and the rules the code has to follow, such as keeping each organization’s data apart and storing money in whole cents.

  4. On the pull request, the Test check runs by itself: the type check, the server tests and a build. Wait for a green tick. If it fails, ask the assistant to fix it.

  5. Read the assistant’s summary of what it changed. If you want, ask it to explain any part in plain words.

    Click the picture to zoom in.
    A pull request in your copy: the summary of what changed, the Test check passed, and the Merge pull request button

  6. Click Merge pull request. On Render your app updates by itself within a few minutes; most other hosts do the same. With Docker Compose on your own server, run git pull and then docker compose up -d --build there.

  7. Open your app and try the change.

If something isn’t right

Section titled “If something isn’t right”
  • Before merging: ask the assistant to change it, or close the pull request. Nothing changed in your app.
  • After merging: open the pull request on GitHub and click Revert, then merge the pull request that creates. Your app goes back to how it was.
  • If the change added to the database (a new field or table), reverting the code doesn’t remove what it added. If something went wrong with your data, restore the backup you took first.

Updates keep your changes

Section titled “Updates keep your changes”

New versions of Workletto arrive as a pull request in your copy: you run the Update app workflow from your repository’s Actions tab (see About, versions and diagnostics). It merges our changes with yours. If GitHub reports a conflict, where we and you changed the same lines, ask your AI assistant to merge the update and keep both sets of changes.

Small, focused changes make updates easiest. The AGENTS.md file asks the assistant to change only what you asked for.

Good to know

Section titled “Good to know”
  • An AI assistant can be wrong. The tests can miss problems. Check the change in your app before relying on it, especially anything about money, permissions or who can see what.
  • Your changes stay in your copy. Workletto’s own updates won’t overwrite them, but we can’t test them, so when something goes wrong in a part you changed, start by reverting your change.