catchup: a lazy morning brief for group chats, on a laptop with no internet
catchup: a lazy morning brief for group chats, on a laptop with no internet
catchup 讀取 WhatsApp 聊天匯出檔,透過本機 Gemma 3 1B 生成羣組聊天簡報,不需連接伺服器或帳戶。測試的 4 份合成聊天中,3 份簡報通過來源核對,但其中兩份仍有錯誤陳述。規則式簡報有時比模型摘要更有用。
This is a submission for the Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady
What I Built
catchup reads a WhatsApp chat export and gives you a short brief: what the chat was about, what got decided, and which questions are still open. it is for the group chat you skipped last night and don't want to scroll.
the lazy part: you export once, run one command, and read three lines instead of two hundred messages.
it runs on a small open-weight model (Gemma 3 1B, GGUF, through llama.cpp). nothing leaves the machine.
this project was built fully autonomously by an AI coding agent on my behalf. i did not write the code myself.
Demo
https://maybesomeone-arc18.github.io/catchup/demo/
the page runs the rules-only brief in your browser (paste an export, no upload). the Gemma output is precomputed from the CLI and shown as it came out, including where it is wrong.
Code
https://github.com/MaybeSomeone-arc18/catchup
How I Built It
the model does not decide what matters. plain rules do:
- a parser reads the export, drops system lines, joins wrapped lines, flags media.
- a scorer picks the load-bearing lines: question marks, question words, dates and times, plan words, your name.
- Gemma 3 1B gets only those lines and writes at most three short lines of prose.
- a checker compares every name, number and date in the answer with the chat. if something is not in the source, the answer is thrown away and a plain extractive brief is printed.
stack: Python, llama-cpp-python 0.3.36, Gemma 3 1B instruct Q4_K_M. 15 unit tests for the parser, scorer and checker.
What I measured
4 hand-written chats (3 to 19 messages), on a 2-core, 2 GB RAM sandbox:
- 3 of 4 Gemma briefs passed the source check. 1 was rejected and replaced by the template.
- 7.1 s median, 8.8 s max per brief.
then i read the 3 passing briefs against the chats myself. one was vague but fine. two had wrong claims. for example it wrote that Ma called Didi, when Rohan did. it also turned "finalising the plan" into "finalising goals".
so the checker does what it says: it stops invented names and numbers. it does not stop a 1B model from mixing up who did what. a brief can pass and still be wrong.
the other result surprised me. on the exam chat, the rules-only brief in the demo (the five rule-picked messages, verbatim) was more useful than the Gemma summary. it kept "deadline moved to wednesday 6 pm" and "does wednesday's test cover unit 5 as well?" word for word. the model dropped both.
Why Does Open Innovation Matter?
- group chats are private. with an open-weight model the chat stays on your own machine, with no server and no account.
- it costs nothing to run, today or later, so a lazy tool does not turn into a subscription.
- the checker only works because i can see and control the whole pipeline. i can swap the model file, tighten the check, or drop the model and keep the rules. with a closed API i could not guarantee the "only numbers from the source" rule.
where open was worse: a 1B model is weak at attribution. a bigger open model would likely do better, but i did not test one.
Limits
- 4 synthetic chats, no real private chats, no field use.
- only the
d/m/yy, h:mm am - name: textexport shape is parsed. - i did not compare against a closed model.
- the numbers above are from one run, not an average.
來源:DEV Community · dev.to