LazyTask AI: Let AI Organize Your To-Do List

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady.

What I Built

I built LazyTask AI, an AI-powered productivity assistant that helps students and busy people organize their tasks without spending too much time deciding what to do first.

We all have days when our to-do list feels overwhelming. We know what needs to get done, but figuring out where to start can be exhausting.

LazyTask AI makes that process easier. Users enter their tasks, and the AI organizes them by urgency and importance, creates a realistic schedule, and briefly explains its recommendations.

Features

• Enter multiple tasks, one per line.
• Generate an AI-powered task-priority list.
• Get a suggested daily schedule.
• Receive a clear explanation of the recommended order.
• Plan another day without refreshing the application.

The goal is simple: spend less energy organizing work and more energy actually doing it.

Demo

Live demo:

Try it locally: Follow the setup instructions in the repository below to run the application on your computer.

A short screen recording or GIF demonstrating task entry, AI prioritization, and the generated schedule can be added here.

Code

GitHub repository: https://github.com/Sathi-Seth/lazytask-ai

The project uses a React frontend and an Express.js backend to connect the user interface to the AI model.

How I Built It

I built LazyTask AI using JavaScript and a full-stack web development approach.

Technology stack:

• Frontend: React.js and Vite
• Backend: Node.js and Express.js
• AI inference: GroqCloud
• AI model: openai/gpt-oss-20b
• API communication: HTTP requests using JSON
• Configuration: Environment variables managed through .env

Here's how it works:

1. The user enters a list of tasks in the React interface.
2. The frontend sends those tasks to the Express backend through a POST /api/prioritize endpoint.
3. The backend sends a structured prompt to the open-weight AI model through GroqCloud.
4. The model generates a prioritized task list and a suggested schedule.
5. The backend returns the response to the frontend, where it is displayed to the user.

I chose a hosted inference approach instead of downloading and running a large model locally. This allowed me to experiment with an open-weight model on my available hardware without requiring a large local model installation.

Why Does Open Innovation Matter?

Open innovation matters because developers should have meaningful choices about the AI models they build with.

Using an open-weight model gave me an opportunity to build around model weights that are available for developers to use under the model's applicable license, rather than relying exclusively on a proprietary model ecosystem.

For this project, the hosted inference approach also made experimentation practical on my computer.

Open-weight models create opportunities for developers to explore different models and inference providers, evaluate their behavior, and potentially move toward self-hosting when their hardware and deployment requirements allow it.

A hosted service is not automatically open source just because it serves an open-weight model. LazyTask AI uses an open-weight model through GroqCloud, so the model choice and the inference infrastructure are distinct parts of the project.

For me, this challenge has been about learning how to turn an AI model into something useful, accessible, and practical.

The Lazy Payoff

The intended payoff is less time spent deciding what to do first and more time available for meaningful work.

I have tested the application with sample tasks and confirmed that it can generate an AI-powered plan. I haven't measured actual time savings yet, so I won't claim a specific number of minutes saved.

My next step is to test it over several days and compare the time spent organizing tasks with the time spent using the generated plan.

What I Learned

Building LazyTask AI helped me practice connecting a React frontend to an Express backend, handling API requests, managing environment variables, and integrating hosted AI inference.

It also taught me an important security lesson: API keys belong in private environment files, not in example files or public Git history.

This is a small project, but it represents a step toward building more useful applications with open-weight AI.

Less time planning. More time progressing.

devchallenge #hf26challenge