78 karma · joined July 21, 2024
Is the main differentiator the ownership-based safety model, tighter integration with Rust ecosystems, or idk are there workloads where the Tile IR pipeline has advantages beyond language ergonomics?
Plus after each run you get screen recordings with console logs, network requests, HARs, and Playwright traces so you can inspect exactly what the agent did :)
https://github.com/wizenheimer/canary
P.S. I attempted to do a Show HN but got flagged for some reason
"Shift my afternoon back 30 minutes" → Done. "When am I free next week?" → Answered. "Block Friday for deep work" → Blocked.
Open-Source alternative to Howie.ai, Claralabs, and more
It uses, relies and depends on Chrome exposed primitive such IndexedDB. Hence the term chrome native.
Honestly, didn't give much thought to it. Just rolled with it :D
Unlike it's keyword search counterpart it expensive. Order of magnitude expensive. All because you need to maintain a vector search index and keep it available server side.
Enter Tinkerbird. This little library takes the heavy lifting and pushes it client side. Stream your embeddings, front it via CDN or cache it on client. Now you get benefits of vector index without the costs of maintaining one.
Playground: https://tinkerboard.vercel.app/ Repo: https://github.com/wizenheimer/tinkerboard
PS: Pretty early nonetheless, hacked it together during last Christmas. Gotta make it usable.
PPS: I guess the README is dated. Built out a sample app for Tinkerbird. Feel free to take a look: https://github.com/wizenheimer/tinkerboard