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

How to batch-render sprites with Aseprite in headless mode with Aseprite AI Artist

Run Aseprite without a window so an agent can build a batch of assets in CI.

  • Content
  • Advanced
  • 60 minutes
  • From the README
  • Any agent

Who it is forA developer who maintains a build pipeline or a batch of game assets and needs sprites produced without someone watching a window.

The problemProducing many assets by hand, or keeping a desktop window open on a build server, does not scale.

The outcomeAn agent working against a headless Aseprite instance that saves files only when the agent chooses to save.

What you need first

  • Aseprite 1.3 or newer, open on your machine
  • Node 22.6 or newer
  • One supported agent: Claude Code, omp, OpenCode, Codex CLI, Gemini CLI, Cursor, VS Code or Windsurf

Steps

  1. Install Aseprite 1.3 or newer and Node 22.6 or newer on the machine that will run the batch.
  2. Run npx @pebbly/aseprite-ai-artist install-extension on a machine with a window if you need the extension installed.
  3. Start the server with npx @pebbly/aseprite-ai-artist serve --headless --aseprite /path/to/aseprite.
  4. Point your agent at the server and give it the asset list to draw.

Prompt for your agent

Using the aseprite-ai-artist server from with-pebbly/aseprite-ai-artist in headless mode, draw the assets listed in <asset list file> and save each one to <output folder>. Expected output: one saved .aseprite file per listed asset and no changes to any file your editor has open. Verify that each file is saved and that the agent asked before switching modes if the window was not attached.

Caveat. The README says headless mode is never a fallback, so if the window is not attached the agent asks rather than switching, which can stop an unattended batch.

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