Blue Archive AI roleplay: a weekend group chat with distinct characters

The cover is AI-generated from nine screenshots; the conversation images in the article remain unaltered originals.

“Let's go somewhere this weekend. No early start, and no rushing between attractions.” Shiroko suggests a ride, Hoshino wants the aquarium, and Yuuka worries about fares and whether the teacher has eaten. We wanted a conversation with small disagreements and ordinary care.

This is Day 0 of our Personal Agent from Zero diary. We configured the characters and supplied the topics and follow-up prompts; the replies came from real model calls in DeepSeekBot. The original Chinese screenshots show an Android development build. This cross-school fan scenario is not official Blue Archive dialogue or a collaboration with its creators.

Write the characters before picking the conversation

Our first problem was that everyone sounded like the same helpful assistant: organise the task, produce a checklist, summarise the next action. That can be useful at work. It makes three character portraits feel interchangeable in a casual chat.

We returned to official sources. Yuuka is Millennium's Seminar accountant, not an Abydos accountant simply because she has joined this group. Shiroko is reserved and enjoys running, training and road cycling. Hoshino's relaxed manner and naps coexist with a protective side. The official anime also gives us an everyday aquarium outing to draw on.

The SOUL files separate those facts from our interpretation. Yuuka can check fares without scolding in every reply. Shiroko can show care through a practical suggestion without repeating a catchphrase. Hoshino can want a rest and still notice that the teacher is tired. These are acting instructions, not quotations from the game.

The characters read the revised files in the existing conversation. That is different from automatically replacing the current Session's system-prompt snapshot; the source files are linked below.

How far is “a short ride”?

Shiroko's short ride initially means eight kilometres. When the teacher asks for something easier, she brings it down to two. That exchange was more useful to us than instant agreement on a perfect itinerary: a character keeps her own habits while responding to someone else's needs.

The chat moves on to convenience-store food, the last pudding, taking a bus in the rain and sitting by an aquarium tank without visiting every exhibit. Those choices belong to this new fan conversation. They are not evidence of a canonical favourite food or an official shared outing.

A better SOUL still leaves room for mistakes

Yuuka briefly treats Shiroko's bicycle as a car. We did not edit the mistake out of the screenshot. The teacher corrects it in the actual conversation, Yuuka acknowledges it, and the group returns to buses and warm drinks.

A SOUL file expresses a direction; it does not guarantee faithful characterisation in every sentence. In this run, we looked for mixed-up identities, repetitive catchphrases and whether a correction could bring the conversation back on track.

What belongs in the memory of a fictional weekend?

Original references went into ROLE_CANON.md, stable acting guidance into SOUL.md, and the group's new agreements into separate life notes. We also made the boundary explicit: this is an in-app roleplay plan, not the user's real calendar or a meeting that has already happened.

We saved and read back the files. All ten captures still come from Day 0 and existing Sessions, so they do not establish useful recall days later. The Soul and core memory guide explains how files relate to Session snapshots.

The next small test would be a fresh interaction without repeating “no early start” or “no rushed sightseeing.” Does the character find the right note? If the answer is wrong, was the note missed, outdated or misunderstood? We have recorded the starting point, not preselected the result.

Try one ordinary topic first

Start with a weekend choice rather than ten simultaneous jobs. After following the DeepSeekBot installation guide, give each PersonaBot a separate name, avatar and SOUL, then invite them into a Group. The mobile interface pictured here comes from development source; it is not proof that the stable installation has the same screens.

For the general mechanism, read the existing personal AI agent memory introduction. This diary contributes one concrete group conversation to that broader question.

View all 10 original screenshots (Chinese)

Character sources and capture notes

Official references checked on October 18, 2026: Yuuka's student introduction, the official comic introduction showing her trying a game, Shiroko's character page, Hoshino's character page, and the anime's eighth episode. The avatars are AI-generated fan illustrations. Characters belong to their respective rights holders; this is not an official project.

Chinese source files: Yuuka SOUL, Shiroko SOUL, Hoshino SOUL; reference notes for Yuuka, Shiroko and Hoshino.

Captured October 18, 2026 in the native Android emulator app, light theme, Chinese UI, at product source d2529fe. The SDK 58 compatible development client was reused; this round built no new APK and did not test iOS. An operating Agent organised inputs under our approved topics and sent them through the production CLI; model replies and file-tool writes were real. This is not manual typing, zero-intervention automation, a stable store-release test or cross-day memory evidence. All captures are Day 0 in existing Sessions. Images are unchanged, selected thematically rather than as a continuous video. See the public provenance and SHA256 records.