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

Update prompt.txt #164

Closed
wants to merge 1 commit into from

Conversation

sneljeroen
Copy link

Sometimes it tries to execute commands like "Google Search" instead of "google", specifying clearly which one is the command name fixes this.

Sometimes it tries to execute commands like "Google Search" instead of "google", specifying clearly which one is the command name fixes this.
Copy link
Contributor

@PhilipAD PhilipAD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@Void-n-Null
Copy link
Contributor

Thats a lot of extra tokens, but if its effective in avoiding miscommunication on command names, it might be worth it.

@fire17
Copy link

fire17 commented Apr 4, 2023

@mis046
Copy link

mis046 commented Apr 5, 2023

If token count is a concern, structure the data as a table might help e.g.
instead of

1. Google Search; command name: "google", args: "input": "<search>"
2. Memory Add; command name: "memory_add", args: "string": "<string>"

might be able to use

command key | command name | args
Google Search | "google" | "input": "<search>"
Memory Add | "memory_add" | "string": "<string>"

Tried running this prompt

{
  "prompt": "Here is a table with | as the column delimiter and new line as row delimiter, with the first row being the header:\ncommand key|command name|args\nGoogle Search|\"google\"|\"input\": \"<search>\"\nMemory Add|\"memory_add\"|\"string\": \"<string>\", what is the value of row \"Memory Add\"'s command name field",
  ...
}

and this is the result

{
  "choices": [
    {
      "text": "?\n\n\"memory_add\"",
      "index": 0,
      "finish_reason": "stop",
      "logprobs": null
    }
  ], 
  ...
}

@nponeccop
Copy link
Contributor

  1. Make the PR title more descriptive
  2. Resolve the conflicts (preferrably by rebasing on top of current master)

This was referenced Apr 10, 2023
@github-actions github-actions bot added the conflicts Automatically applied to PRs with merge conflicts label Apr 17, 2023
@github-actions
Copy link
Contributor

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

@k-boikov
Copy link
Contributor

This PR is completely obsolete.

@BillSchumacher
Copy link
Contributor

Yeah this doesn't even exist with plugins, sorry.

Say383 pushed a commit to Say383/Auto-GPT that referenced this pull request Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conflicts Automatically applied to PRs with merge conflicts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants