IdeaRank – Startup Analysis Engine
2 by TMDev | 0 comments on Hacker News.
IdeaRank helps founders decide which startup idea is actually worth building. You paste an idea into a single, centralized hub and get a brutally honest, AI-generated scorecard with market insights, competitor analysis, risks, and suggestions—backed by real-world data and transparent reasoning. You can save multiple ideas, compare their scores, and quickly see which one deserves your time. Check it out here: https://idearank.netlify.app/
Hack Nux
Watch the number of websites being hacked today, one by one on a page, increasing in real time.
New Show Hacker News story: Show HN:Conduit–Headless browser with SHA-256 hash chain - Ed25519 audit trails
Show HN:Conduit–Headless browser with SHA-256 hash chain - Ed25519 audit trails
2 by TaxFix | 0 comments on Hacker News.
I've been building AI agent tooling and kept running into the same problem: agents browse the web, take actions, fill out forms, scrape data -- and there's zero proof of what actually happened. Screenshots can be faked. Logs can be edited. If something goes wrong, you're left pointing fingers at a black box. So I built Conduit. It's a headless browser (Playwright under the hood) that records every action into a SHA-256 hash chain and signs the result with Ed25519. Each action gets hashed with the previous hash, forming a tamper-evident chain. At the end of a session, you get a "proof bundle" -- a JSON file containing the full action log, the hash chain, the signature, and the public key. Anyone can independently verify the bundle without trusting the party that produced it. The main use cases I'm targeting: - *AI agent auditing* -- You hand an agent a browser. Later you need to prove what it did. Conduit gives you cryptographic receipts. - *Compliance automation* -- SOC 2, GDPR data subject access workflows, anything where you need evidence that a process ran correctly. - *Web scraping provenance* -- Prove that the data you collected actually came from where you say it did, at the time you say it did. - *Litigation support* -- Capture web content with a verifiable chain of custody. It also ships as an MCP (Model Context Protocol) server, so Claude, GPT, and other LLM-based agents can use the browser natively through tool calls. The agent gets browse, click, fill, screenshot, and the proof bundle builds itself in the background. Free, MIT-licensed, pure Python. No accounts, no API keys, no telemetry. GitHub: https://ift.tt/zmZY6na Install: `pip install conduit-browser` Would love feedback on the proof bundle format and the MCP integration. Happy to answer questions about the cryptographic design.
2 by TaxFix | 0 comments on Hacker News.
I've been building AI agent tooling and kept running into the same problem: agents browse the web, take actions, fill out forms, scrape data -- and there's zero proof of what actually happened. Screenshots can be faked. Logs can be edited. If something goes wrong, you're left pointing fingers at a black box. So I built Conduit. It's a headless browser (Playwright under the hood) that records every action into a SHA-256 hash chain and signs the result with Ed25519. Each action gets hashed with the previous hash, forming a tamper-evident chain. At the end of a session, you get a "proof bundle" -- a JSON file containing the full action log, the hash chain, the signature, and the public key. Anyone can independently verify the bundle without trusting the party that produced it. The main use cases I'm targeting: - *AI agent auditing* -- You hand an agent a browser. Later you need to prove what it did. Conduit gives you cryptographic receipts. - *Compliance automation* -- SOC 2, GDPR data subject access workflows, anything where you need evidence that a process ran correctly. - *Web scraping provenance* -- Prove that the data you collected actually came from where you say it did, at the time you say it did. - *Litigation support* -- Capture web content with a verifiable chain of custody. It also ships as an MCP (Model Context Protocol) server, so Claude, GPT, and other LLM-based agents can use the browser natively through tool calls. The agent gets browse, click, fill, screenshot, and the proof bundle builds itself in the background. Free, MIT-licensed, pure Python. No accounts, no API keys, no telemetry. GitHub: https://ift.tt/zmZY6na Install: `pip install conduit-browser` Would love feedback on the proof bundle format and the MCP integration. Happy to answer questions about the cryptographic design.
New Show Hacker News story: Show HN: Modulus – Cross-repository knowledge orchestration for coding agents
Show HN: Modulus – Cross-repository knowledge orchestration for coding agents
1 by dasubhajit | 0 comments on Hacker News.
Hello HN, we're Jeet and Husain from Modulus ( https://modulus.so ) - a desktop app that lets you run multiple coding agents with shared project memory. We built it to solve two problems we kept running into: - Cross-repo context is broken. When working across multiple repositories, agents don't understand dependencies between them. Even if we open two repos in separate Cursor windows, we still have to manually explain the backend API schema while making changes in the frontend repo. - Agents lose context. Switching between coding agents often means losing context and repeating the same instructions again. Modulus shares memory across agents and repositories so they can understand your entire system. It's an alternative to tools like Conductor for orchestrating AI coding agents to build product, but we focused specifically on multi-repo workflows (e.g., backend repo + client repo + shared library repo + AI agents repo). We built our own Memory and Context Engine from the ground up specifically for coding agents. Why build another agent orchestration tool? It came from our own problem. While working on our last startup, Husain and I were working across two different repositories. Working across repos meant manually pasting API schemas between Cursor windows — telling the frontend agent what the backend API looked like again and again. So we built a small context engine to share knowledge across repos and hooked it up to Cursor via MCP. This later became Modulus. Soon, Modulus will allow teams to share knowledge with others to improve their workflows with AI coding agents - enabling team collaboration in the era of AI coding. Our API will allow developers to switch between coding agents or IDEs without losing any context. If you wanna see a quick demo before trying out, here is our launch post - https://ift.tt/B86Jp7Z We'd greatly appreciate any feedback you have and hope you get the chance to try out Modulus.
1 by dasubhajit | 0 comments on Hacker News.
Hello HN, we're Jeet and Husain from Modulus ( https://modulus.so ) - a desktop app that lets you run multiple coding agents with shared project memory. We built it to solve two problems we kept running into: - Cross-repo context is broken. When working across multiple repositories, agents don't understand dependencies between them. Even if we open two repos in separate Cursor windows, we still have to manually explain the backend API schema while making changes in the frontend repo. - Agents lose context. Switching between coding agents often means losing context and repeating the same instructions again. Modulus shares memory across agents and repositories so they can understand your entire system. It's an alternative to tools like Conductor for orchestrating AI coding agents to build product, but we focused specifically on multi-repo workflows (e.g., backend repo + client repo + shared library repo + AI agents repo). We built our own Memory and Context Engine from the ground up specifically for coding agents. Why build another agent orchestration tool? It came from our own problem. While working on our last startup, Husain and I were working across two different repositories. Working across repos meant manually pasting API schemas between Cursor windows — telling the frontend agent what the backend API looked like again and again. So we built a small context engine to share knowledge across repos and hooked it up to Cursor via MCP. This later became Modulus. Soon, Modulus will allow teams to share knowledge with others to improve their workflows with AI coding agents - enabling team collaboration in the era of AI coding. Our API will allow developers to switch between coding agents or IDEs without losing any context. If you wanna see a quick demo before trying out, here is our launch post - https://ift.tt/B86Jp7Z We'd greatly appreciate any feedback you have and hope you get the chance to try out Modulus.
New Show Hacker News story: Show HN: What's my JND? – a colour guessing game
Show HN: What's my JND? – a colour guessing game
15 by Keithamus | 16 comments on Hacker News.
https://ift.tt/pjK4d0k
15 by Keithamus | 16 comments on Hacker News.
https://ift.tt/pjK4d0k
New ask Hacker News story: AI is to software as power tools are to woodworking
AI is to software as power tools are to woodworking
4 by danfunk | 2 comments on Hacker News.
Power tools did not remove people. They make woodworking accessible to more people. They make more complex projects possible. They make furniture less expensive. We don't have less jobs because of power tools. And with power tools came a proliferation of hardware stores to support all the people suddenly empowered to try their hand. To take the analogy further, agents are like factories. Yes the drill can do the work on it's own, when it's on an assembly line, getting exactly the right part at the right time at the right angle. But it is insanely hard and expensive to set up a factory, and when it is done, it produces one thing. Shit will change. But that is exactly what I liked about this industry to begin with. And people are highly motivated by fear, so the manipulators and influencers peddle it for all they are worth. There is nothing to fear here. It's just a new kind of tool for you to pick up, if you have the courage and heart to do so.
4 by danfunk | 2 comments on Hacker News.
Power tools did not remove people. They make woodworking accessible to more people. They make more complex projects possible. They make furniture less expensive. We don't have less jobs because of power tools. And with power tools came a proliferation of hardware stores to support all the people suddenly empowered to try their hand. To take the analogy further, agents are like factories. Yes the drill can do the work on it's own, when it's on an assembly line, getting exactly the right part at the right time at the right angle. But it is insanely hard and expensive to set up a factory, and when it is done, it produces one thing. Shit will change. But that is exactly what I liked about this industry to begin with. And people are highly motivated by fear, so the manipulators and influencers peddle it for all they are worth. There is nothing to fear here. It's just a new kind of tool for you to pick up, if you have the courage and heart to do so.
New ask Hacker News story: Ask HN: What game engine would you recommend for vibe coding?
Ask HN: What game engine would you recommend for vibe coding?
5 by general_reveal | 2 comments on Hacker News.
I feel like things like Unity and Unreal have a lot of UI-centric workflows that wouldn’t be great for vibing.
5 by general_reveal | 2 comments on Hacker News.
I feel like things like Unity and Unreal have a lot of UI-centric workflows that wouldn’t be great for vibing.