Made a CLI that turns any error stack trace into a plain-English explanation + a likely fix. Pipe stderr into it.
$ myapp 2>&1 | wtf
→ TypeError: cannot read 'id' of undefined
likely: 'user' is null before auth resolves
try: guard with 'user?.id' or await getUser()
Piping stderr into an explainer is the kind of tool I didn't know I needed. Shipping this into my dotfiles today.
Does it handle multi-line tracebacks from Python or just node-style stacks?
Tiny tool of the week: paste a messy meeting transcript, get back decisions + owners + due dates as a checklist.
74Thread: how I wired streaming tool-use with the Claude API in ~40 lines. The trick is buffering partial JSON until the block closes.
53My entry: a tiny standup agent that reads our repo's merged PRs + issue moves each morning and posts a 5-line summary to the team channel. One cron, one prompt, no dashboard. The team thinks I write them by hand.
5