Skip to content

[FEATURE] Soul & Personality System — Hermes-inspired persistent identity + session switching #20334

New issue
New issue
Closed as not planned
Closed as not planned
[FEATURE] Soul & Personality System — Hermes-inspired persistent identity + session switching#20334
Assignees
thdxr
Labels
coreAnything pertaining to core functionality of the application (opencode server stuff)docsneeds:complianceThis means the issue will auto-close after 2 hours.

Description

@robinmordasiewicz
robinmordasiewicz
opened on Mar 31, 2026

Overview

Add a Hermes Agent-inspired personality system to OpenCode that separates intent-routing from identity, supports built-in and custom personalities, and adds session-level switching via `/personality`.

Motivation

The current `soul.txt` is a static F5-specific intent-routing table — not a personality. Users have no way to customize the agent's identity, tone, or communication style. The community-submitted PR #11838 shows demand for this.

Reference

Architecture

Prompt Stack (slot order):
1. Soul identity  — SOUL.md (user-editable, auto-seeded)
2. Personality overlay — /personality session switching (ephemeral)
3. Routing — routing.txt (F5 capability routing, internal)
4. Provider prompt — model-specific guidance
5. Environment — model info, working dir, date
6. Skills — available skill listing
7. Instructions — AGENTS.md, CLAUDE.md, etc.

Child Issues

  • Phase 2: Split soul.txt → routing.txt + default-soul.txt
  • Phase 3: Personality types & config schema
  • Phase 4: SOUL.md file loading (global + project)
  • Phase 5: Built-in personality presets
  • Phase 6: /personality slash command
  • Phase 7: System prompt assembly integration
  • Phase 8: Documentation & cleanup

Development

Branch: `feature/soul-personality`
Approach: Test-driven development (TDD) — tests written before implementation.

Activity

  1. github-actions
    assigned
    thdxr
    on Mar 31, 2026
  2. github-actions
    added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    docs
    needs:complianceThis means the issue will auto-close after 2 hours.
    on Mar 31, 2026

  3. github-actions commented on Mar 31, 2026

    @github-actions
    github-actionsBot
    on Mar 31, 2026 – with GitHub Actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • The feature request template was not used — the issue is missing the required verification checkbox confirming you've checked for existing issues and read the docs.
    • The title uses [FEATURE] but the template requires [FEATURE]: (with a colon).
    • The issue reads as an AI-generated design document / architectural spec rather than a focused feature request. Long, AI-generated walls of text are not acceptable per our guidelines. Please describe the feature request concisely in your own words, explaining the problem it solves.
    • This issue spawns multiple child issues as a planning tracker, which is more suited to a project board than an issue tracker. Please consolidate into a single focused request.

    Please edit this issue to address the above within 2 hours, or it will be automatically closed.

    This issue might be a duplicate of existing issues. Please check:

    If you believe this was flagged incorrectly, please let a maintainer know.

  4. rekram1-node commented on Mar 31, 2026

    @rekram1-node
    rekram1-node
    on Mar 31, 2026
    Collaborator

    closing for spam

  5. rekram1-node
    closed this as not plannedon Mar 31, 2026

  6. R44VC0RP commented on Mar 31, 2026

    @R44VC0RP
    R44VC0RP
    on Mar 31, 2026
    Contributor

    denounce @robinmordasiewicz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

coreAnything pertaining to core functionality of the application (opencode server stuff)docsneeds:complianceThis means the issue will auto-close after 2 hours.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions