Needed 10 messy texts turned into calendar entries, like "pickup moved to 3:15 thursday" and "moms bday dinner is the 28th at 6".
Ran BotPsy-0.8B, Tether's tiny tool-use model, locally on llama.cpp, CPU only. It took 1:53 for all 10. Didn't time myself typing them in, so minutes saved isn't measured.
It got 5 of 10 dates wrong. Every miss was a relative day: "sat" became today, "next mon" and "the 28th" both became Nov 17, and Friday and Sunday each landed a day off. Times were right, but most had no am/pm.
Kill for scheduling from texts. A wrong date is worse than no entry.
Small test on one machine, not a benchmark.
1
1
23
Needed a long contractor email read to me so I could listen instead of read.
Ran ZONOS3-Mini on the free Hugging Face Space. Reading it myself took 4:59. Listening took 4:25 total, counting generate time for both runs. So 34 seconds saved, and my hands were free the whole time.
Heads up: the free Space cut off near the end. Pasting the rest took 14s to generate and 51s to play, and it read the rest cleanly.
Keep for listening to long emails while doing something else. Split anything long into two on the free demo.
Small test on one email, not a benchmark.
1
22
Needed to know which of my last 30 emails actually needed a reply today.
Ran Kev-4B (CPU only, llama.cpp) on the same 30. It got through all of them in 1:24. I did it by hand in 2:58. So 94 seconds saved.
Only 1 of the 30 needed a reply, and Kev missed it. It flagged 3 neighborhood app posts instead.
Kill for sorting my inbox. Saving a minute and a half doesn't help if it skips the one email I had to answer.
Small test on one inbox, not a benchmark.
1
3
21
Asked Grok Bot to test kniv v7 large (INT8, CPU) on a fictional PCB handoff.
First run: 4.734s, no facts extracted.
Follow-up: identical input gave inconsistent results. One CPU thread made our tested runs repeatable, but only 3/10 expected facts matched exactly. It turned “might work on” into a definite fact.
Kill for unattended handoff capture in this setup. Small test on one machine, not a benchmark.
1
2
26
Asked free Gemini to code an app from a drawing on paper.
Job: a one-screen event signup (name, team, submit), plus one fix: green submit button.
Free Gemini Canvas: 37.34s, fix included. Preview took input and submitted.
Me in Google Forms: 4:19.21.
About 3:42 saved.
Keep for a quick form from a sketch.
2
28
Typing my Monday workout into Sheets took 6:04. Photo Sheet did it in 25.47s with every number right.
Timed Photo Sheet (OpenKrill, free, no signup) against typing the same list myself.
Typing into Google Sheets, with edits: 6:04.
Photo Sheet through Grok Bot: 25.47s for 10 rows. Every number matched. Nothing marked unclear.
About 5:39 saved.
Heads up: OpenKrill reads the photo with Gemini/Groq free tiers and keeps the CSV link about 24 hours.
Keep for a handwritten list into a spreadsheet. Kill if you need live cell edits inside Google Sheets chat (that one wasn't free on my account).
1
19
Tested Spacely AI's free plan on my gaming room/office. It makes you pick a room type, so I kept it a gaming room.
68.06s for 4 full redesigns, plus a zip with depth maps, albedo and other 3D files. It kept the back window, the shutters and the sloped ceiling. The free plan adds a watermark.
For comparison, free Gemini did one modern LA version in 42.25s, kept every window, and listed 5 products to buy. About 3 of the 5 match the image.
Keep if you do interior or architecture work and need options plus 3D files. Check the windows and doors before you show a client. For one quick concept, free Gemini is enough.
🤖 Made with AI
29
Asked NVIDIA's new Nemotron 3.5 Transcribe for the 5 key points of a 15-min Joe Rogan clip with Robert Whittaker, and who said each.
Free demo: 6.47s.
Me at 2x, taking notes: 8:47, almost 9 minutes.
4 of 5 matched mine, all with the right speaker, and nothing made up. It missed Rob breaking down his own fighting style (around 5:20), used the intro as a point, and one timestamp was off by 30s.
Keep for pulling key points. It saved me 8 minutes on one clip.
Heads up: the free demo 504'd on the full 55 min, so I cut it to 15.
What would you make it listen to?
2
42
Asked a 2B vision model running on my own GPU: can I park here at 11am on a Tuesday?
LFM3-VL-2B (local, thinking off): "No." 17.46s.
Free Claude Sonnet 5.5 (medium, no extended thinking): "No." 9.23s.
Both got it right. But LFM read the hand-covered sign as "7-9pm Sunday." The real sign says 7am-7pm. Claude said the hand blocks it and didn't guess.
With thinking on, LFM looped for 2,048 tokens and never answered.
Kill for sign reading. Twice as slow and it made up a detail.
Would you trust a local model to read parking signs?











