Reference images

/showrefs and /addrefs manage a character’s stored reference images on the GPU box — up to 4 per character.

/showrefs

/showrefs needs no argument on a bot with exactly one character. On a bot with more than one, it needs the trigger: /showrefs <trigger> — with or without the trigger’s own leading slash, so /showrefs mychar and /showrefs /mychar both work.

With no argument on a multi-character bot, the bot replies usage: /showrefs <trigger> followed by every character’s trigger. On a bot with no characters at all, it replies no character LoRA assigned.

On success, the bot posts the character’s stored reference images — up to 4 — captioned /{trigger} · {lora}, followed by a controls message: one Delete image N button per stored image, all in one row, and an Add reference image button underneath. The Add button disappears once 4 images are stored.

With nothing stored yet, there are no photos to post; the bot sends the add prompt instead: Send up to 4 refs.

The GPU box streams the stored files straight to Telegram for this command — no GPU compute runs.

/addrefs

/addrefs resolves its target the same way /showrefs does: a trigger argument on a multi-character bot, nothing needed on a single-character bot.

Send /addrefs as the caption on a photo, or as a reply to a photo, and that image queues immediately.

Send bare /addrefs — or tap Add reference image under a /showrefs controls message — and the bot prompts and waits for photos: Send up to 4 refs. with nothing stored, Send up to {n} refs. with some stored, or Please delete a reference image first. at the 4-image cap.

Every photo sent while the bot is waiting is uploaded as a reference image, one at a time; the bot re-posts the updated /showrefs view after each one.

Deleting a reference image

Tap Delete image N under a /showrefs controls message. The bot removes that file and re-posts the updated set.

Facts and limits