mirror of
https://github.com/entropy-research/Devon.git
synced 2026-04-03 00:18:30 -06:00
Prompt for File Tree Display Permission #17
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#17
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 @99Gens on 7/17/2024
Devon burns excessive amounts of tokens reading a non abbreviated version of the tree. So there either needs to be a light LLM client side which abbreviates it or a always-active request to the user to perform the action, allowing the user to submit their own abbreviated version. With these rate limits, allowing Devon to run known tasks that can eat up a ton of usage is illogical. I see the pair programmers of the future using lite llms on their local machines to reduce the token exposure going up. For the specific task of abbreviating a file tree, you might not even need a full LLM. A simpler natural language processing (NLP) model or even a well-crafted rule-based system could potentially handle this task effectively.