DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to clean up a messy Blender scene from one message with Loopcut

Rename, sort, fix normals and purge orphans in one request, with each step approved first.

  • Top pick
  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Remote script. Loopcut writes and runs Python inside your open scene, so review each code step before approving it, especially on files you cannot easily recreate.

Who it is forA 3D artist or technical artist with a cluttered .blend file who needs naming, collections and mesh hygiene fixed before handoff or rendering.

The problemManual cleanup of names, collections, normals and unused data is slow and easy to get wrong across many objects.

The outcomeThe scene is renamed, sorted and cleaned, with a Scene changes card listing what was added, removed and changed.

What you need first

  • A Mac with Apple silicon or a 64-bit Windows PC (the README lists these builds)
  • An Anthropic key, an OpenAI-compatible key, a local model server such as Ollama, or a Loopcut hosted account
  • Blender scene files you are happy to let the agent modify, since each step runs Python in the open scene

Steps

  1. Download the latest build from the releases page (https://github.com/Samffprice/loopcut/releases/latest) and install it: drag Loopcut to Applications on macOS, or run the .msi on Windows.
  2. On first launch, choose Import Blender 5.2 Settings or Start Fresh, then connect a model in the panel.
  3. Open the Loopcut panel with ⌘ L on macOS or Ctrl Alt L on Windows.
  4. Type a request such as: Rename everything after what it is, put the lights in their own collection, and apply scale on everything.
  5. Approve each code step as it appears, or tell the agent to stop asking for this conversation.
  6. Read the Scene changes card, and use Undo all if the result is not what you wanted.

Prompt for your agent

Using the Loopcut add-on in the Samffprice/loopcut repo, ask the agent to rename objects in <path to .blend> by what they are, sort lights into their own collection, and purge orphan data. Expect a Scene changes card listing every added, removed and changed item. Verify that the card matches the outliner, and that Undo all restores the scene.

Caveat. The README says the builds are not yet signed, so macOS and Windows will each show a warning on first launch that you must click through.

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