Skip to content

Feature: agent capability to update session name #1527

@bhavenst

Description

@bhavenst

🚀 Feature Description

Is your feature request related to a problem?

I would like to have the agent set the name of the session so that it's easier for a human to come back and reference later. For instance, the agent will select a Jira ticket during the workflow and work on it. I'd like to include that Jira ticket ID in the session name so someone can come back and find it to continue working or look at what happened or whatever.

This is especially true for scheduled/repeated sessions since they stack up and look similar to one another.

Describe the solution you'd like
There is already a menu option to rename the session, perhaps it can be exposed through the platform interaction MCP that appears to be available to the agent (but does not seem to have this functionality currently).

💡 Proposed Solution

Detailed Description: How should this feature work?

User Experience: How will users interact with this feature?

API Changes: [If applicable] What API changes are needed?

🎯 Use Cases

Primary Use Case: Who will use this and why?

User Stories:

  • As a member of an ACP using team, I want the executing agent be able to update the session title so that team members can locate the session they want to look at or continue using more easily

  • As a [user type], I want [functionality] so that [benefit]

🔧 Technical Considerations

Component: [RAT System / Ambient Agentic Runner / vTeam Tools / Infrastructure]

Implementation Approach: [High-level technical approach]

Dependencies: [Any new dependencies or integrations needed]

Breaking Changes: [Will this introduce breaking changes?]

📊 Success Metrics

How will we measure the success of this feature?

  • Metric 1: [Quantifiable measure]
  • Metric 2: [Quantifiable measure]
  • User feedback: [Qualitative measure]

🔄 Alternatives Considered

Alternative 1: [Description and why it was rejected]

Alternative 2: [Description and why it was rejected]

Do nothing: [Consequences of not implementing this feature]

📋 Additional Context

Screenshots/Mockups: [Add any visual aids]

Related Issues: [Link to related issues or discussions]

External References: [Links to similar features in other projects]

✅ Acceptance Criteria

  • Feature requirements clearly defined
  • Technical design reviewed and approved
  • Implementation completed and tested
  • Documentation updated
  • User acceptance testing passed
  • Feature flag implemented (if applicable)

🏷️ Labels

  • Priority: [low/medium/high]
  • Effort: [S/M/L/XL]
  • Component: [frontend/backend/operator/tools/docs]
  • Type: [new-feature/enhancement/improvement]

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions