Add Viewer role for agents

[csalvato]

Problem Statement

Currently, users can only see an agent's system prompt and configuration if they have full edit rights.

But team members that want to understand how an agent works must be granted full editing permissions, which is often not desired.

Current pain points:

• Users with basic access can use agents but have no visibility into their implementation
• Teams must grant full edit rights just to allow configuration visibility
• This creates an "all or nothing" permission model that doesn't fit real-world team structures

Proposed Solution

Introduce a three-tier permission system for agents:

1. User - Can use the agent
2. Viewer - Can use the agent and see the agent's configuration (read-only)
3. Editor - Can change the agent, use the agent, and see the agent's config

This would require implementing a read-only view of the agent configuration form for users with Viewer permissions.

Benefits

• Better transparency: Team members can understand how agents work without editing permissions
• Improved security: Granular permissions reduce the need to grant unnecessary edit access
• Enhanced collaboration: Teams can review and understand agent implementations more easily
• Maintains existing workflow: Current User and Editor roles remain unchanged

Use Case

This feature would be particularly valuable for organizations where:

• Multiple team members need to understand agent behavior
• Security policies restrict editing permissions
• Teams want to review and audit agent configurations
• Knowledge sharing about agent implementation is important

Community Interest

This proposal originated from feedback at Coinbase and has received positive response from @danny-avila on Discord. Looking for additional community input and potential contributors.