Show HN: SSH Ache – open-source desktop SSH client with SFTP, tunnels and MCP
2 by tanvirmahin24 | 0 comments on Hacker News.
Hack Nux
Watch the number of websites being hacked today, one by one on a page, increasing in real time.
New ask Hacker News story: Ask HN: Best way to archive 25 years of emails
Ask HN: Best way to archive 25 years of emails
2 by astatine | 6 comments on Hacker News.
I have emails from 1997-98 onwards all in one massive inbox, currently on gmail with emclient on Mac as the mail client (there have been probably a dozen services starting from self-hosted in the beginning). I would like to archive the historic mails for the first 25 years, but in a way that's actually searchable and usable in the future (and potentially importable to a new mail client/service) and not in any particular mailbox format that may go obsolete. There is no good reason to hoard them, other than "I feel like doing so". What are the best options, and tools?
2 by astatine | 6 comments on Hacker News.
I have emails from 1997-98 onwards all in one massive inbox, currently on gmail with emclient on Mac as the mail client (there have been probably a dozen services starting from self-hosted in the beginning). I would like to archive the historic mails for the first 25 years, but in a way that's actually searchable and usable in the future (and potentially importable to a new mail client/service) and not in any particular mailbox format that may go obsolete. There is no good reason to hoard them, other than "I feel like doing so". What are the best options, and tools?
New Show Hacker News story: Show HN: Convert PNG and JPG to clean SVG in seconds
Show HN: Convert PNG and JPG to clean SVG in seconds
3 by not_wowinter13 | 1 comments on Hacker News.
3 by not_wowinter13 | 1 comments on Hacker News.
New Show Hacker News story: Show HN: Kosh – Bash shell runtime with 100x faster Shellcheck and LSP built-in
Show HN: Kosh – Bash shell runtime with 100x faster Shellcheck and LSP built-in
2 by toiletbril | 0 comments on Hacker News.
Kosh is a Bash-compatible runtime focused on VERY detailed diagnostics and performance. The project started from frustration with how difficult shell errors can be to debug. And how slow some tools are. The project is feature-complete and the core is usable enough to experiment with. There is a Language Server that works on shell scrips, but I'm planning to expand it to support every conf/YAML/etc file that may have Bash embedded in, e.g. GitHub workflows. Report: bash incompatibility, broken diagnostics, cases where existing tools may solve the problem better Thanks!
2 by toiletbril | 0 comments on Hacker News.
Kosh is a Bash-compatible runtime focused on VERY detailed diagnostics and performance. The project started from frustration with how difficult shell errors can be to debug. And how slow some tools are. The project is feature-complete and the core is usable enough to experiment with. There is a Language Server that works on shell scrips, but I'm planning to expand it to support every conf/YAML/etc file that may have Bash embedded in, e.g. GitHub workflows. Report: bash incompatibility, broken diagnostics, cases where existing tools may solve the problem better Thanks!
New ask Hacker News story: Is "An agent with tools" the only valid LLM application?
Is "An agent with tools" the only valid LLM application?
3 by gmarkwa | 0 comments on Hacker News.
Brex's CEO said this and I understand where he comes from, but is there a place for end to end workflows in LLM based applications? At the end of the day I agree that cutting edge software should be fully usable by agents, but I can't decide if every product should be an agent. I personally hate the UX of most agentic applications. I have this fantasy of future products where I can simply enter input X and get output Y without having to give feedback on every little thing. Of course when you're designing something it needs to be a process, but what if I can tell my phone to "buy dinner" and it just does it without bothering me at every step? What if it was just good enough? I think a conversable agent is necessary as long as the application is unsure of the accuracy of the output, but I wonder if the UX of LLM applications could be more like a rich person fixing their car, like here is my situation, just do what you need to do and don't bother me.
3 by gmarkwa | 0 comments on Hacker News.
Brex's CEO said this and I understand where he comes from, but is there a place for end to end workflows in LLM based applications? At the end of the day I agree that cutting edge software should be fully usable by agents, but I can't decide if every product should be an agent. I personally hate the UX of most agentic applications. I have this fantasy of future products where I can simply enter input X and get output Y without having to give feedback on every little thing. Of course when you're designing something it needs to be a process, but what if I can tell my phone to "buy dinner" and it just does it without bothering me at every step? What if it was just good enough? I think a conversable agent is necessary as long as the application is unsure of the accuracy of the output, but I wonder if the UX of LLM applications could be more like a rich person fixing their car, like here is my situation, just do what you need to do and don't bother me.
New Show Hacker News story: Show HN: Watches user sessions, finds bugs that matter, and fixes them
Show HN: Watches user sessions, finds bugs that matter, and fixes them
11 by aray07 | 0 comments on Hacker News.
Hey HN, I’m Abhishek. I'm building Opslane, an open-source agent that identifies user-facing issues and investigates them. It only creates a PR if it can verify the fix. Demo: https://youtu.be/ccuOTYQMeYg Docs: https://ift.tt/5lgUM6E At my last job at Robinhood, we used to do a quarterly bug bash. We would go through our Sentry backlog and try to fix as many of them as possible. We only fixed bugs we knew were reported by customers. We had hundreds of bugs, and Sentry’s default priority levels made no sense. After the bug bash, we would declare bankruptcy - select all remaining bugs and mark them as resolved. This problem has only gotten worse since coding agents have become more prevalent. So I started thinking: what would Sentry look like if it were built in 2026? To me, error trackers have two failure modes: 1. False positives: They show you thousands of errors, and you can’t tell the impact on the user 2. False negatives: Many user-facing issues don’t throw exceptions, so they go unnoticed. Opslane combines error tracking and session recording. And there is an agent that acts on both. To get started, you install the Opslane SDK. It captures everything the user did: errors, console logs, network requests, and session recordings. Opslane reduces false positives by ranking issues based on how many users are facing a particular issue. It also learns about your product by reading your code and watching your session recordings. False negatives are harder. Opslane reviews session recordings to spot frustration. They look for rage clicks, dead clicks, and abandoned forms. This recently caught a bug in an early customer’s onboarding flow: a dropdown that closed itself when clicked. No exception, no bug report. The recordings showed users clicking it, selecting nothing, and dropping out of onboarding. Opslane flagged it and the team fixed it. Three guiding principles when building Opslane: 1. Open Source: Self-host with one Docker Compose file. 2.Agent-first: I never want to open an error dashboard again. Opslane ships an MCP server, so you can ask "what broke for users this week" from Claude Code. You get back issues that need your attention and you drive the resolution. 3. It knows about your product: Opslane is continuously learning about your product. Every investigation begins with what it knows about your product. It’s early. Frontend apps work end to end today.I am currently focused on improving reliability and accuracy. Here is a link to our repo: https://ift.tt/hCMRvK4 Would love to get feedback from folks on our approach to this problem!
11 by aray07 | 0 comments on Hacker News.
Hey HN, I’m Abhishek. I'm building Opslane, an open-source agent that identifies user-facing issues and investigates them. It only creates a PR if it can verify the fix. Demo: https://youtu.be/ccuOTYQMeYg Docs: https://ift.tt/5lgUM6E At my last job at Robinhood, we used to do a quarterly bug bash. We would go through our Sentry backlog and try to fix as many of them as possible. We only fixed bugs we knew were reported by customers. We had hundreds of bugs, and Sentry’s default priority levels made no sense. After the bug bash, we would declare bankruptcy - select all remaining bugs and mark them as resolved. This problem has only gotten worse since coding agents have become more prevalent. So I started thinking: what would Sentry look like if it were built in 2026? To me, error trackers have two failure modes: 1. False positives: They show you thousands of errors, and you can’t tell the impact on the user 2. False negatives: Many user-facing issues don’t throw exceptions, so they go unnoticed. Opslane combines error tracking and session recording. And there is an agent that acts on both. To get started, you install the Opslane SDK. It captures everything the user did: errors, console logs, network requests, and session recordings. Opslane reduces false positives by ranking issues based on how many users are facing a particular issue. It also learns about your product by reading your code and watching your session recordings. False negatives are harder. Opslane reviews session recordings to spot frustration. They look for rage clicks, dead clicks, and abandoned forms. This recently caught a bug in an early customer’s onboarding flow: a dropdown that closed itself when clicked. No exception, no bug report. The recordings showed users clicking it, selecting nothing, and dropping out of onboarding. Opslane flagged it and the team fixed it. Three guiding principles when building Opslane: 1. Open Source: Self-host with one Docker Compose file. 2.Agent-first: I never want to open an error dashboard again. Opslane ships an MCP server, so you can ask "what broke for users this week" from Claude Code. You get back issues that need your attention and you drive the resolution. 3. It knows about your product: Opslane is continuously learning about your product. Every investigation begins with what it knows about your product. It’s early. Frontend apps work end to end today.I am currently focused on improving reliability and accuracy. Here is a link to our repo: https://ift.tt/hCMRvK4 Would love to get feedback from folks on our approach to this problem!