Persona Description Does Not Clearly Influence Agent Behavior
b
bilalreflexai-hub
Product feedback submitted from Reflex.
Description
: Steps to Reproduce- Create a Session using an OpenCode agent.
- Perform a development/QA task in the Session.
- From the Session, select Save as Persona.
- Create a Persona named Python Development & QA Agent with a description stating that it is a reusable development and QA agent capable of implementation, verification, investigation, and providing test summaries.
- Save the Persona.
- Navigate to Agent Personas and launch the newly created Persona.
- Observe that the Launch screen displays the Persona description and the captured configuration.
- Replace the captured To-Do List prompt with a different task, such as creating a Python Calculator application.
- Launch the new Session and allow the agent to complete the task.
Ask the agent:
Based only on the instructions and configuration actually provided to you, what role, Persona-specific instructions, or specialization did you inherit from the Python Development & QA Agent Persona?
- Ask the agent to distinguish which behaviors came from the Persona, the underlying OpenCode configuration, and the task-specific prompt.
- Observe that the agent identifies its verification behavior as coming from the base OpenCode instructions and the written verification summary as coming from the task prompt, but cannot identify any Persona-specific Python/QA instructions.
Actual Result
The launched agent could not identify any Persona-specific instructions or specialization. It reported that its behavior was based on the underlying OpenCode configuration/default instructions and the current task prompt.
Expected Result
The launched agent should either:
receive and be able to identify the behavioral instructions defined by the Persona, or
Reflex should clearly communicate that the Persona description is informational/metadata and does not influence the agent's behavior.
What Should Change
Reflex should clearly distinguish between Persona metadata and instructions actually passed to the agent. If the Persona description is intended to define agent behavior, those instructions should be explicitly applied to the launched agent. Alternatively, the Persona UI should clearly show which configuration and instructions will affect the launched Session.
Impact
Users may assume that creating a specialized Persona such as Python Development & QA Agent will cause future Sessions to inherit that specialization. Without visibility into what is actually applied, users cannot confidently understand the behavior or value of the Persona.
Filed from an agent session (Python Calculator Application Implementation Verification).
Photo Viewer
View photos in a modal