🌱 GrowWise: An AI Garden Coach That Wants You to Close This Tab and Touch Some Actual Grass

A developer built GrowWise, an open-source AI gardening companion that runs on a locally hosted open-weight model with no API tokens or cloud AI costs. The app combines an AI Garden Coach, outdoor "Touch Grass" missions, plant health guidance, and a gardening journal stored in browser local storage, and was submitted to the Hacktoberfest Open-Source AI Challenge Week 1. Its stated goal is to use AI as a starting point for real-world activity rather than as a destination.

An AI gardening companion powered by a locally running, open-weight model. No API tokens. No cloud AI bill. Just plants, dirt, and a gentle reminder that your houseplants have been waiting for attention since your last software deployment. This is a submission for the Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass https://dev.to/challenges/hacktoberfest-week1-2026-10-05 Meet GrowWise — an AI-powered gardening companion designed to turn screen time into green time. Here is a problem I think many of us can relate to: You open your laptop to learn something productive. Three hours later, you have read 17 articles about productivity, watched six videos about building better habits, and somehow become an expert at watching other people grow plants. Meanwhile, the plant on your windowsill is fighting for its life. We have AI that can write code, summarize meetings, generate presentations, and help us avoid typing a five-line email. But what if we used AI to help us do something away from our screens? That is the idea behind GrowWise . GrowWise helps users start and maintain their gardening journey with an AI Garden Coach, outdoor missions, plant health guidance, and a gardening journal. The goal is simple: make getting outside feel less intimidating, more rewarding, and easier to turn into a habit. Modern life makes it surprisingly easy to spend an entire day indoors. Work, social media, streaming, and the endless “just one more video” loop compete for our attention. Gardening can be a simple way to reconnect with nature, but beginners often face questions such as: GrowWise addresses these challenges by combining practical gardening guidance with small, achievable outdoor activities. Instead of making AI the destination, GrowWise uses AI as the starting point for a real-world activity. Ask a question, get guidance, step outside, and let the plants have the spotlight. 1. AI Garden Coach Get gardening guidance and recommendations tailored to your question. Whether you are a complete beginner or someone trying to keep a suspiciously droopy plant alive, the coach helps you figure out your next step. Example: “I'm a beginner with a small balcony and 15 minutes a day. Where should I start?” Instead of opening 27 browser tabs, you can use the Garden Coach to get a practical starting point. 2. 🌳 Touch Grass Missions Small, actionable missions encourage users to step away from their screens and do something outdoors. The idea is to make nature accessible even when you do not have a large garden, expensive equipment, or an entire Saturday free. Examples include checking the soil of a plant, observing sunlight on your balcony, or spending a few minutes caring for your garden. Because sometimes the most ambitious outdoor plan you can manage on a Tuesday is watering a plant. And that counts. 3. 🩺 Plant Health Check Need help figuring out what might be wrong with a plant? The health-check feature helps users think through plant-care concerns and explore practical next steps. It is designed as a gardening aid, not a magical botanical emergency room. For serious plant problems, local gardening experts and reliable horticultural resources are still valuable. 4. 📔 Gardening Journal Record your gardening journey and keep track of what you have been doing. The journal helps turn individual gardening activities into a continuing habit. Mission completion and journal entries are stored in the browser's local storage in the current implementation, so this data is local to that browser rather than automatically synced across devices. 5. 🌱 Beginner-friendly gardening experience GrowWise brings the gardening coach, missions, health guidance, and journal into one experience, helping users move from “I should probably grow something” to actually doing something about it. The aim is not to build another app that keeps you scrolling forever. It is to give you enough guidance to close the app and get your hands dirty. Live website: https://grow-wise-rho.vercel.app/ https://grow-wise-rho.vercel.app/ GitHub repository: https://github.com/praniket01/GrowWise https://github.com/praniket01/GrowWise Local AI demo: https://drive.google.com/file/d/1lF92-iEjizUswAQMT7f1x8om3OSxqjid/view?usp=drive link https://drive.google.com/file/d/1lF92-iEjizUswAQMT7f1x8om3OSxqjid/view?usp=drive link The web application is deployed on Vercel, while the AI inference demo runs locally on my machine using Ollama and Qwen2.5 3B. The public website and the locally running AI service are not the same deployment. The local AI functionality should therefore be demonstrated using the actual local setup and screenshots rather than implying that the public website is connected to a publicly hosted AI backend. This setup also demonstrates an important part of the project: a capable AI model can run on your own machine without requiring a paid cloud inference API. Source code: https://github.com/praniket01/GrowWise https://github.com/praniket01/GrowWise The project is built with a modular architecture so the web application and AI service can be developed and run separately. The repository includes the frontend, AI service, Docker configuration, and environment-variable examples needed to understand and run the application. If you explore the code, start with the AI recommendation endpoint and follow how a gardening request moves from the web application to the Python service and then to the local model. GrowWise combines a modern web stack with locally hosted open-weight AI. For the AI component, I chose Qwen2.5 3B through Ollama . Rather than sending each gardening question to a paid, hosted AI API, I run the model locally and expose it through Ollama's local API. The FastAPI service communicates with that endpoint and provides the response to the application. The flow looks like this: User → Next.js → FastAPI → Local Ollama → Qwen2.5 3B → Gardening response In the local setup, this means: There is one practical detail worth mentioning: the model needs to be downloaded first, and the computer still needs enough resources to run it. Local inference is not the same as having zero hardware costs or never needing an internet connection. But once the model is available locally, the AI inference itself does not depend on a paid hosted model endpoint. Keeping the AI service separate from the frontend makes the architecture easier to understand and extend. The frontend handles the user experience. FastAPI handles the recommendation request. Ollama handles local model inference. This separation also makes it easier to experiment with a different open-weight model or a different inference environment in the future. For GrowWise, open innovation is not just a checkbox that says “uses AI.” It changes how the application can be run, understood, and extended. A closed, hosted AI API would certainly be a convenient way to build the Garden Coach. However, it would also introduce a dependency on an external inference service, its pricing, its availability, and its API credentials. Using an open-weight model locally gives this project a different set of possibilities. 1. Experiment without an API-token scavenger hunt Getting started with local inference does not require obtaining a paid model API key. Developers can download a supported model and experiment on their own machine. 2. More control over data flow In the local configuration, gardening prompts are sent to the locally running model rather than an external model provider. That gives the developer more control over where those prompts go. This is especially useful when building applications where users may share personal notes or other information they would prefer to keep local. 3. Freedom to switch models The AI service communicates through an API-compatible interface, so another compatible model or inference provider can be explored without rebuilding the entire frontend. Today it is Qwen2.5 3B. Tomorrow, it could be another open-weight model that performs better for gardening advice or runs more efficiently on modest hardware. 4. Lower barriers to learning and building Not everyone wants to pay for cloud inference just to experiment with an idea. Local models let developers prototype, learn, and test without a per-request inference bill. 5. Technology that serves the real world The most important reason is the project's purpose. AI is often used to generate more content, more notifications, and more reasons to remain online. GrowWise explores a different direction: use AI to provide enough useful guidance that the user can leave the screen behind. The ideal user journey is not: Question → AI response → 40 follow-up questions → 3 hours online It is: Question → Practical guidance → Outside → Happy plants 🌱 That is what open innovation makes possible here: not just a different way to access AI, but a different way to use it. GrowWise started with a simple question: What if AI helped us spend less time using technology and more time doing something meaningful outside? It is a small step toward that idea. A garden coach, a few outdoor missions, a place to record progress, and an open-weight model running locally without a paid AI API token. You do not need a sprawling garden, a greenhouse, or the knowledge of a professional botanist to begin. You might only need a pot, some soil, a little curiosity, and ten minutes away from your screen. So go ahead. Ask the AI what to plant. Then close the tab. Your plants have been waiting for this meeting to end. 🌿