The Lantern’s signature feature: AI-generated landscape images that appear behind your chat content at 45% opacity, creating a visual sense of place for each conversation. Not a generic wallpaper selected from a library—an image derived from the actual content of your chat, featuring the characters as they currently appear, in a setting that reflects the mood and narrative of the conversation.

Every chat gets its own avatars. When a character joins a conversation, the Lantern composes their portrait from their physical description and whichever outfit was selected at chat start; when their wardrobe changes mid-chat, the portrait regenerates to match. The image you see beside a participant’s name today is the portrait of this character, in this chat, in this outfit—not a stored default rolled forward indefinitely.

Beyond story backgrounds, the Lantern handles all on-demand image generation within conversations. A generate_image tool is available to every character, invocable by the AI mid-conversation or by you via the composer toolbar. Results land in a per-chat gallery for reuse as avatars, attachments, or conversation context.

Automatic image resizing handles provider size limits—Anthropic caps at 5 MB, others at 20 MB. Images paste directly into the chat composer, are auto-uploaded and attached, and can be tagged to characters for gallery organization. For chats flagged by the Concierge, both user prompts and their expanded versions are classified, and generation reroutes to an uncensored image provider when needed.

The Lantern does not work alone. Every image—whether a story background or an on-demand generation—passes through a pipeline that draws on multiple subsystems:

The Lantern is not a silent technician. When he generates an image he says so, and with reasonable specificity: a freshly composed character avatar after an outfit change, a story background after a scene shift, or a one-off character image conjured by a generate_image call. Each kind of announcement carries a stable systemKind—avatar, background, or character-image—so the Salon can render the more frequent ones (avatar regenerations especially) as collapsible bars rather than full-message rows that crowd the transcript.

The body of each announcement carries the prompt that was actually sent to the image provider, not a pre-expansion summary—so the LLM in the conversation can read precisely what the Lantern crafted on its behalf and adjust subsequent narration in light of it. Opaque characters—those without systemTransparency—continue to receive the body of the announcement as an anonymous assistant line; only transparent characters see his attribution and his portrait. As with every other Staff announcement, a posting failure logs and moves on rather than disrupting the work it was annotating.

He is, taken across an active session, the most prolific speaker on the Staff. This is forgiven on grounds of contribution: he is also the only member of the household who is visibly thrilled to be on the team.

Generated images are not ephemeral. They are stored in the file system, tagged to chats and characters, and browsable through the file browser with grid and list views, image thumbnails, and a preview modal. Images can be set as character avatars, attached to messages, or used as default character portraits. A character’s photo gallery collects every image tagged to them across all conversations.

File deletion respects associations: if an image is linked to a character as an avatar or gallery item, the deletion dialog shows all affected entities before proceeding. Orphaned image references render a cleanup prompt rather than broken thumbnails. The Lantern may be artless, but his filing system is not.