Try ideas without risking your project

Make save points with commits

A commit is a saved version of your project with a short description. Once a version is committed, an agent can bring it back later.

• Ask for commits when something works. “That works. Commit it with a short description.” To make it a standing habit, add a rule to your project’s Instructions, like the example Enjoy suggests there: “commit changes after every change.”
• See what changed. When an agent commits, its final reply shows View changes. Open it to see each changed file, as Changes or Before / after.
• Go back by asking. “Undo the changes from your last commit,” or “Put the homepage back the way it was before the newsletter change.” The agent uses your commits to do it.
• Keep a copy online. If your project is connected to a service like GitHub, open the branch button in the message box and select Push to upload your commits. See Push your branch.

If your project doesn’t use Git yet, ask: “Set up Git for this project and commit everything as a first version.”

Try bigger ideas in a worktree

Enjoy describes a worktree as “a copy of your project where an agent can try an idea, like a new look or a new page, without changing the original.” As long as your project uses Git, there’s nothing to set up.

1. Ask for one. “Try a dark mode in a new worktree.” The conversation keeps going in the copy, with everything the agent already knows. A band at the top of the message box reads Working in, followed by the worktree’s name.
2. Check the result. Ask the agent to show you the copy in the preview.
3. Keep it. Ask the agent to commit its work in the worktree first. Then select Merge into and your project’s name, in the band, and confirm with Merge. Only committed changes are merged, and the dialog says so if any aren’t. Leave Delete the worktree after merging selected to tidy up.
4. Or drop it. Select the trash button, Delete worktree, and confirm. The conversation moves back to the main project folder. Uncommitted changes in the copy are lost, and Enjoy warns you first.

Merging and deleting worktrees work in the computer app. If both versions changed the same files, Enjoy shows Both versions changed these files and offers Ask the agent to merge.

An example

“Try a calmer color scheme for the whole site in a new worktree. Commit it when you’re done and show me the preview.” You compare it with the original. You like it, so you select Merge into your project. If you hadn’t, you’d select Delete worktree and your project would be exactly as before.

Common pitfalls

• Going hours without a commit. The longer the gap, the more there is to untangle when something breaks.
• Merging before the agent commits. The merge leaves uncommitted files out. If you also delete the worktree, they’re gone.
• Running two experiments on the same files in the main folder. Each conversation edits the same files directly, so they can undo each other’s work. Give each experiment its own worktree. OpenAI’s Codex guide lists “running live tasks on the same files without using Git worktrees” as a common mistake.
• Uncommitted changes in your main project. Enjoy asks you to commit them before it can merge a worktree in. Ask an agent to commit them.