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

Use case tools + plan #7636

Open
mrm1001 opened this issue May 2, 2024 · 0 comments
Open

Use case tools + plan #7636

mrm1001 opened this issue May 2, 2024 · 0 comments
Labels
P2 Medium priority, add to the next sprint if no P1 available topic:agent

Comments

@mrm1001
Copy link
Member

mrm1001 commented May 2, 2024

Goal

The goal is to refine this task into smaller sub-tasks which might include a review of existing approaches (with limitations), creating a proposal, implementing the solution.

User story

Users should be able to create a pipeline that can answer user queries by using previous queries, responses, as well as previous outputs from tools. In order to solve the user query, it might be necessary to invoke multiple tools.

It needs to support the following patterns:

App plans the sequence of tools that need to be invoked.

Tools available: check_balance(account_id), add_payment_dollars(account_id, amount), get_account_details(email)

User: I would like to check my balance, add $100 to my account if less than $200 and check my balance again. My account id is 1234.
App: Balance for account 1234 is $100.
App: Payment of $100 confirmed.
App: Balance for account 1234 is $300.

App might need to ask for user's input to perform a task.

Tools available: check_balance(account_id), add_payment_dollars(account_id, amount), get_account_details(email)

User: I would like to check my balance, add $100 to my account if less than $200 and check my balance again.
App: what is your account id?
User: 1234
App: Balance for account 1234 is $100.
App: would you like to confirm payment of $100 to your account id 1234?
User: yes.
App: Payment of $100 confirmed.
App: Balance for account 1234 is $300.

App can start a new tool process in the middle of an existing transaction.

Tools available: check_balance(account_id), add_payment_dollars(account_id, amount), get_account_details(email)

User: I would like to check my balance, add $100 to my account if less than $200 and check my balance again.
App: what is your account id?
User: I don't know.
App: what is your email?
User: xxx@gmail.com
App: your account id is 1234.
App: Balance for account 1234 is $100.
App: would you like to confirm payment of $100 to your account id 1234?
User: yes.
App: Payment of $100 confirmed.
App: Balance for account 1234 is $300.

User can change intent in the middle of a transaction.

Tools available: check_balance(account_id), add_payment_dollars(account_id, amount), get_account_details(email)

User: I would like to add $100 to my account.
App: what is your account id?
User: I don't know.
App: what is your email?
User: Actually, I want to check my balance. My email is maria@me.com.
App: Your balance is $100.
@mrm1001 mrm1001 added P1 High priority, add to the next sprint topic:agent P2 Medium priority, add to the next sprint if no P1 available and removed P1 High priority, add to the next sprint labels May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Medium priority, add to the next sprint if no P1 available topic:agent
Projects
None yet
Development

No branches or pull requests

1 participant