DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to rehearse a risky file change before it touches your folder with Bloks

Let an agent do a task on a copy of your folder, compare attempts, and apply only the one you want.

Who it is forA person who wants an agent to reorganise or edit files in a working folder but does not want the first attempt to land in the real folder.

The problemAn agent that edits the real folder directly can leave changes you did not expect, and sorting them out afterwards is slow.

The outcomeYou see the changes as a card with Apply and Discard, and applying writes only files you have not changed since the rehearsal started.

What you need first

  • The Bloks desktop app installed on your machine
  • At least one provider you can use: a Claude Code, Codex or Gemini CLI you already signed in to, or an API key for a chat engine
  • A project folder or files the agent is allowed to work in
  • For the iPhone steps: the Bloks iPhone app and a six digit pairing code from your Mac

Steps

  1. Describe the task to the agent in the message box, such as renaming and sorting the files in a folder.
  2. Press the flask beside the microphone so the agent works on an instant copy of its folder.
  3. Pick other agents in the same bar if you want them to rehearse the same task on their own copies.
  4. Compare the attempts side by side in the Rehearsals panel and read each change card.
  5. Press Apply on the attempt you want, or Discard to drop it; then undo from the card if needed.

Prompt for your agent

Using the Bloks repo at hamedgitty/bloks, rehearse the task <task-description> on a copy of the folder <target-folder> with the agent in Bloks. Expected output: a change card listing each changed file with its line count and diff, with Apply and Discard buttons. Verify that the real folder <target-folder> is unchanged until you press Apply.

Caveat. Rehearsals work on a copy of the folder, so anything the agent does outside that folder is not covered by the rehearsal.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page