Great research shouldn't just be readβ€”it should be used. I see the open-source community as a living laboratory where real-world impact is the only metric that truly matters. Let's build in the open!

Open-source map

Lead
DeepTutor

Lifelong personalized tutoring β€” an agent-native workspace where chat, quizzes, research and practice all run on one loop.

36k 4.5k Python docs pypi paper
Member
nanobot

Self-hosted personal AI agent framework β€” tools, memory, MCP, multi-agent workflows.

47k 8.3k Python docs pypi
Lead
CatchMe

Vectorless screen memory that makes your agents truly personal.

468 73 Python blog
Member
Litewrite

Vibe writing β€” draft faster, with the model in the sentence.

159 20 TypeScript demo
Personal
Smart-Car-Competition

FOC dual-driver control for an Infineon TC264 smart car.

C 2025
Personal
Academic-Support-System

Django study assistant β€” notes, mind maps and practice questions.

Django 2025
Personal
Pose-Evaluation-System

Per-limb movement scoring from video, with local-LLM feedback.

PyQt5 2025
Personal
Model-Agent

Multi-agent solver that critiques its own math modelling attempts.

Python 2025

What I build

DeepTutor treats tutoring as one agent loop rather than a collection of features. Chat, Quiz, Research, Visualize, Solve and Mastery Path are objectives on the same loop, so knowledge bases, notebooks, question banks and personas stay addressable from any of them instead of being siloed per tool. Retrieval is pluggable across LlamaIndex, PageIndex, GraphRAG, LightRAG and linked Obsidian vaults, and an external coding CLI can be consulted as a subagent mid-turn. The learner model is three explicit layers β€” L1 traces, L2 summaries, L3 synthesis β€” exposed through a memory graph, so every inference the system draws about a learner is inspectable and editable rather than latent in a prompt.

36k 4.5k code docs pypi paper

CatchMe argues that personal memory is a navigation problem, not a search problem. Six recorders capture GUI activity β€” window focus, keystrokes, mouse, screenshots, clipboard, notifications β€” and deterministic rules (window switches, idle timeouts, temporal clustering) fold them into a five-level tree: day β†’ session β†’ app β†’ location β†’ action. Structure is rule-based; content is LLM-summarised bottom-up as nodes close, incrementally rather than in an end-of-day batch. Retrieval carries no embedding index: a rule pass prunes by time, then an LLM traverses the tree, selecting multiple branches per level and reading raw evidence only where it needs to. That holds up on fragmented, cross-modal activity data where similarity search does not, in ~0.2 GB locally, behind a single skill file any CLI agent can call.

468 73 code blog