Skip to content

Weight personality and tonal reactions in the reflection prompt#217

Merged
sysread merged 1 commit into
mainfrom
claude/memory-ingestion-personality-gBTQj
May 29, 2026
Merged

Weight personality and tonal reactions in the reflection prompt#217
sysread merged 1 commit into
mainfrom
claude/memory-ingestion-personality-gBTQj

Conversation

@sysread
Copy link
Copy Markdown
Owner

@sysread sysread commented May 29, 2026

SYNOPSIS

Give the reflection agent's personality and reaction analysis axes explicit weight, and name tone directly.

PURPOSE

The reflection prompt currently enumerates four analysis axes (user facts, personality signals, reactions, self-guidance) as co-equal. Left to its defaults a model harvests the easy, extractable layer - concrete facts - and glosses over the behavioral signal that actually changes how the next turn should sound: how the user reacted to the assistant's tone and phrasing. The result is a memory store that knows what the user does but not how they like to be talked to.

DESCRIPTION

How it behaves now. REFLECTION_PROMPT lists four bullets the agent should "think about." Personality and reactions are present but flat - "how they communicate, what they value" and "did they push back? agree? redirect?" - with no signal that these matter more than fact extraction.

What this PR changes, parallel to the same axes:

  • Personality signals - add a "pay special attention" weight; name the dimensions concretely (terse/expansive, formal/casual, blunt/hedged, humor) and call out the tone they use and the tone they want back.
  • Reactions to you - also flag for special attention; broaden push-back/agree/redirect w/ went-quiet, warmed-up, got-short, and whether a phrasing or register landed or missed.
  • Self-guidance - add a tone-matching example.
  • Closing line stating the priority outright: fact extraction is the floor, not the goal.
  • Design-comment + user doc (docs/user/memory.md) synced to the strengthened emphasis.

How that closes the loop. Naming tone explicitly and weighting the two behavioral axes pushes the agent past easy fact-harvesting into capturing how this person likes to be addressed - the data a future turn most benefits from.

Notes:

  • intentional behavioral change to prompt text only; no code-path changes.
  • reflection tests assert on the imported constant by reference, not hardcoded text, so they're unaffected. Full gate green (1769 tests, markdownlint 0 errors).

https://claude.ai/code/session_01E2b3VvyyEgZwjvczp1jvUg


Generated by Claude Code

The reflection agent already enumerated four analysis axes (user
facts, personality signals, reactions, self-guidance), but treated
them as co-equal. Left to its defaults a model harvests concrete
facts - the easy, extractable layer - and glosses over the
behavioral signal that actually changes how the next turn should
sound: how the user reacted to the assistant's tone and phrasing.

Give the personality and reaction axes an explicit "pay special
attention" weight, and name tone directly (the register the user
uses and the register they want back, whether a phrasing landed or
missed). Add a closing line stating the priority outright - fact
extraction is the floor, not the goal; a future turn improves more
from knowing how this person likes to be talked to than from another
stored fact. Sync the design-comment block and the user-facing
memory doc to the strengthened emphasis.
@sysread sysread merged commit 80ee01f into main May 29, 2026
1 check passed
@sysread sysread deleted the claude/memory-ingestion-personality-gBTQj branch May 29, 2026 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants