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

CodeSnap AI: Let AI Handle the Tedious Parts of Learning to Code 🦥

What I Built

Learning to code through YouTube tutorials is great, but collecting code snippets from videos can be surprisingly tedious. You pause the video, try to capture the code, copy it manually, fix OCR errors, figure out what it does, and organize it somewhere for later.

I wanted to make that process easier.

CodeSnap AI is an AI-powered extension of my CodeSnap Chrome extension that helps learners capture, understand, and organize code from programming tutorials.

The goal is simple: capture code once and let AI handle the repetitive work.

Instead of manually organizing every snippet, users can:

• Extract code from tutorial screenshots using OCR.
• Use a local open-weight AI model to help correct OCR mistakes.
• Generate concise explanations of code snippets.
• Organize snippets by programming language and topic.
• Create revision notes from saved code.

The idea is to spend less time managing learning materials and more time actually learning.

Demo

Demo video: [Add your demo video link here]

Live demo: [Add your deployed extension or project link here]

A demo would show a coding tutorial, capture a code snippet, process it locally with AI, and save an organized explanation for later revision.

Code

GitHub repository: https://github.com/ikshita22/Codesnap_v2

CodeSnap is the starting point for this project. The AI-powered features build on its existing code-capture workflow.

How I Built It

I built this project around an existing browser extension workflow, with the goal of introducing AI without making the entire experience dependent on a remote AI service.

The planned architecture combines:

• Chrome extension: Provides the interface for capturing and managing code snippets.
• OCR: Extracts text from code displayed in tutorial videos.
• Open-weight language model: Helps correct OCR errors, explain code, and generate useful notes.
• Local inference: Runs the model on the user's machine through a local inference runtime such as Ollama.
• Snippet organization: Keeps captured code and its explanations accessible for later revision.

The important design choice is that the language model should do useful work rather than simply power a chatbot. It takes an existing, repetitive task and turns it into a more automated workflow.

Why Does Open Innovation Matter?

For a tool that processes learning materials and personal code snippets, running AI locally offers meaningful advantages.

1. Privacy by design

Code snippets can contain proprietary code, personal projects, or unfinished assignments. Local inference can keep that content on the user's machine instead of sending it to a third-party AI API.

2. Less dependence on external services

Once the model and required dependencies are installed, local inference can work without an internet connection. Capturing content directly from YouTube still requires connectivity unless the video is available locally.

3. Freedom to change models

Open-weight models make it possible to experiment with different models and choose one that works best for code correction, explanations, and note generation. The application does not have to be permanently tied to a single proprietary provider.

4. More control over cost

There is no per-request fee from a hosted AI API when inference runs locally. Users still need suitable hardware, storage, and electricity, and larger models may require more resources.

For this project, open innovation is about making AI more private, customizable, and accessible—not just adding another AI feature to a browser extension.

The Lazy Payoff 🦥

The payoff is fewer repetitive steps between watching a programming tutorial and having useful, organized notes.

Instead of repeatedly pausing, copying, correcting, explaining, and filing snippets by hand, learners can automate much of that process.

I haven't included a numerical time-saving claim because it should be measured through an actual comparison. A useful test would compare the time required to collect and organize several snippets manually against the time required with CodeSnap AI.

The aim is to make learning a little less tedious, one snippet at a time.