Livebound 1.0 — From local to live.

(Update: Add screenshots at the end, add shop info)

I will keep this one short. Yesterday I sat down to write about my drive having no idea what I have posted and could not get my fingers off the keyboard. Full disclosure: that piece was not really about lost images. It was me checking whether anyone else has the same problem, one day before shipping what I built about it.

Don't believe a word of it and just want the thing? → GitHub · Documentation

Still here? Good.

Livebound is a local-first workspace for everything between "the render finished" and "the post is live". One process, one browser tab, on your own machine. It reads the folders you already have and publishes to CivitAI from your own account over OAuth. Your images stay where they are, and your original files are never rewritten.

The idea

Making the images is the fun part. Everything after it is bookkeeping. Did I already post this one? What model was this? The metadata says a hash and nothing else. Was this picture in a post three weeks ago? Can I line up a week of posts on a Sunday instead of remembering every evening?

None of that needs a cloud service. It needs something that reads your folders, keeps notes and talks to CivitAI when you tell it to. That is the whole thesis: your folders are the source of truth, CivitAI is the destination, and the boring middle gets automated.

Three ways to use it

New posts. Library → new post → editor (metadata, tags, publishing options) → Ready → push to CivitAI. With drafts, scheduling, a calendar and preflight checks that run before anything leaves your machine.

Existing posts. Find your own posts on CivitAI, adopt them, match them back to your local files and keep both sides in sync. Your back catalogue is not left behind.

Archive. Once a post is verified published, an archive run moves those files into a dated folder. Explicit, and never automatic.

Along the way: exact and perceptual duplicate detection with a recoverable trash, a full metadata and resource review before upload (models, LoRAs, prompts, with per-image exclusions), bulk editing and optional writing help from a local language model or an Ollama server on your own hardware.

One thing worth naming: several generators write metadata CivitAI has no parser for, and those images arrive on the site with nothing attached. Livebound brings that into the shape the platform reads. Better parsing and proper attribution for the people who made the models you use.

Built in 24 days

First commit: 20 August 2026. Public release: 13 September 2026. I worked 23 of those 24 days. At roughly ten hours a day, that puts the build at give or take 230 hours.

What is not an estimate: 6.06 billion tokens went through the two models that built this. 4.94 billion on Claude, 1.13 billion on Codex.

I do not write most of the code myself any more. The loop looks like this:

me → Claude → me → Claude → Codex → Claude → Codex → Claude → me → repeat

I decide what gets built and why. The models do the work in between, and they check each other on the way. Then I check it again myself. Nothing ships that I have not used on my own posts, and nothing I have not read twice.

Used on real posts from day one

The first post published through Livebound went live on 20 August 2026 at 23:21 UTC — nine and a half hours after the first commit. Since then 51 posts and 164 images have gone to CivitAI through it, and 288 of my existing posts, with 731 images, have been adopted back into it. Every feature in 1.0 is there because something annoyed me while doing exactly that.

About your files

Livebound moves and deletes files on your disk when you ask it to. The duplicate trash, restoring from it, the archive run and permanent deletion all touch real files. The irreversible ones make you type a confirmation first.

Those paths are tested and no defect in them is known. That is a statement about the care taken, not a guarantee.

Keep your own backups of your image folders. Livebound's database backup covers Livebound's own state; it does not contain your images. By using Livebound you take responsibility for your own files.

Getting it

GitHub: https://github.com/MoonBlack87/livebound (release ZIP or git clone)
Documentation: https://moonblack87.github.io/livebound/
Windows, Linux and WSL are the tested paths. The shell path is there for macOS too and should be fine, but it has not been tested. Treat it as use-at-your-own-risk.
Free and open source, AGPL-3.0-or-later.
You need a CivitAI account. Livebound connects over OAuth and never asks for your password.

When something breaks

It will. Open an issue on GitHub: that is the fastest route, and the fix reaches everybody. If you would rather talk than file: DM me here on CivitAI, or find me on Discord as rokudesigns_007.

A bug report I can reproduce is worth more than a compliment.

I hope you enjoy it, and that it helps you as much as it currently helps me. I am looking forward to your feedback.

— Moonbear 🐻