RECALLMATE

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine

What I Built

RecallMate is a voice journal that listens, remembers, and lets you talk to your own past.

You speak instead of typing. RecallMate transcribes what you said, turns it into a structured entry, and stores it. When you later ask “what did I say about that exam?” or “what was I feeling that week?”, it answers from your own recorded words.

For Ghost in the Machine, I took the theme literally and personally: the ghost is your past self. Every entry you record is a small haunting, a voice from an earlier day that still has something to tell you. Día de los Muertos is about keeping memories alive so they don’t fade, and RecallMate does that for the everyday moments we usually forget by next week. [Add one line on what inspired you, e.g. a moment you forgot something that mattered.]

It has journal modes (Health, Daily log, Study log) so the same pipeline fits different kinds of remembering.

Demo

[Video link or deployed link]

Code

github.com/AWT-SRIRAM/RECALLMATE

How I Built It

Everything in the core pipeline is open-source and runs locally:

faster-whisper transcribes the voice recordings.
Ollama running qwen2.5:7b is the open-weight model that understands each entry and answers questions about past ones.
Instructor forces the model’s output into clean, structured fields instead of loose text, so entries can be saved and searched reliably.
SQLite stores the journal in a single file you own.
Streamlit provides the interface.
The whole thing runs from one all-in-one Python script, which I ran as a single Google Colab cell and exposed with localtunnel for the demo.

The flow is: voice → transcript → structured entry → database → conversational recall.

[Add one or two lessons from building it, such as a debugging story or a prompt that took many tries.]

Why Does Open Innovation Matter?

A journal is about the most private thing you can give an AI, so this matters here more than for most projects.

Your voice and memories stay yours. Transcription, the model, and the database all run on your own machine or runtime. No audio or diary entry has to be sent to a company’s server.
Nothing locks it in. The journal is a SQLite file, and the models are swappable. If a hosted service shuts down, raises prices, or changes its terms, your memories don’t go with it. For a project about not losing the past, that matters.
It costs nothing to run. There are no per-minute transcription fees or API bills, so keeping a daily journal stays affordable.
I can change how it behaves. I could swap qwen2.5 for another model, change the prompts, and add the journal modes without asking anyone’s permission.

[If you tested it offline, say so here. It’s your strongest “works with the lights off” point.]

My Agent Session

[Link or embed your DevRelay session with the agent_session tag, or remove this section.]

The Spirit of It

[Optional. Add the moment it landed, for example Ragul’s reaction, or a time it played back something you’d forgotten. If there isn’t one yet, delete this section rather than inventing it.]

Prize Categories

[List the partner categories you’re entering, or remove this section.]