What I Built:
I built SlothDesk, a local-first AI assistant designed to make everyday digital housekeeping less painful.
We all have that folder full of vaguely named documents, notes we meant to summarize, and information we know we'll need later. The problem isn't that these tasks are difficult. It's that they're repetitive enough to keep getting postponed.
SlothDesk helps by:
Summarizing long text files into short, useful notes.
Suggesting clear, descriptive filenames.
Categorizing documents by their content.
Creating a daily digest of important information.
Preparing proposed file changes for review before applying them.
The goal is simple: spend less time managing information and more time doing whatever actually matters.
Think of it as a tiny digital sloth that does the boring work at its own pace.
Demo
https://github.com/rudrakshk25060-csds/slothdesk-ai
The ideal demo is straightforward: drop a messy collection of text files into SlothDesk, run the assistant, and show the summaries, suggested filenames, and organized output.
Code
https://github.com/rudrakshk25060-csds/slothdesk-ai
How I Built It
SlothDesk is designed around open-source AI rather than a closed AI API.
The planned stack is:
Ollama for running models locally.
An open-weight language model, such as Qwen2.5 or another compatible model, for summarization and categorization.
Python for file handling, task orchestration, and validation.
A lightweight interface for reviewing suggested changes and approving actions.
The workflow is deliberately simple:
The user selects a folder or supplies text files.
The application extracts the relevant text.
The local model generates summaries, categories, and filename suggestions.
The application validates the results and prepares proposed changes.
The user reviews the proposals before any files are renamed or moved.
This keeps the model focused on understanding and organizing information while ordinary code handles predictable file operations.
The architecture also makes it possible to switch compatible models as better options become available.
Why Does Open Innovation Matter?
For a tool that reads personal documents, where the AI runs matters just as much as what it can do.
Privacy: With local inference, document contents can remain on the user's machine instead of being sent to a third-party inference API. The application must also avoid unnecessary network calls in its own implementation.
Freedom to experiment: Open-weight models let developers compare different models, tune prompts, and adapt the system to their specific workflow without tying every decision to one hosted provider.
Control over costs: Local inference avoids per-request API charges, although running the model still consumes hardware resources and electricity.
Offline potential: Once the application and model weights are downloaded, the core workflow can operate without an internet connection, provided all dependencies are installed locally.
A simpler, more transparent agent: SlothDesk uses deterministic code for file operations and AI for tasks that benefit from language understanding. That makes its behavior easier to inspect and its changes easier to review.
A closed API might provide a convenient starting point, but a local, open-model architecture gives this project more control over privacy, deployment, and long-term flexibility.
The Lazy Payoff
The real win is eliminating the small decisions that accumulate throughout the week.
Instead of opening every document, reading it, inventing a filename, and deciding where it belongs, users get a first pass prepared for them.
To measure the payoff, I plan to compare the time required to organize the same set of files manually against the time required with SlothDesk, including review and correction time.
The goal isn't to remove people from the process entirely. It's to make the tedious 80% easier, leaving people to handle the decisions that actually need their attention.
Less clicking. Less procrastinating. More doing nothing when you finally have free time.
Top comments (0)