base on A self-organizing file system with llama 3 # LlamaFS <img src="electron-react-app/assets/llama_fs.png" width="30%" /> ## Inspiration [Watch the explainer video](https://x.com/AlexReibman/status/1789895425828204553) Open your `~/Downloads` directory. Or your Desktop. It's probably a mess... > There are only two hard things in Computer Science: cache invalidation and **naming things**. ## What it does LlamaFS is a self-organizing file manager. It automatically renames and organizes your files based on their content and well-known conventions (e.g., time). It supports many kinds of files, including images (through Moondream) and audio (through Whisper). LlamaFS runs in two "modes" - as a batch job (batch mode), and an interactive daemon (watch mode). In batch mode, you can send a directory to LlamaFS, and it will return a suggested file structure and organize your files. In watch mode, LlamaFS starts a daemon that watches your directory. It intercepts all filesystem operations and uses your most recent edits to proactively learn how you rename file. For example, if you create a folder for your 2023 tax documents, and start moving 1-3 files in it, LlamaFS will automatically create and move the files for you! Uh... Sending all my personal files to an API provider?! No thank you! It also has a toggle for "incognito mode," allowing you route every request through Ollama instead of Groq. Since they use the same Llama 3 model, the perform identically. ## How we built it We built LlamaFS on a Python backend, leveraging the Llama3 model through Groq for file content summarization and tree structuring. For local processing, we integrated Ollama running the same model to ensure privacy in incognito mode. The frontend is crafted with Electron, providing a sleek, user-friendly interface that allows users to interact with the suggested file structures before finalizing changes. - **It's extremely fast!** (by LLM standards)! Most file operations are processed in <500ms in watch mode (benchmarked by [AgentOps](https://agentops.ai/?utm_source=llama-fs)). This is because of our smart caching that selectively rewrites sections of the index based on the minimum necessary filesystem diff. And of course, Groq's super fast inference API. 😉 - **It's immediately useful** - It's very low friction to use and addresses a problem almost everyone has. We started using it ourselves on this project (very Meta). ## What's next for LlamaFS - Find and remove old/unused files - We have some really cool ideas for - filesystem diffs are hard... ## Installation ### Prerequisites Before installing, ensure you have the following requirements: - Python 3.10 or higher - pip (Python package installer) ### Installing To install the project, follow these steps: 1. Clone the repository: ```bash git clone https://github.com/iyaja/llama-fs.git ``` 2. Navigate to the project directory: ```bash cd llama-fs ``` 3. Install requirements ```bash pip install -r requirements.txt ``` 4. Update your `.env` Copy `.env.example` into a new file called `.env`. Then, provide the following API keys: * Groq: You can obtain one from [here](https://console.groq.com/keys). * AgentOps: You can obtain one from [here](https://app.agentops.ai/settings/projects). Groq is used for fast cloud inference but can be replaced with Ollama in the code directly (TODO.) AgentOps is used for logging and monitoring and will report the latency, cost per session, and give you a full session replay of each LlamaFS call. 5. (Optional) Install moondream if you want to use the incognito mode ```bash ollama pull moondream ``` ## Usage To serve the application locally using FastAPI, run the following command ```bash fastapi dev server.py ``` This will run the server by default on port 8000. The API can be queried using a `curl` command, and passing in the file path as the argument. For example, on the Downloads folder: ```bash curl -X POST http://127.0.0.1:8000/batch \ -H "Content-Type: application/json" \ -d '{"path": "/Users/<username>/Downloads/", "instruction": "string", "incognito": false}' ``` ", Assign "at most 3 tags" to the expected json: {"id":"10440","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"