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

LMQL #3460

Closed
Pwuts opened this issue Apr 28, 2023 · 8 comments
Closed

LMQL #3460

Pwuts opened this issue Apr 28, 2023 · 8 comments

Comments

@Pwuts
Copy link
Member

Pwuts commented Apr 28, 2023

Current status

While we consider LMQL to be a powerful tool to supercharge interaction with text-only LLMs, it currently doesn't suit all needs of the project.

  • The landscape of LLMs is rapidly evolving, with OpenAI announcing only yesterday that their GPT-3.5 and GPT-4 models are being enhanced with a function calling interface. This feature has the potential to solve multiple current issues in Auto-GPT. LMQL doesn't currently have support for this feature, and adding support may be a challenge as other LLMs do not provide a similar interface.

  • We need high observability of interaction with the LLM, which LMQL currently does not offer.

Resources

@AbTrax
Copy link
Contributor

AbTrax commented Apr 28, 2023

I've read into it and am more than happy to get started on it. Where do you see it, as of now, would it have the most benefit to the project?

@Pwuts
Copy link
Member Author

Pwuts commented Apr 28, 2023

@AbTrax by restructuring the prompts using LMQL we might be able to greatly reduce the number of JSON errors.
Most if not all of the needed changes can be done in autogpt/prompts/. Start there, try to minimize changes to files outside that directory, and ping us on Discord when you have an update :)

@ether8unny
Copy link

Question is, can this also be used to identify true relevant data points that can be used as memory mets data

@khongminhtn
Copy link

Hello, is the current architecture implementing LMQL ?

@Boostrix Boostrix mentioned this issue May 9, 2023
@Pwuts
Copy link
Member Author

Pwuts commented Jun 15, 2023

@khongminhtn no, see the description under Current Status

@github-actions
Copy link
Contributor

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
@Pwuts Pwuts removed this from the Auto-GPT v0.5.0: Hackathon Ready milestone Sep 8, 2023
@github-actions github-actions bot removed the Stale label Sep 9, 2023
@github-actions
Copy link
Contributor

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 Oct 30, 2023
Copy link
Contributor

github-actions bot commented Nov 9, 2023

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 Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

4 participants