Feedback

Product feedback submitted from Reflex. Description : Currently in the edit mode Live/Draft tags are the same color - blue. When user exits edit mode those tags become green and yellow. For the consistency I would recommend keeping Live tag green and Draft tag yellow throughout the platform

Product feedback submitted from Reflex. Description : The "Click to continue" button is not functioning.

Product feedback submitted from Reflex. Description : test Filed from an agent session (Inspect the repository and identify potential QA security usability and quality).

Product feedback submitted from Reflex. Description : When I hit the 429 devbox limit while running my automation, I wasn't immediately sure where to manage the active devboxes or which environment was consuming my limit. I had to navigate to the Devboxes dashboard, identify the completed README automation devbox, and verify that it had actually shut down before retrying. The error message explains the limit, but the recovery path could be more discoverable by linking directly to active devboxes or offering a clear “Manage devboxes” action.

Product feedback submitted from Reflex. Description : Sometimes a work is done, the left panel has white circle, but the one in the title is still spinning

Product feedback submitted from Reflex. Description : I got an out of memory issue in the browser. I am not sure if it is because of the task was too complex, or the Loom app is causing the issue.

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).

Product feedback submitted from Reflex. Description : giving it to the left side with a full opened state like with the names of the pages and maybe a option to collapse it. Filed from an agent session (Python Minesweeper Game Execution And Display).

Product feedback submitted from Reflex. Description : Issue: The current Automation Builder flow is not intuitive enough for a new or regular user. It is not immediately clear how the different nodes should be connected, what each node is supposed to do, or which node should be used for a particular use case. Creating an automation requires the user to understand the purpose and relationship between multiple components such as Trigger, Agent Task, Agent, Approval, Router, and Action before they can successfully build a flow. User Impact The overall flow is difficult to understand at first glance. Users may not know which node to select or where to start. The relationship between different nodes is not always obvious. Users may need prior knowledge of the platform before creating an automation. Building a simple automation can feel unnecessarily complex. There is limited guidance when configuring the flow and connecting nodes. Expected / Recommendation The Automation Builder should provide a more intuitive and guided flow-creation experience. Possible improvements include: Provide a guided workflow/template for common automation scenarios. Clearly explain the purpose of each node when adding it. Provide contextual help/tooltips for nodes and configuration fields. Show examples of how nodes should be connected. Provide suggested next nodes based on the current node. Clearly indicate where the flow should start and end. Provide simple starter templates such as: Trigger → Agent → Action Trigger → Agent Task → Approval → Router Trigger → Agent → PASS/FAIL branches Provide validation or guidance while building the flow instead of only showing errors after Create is clicked. QA Recommendation The Automation Builder could be made significantly easier to use by moving from a configuration-first experience toward a more guided, visual workflow-building experience, especially for first-time users.

Product feedback submitted from Reflex. Description : Make personas more readily avialable in the home screen