Skip to content

Avatar random: full-domain seed for new Bots #1214

New issue
New issue
Closed
#1235
Closed
Avatar random: full-domain seed for new Bots#1214
#1235
Labels
area:fullstackEnd-to-end Host and Client implementationarea:ui-uxInteraction and visual experience; may accompany a code-layer areafeature:avatarPersonaBot avatar media and activity frameready-for-agentFully specified, ready for an AFK agentscope:tracerHuman-testable implementation slice
Milestone
v1.2

Description

@DoodleBears
DoodleBears
opened on Oct 8, 2026

Parent

Part of #1209.

What to build

A Human presses random in the Avatar editor and gets a character from every available species and part. A newly created PersonaBot gets its first face from its name across every species. Existing Bots that were never edited keep their current human face. Once a Human edits an appearance, renaming the Bot never changes it.

Acceptance criteria

  • The editor's random action covers every available species, hair piece color and headpiece. Results respect each species' compatibility rules.
  • New PersonaBots record a lightweight seed version at creation and use a full-domain name seed. The version is not a saved appearance.
  • Bots without a seed version keep today's human-only name seed with unchanged output, and BotPixel's existing seeded golden output is unchanged.
  • Before any edit, renaming re-derives the face within the Bot's own seed version. After an edit, the saved Avatar Appearance stays fixed across renames.
  • The random domain grows automatically as later species tickets land, with no per-species change to this logic.
  • Tests cover old and new seed versions, the rename behavior and determinism of the new seed.

Blocked by

Activity

  1. DoodleBears
    added this to the v1.2 milestone on Oct 8, 2026
  2. DoodleBears
    added
    ready-for-agentFully specified, ready for an AFK agent
    area:ui-uxInteraction and visual experience; may accompany a code-layer area
    feature:avatarPersonaBot avatar media and activity frame
    area:fullstackEnd-to-end Host and Client implementation
    scope:tracerHuman-testable implementation slice
    on Oct 8, 2026
  3. DoodleBears
    added a parent issue on Oct 8, 2026
  4. DoodleBears
    marked this as blocked on Oct 8, 2026

  5. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    DoodleBears
    on Oct 8, 2026 – with Claude
    ContributorAuthor

    Agent work claim

    Generated by Claude Code

  6. DoodleBears
    added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 8, 2026
  7. DoodleBears
    added 4 commits that reference this issue on Oct 8, 2026

    feat(avatar): seed version 2 faces from a name across every species

    fff5ad5

    Seed new PersonaBots from every species and part

    405cb2d

    feat(avatar): elf, dwarf, orc and flower species, beards, medieval ou…

    c89ff86

    feat(avatar): elves, dwarves, orcs, talking flowers and full-domain s…

    f1e6fc6
  8. DoodleBears
    closed this as completedin #1235on Oct 8, 2026

  9. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    DoodleBears
    on Oct 8, 2026 – with Claude
    ContributorAuthor

    Delivered in #1235 (squash f1e6fc6).

    • Stamp at creation: PersonaBotRegistry.create stamps avatarSeed: 2. A stamped Bot with no saved Avatar gets a face seeded from its name across every species, beard, outfit and flower part (seededRecipeV2 in @botharness/pixel-avatar 0.4.0).
    • Older Bots: Bots without the stamp keep their v1 face in Client avatars, the editor's starting recipe, the shared bot.json descriptor, the Window Companion, session owners and the Activity Center.
    • Validation: the record validator accepts only the value 2.
    • Create dialog: previews the v2 face as you type a name.
    • After editing: an edited Avatar is saved, so a rename no longer changes it.
    • Tests: registry, descriptor sync, bridge and editor tests cover both seed versions.

    Agent-Task: claude/cloud/session_01MozvQ2eMvqX1MzSqm9G2o8

    Generated by Claude Code

  10. DoodleBears
    removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:fullstackEnd-to-end Host and Client implementationarea:ui-uxInteraction and visual experience; may accompany a code-layer areafeature:avatarPersonaBot avatar media and activity frameready-for-agentFully specified, ready for an AFK agentscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions