behat's comments

On: Ask HN: What are you working on? (February 2026)

[behat]

An on-call runbook execution engine - being able to take plain text runbook steps like - look at logs for $service, check for dependency failures - look at so-and-so dashboard.

and execute them when an alert fires.

We are at https://www.relvy.ai

On: The killer app of Gemini Pro 1.5 is using video as an input

[behat]

Heh. Built a macOS app that does something like this a while ago - https://github.com/bharathpbhat/EssentialApp

Back then, I used on device OCR and then sent the text to gpt. I’ve been wanting to re-do this with local LLMs

On: Show HN: Open-source macOS AI copilot using vision and voice

[behat]

Nice! Built something similar earlier to get fixes from chatgpt for error messages on screen. No voice input because I don't like speaking. My approach then was Apple Computer Vision Kit for OCR + chatgpt. This reminds me to test out OpenAI's Vision API as a replacement.

Thanks for sharing!

[ralfelfving → behat]

Thanks! You could probably grab what I have, and tweak it a bit. Try checking if you can screenshot just the error message and check what the value of the window.owner is. It should be the name of the application, so you could just append `Can you help me with this error I get in ${window.owner}?` to the Vision API call.

On: Tech stack for fine-tuning LLMs

[behat]

Thank you for sharing! The HF docs seem easy to follow. My application is text generation itself, so may have different results.

On: Tech stack for fine-tuning LLMs

[behat]

Thank you for sharing your experience. The linked blog post is great!

On: Show HN: Aider, a command line GPT coding copilot

[behat]

Very interesting! Good to know that gpt-4 was a step change here.

I tried with 3.5 since that's all I have access to currently, I asked it to do a few things in a ruby app step by step, touching one file at a time, and it worked well! A configuration option that lets you ask the tool to just make file edits, and let me commit later would be useful.

What happens when the files are too large?

[anotherpaulg → behat]

Thanks for giving it a try! Glad to hear it was working for you with 3.5.

If you exceed the context window, it will just throw an exception and fail.

I will add a config to disable auto commits. But I find it liberating to use the git history as an undo stack. You can do experiments on a branch and discard it if things don't work out.

[anotherpaulg → behat]

If you upgrade to the newest version, it has a --no-auto-commit switch.