Jeffser
Some form of filesystem
Describe the tool
A tool that would let me tell the LLM that it can read any file in /home/some_directory
Requirements
Check with an X what the tool might need to use
- [ ] Code Runner (Internal Terminal)
- [ ] Network Access
- [ ] API Key
- [ ] Message History (Access to Chat)
- [ ] Image Manipulation
- [ ] Python Library (Mention it below)
Write the Expected Result
What the AI model might expect when the tool is executed correctly
- list of files in a directory
- contents of a specified file
Personally I wouldn't mind being able to give the AI a website/domain to query documentation from, I basically have a self-hosted documentation for some projects.
The file access thing aligns with that as well for me, as some of them aren't in PDF format and are instead a folder with .html files scattered about so if you didn't install it on apache/nginx with vhosts.
I have documentation hosted on my mini pc and this could come in handy.
Because as it stands we give the AI access to the web browser activity, but it uses the web browser with a starting point always being going to startpage.com and we might want to lock the AI to using a specific domain/website.
And then maybe some "manpage" integration could be nice.
gpt-oss:20b for example doesn't really know how to query documentation with the terminal tool, because it tries to query man-page section (1 - Executable programs or shell commands) for documentation which should exist in manpage(3 - Library calls (functions within program libraries)) and (7 - Miscellaneous (including macro packages and conventions), e.g. man(7), groff(7), man-pages(7)).
But I think at somepoint we ask Jeffry to create a whole-ass agentic platform.
At somepoint scope creep could become a problem.
At somepoint someone is going to ask for MCP server(Model Context Protocol) tool.
