Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add description to the agent-selection (or rename agents) #756

Closed
stracker-phil opened this issue Jan 1, 2024 · 3 comments
Closed

Add description to the agent-selection (or rename agents) #756

stracker-phil opened this issue Jan 1, 2024 · 3 comments
Assignees
Labels
auto-closed enhancement New feature or request priority Merge ASAP

Comments

@stracker-phil
Copy link

Is your feature request related to a problem? Please describe.

When creating a new conversation, it's always identified with agent_1, agent_2, and so on. After a while, I forget what persona & human & tasks a specific agent handles.

I have to load the agent and wait for the initial message, so I see which conversation it handles.

Describe the solution you'd like

Ideal solution:

  1. In the agent selection, I'd love to see the Persona & Human which is used by the agent
  2. Provide a command like memgpt describe agent_1 "What this agent does" or /describe "Task of current agent"

Sample:

❯ memgpt run

? Would you like to select an existing agent? Yes
? Select agent: (Use arrow keys)
   agent_1 - 🤖 [Persona] | 👤 [Human] | ℹ️ [Description]
 » agent_2 - 🤖 Assistant | 👤 Philipp | ℹ️ Personal assistant
   agent_3 - 🤖 Marketing | 👤 Client_A | ℹ️ Social Media Specialist

Alternative

Another option would be to add a memgpt rename agent_2 client1_seo command to simply rename the agent.

Sample:

❯ memgpt run

? Would you like to select an existing agent? Yes
? Select agent: (Use arrow keys)
   client1_marketing_social
 » assistant_philipp
@stracker-phil
Copy link
Author

@cpacker I've just added a small PR to address the visual changes for my request.

The PR uses the "name" attribute of the config.json file as an agent description; changing that name attribute in the JSON file will display it in the agent selection.

Also, the first part of the choices is still the agents file name, as the user needs this name in some places, and it should be included in this list.

There's a screenshot of the change in the PR

@cpacker cpacker linked a pull request Jan 1, 2024 that will close this issue
@stracker-phil
Copy link
Author

@sarahwooders thanks for the heads-up in my PR, and happy to hear you're improving the agent configuration storage 👍

When I have some time to spare, I'd be happy to contribute another PR for the new DB-based agent configuration. Just to be clear: the current version (0.2.11) does not include those changes yet?

Once the DB switch is official, I'll review the code.

Copy link

github-actions bot commented Dec 6, 2024

This issue has been automatically closed due to 60 days of inactivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-closed enhancement New feature or request priority Merge ASAP
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants