kangraemin

11 ms·

1. 1.▲
   by kangraemin 6mo ago

   This is essentially tool use with a filesystem interface — the LLM decides what to read instead of a retrieval pipeline choosing for it. Clean idea, and it sidesteps the chunking problem entirely. Curious about the latency though. RAG is on
2. 2.▲
   by kangraemin 6mo ago

   Moving from a menu bar app to a proper window is a bold call. Menu bar was convenient for "set it and forget it" but terrible for anything beyond toggling on/off. Curious if they'll keep the menu bar icon as a quick shor
3. 3.▲
   by kangraemin 6mo ago

   "Risk aversion preventing fixes" is the most accurate part. I've seen this at other large companies too. You have a known bug, you know exactly how to fix it, but nobody will approve the change because "what if it breaks
4. 4.▲
   by kangraemin 6mo ago

   The "sanitised optimism" problem is real. I've seen agents report "fixed!" when they just suppressed the error. Role separation (builder/reviewer/tester) helps but the reviewer agent also tends to be too p
5. 5.▲
   by kangraemin 6mo ago

   I did something similar with Slack as the transport layer. Threads work well as conversation context — the bot fetches previous thread messages and rebuilds the full history before each request. The part that got tricky was queueing. The CL