My private Day planner

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend What We Built Shruthi is a close friend of all three of us. She told us that [HER REAL PROBLEM, IN HER OWN WORDS, e.g. "my days feel messy and I never stop to reflect"]. She also said she would never type her personal thoughts into an online app. That last sentence shaped everything. So we built a private day planner that runs fully on a laptop, with no account, no API key and no server. It has two tabs: - Morning plan: she types her day ("college 9 to 4, assignment due tomorrow, I want to exercise and sleep by 11") and gets an hour-by-hour schedule. - Night reflection: she writes a few lines about her day. The app saves them to a text file on the laptop, then gives a short summary, one thing that went well, and a small goal for tomorrow. Team @himacharan69: wrote the first version and the system prompt. @vyshu1230 : built the Night reflection tab. @pashya_rishitha_0610 : model testing and screenshots. Demo The app runs locally, so there is no hosted link. That is the point: her diary never leaves the machine. : Morning plan tab with a schedule. : Night reflection tab with the saved message What shruthi Said I want a proper private dairy which I used check that often Ly and it is very usefull to me the main thing i want is it should be in my device. Code https://github.com/Himacharan69/private-day-planner.git How We Built It - Model: llama3.2, an open-weight model, run locally with Ollama. - Interface: Streamlit, so the whole page is plain Python. - Storage: diary entries are appended to a diary.txt file on the laptop. - Hardware: a normal Windows laptop with 32 GB of RAM. - Learning along the way: we used an AI assistant to learn Ollama and Streamlit and to debug errors. The most important part turned out to be one short instruction (a system prompt) that tells the model how to behave: You are a kind day planner. Use ONLY the times and tasks the user gives. Do not change fixed times like classes. Fill the free time with study, meals, exercise and rest. Format as a markdown list with each time slot on its own line. End with one short encouraging sentence. To see how much it mattered, we ran the same input ("College 9 to 4, assignment due tomorrow, I want to exercise and sleep by 11") two ways: - Plain terminal chat, no instructions: llama3.2 ignored the college hours, wrote "11:00 PM" twice, and invented a 6 AM wake-up. - Inside our app, with the system prompt: it kept college from 9 to 4, fitted in the assignment, exercise and dinner, and ended with sleep at 11. Same model, very different result. Where it falls short: a small model still makes mistakes. [ONE REAL PROBLEM YOU SAW, e.g. an invented task or a strange time slot.] Why Does Open Innovation Matter? A diary is the most personal thing a person writes. On a closed API, every entry would travel to someone else's server, and the app would need internet and a paid account. With an open-weight model: - Her data stays with her. Nothing is sent anywhere. - We could change the model's behavior ourselves. One short prompt fixed the biggest problems in minutes, for free. - We could swap models. Trying a different one meant changing a single line of code. - It costs nothing to run. One honest note: llama3.2 is open-weight, not fully open source. We can download and run it, but the training data is not public. What's Next We want the morning plan to read yesterday's diary goal, so the two tabs become one daily loop. Building this for someone we all know taught us more than any demo project would have. Top comments (0)