mirror of
https://github.com/entropy-research/Devon.git
synced 2026-04-03 00:18:30 -06:00
Exceeding per-minute rate limit #65
Labels
No labels
✨ enhancement
✨ enhancement
✨ enhancement
✨ enhancement
✨ enhancement
✨ enhancement
✨ enhancement
✨ enhancement
✨ enhancement
✨ enhancement
✨ enhancement
✨ enhancement
✨ enhancement
⭐ feedback
👋 good first issue
👋 good first issue
👋 good first issue
💬 discussion
💬 discussion
💬 discussion
🔃 duplicate
🕹️ issue: agent
🕹️ issue: agent
🕹️ issue: agent
🕹️ issue: agent
🕹️ issue: agent
🕹️ issue: agent
🕹️ issue: agent
🤖 feat: agent
🪲 bug
🪲 bug
🪲 bug
🪲 bug
🪲 bug
🪲 bug
🪲 bug
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github/Devon#65
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @basher83 on 5/21/2024
It would be great if there could be some way that Devon outputs a history so that if the workflow is stopped it can be resumed again upon reloading. I Have tried a few tricks to keep my workflow going but I still keep hitting rate limits. My attempt was to create an instructions.txt with a very detailed explanation of what I wanted. In my instructions I told Devon to keep a running log in a separate txt file so that the workflow could be easily restarted in case of a crash. Within my instructions.txt I tell Devon to first read the previous log and then continue working. It kind of works, but not well enough to get me through the entire project.