Show HN: Reame – a CPU inference server that gets faster as it runs
7 by targetbridge | 2 comments on Hacker News.
7 by targetbridge | 2 comments on Hacker News.
Saturday, July 11, 2026
Friday, July 10, 2026
Thursday, July 9, 2026
New top story on Hacker News: Show HN: Abralo – Free, easy way to run several Claude Code agents in one window
Show HN: Abralo – Free, easy way to run several Claude Code agents in one window
15 by cwbuilds | 4 comments on Hacker News.
Hi guys, I've been using Claude Code for almost everything lately. Have given one an email account so it can research business leads, draft emails, fact-check them and clear them with me before sending (works really well by the way). I also tend to have a few Claude Code agents running at any one time for coding. I used to create a split terminal to manage them from there, but found working in the terminal all day pretty depressing and, more importantly, found it hard to follow Claude Code's process and see which agents needed my immediate attention. I tried Anthropic's VS Code Claude Code extension and it had a great UI (more info on Claude Code's process and easier to read), but it crashed my PC when I ran more than 3 and I couldn't watch multiple agents in parallel (had to constantly switch between them). So I built a lightweight Tauri desktop app which lets you run multiple Claude Code agents in one window alongside each other. It's easier to read the output and see which agents need your attention than a terminal. Have been using this all day everyday instead of an IDE and have obsessed over every detail to make sure it's easy-to-use, but also lightweight and fast (so you can manage multiple agents without your PC crashing). There are some nice features like better usage alerts for when you're going to hit your 5-hour and weekly limits (with sparklines to show when usage peaked, and which agents are the most token-intensive). It's free to use (you just need to log in with your existing Claude Code account) for up to 4 agents simultaneously. This app doesn't store your Claude Code account details and doesn't store any of your interactions with Claude Code. They remain between you and Anthropic. It's compatible with Windows, MacOS and 64-bit Linux. Would really appreciate any feedback, so if you have any thoughts, issues or suggestions please let me know. Thanks, Chris
15 by cwbuilds | 4 comments on Hacker News.
Hi guys, I've been using Claude Code for almost everything lately. Have given one an email account so it can research business leads, draft emails, fact-check them and clear them with me before sending (works really well by the way). I also tend to have a few Claude Code agents running at any one time for coding. I used to create a split terminal to manage them from there, but found working in the terminal all day pretty depressing and, more importantly, found it hard to follow Claude Code's process and see which agents needed my immediate attention. I tried Anthropic's VS Code Claude Code extension and it had a great UI (more info on Claude Code's process and easier to read), but it crashed my PC when I ran more than 3 and I couldn't watch multiple agents in parallel (had to constantly switch between them). So I built a lightweight Tauri desktop app which lets you run multiple Claude Code agents in one window alongside each other. It's easier to read the output and see which agents need your attention than a terminal. Have been using this all day everyday instead of an IDE and have obsessed over every detail to make sure it's easy-to-use, but also lightweight and fast (so you can manage multiple agents without your PC crashing). There are some nice features like better usage alerts for when you're going to hit your 5-hour and weekly limits (with sparklines to show when usage peaked, and which agents are the most token-intensive). It's free to use (you just need to log in with your existing Claude Code account) for up to 4 agents simultaneously. This app doesn't store your Claude Code account details and doesn't store any of your interactions with Claude Code. They remain between you and Anthropic. It's compatible with Windows, MacOS and 64-bit Linux. Would really appreciate any feedback, so if you have any thoughts, issues or suggestions please let me know. Thanks, Chris
Wednesday, July 8, 2026
Tuesday, July 7, 2026
New top story on Hacker News: Show HN: Halo – open-source, tamper-evident runtime evidence for AI agents
Show HN: Halo – open-source, tamper-evident runtime evidence for AI agents
3 by brian_kuan | 0 comments on Hacker News.
Hi HN, I'm Brian, I spent the last few years at Vanta (YC W18), helping startups and enterprises become compliant and I recently started exploring what that might look like in a post-agentic world. The problem Halo solves is: when a company buys an AI agent from a vendor and gives it access to their data, they have no way to check what the agent did with that data. Vendors may have built observability dashboards and audit logs, but those are editable and partisan. SOC 2 and ISO 27001 audit a company's controls, but controls are less predictive when the software is agentic. TLDR: give an agent the same prompt 50 times, and you get 50 slightly different actions/answers - so the only thing worth auditing in a post-agentic world is what happened at runtime. Halo is an open-source project that produces agent runtime evidence. It's a small recorder that records every action an agent takes (eg. tool calls, model calls, data access, etc), and becomes a record in an append-only log. It's hash-chained, so anyone can re-verify. Run the following command to see a fictional example: uvx --from halo-record halo demo --serve Then, delete a line from one of the .jsonl files and reload, and the report will catch that it's been tampered with. To wire up your own agent, run this line of Python: agent = trace(run_my_agent, profile="my-agent", log="audit.jsonl") Then use this to generate a real report and give it to your customers: halo report audit.jsonl -o report.html Disclaimer: this proves integrity, not completeness (as a self-held chain proves nothing was edited but does NOT prove that nothing was omitted). Catching this requires a witness outside the vendor and is what I'm working on next. Halo is Apache-2.0, contains zero runtime dependencies, and is about 4,300 lines of Python with 125 tests (if you prefer TypeScript, here's that repo: https://ift.tt/ga7Af5w ). Give it a try, and please let me know if you have any feedback!
3 by brian_kuan | 0 comments on Hacker News.
Hi HN, I'm Brian, I spent the last few years at Vanta (YC W18), helping startups and enterprises become compliant and I recently started exploring what that might look like in a post-agentic world. The problem Halo solves is: when a company buys an AI agent from a vendor and gives it access to their data, they have no way to check what the agent did with that data. Vendors may have built observability dashboards and audit logs, but those are editable and partisan. SOC 2 and ISO 27001 audit a company's controls, but controls are less predictive when the software is agentic. TLDR: give an agent the same prompt 50 times, and you get 50 slightly different actions/answers - so the only thing worth auditing in a post-agentic world is what happened at runtime. Halo is an open-source project that produces agent runtime evidence. It's a small recorder that records every action an agent takes (eg. tool calls, model calls, data access, etc), and becomes a record in an append-only log. It's hash-chained, so anyone can re-verify. Run the following command to see a fictional example: uvx --from halo-record halo demo --serve Then, delete a line from one of the .jsonl files and reload, and the report will catch that it's been tampered with. To wire up your own agent, run this line of Python: agent = trace(run_my_agent, profile="my-agent", log="audit.jsonl") Then use this to generate a real report and give it to your customers: halo report audit.jsonl -o report.html Disclaimer: this proves integrity, not completeness (as a self-held chain proves nothing was edited but does NOT prove that nothing was omitted). Catching this requires a witness outside the vendor and is what I'm working on next. Halo is Apache-2.0, contains zero runtime dependencies, and is about 4,300 lines of Python with 125 tests (if you prefer TypeScript, here's that repo: https://ift.tt/ga7Af5w ). Give it a try, and please let me know if you have any feedback!