nicola_alessi

↗ HN profile [ 56.7 ms ] full profile
Karma
0
Created
()
Submissions
0
  1. Shipped today. The benchmarks are real: 87.6% SWE-bench (from 80.8%), +13% on coding tasks, 3x more resolved production tasks on Rakuten-SWE-Bench. But there are a few changes that compound on each other for token…

  2. I ran a controlled benchmark on AI coding agents (42 runs, FastAPI, Claude Sonnet 4.6) and found something that broke my mental model of LLM costs. The setup: I built an MCP server that pre-indexes a codebase into a…

  3. I built an MCP server (vexp) that pre-indexes a codebase into a dependency graph and serves only relevant code to AI coding agents. While benchmarking it, I found something I wasn't looking for. The expected results…

  4. I got tired of watching Claude Code read entire files when it needed one function. Built an MCP server that pre-computes a dependency graph with tree-sitter and serves only the relevant code nodes to the agent. Ran a…

  5. I've spent months building tooling for AI coding agents and hit something I can't fully explain. If you give an agent (Claude Code, Cursor, Codex) a tool to save observations — "save_observation: persist this insight…

  6. I built vexp because AI coding agents have two expensive problems: they waste tokens reading irrelevant code, and they forget everything between sessions. The token problem: agents read entire files linearly to build…

  7. I built vexp to solve two problems I kept hitting with AI coding agents (Claude Code, Cursor, etc.): 1. Token waste: agents read entire files linearly to understand a codebase. On a medium TypeScript project, a single…

  8. I've been building vexp for the past months to solve a problem that kept bugging me: AI coding agents waste most of their context window reading code they don't need. The problem When you ask Claude Code or Cursor to…

  9. For the last year, I've been obsessed with a problem: finding something to watch is a chore. The interfaces of Netflix, Prime, and others feel like slot machines designed for maximum engagement, not for matching my…

  10. The Problem: LLMs are terrible at understanding eCommerce sites. They: Hallucinate prices/specs from messy HTML Waste tokens on UI boilerplate (headers, popups, ads) Struggle with real-time inventory/pricing updates Our…

  11. We've forked Answer.AI's llms.txt to solve a specific problem: how eCommerce sites with 10K+ products can expose clean product data to LLMs without inefficient scraping. What it does: site-llms.xml is a machine-readable…

  12. Every solution I've seen either: 1. Replicates Google's ad-driven model (but worse) 2. Claims 'AI' but acts as a black box Yet we all waste hours daily on: - Decoding fake reviews - Reverse-engineering SEO-optimized…