Show HN: Code review for AI native teams https://ift.tt/9AgruFn

Show HN: Code review for AI native teams Bottleneck is a desktop app for code reviewing AI-written pull requests. The goal is to be able to track PRs on GitHub authored by agents (i.e. Codex, Devin, Cursor, Claude Code) and compare branches. So if you throw multiple coding agents at a ticket, this would be an easier way to let agents "bake off" against each other and pick the best one. (No need to open the Github website and switch between slow loading tabs). I'd love feedback from any power users who are deep with AI coding agents. https://ift.tt/EPN8ohT October 18, 2025 at 05:52AM

Show HN: I turned my resume into a catchy song. It's a game changer https://ift.tt/OTg1ndr

Show HN: I turned my resume into a catchy song. It's a game changer I turned my resume into a catchy pop song. Thought you'd all appreciate it. Worked directly on the Song Style prompt, which you can duplicate for your own fun catchy resume song. Just replace the lyrics! https://ift.tt/3v8AhPO October 18, 2025 at 02:22AM

Show HN: We packaged an MCP server inside Chromium https://ift.tt/YUKN7mw

Show HN: We packaged an MCP server inside Chromium Hey HN, we just shipped a browser with an inbuilt MCP server! We're a YC startup (S24) building BrowserOS — an open‑source Chromium fork. We're a privacy‑first alternative to the new wave of AI browsers like Dia, Perplexity Comet. Since launching ~3 months ago, the #1 request has been to expose our browser as an MCP server. -- Google beat us to launch with chrome-devtools-mcp (solid product btw), which lets you build/debug web apps by connecting Chrome to coding assistants. But we wanted to take this a step further: we packaged the MCP server directly into our browser binary. That gives three advantages: 1. MCP server setup is super simple — no npx install, no starting Chrome with CDP flags, you just download the BrowserOS binary. 2. with our browser's inbuilt MCP server, AI agents can interact using your logged‑in sessions (unlike chrome-devtools-mcp which starts a fresh headless instance each time) 3. our MCP server also exposes new APIs from Chromium's C++ core to click, type, and draw bounding boxes on a webpage. Our APIs are also not CDP-based (Chrome Debug Protocol) and have robust anti-bot detection. -- Few example use cases for BrowserOS-mcp are: a) *Frontend development with Claude Code*: instead of screenshot‑pasting, claude-code gets WYSIWYG access. It can write code, take a screenshot, check console logs, and fix issues in one agentic sweep. Since it has your sessions, it can do QA stuff like "test the auth flow with my Google Sign‑In." Here's a video of claude-code using browserOS to improve the css styling with back-and-forth checking: https://youtu.be/vcSxzIIkg_0 b) *Use as an agentic browser:* You can install BrowserOS-mcp in claude-code or Claude Desktop and do things like form-filling, extraction, multi-step agentic tasks, etc. It honestly works better than Perplexity Comet! Here's a video of claude-code opening top 5 hacker news posts and summarizing: https://youtu.be/rPFx_Btajj0 -- *How we packaged MCP server inside Chromium binary*: We package the server as a Bun binary and expose MCP tools over HTTP instead of stdio (to support multiple sessions). And we have a BrowserOS controller installed as an extension at the application layer which the MCP server connects to over WebSocket to control the browser. Here's a rough architecture diagram: https://dub.sh/browseros-mcp-diag -- *How to install and use it:* We put together a short guide here: https://ift.tt/UNyr2Fh Our vision is to reimagine the browser as an operating system for AI agents, and packaging an MCP server directly into it is a big unlock for that! I'll be hanging around all day, would love to get your feedback and answer any questions! https://ift.tt/l3tgZs6 October 17, 2025 at 09:52PM

Show HN: Stop Chasing Success: Write for Wonder Instead https://ift.tt/7UqtVHT

Show HN: Stop Chasing Success: Write for Wonder Instead Why novels are an ideal project for bringing wonder into your life https://ift.tt/HcqXEz6 October 17, 2025 at 11:16PM

Show HN: Arky – Visual 2D Markdown editor (access codes below) https://ift.tt/zgp2dY1

Show HN: Arky – Visual 2D Markdown editor (access codes below) Hey HN! Arky is a markdown editor with a twist — instead of linear documents, you work on a 2D canvas where you can: • Place ideas anywhere spatially • Organize into hierarchy with drag & drop • See the full document structure at a glance • AI writes contextually — drag & drop responses anywhere on canvas More info: https://arky.so/ Try it: https://app.arky.so/ (Access codes are in the comment below!) Quick demo(60s): https://youtu.be/Nxsr5Ag2vEM?si=g6nKheRWWNuaLTe8 Would love to hear your thoughts! https://app.arky.so October 17, 2025 at 01:20AM

Show HN: We priced basic needs in work hours (global ranking and CSVs) https://ift.tt/RgvEGQA

Show HN: We priced basic needs in work hours (global ranking and CSVs) https://ift.tt/BEqpGPy October 17, 2025 at 01:23AM

Show HN: Inkeep (YC W23) – Agent builder that works both visually and in code https://ift.tt/zR7gM9P

Show HN: Inkeep (YC W23) – Agent builder that works both visually and in code Hi HN! I'm Nick from Inkeep. We built an agent builder with true 2-way sync between code and a drag-and-drop visual editor, so devs and non-devs can collaborate on the same agents. Here’s a demo video: https://ift.tt/KAOCZwm . As a developer, the flow is: 1) Build AI Chat Assistants or AI Workflows with the TypeScript SDK 2) Run `inkeep push` from your CLI to publish 3)Edit agents in the visual builder (or hand off to non-technical teams) 4) Run `inkeep pull to edit in code again. We built this because we wanted the accessibility of no-code workflow builders (n8n, Zapier), but the flexibility and devex of code-based agent frameworks (LangGraph, Mastra). We also wanted first-class support for chat assistants with interactive UIs, not just workflows. OpenAI got close, but you can only do a one-time export from visual builder to code and there’s vendor lock-in. How I've used it: I bootstrapped a few agents for our marketing and sales teams, then was able to hand off so they can maintain and create their own agents. This has enabled us to adopt agents across technical and non-technical roles in our company on a single platform. To try it, here’s the quickstart: https://ift.tt/BXHx3AV . We leaned on open protocols to make it easy to use agents anywhere: An MCP endpoint, so agents can be used from Cursor/Claude/ChatGPT A Chat UI library with interactive elements you can customize in React An API endpoint compatible with the Vercel AI SDK `useChat` hook Support for Agent2Agent (A2A) so they work with other agent ecosystems We made some practical templates like a customer_support, deep_research, and docs_assistant. Deployment is easy with Vercel/Docker with a fair-code license and there's a traces UI and OTEL logs for observability. Under the hood, we went all-in on a multi-agent architecture. Agents are made up of LLMs, MCPs, and agent-to-agent relationships. We’ve found this approach to be easier to maintain and more flexible than traditional “if/else” approaches for complex workflows. The interoperability works because the SDK and visual builder share a common underlying representation, and the Inkeep CLI bridges it with a mix of LLMs and TypeScript syntactic sugar. Details in our docs: https://docs.inkeep.com . We’re open to ideas and contributions! And would love to hear about your experience building agents - what works, hasn’t worked, what’s promising? https://ift.tt/3g8OwPf October 16, 2025 at 06:20PM