Repository navigation
v0.8.1
Fixed
- agents: a file attached to a chat is findable on disk, not just by
search. The document tools said in their own description that an attached
file "has no path, use vector_search for it" — it has one since the chat
keeps its uploads in its own directory, and a model follows the tool's
description over the prompt, so it never opened the file. The prompt now
also names the path the tools take (uploads/<name>from the working
directory) beside the absolute one,globsays that it returns files and
never directories —*in a directory of sub-directories finds nothing —
and the bundledcoding-assistantgetsfile_list, which it was missing. - agents:
vector_searchno longer claims to be the only way to an
attached file. Its description said in capitals that attached files are not
on the filesystem, which outweighed both the prompt and the file tools; it
now says what search is good for — a passage in a long document, several
files at once, a knowledge store — and that a file the prompt names with a
path is better opened. The bundleddefault-chatsays the same. - agents: an image attached to a chat is a file like any other. It was
only recorded on the session and handed to the model with the next message,
sofile_listdid not show it and no tool could open it; it is now copied
into the chat's uploads directory as well, named in the prompt with its
path, and removed again when the attachment is removed. Its content is
still not indexed — an image is not text to search. - agents: attaching a file activates
file_readandfile_listfor the
chat, next tovector_search. An agent that finds its tools by searching
had the search tool in front of it and the file tools only behind a
tool_searchcall, so it searched an attachment it was told to open.
What's Changed
- An attached file is a file on disk, and the tools say so by @beisdog in #79
- An attached image is a file on disk too, and the tools that read it are switched on by @beisdog in #80
Full Changelog: v0.8.0...v0.8.1