Chalte-Chalte: Building a Local-First AI Companion for Reflective Walks
Chalte-Chalte — The Walking Philosopher
What if your next walk became a conversation with yourself?
We spend hours staring at screens, consuming content, and asking AI to give us answers. But what if AI could help us slow down, step outside, and ask ourselves better questions instead?
That idea led me to build Chalte-Chalte — The Walking Philosopher, a project for the Touch Grass challenge at MLH Global Hack Week: Hacktoberfest.
The idea
Chalte-Chalte is a mobile-friendly web app designed to turn an ordinary walk into a reflective experience.
Instead of scrolling through another feed while walking, you choose a topic, set your mood, and let an AI companion prepare thoughtful questions for your walk.
The idea is simple: AI should not always give us answers. Sometimes, it should help us discover our own.
How it works
The intended experience follows a simple flow:
1. Choose your intention: Pick a topic or mood for your walk.
2. Prepare to walk: Generate three open-ended questions to think about.
3. Step outside: Walk, observe your surroundings, and reflect on the questions.
4. Capture your thoughts: Use voice notes to record reflections when you want to.
5. Create a walk journal: Turn your thoughts into a personal record of ideas and reflections.
The goal isn't to keep you glued to your phone. It's to make the technology useful while encouraging you to spend more time away from the screen.
Why local AI?
One of the most interesting parts of this project is exploring open-source AI that can run locally.
The backend uses FastAPI to communicate with Ollama, and I have Gemma 3 1B available locally for experimentation. The project is designed around local inference rather than requiring a paid, hosted AI API for its core reflective experience.
Why does this matter?
- Privacy: Personal reflections can be sensitive. Local inference offers a path toward keeping AI processing on your own machine.
- Accessibility: A small model can make experimentation possible without depending on a large hosted model.
- Open innovation: Developers can inspect, modify, and experiment with the system instead of treating AI as a black box.
- Ownership: Tools for personal reflection should give people more control over their experiences and data.
Local inference alone doesn't guarantee complete privacy, so the app still needs careful handling of recordings, storage, and any network requests. That's an important part of building this responsibly.
The technology behind it
Here's the current technology stack:
- Frontend: React, Vite, TypeScript
- Backend: Python, FastAPI
- Local AI: Ollama and Gemma 3 1B
- Transcription: Optional local Whisper integration, depending on configuration
- Experience: Mobile-friendly Progressive Web App
I wanted the project to remain approachable to contributors who want to experiment with frontend development, local AI inference, or privacy-conscious AI applications.
Building under a hackathon deadline
This project has been a reminder that building an AI application involves much more than generating text from a model.
The frontend and backend must communicate correctly. Request schemas need to match, model outputs need validation, and the application needs to handle failures honestly.
I've prepared the FastAPI backend, added automated backend tests, and verified that the local Gemma model can generate reflective questions. The remaining challenge is validating the complete experience across the frontend, backend, and local model.
I'm treating that distinction seriously: a passing unit test is useful, but it isn't the same as proving that the entire application works end to end.
What's next?
My next priorities are:
- Verify the complete question-generation and journal-generation flow.
- Improve the walking experience on mobile screens.
- Refine voice-note and transcription support.
- Make local data handling transparent and privacy-conscious.
- Make it easier for contributors to run and extend the project.
Why I built this
I like building AI systems, but I also think we should question how we use them.
Not every interaction needs to be optimized for engagement. Not every thought needs an instant answer. And not every AI application needs to send personal information to a remote service.
Sometimes, the best thing technology can do is encourage us to put our phones away and pay attention to the world around us.
That's the idea behind Chalte-Chalte.
Walk a little. Think a little deeper. Let AI ask the questions.
Explore the project
- GitHub repository: Chalte -Chalte
I'd love to hear your thoughts: Would you use an AI companion that helps you reflect during a walk? What would you want it to do—and what should it never do?
Built for the MLH Global Hack Week: Hacktoberfest — Week 1 “Touch Grass” challenge.
#devchallenge #hf26challenge
Mentions
Chalte-Chalte: Building a Local-First AI Companion for Reflective Walks Chalte-Chalte — The Walking Philosopher What if your next walk became a conversation with yourself? We spend hours staring at screens, consuming content, and asking AI to give us answers. But what if AI could help us slow down, step outside, and ask ourselves better questions instead? That idea led me to build Chalte-Chalte — The Walking Philosopher, a project for the Touch Grass challenge at MLH Global Hack Week: Hacktoberfest. The idea Chalte-Chalte is a mobile-friendly web app designed to turn an ordinary walk into a reflective experience. Instead of scrolling through another feed while walking, you choose a topic, set your mood, and let an AI companion prepare thoughtful questions for your walk. The idea is simple: AI should not always give us answers. Sometimes, it should help us discover our own. How it works The intended experience follows a simple flow: 1. Choose your intention: Pick a topic or mood for your walk. 2. Prepare to walk: Generate three open-ended questions to think about. 3. Step outside: Walk, observe your surroundings, and reflect on the questions. 4. Capture your thoughts: Use voice notes to record reflections when you want to. 5. Create a walk journal: Turn your thoughts into a personal record of ideas and reflections. The goal isn't to keep you glued to your phone. It's to make the technology useful while encouraging you to spend more time away from the screen. Why local AI? One of the most interesting parts of this project is exploring open-source AI that can run locally. The backend uses FastAPI to communicate with Ollama, and I have Gemma 3 1B available locally for experimentation. The project is designed around local inference rather than requiring a paid, hosted AI API for its core reflective experience. Why does this matter? - Privacy: Personal reflections can be sensitive. Local inference offers a path toward keeping AI processing on your own machine. - Accessibility: A small model can make experimentation possible without depending on a large hosted model. - Open innovation: Developers can inspect, modify, and experiment with the system instead of treating AI as a black box. - Ownership: Tools for personal reflection should give people more control over their experiences and data. Local inference alone doesn't guarantee complete privacy, so the app still needs careful handling of recordings, storage, and any network requests. That's an important part of building this responsibly. The technology behind it Here's the current technology stack: - Frontend: React, Vite, TypeScript - Backend: Python, FastAPI - Local AI: Ollama and Gemma 3 1B - Transcription: Optional local Whisper integration, depending on configuration - Experience: Mobile-friendly Progressive Web App I wanted the project to remain approachable to contributors who want to experiment with frontend development, local AI inference, or privacy-conscious AI applications. Building under a hackathon deadline This project has been a reminder that building an AI application involves much more than generating text from a model. The frontend and backend must communicate correctly. Request schemas need to match, model outputs need validation, and the application needs to handle failures honestly. I've prepared the FastAPI backend, added automated backend tests, and verified that the local Gemma model can generate reflective questions. The remaining challenge is validating the complete experience across the frontend, backend, and local model. I'm treating that distinction seriously: a passing unit test is useful, but it isn't the same as proving that the entire application works end to end. What's next? My next priorities are: - Verify the complete question-generation and journal-generation flow. - Improve the walking experience on mobile screens. - Refine voice-note and transcription support. - Make local data handling transparent and privacy-conscious. - Make it easier for contributors to run and extend the project. Why I built this I like building AI systems, but I also think we should question how we use them. Not every interaction needs to be optimized for engagement. Not every thought needs an instant answer. And not every AI application needs to send personal information to a remote service. Sometimes, the best thing technology can do is encourage us to put our phones away and pay attention to the world around us. That's the idea behind Chalte-Chalte. Walk a little. Think a little deeper. Let AI ask the questions. Explore the project - GitHub repository: Chalte -Chalte I'd love to hear your thoughts: Would you use an AI companion that helps you reflect during a walk? What would you want it to do—and what should it never do? Built for the MLH Global Hack Week: Hacktoberfest — Week 1 “Touch Grass” challenge. #devchallenge #hf26challenge