News for hackers. Stuff that matters.

ilusion

Have you tested what it remembers from early in the stream after a shift in the topics thrown at it?
Re:Cloudflare Quick Tunnels on Saturday September 19, 2026 @12:11AM (#49763251)
I have my own solution here that also works for sharing stuff with clients with configurable whitelists at artifacts.iofold.com (also open-source for self hosting on cf workers for almost free, github linked on the homepage)
Re:Ask HN: What Are You Working On? (July 2026) on Monday July 13, 2026 @01:49AM (#48888399)
I'm working on https://artifacts.iofold.com, a way to use artifacts (self contained html + optional assets like image/video/json) easily across agents, with feedback loop and docsend style wttribiti gates.

Have made it agent friendly enough that my teammates' agents can read and drop commennts on specs/storyboards etc, and my agent can close the loop by iterating with a new artifact version.

Re:Show HN: RLM-based local debugger for AI agent traces on Tuesday June 23, 2026 @11:59PM (#48654931)
I'm very curious to see a benchmark for this - have toyed with the idea myself but haven't put in the hard work to test these hypothesis on extracting learning signal from deep-agent traces.
Excited to see this launch, have been using bhatti for some time now!
The profile as a memory primitive is pretty interesting, how do you scale it for a scoped access/hierarchical setting? (for example, overall memory of processes => customer specific => project specific memory)
Re:A 54KB client-side HNSW vector search engine in WASM on Friday March 27, 2026 @01:03AM (#47539256)
This is insane and obvious at the same time - why is everyone not doing this instead of server side retrieval for webrtc based voice agents?
Does this mean opencode (and other such agent harnesses that auto update) might also be compromised?
Re:Ask HN: What Are You Working On? (October 2025) on Monday October 13, 2025 @12:20AM (#45564641)
I've struggled with adding evals to my AI agents for last few months, and felt that vibe evals should have a path to building a robust system down the line.

Working on a plugin for langfuse to create evals functions and dataset from ingested traces automatically, based on ad-hoc user feedback.

bitcoin just needs to achieve a closed loop economy, and this won't sound as bad