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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow multiple commands at once #3945

Closed
1 task done
yangkyeongmo opened this issue May 7, 2023 · 3 comments
Closed
1 task done

Allow multiple commands at once #3945

yangkyeongmo opened this issue May 7, 2023 · 3 comments
Labels

Comments

@yangkyeongmo
Copy link

yangkyeongmo commented May 7, 2023

Duplicates

  • I have searched the existing issues

Summary 馃挕

Although I'm working on it, I thought it would be nice to make an issue and maybe someone else better(and more time) on this repo could work on it.

Not all commands are costly. Some API calls like speaking could be expensive, but searching on internet, writing file, reading file or else are not. These commands could be done at once, and if it happens it'll save queries.

For example, if the bot wants to search about some information, it could simultaneously search about multiple topics.

To acheieve this, these changes should be done:

  1. Allow bot to make more than one commands
  2. Parse many commands from agent
  3. Agent calls multiple commands at once, possibly using asynchronous calls
  4. Mark cheap commands which can allow multiple calls

Examples 馃寛

Since bot is already told it should answer in json format, even though it was told command in answer should be in dictionary, sometimes its answer is in list format.

This is not an actual answer, it's how the answer would look like.

{
    ...
    "command": [
        {"name": "command name", "args": {"arg name": "value"},
        {"name": "command name", "args": {"arg name": "value"},
        ...
    ],
    ...
}

Motivation 馃敠

No response

@Boostrix
Copy link
Contributor

Boostrix commented May 7, 2023

See also: #1060
If/when this is revisited, should take into account:

@github-actions
Copy link

github-actions bot commented Sep 6, 2023

This issue has automatically been marked as stale because it has not had any activity in the last 50 days. You can unstale it by commenting or removing the label. Otherwise, this issue will be closed in 10 days.

@github-actions github-actions bot added the Stale label Sep 6, 2023
@github-actions
Copy link

This issue was closed automatically because it has been stale for 10 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants