-
Notifications
You must be signed in to change notification settings - Fork 43.9k
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
Make Auto-GPT aware of it's running cost #6
Comments
could use this? |
My thoughts exactly. If someone wants to tackle this. Suggested Implementation:
Displaying
If you'd like to work on this (please do!), assign it to yourself so we don't both work on the same thing. |
I can pick this, but first, I'll spend a little time on #4 . |
I'm going to start work on this now, @Torantulino . please assign this to me so others don't work on the same issue. |
I agree with all @Torantulino's ideas here. In that case, it might be a reason to use a real TUI instead of a simple set of print statements for this application. It could have a top-bar that contains running price for example. I'd also make a flag in the cli that allows for rate limiting the application: Sleep 10 seconds between requests, for example. Some tasks the AI may be given may not require frequent polling. For example I'm using the bot for research, and notifications of major news events. Major news event searching may only need the bot to check the internet every day. This polling frequency option will be critical for giving some applications amazing speed, and others sort of dumb infrequent inexpensive speed. |
hey @0xcha05 are you currently working on this issue? |
I went ahead and implemented this in my own fork (branch "running_cost"). I'll submit a pull request later tonight. Here it is in action, but also an example of it not working quite right. I think I'll prompt engineer it a bit before submitting the pull request. I find that it works better if I send its remaining budget in the system message context, and yell at it if it goes over budget
|
I'm very close, now. Auto-GPT is beginning to behave with the appropriate behavior of hurrying up when the budget is nearly depleted, and shutting itself down when the budget is exceeded. Too tired to finish this tonight, though. I'll give another update tomorrow night. |
Okay! It's working, now. It prints the running cost, the AI is aware of the running cost, and the user can optionally provide a budget (of which the AI is also aware, and behaves appropriately). Please refer to my pull request. #762 |
Woohoo, it's merged in! 🎉 @rob-luke would you be interested in tackling the final task of making the total running cost visible to the user? See #762 (comment) |
@Vwing shoot me a DM on the discord :) |
Thanks for tackling this issue @Vwing. |
Fixed in #762 |
has anybody thought about exposing this in a shell prompt-style manner at runtime, per agent (task/job) ? |
…ixes-01 Dev fixes 01
* Upsert in batch * Improve update context, support customized answer prefix * Update tests * Update intermediate answer * Fix duplicate intermediate answer, add example 6 to notebook * Add notebook results * Works better without intermediate answers in the context * Bump version to 0.1.2 * Remove commented code and add descriptions to _generate_retrieve_user_reply --------- Co-authored-by: Qingyun Wu <qingyun.wu@psu.edu>
Auto-GPT is expensive to run due to GPT-4's API cost.
We could experiment with making it aware of this fact, by tracking tokens as they are used and converting to a dollar cost.
This could also be displayed to the user to help them be more aware of exactly how much they are spending.
The text was updated successfully, but these errors were encountered: