Update todo after PDF testing
This commit is contained in:
@@ -1 +1,7 @@
|
||||
# TODO
|
||||
|
||||
- [ ] On sync brain of reese rewrites all the summaries for every directory. So even if just one file changed this can result in 700+ directory summary rewrites in production which can take a very long time.
|
||||
- [ ] The `Syncing… name/of/file/here (2/3)` doesn't show up on mobile, it needs to
|
||||
- [ ] The `Syncing… name/of/file/here (2/3)` needs to show what chunk we're on out of how many
|
||||
- [ ] The chat output is getting messy. I think it's because the `source-chip`, `source-image`, `tune-btn`, `retry-btn`, and `save-as-doc-btn` end up in the same div which causes them to push each other in weird ways. Those three buttons should be in a button cluster in the bottom right. We don't need to display the `source-chip` for images, just the image itself is fine. `source-chips` should show up before images in their own cluster, then images in their own cluster to keep things organized.
|
||||
- [ ] The agent is struggling with huge documents. It can search for the text it wants and it finds the text, including line number, but then it gets stuck saying "However, read takes a path, not a line number." and can't figure out how to read that part of the document. Does the read tool support that? If not, it should. If it does, improve the description so the agent doesn't get stuck. I have a huge test pdf (the DND player's handbook) in test_sources called "pdf_tests.tar" that you can use for testing. It's a massive pdf. The question the agent got stuck on was "What are the components of the find traps spell?" which is toward the end of the players handbook so it will need to search and read specific lines. I've been setting BOR_READ_MAX_CHARS to 24000 to keep things relatively quick so the agent realizes quickly its answer isn't in the first few pages.
|
||||
Reference in New Issue
Block a user