mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Personality Module - Configurable communication styles #82

New Issue
Closed
opened 2026-01-29 22:01:09 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-29 22:01:09 +00:00
Owner
Copy Link

Overview

A system for configurable personality types and communication styles, allowing users to customize how Mosaic/agents interact with them.

Core Concept

Different users have different communication preferences. Rather than hardcoding one style, Mosaic should offer:

  1. Personality Presets — Pre-built profiles (e.g., PDA-avoidant, Direct, Supportive, Professional)
  2. Customizable Settings — Fine-grained control within each preset
  3. Per-User Configuration — Each user can select/customize their preference
  4. Context Awareness — May vary by domain or situation

Example Presets

PDA-Avoidant

  • Suggestions instead of commands
  • Options instead of directives
  • Low pressure, high autonomy
  • "You might consider..." vs "You should..."

Direct

  • Clear, concise instructions
  • No hedging or softening
  • Action-oriented language
  • "Do X, then Y"

Supportive

  • Encouraging tone
  • Acknowledgment of effort
  • Gentle corrections
  • Celebration of progress

Professional

  • Formal language
  • Structured responses
  • Executive summary style
  • Minimal personality

Customizable Dimensions

  • Directness — How direct vs suggestive
  • Formality — Casual vs formal tone
  • Verbosity — Concise vs detailed
  • Encouragement — Level of positive reinforcement
  • Autonomy — How much control given to user
  • Structure — Freeform vs organized responses

Technical Considerations

  • Store as user preference (User model extension)
  • Inject into system prompts for agent interactions
  • May affect UI copy as well as agent responses
  • Could be workspace-level default with user override

Subsumes

  • #20 PDA-friendly UI optimizations
  • #28 PDA-friendly response formatting

PDA (Pathological Demand Avoidance) is one personality type, but the system should be extensible to many styles.

## Overview A system for configurable personality types and communication styles, allowing users to customize how Mosaic/agents interact with them. ## Core Concept Different users have different communication preferences. Rather than hardcoding one style, Mosaic should offer: 1. **Personality Presets** — Pre-built profiles (e.g., PDA-avoidant, Direct, Supportive, Professional) 2. **Customizable Settings** — Fine-grained control within each preset 3. **Per-User Configuration** — Each user can select/customize their preference 4. **Context Awareness** — May vary by domain or situation ## Example Presets ### PDA-Avoidant - Suggestions instead of commands - Options instead of directives - Low pressure, high autonomy - "You might consider..." vs "You should..." ### Direct - Clear, concise instructions - No hedging or softening - Action-oriented language - "Do X, then Y" ### Supportive - Encouraging tone - Acknowledgment of effort - Gentle corrections - Celebration of progress ### Professional - Formal language - Structured responses - Executive summary style - Minimal personality ## Customizable Dimensions - **Directness** — How direct vs suggestive - **Formality** — Casual vs formal tone - **Verbosity** — Concise vs detailed - **Encouragement** — Level of positive reinforcement - **Autonomy** — How much control given to user - **Structure** — Freeform vs organized responses ## Technical Considerations - Store as user preference (User model extension) - Inject into system prompts for agent interactions - May affect UI copy as well as agent responses - Could be workspace-level default with user override ## Subsumes - #20 PDA-friendly UI optimizations - #28 PDA-friendly response formatting --- *PDA (Pathological Demand Avoidance) is one personality type, but the system should be extensible to many styles.*
jason.woltje added the apifrontendp1 labels 2026-01-29 22:01:27 +00:00
jason.woltje added this to the M3-Features (0.0.3) milestone 2026-01-29 22:01:27 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label api frontend p1
Milestone
No items
No Milestone M3-Features (0.0.3)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#82
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?