Cloudflare

Cloudflare AI

Cloudflare AI

Cloudflare AI

Cloudflare AI

Cloudflare AI

Cloudflare AI

Cloudflare AI

Cloudflare AI

Cloudflare AI

Cloudflare AI

Anthropic just bought the company that generates most production MCP servers

Anthropic acquired Stainless on Monday for a reported $300M+. Most coverage is framing this as a developer tools acquisition. Stainless is best known for generating the official Python and Node SDKs that ship with OpenAI, Google, Meta, Cloudflare, and Anthropic. The SDK story is real. The MCP side is the part that matters here. Stainless was one of the first vendors to extend their compiler to produce MCP servers from the same OpenAPI specs that produce their SDKs. MCP hit ~97M monthly SDK downloads by December 2025 and around 10,000 production servers by early 2026. A lot of that production code was Stainless-generated. Anthropic now owns the dominant MCP server generator. What actually changed hands on Monday: The engineering team. Roughly 40-50 people including founder Alex Rattray, who previously built Stripe's patented SDK generation system. Now reporting to Katelyn Lesse in Anthropic's Platform Engineering org. The technology. The generator, the templates, the language-specific runtimes, the OpenAPI extensions Stainless invented for SDK-specific edge cases. The hosted product is winding down. New signups stopped Monday. New SDK and MCP server generations stopped Monday. Existing customers keep what they've already generated but the pipeline is closed. My read: this is closer to what Google did with Kubernetes than to a normal acquisition. Anthropic created MCP. Anthropic donated MCP to the Linux Foundation last December. Anthropic now owns the dominant implementation toolchain. The protocol is vendor-neutral on paper. The implementation toolchain isn't. Six months of Anthropic M&A starts looking less coincidental: December 2025: Bun, the JS runtime, pulled into Claude Code February 2026: Vercept, computer-use AI April 2026: Coefficient Bio, ~$400M healthcare AI May 2026: Stainless, SDK and MCP plumbing They're not buying training infrastructure or GPU clusters. They're buying the integration layers around the model. The bet seems to be that frontier models are converging faster than anyone expected, so the moat is everywhere except the model. If you're building on MCP today, tooling quality probably improves. Stainless's generator was already the cleanest in the space and the team that built it is now at Anthropic. Patterns will standardize faster as Stainless-derived templates become the de facto reference. The flip side is concentration risk. Cloudflare's MCP server framework, Pulse MCP, and the open-source generators Stainless released during the transition all become strategically important if you want any diversity in your stack. Sources: Anthropic announcement Why Anthropic actually did this, and migration math Curious whether Stainless ending up inside Anthropic reads as good news (better tooling) or concentration risk (one company owns the standard and the reference implementation) from your seat. submitted by /u/Ok-Constant6488 [link] [comments]

Self-hosted sandboxes and MCP tunnels for Claude Managed Agents are now in public beta.

Self-hosted sandboxes lets you run agents in any environment you control: your own infrastructure, or managed providers like Cloudflare, Daytona, Modal, or Vercel. MCP tunnels connect your agents to MCP servers deployed in your private network without exposing them to the public internet. Available today on the Claude Platform. Read more: https://claude.com/blog/claude-managed-agents-updates submitted by /u/ClaudeOfficial [link] [comments]

Cloudflare just published what they found after running Anthropic's Mythos Preview against 50+ of their own repos and the results are worth reading

If you missed the Project Glasswing announcement last month: Anthropic built a security-focused model that autonomously found thousands of high-severity vulnerabilities across every major OS and web browser, then decided it was too dangerous to release publicly. Instead they gave access to ~40 organizations to use it defensively . Cloudflare just posted their honest breakdown of the experience. The genuinely impressive part: the model can take several exploit primitives and reason about how to chain them into a working proof. The reasoning looks like the work of a senior researcher, not an automated scanner The catch: its built-in guardrails aren't consistent. The same task framed differently could produce completely different outcomes. Cloudflare's point is that this inconsistency is exactly why any future public release needs hardened safeguards layered on top. They also acknowledge the same capabilities that helped them find bugs in their own code will, in the wrong hands, accelerate attacks against every application on the internet. Worth a read if you've been following the Glasswing story. submitted by /u/Direct-Attention8597 [link] [comments]

Project Glasswing: what Mythos showed us (Cloudflare)

submitted by /u/error1212 [link] [comments]

built a CLI for ChatGPT so I could script it from the terminal

wanted to ask ChatGPT questions and generate images from shell scripts without using a third-party API key. so I built a CLI that wraps the same endpoints chatgpt.com uses, with browser-based OpenAI SSO for auth (Camoufox for the Cloudflare check). what it does: chat ask "question" and pipe the answer wherever chat image "prompt" to generate, plus a download command list past conversations and models every command has a --json flag so it slots into agent pipelines. it's part of a bigger open-source project that auto-generates CLIs from any website's HTTP traffic, MIT licensed: https://github.com/ItamarZand88/CLI-Anything-WEB/tree/main/chatgpt I built it, not affiliated with OpenAI. uses the same endpoints the web app uses, so things can break when ChatGPT pushes changes. submitted by /u/zanditamar [link] [comments]

built a Claude Code plugin that turns any website into a Python CLI (19 generated so far)

most web apps don't have public APIs. so I built a plugin that watches you use a site in a browser, captures all the HTTP traffic, figures out the protocol, and writes a full Python CLI from it. auth, tests, --json everywhere. it also writes a SKILL.md for each generated CLI, so Claude can call them on its own without extra prompting. ask "find me a hotel in Paris under 200", it runs the booking CLI by itself. the harder parts: bypassing Cloudflare and AWS WAF, decoding Google's batchexecute RPC, handling auth cookie refresh without user interaction. 19 sample CLIs in the repo so people can see how each protocol is handled (Reddit, NotebookLM, Booking, Airbnb, ChatGPT, Stitch, Capitol Trades, LinkedIn, and others). open source, MIT, no affiliation with any of those sites. repo: https://github.com/ItamarZand88/CLI-Anything-WEB would love feedback, especially on which sites you'd want it pointed at next. submitted by /u/zanditamar [link] [comments]

Why claude code doesn’t have SSH?

submitted by /u/Alternative-Way-3685 [link] [comments]

How to fix “VM service not running. The service failed to start” in Claude Desktop for Windows

How to fix “VM service not running. The service failed to start” in Claude Desktop for Windows If Claude Desktop on Windows is showing this error: VM service not running. The service failed to start. especially when trying to use Cowork, Claude Code, or local agent features, one possible fix is to delete Claude’s local VM packages. On macOS, many people suggest deleting the vm_bundles folder. On Windows, however, this folder may not be in the obvious location. Instead of searching manually, do this: 1. Fully close Claude Do not just close the window. Open Task Manager with: Ctrl + Shift + Esc End processes such as: Claude Claude Desktop Claude Code node.exe Only end node.exe if it appears to be related to Claude. 2. Disable VPNs or tunnels Before trying again, temporarily disable tools such as: VPN Cloudflare WARP Tailscale ZeroTier ProtonVPN NordVPN Surfshark These tools may interfere with Claude’s local VM service. 3. Find the vm_bundles folder Open PowerShell and run: Get-ChildItem -Path "$env:USERPROFILE" -Recurse -Directory -Filter "vm_bundles" -ErrorAction SilentlyContinue If the folder exists, Windows will show a path ending with: ...\Claude\vm_bundles 4. Delete the folder Copy the path that appeared and run: Remove-Item -Recurse -Force "PASTE_THE_FULL_vm_bundles_PATH_HERE" Generic example: Remove-Item -Recurse -Force "C:\Users\YOUR_USER\AppData\...\Claude\vm_bundles" 5. Restart Windows After deleting the folder, restart your computer. Then open Claude Desktop again and test Cowork / Claude Code. If it still does not work You can also clear the Claude Code VM folder, if it exists. In PowerShell, search for it with: Get-ChildItem -Path "$env:USERPROFILE" -Recurse -Directory -Filter "claude-code-vm" -ErrorAction SilentlyContinue If a claude-code-vm folder appears, delete it with: Remove-Item -Recurse -Force "PASTE_THE_FULL_claude-code-vm_PATH_HERE" Then restart Windows again. Summary To fix: VM service not running. The service failed to start. in Claude Desktop for Windows: Fully close Claude. Disable VPNs or tunnels. Search for the vm_bundles folder. Delete the folder. Restart Windows. Open Claude again. The key point: on Windows, the vm_bundles folder may be inside an internal application package folder, not necessarily in %APPDATA%\Claude. That is why the safest method is to search for it with PowerShell and delete the exact path found. VERSÃO EM PORTUGUÊS Como corrigir o erro “VM service not running. The service failed to start” no Claude Desktop para Windows Se o Claude Desktop no Windows estiver mostrando o erro: VM service not running. The service failed to start. especialmente ao tentar usar o Cowork, Claude Code ou recursos de agente local, uma possível solução é apagar os pacotes locais da VM do Claude. No Mac, muita gente recomenda apagar a pasta vm_bundles. No Windows, essa pasta pode não estar no lugar óbvio. Em vez de procurar manualmente, faça assim: 1. Feche totalmente o Claude Não basta fechar a janela. Abra o Gerenciador de Tarefas com: Ctrl + Shift + Esc Finalize processos como: Claude Claude Desktop Claude Code node.exe Finalize node.exe apenas se parecer relacionado ao Claude. 2. Desative VPNs ou túneis Antes de tentar novamente, desligue temporariamente: VPN Cloudflare WARP Tailscale ZeroTier ProtonVPN NordVPN Surfshark Essas ferramentas podem interferir no serviço local da VM. 3. Encontre a pasta vm_bundles Abra o PowerShell e rode: Get-ChildItem -Path "$env: USERPROFILE " -Recurse -Directory -Filter "vm_bundles" -ErrorAction SilentlyContinue Se a pasta existir, o Windows vai mostrar um caminho terminando em: ...\Claude\vm_bundles 4. Apague a pasta encontrada Copie o caminho que apareceu e rode: Remove-Item -Recurse -Force "COLE_AQUI_O_CAMINHO_DA_PASTA_vm_bundles" Exemplo genérico: Remove-Item -Recurse -Force "C:\Users\SEU_USUARIO\AppData\...\Claude\vm_bundles" 5. Reinicie o Windows Depois de apagar a pasta, reinicie o computador. Abra novamente o Claude Desktop e teste o Cowork/Claude Code. Se não resolver Você pode limpar também a pasta da VM do Claude Code, se ela existir. No PowerShell, procure por: Get-ChildItem -Path "$env:USERPROFILE" -Recurse -Directory -Filter "claude-code-vm" -ErrorAction SilentlyContinue Se aparecer uma pasta claude-code-vm, apague com: Remove-Item -Recurse -Force "COLE_AQUI_O_CAMINHO_DA_PASTA_claude-code-vm" Depois reinicie o Windows novamente. Resumo Para corrigir: VM service not running. The service failed to start. no Claude Desktop para Windows: Feche totalmente o Claude. Desative VPNs/túneis. Procure a pasta vm_bundles. Apague a pasta. Reinicie o Windows. Abra o Claude novamente. O ponto principal: no Windows, a pasta vm_bundles pode ficar em um caminho interno do pacote do aplicativo, não necessariamente em %APPDATA%\Claude. Por isso, o jeito mais seguro é procurar pelo PowerShell e apagar exatamente o caminho encontrad

If you are treating a one-shot generated file as your deliverable, you got it wrong.

I've been seeing a lot of posts and comments about people debating where to host files: GitHub Pages, Netlify, Vercel, SharePoint, Cloudflare etc.. Why is a static file the deliverable in the first place? you are stripping prompt history, iteration path, the ability to re-run on new data and to ingest feedback without starting over. You are essentially sending a postcard of a session. The right unit of work is the session it self. The prompts, the context, the skills that produced the dashboard, the path of the revision. That is what the recipient actually needs to engage with, because that is what gets rerun when they ask for the next version. The artifact is just one moment of an output. What does your deliverables looks like? Internally/ externally? Are you trying to relay context or still with single files or folders? submitted by /u/Ok-Dragonfly-6224 [link] [comments]

I spent much of this year in the hospital with my mom. I built this so I could keep iterating on my more automated workflows while my dev machine was at home.

Wanted to share my mobile claude/codex session tool: Chroxy. TL;DR Chroxy is a (yet another!) self-hosted remote client for Claude Code. You run a small daemon on your dev machine, scan a QR code with the app. Then you have access to your terminal sessions and a clean chat view that renders Claude's output as readable messages. Everything goes over a Cloudflare tunnel so there's no port forwarding or VPN setup. Originally, I'd be sitting in a hospital room for hours and come back to my laptop just to find Claude sitting at "Ready to start?" the whole window wasted. I needed a way to stay in the loop, approve a permission prompt, or kick off the next task without physically moving to my machine. The Anthropic billing changes in June are going to steal some of the benefits away from the app... I'm aware that makes it less accessible for some people, and I thought about that before deciding to release it anyway. Honestly, it's been useful enough to me that I'm willing to make that trade. If you're already on API billing it won't change anything for you. Why not /remote-control? When Anthropic launched the rc feature, I stopped development and spent some time with it. It was underwhelming to me (Maybe user error). So, I came back and kept refining this. The stack Server: Node.js 22, ES modules, runs Claude via the Agent SDK (in-process) or the legacy CLI. WebSocket protocol with Zod-validated message types. Mobile app: React Native + Expo, TypeScript, xterm.js terminal emulation in a WebView, Zustand for state, native speech-to-text Desktop: Tauri tray app wrapping the web dashboard Security: E2E encrypted — X25519 key exchange, XSalsa20-Poly1305. The tunnel sees ciphertext only. Other bits: pluggable provider system (Claude, Gemini, Codex all work with the same app), Docker container isolation for sessions, permission rule engine, git worktree support I built it because I needed it, it let me play with tools I find genuinely interesting, and it feels like a waste to keep it private. If you're into LLM tooling or just want a self-hosted way to run Claude Code remotely, maybe it's useful to you too. My mom passed away in March. I'm sharing this partly because building it kept me sane during the months in the hospital thinking she'd be fine, and I think it might be useful to other people. Repo is blamechris/chroxy. There are many like my project, but this one is mine. :') submitted by /u/xcVosx [link] [comments]

temporal-mcp: wall-clock awareness for LLMs, with OAuth

One of the small failure modes I keep hitting with agent stacks is that the model has no idea how much time passed between turns. It'll greet you with "good morning" at 11 PM, or pick up a conversation three weeks later as if no time has passed, or compute "today's data" off whatever fragment of context happens to be in scope. Built a minimal MCP server to fix it. Two tools: temporal_tick and temporal_peek. They return elapsed-time-since-last-turn, day-rollover detection, and a fresh-thread flag, both as a human-readable header and as JSON. Ways to use: Local stdio: pip install temporal-mcp (works with Claude Desktop, Cursor, Cline, Zed, Claude Code) Hosted with OAuth (claude.ai / ChatGPT): visit https://temporal-mcp.dev/connect, click "Generate OAuth Credentials", paste into your custom connector. Full OAuth 2.0 with PKCE and refresh tokens, but no signup, the credential pair is the identity. (Verified working in claude.ai) Hosted with raw bearer (any client that supports custom headers): Authorization: Bearer against https://temporal-mcp.dev/mcp. The token gets SHA-256'd; we never see the plaintext. Self-host: Cloudflare Workers deploy in workers/ in the repo, free tier covers ~100k req/day. Grok/xAI: https:temporal-mcp.dev/mcp/ (Verified working in Grok) MIT, ~150 lines of stdlib Python on the local side, ~400 lines of TypeScript on the hosted side (engine + OAuth provider), both with tests. Listed in the official MCP Registry. Smithery and Glama submissions in flight. Curious to hear how folks would use the JSON day_rollover and delta_sec signals I've been using them for context decay and resume detection but there are probably more interesting use cases. Source: github.com/MirrorEthic/temporal-mcp submitted by /u/MirrorEthic_Anchor [link] [comments]

PullMD v2.4.1 is out - claude.ai web custom connector works natively now, plus what 2 weeks of your feedback turned into

Two weeks ago I posted PullMD here. 385 upvotes, around 60 comments, a bit over 20 GitHub issues, and 7 releases (v1.1.3 → v2.4.0) in 14 days. That was a great experience - and this sub in particular has been a genuinely good place to share something. So: thanks! Quick refresher for anyone who missed the first post: PullMD turns any URL into clean Markdown via MCP, fully self-hosted. Three services in Docker (main app + Trafilatura sidecar + optional Playwright sidecar for JS-heavy pages), zero third-party LLM calls, ships an MCP server so Claude Code / Claude Desktop / claude.ai web can pull clean content directly instead of parsing HTML in your context window. This post is what's new and how to get it. What's new claude.ai web + Claude Desktop work natively now This is the biggest unlock from v2.x. The claude.ai web custom-connector dialog and Claude Desktop's custom-connector dialog now both work against self-hosted PullMD instances. So you can point claude.ai at your own homelab box, hit "Add custom connector," and it works end-to-end. Setup is two env vars: OAUTH_JWT_SECRET=$(openssl rand -hex 32) PUBLIC_URL=https://your-host.example.com Restart. Then in claude.ai web → Settings → Connectors → Add custom, point at https://your-host.example.com/mcp. The connector dialog discovers the server's metadata, registers itself, and walks you through a consent screen. Same flow works in Claude Desktop. Under the hood: standard OAuth 2.1 Authorization Code flow with PKCE-S256 and Dynamic Client Registration - RFC-compliant so any spec-compliant MCP client should work, not just claude.ai/Desktop. Opt-in: if OAUTH_JWT_SECRET isn't set, behavior is identical to v1.x. The Anthropic-side claude-ai-mcp#237 proxy bug I flagged in EDIT2 of post 1 has cleared on their end - though in hindsight, a forgotten custom WAF rule on my side was likely the actual culprit anyway. Verified end-to-end against both dialogs. Multi-user auth Until v2.0, PullMD was effectively single-tenant - a personal homelab tool, open like a barn door to anyone who landed on it. v2.0 adds three auth modes via PULLMD_AUTH_MODE: disabled - the default. Identical to v1.x. No login, no API key required. Right if you're the only one using your instance and you trust your network. single-admin - one user, password-protected, no self-signup. Right for a homelab box where you want the GUI gated but don't want to manage users. multi-user - self-signup at /signup, per-user history isolation, per-user API keys. Right for a shared instance (team, office, friend group). API keys are pmd_ , sent as Authorization: Bearer pmd_xxx, managed at /settings. Share links (/s/:id) stay public in all modes - the whole point of a share link is to be shareable. Minimal upgrade for a shared instance: PULLMD_AUTH_MODE=multi-user PULLMD_ADMIN_EMAIL=you@example.com PULLMD_ADMIN_PASSWORD=change-me-please PullMD works on more sites A bunch of things in v1.2 and v2.2 together close gaps where PullMD used to silently return half-articles, empty bodies, or garbled text: Future PLC family (windowscentral.com, tomshardware.com, techradar.com, pcgamer.com, gamesradar.com, t3.com) used to return mangled content because Readability got confused by recommendation widgets stuffed mid-article and an aria-hidden paywall pattern. The default site-recipes shipped with v2.2 strip both, no config needed. GitHub Issues pages used to return only the original issue body - the JS-rendered comment thread never made it in. The default recipe for */*/issues/* now forces Playwright with wait_for: .js-comment-body, so you get the full comment tree. Sites that fingerprinted the old hardcoded Chrome 131 UA now extract cleanly - UA rotation pulls from a real-world UA pool that updates regularly (v1.2). Pages with navigator.webdriver-style anti-bot detection go through more often - the headless-Chromium sidecar bundles playwright-stealth (v2.2). Sites without an explicit charset declaration (a lot of older German news sites, for example) no longer return mojibake - charset is detected from the byte stream when the response is silent (v1.2). If you have a specific site that still misbehaves, v2.2 lets you (or your Claude Code) write your own recipe - declarative JSON with four rule categories (preprocess, fetch, select, extractor). Drop it at data/site-recipes.json and your rules layer on top of the defaults. There's also a /api/recipes/status endpoint for monitoring. Web GUI: rendered Markdown view + persistent settings Two smaller improvements in the browser frontend (the PWA you get when you open your PullMD instance directly): Rendered Markdown toggle. The result header now has a Raw | Rendered switch, so you can read what you pulled as formatted HTML directly in the browser instead of squinting at the source. Raw stays the default; your choice persists across sessions (v2.4). Settings persist across reloads - frontmatter toggle, comments toggle, comment-depth input.

I used Claude to build a live election dashboard in 2 days. It handled 430K requests from 24K visitors without spending money

Tamil Nadu had state elections on May 4. I wanted to see if I could build a better results site than what exists (everything out there is ad-ridden, slow, and unusable on mobile). Started building on May 2 with Claude as my coding partner. The constraint: spend nothing. Zero hosting, zero domain, zero database. The solution ended up being stupidly simple. A Python script on my laptop scrapes all 234 constituency pages from the Election Commission (they don't have an API, just raw HTML pages),stitches the data together, and pushes it to Cloudflare's free key-value store. Their CDN serves it to everyone globally. The browser just refreshes every 30 seconds. On election day it got way more traffic than I expected. 24K visitors, 430K requests, 8.7 GB bandwidth, 24 countries. My scraper used997 writes that day. The free tier limit is 1,000. Three writes to spare. The craziest part was shipping features live. People kept asking for things during counting, "can you show close races?", "what percentage is counted?", and I'd have it deployed in 5 minutes.60+ commits that day. Claude wrote the code, I made the calls on what to build and whether it was safe to push. Wrote up the whole story in a blog if anyone's interested. Links in comments. submitted by /u/Naive-Performance-18 [link] [comments]

I built a catalog of MCP servers with paste-ready install configs. One of them is hosted so you can try it without setting anything up

Every time I added a new MCP server to Claude Desktop I ended up doing the exact same thing. Hunt down the github, dig through the README to find the install line, then build the JSON config by hand. Doing it once is fine, doing it five times in a week got old. Built agentalmanac.org. 23 servers indexed so far, each one has a detail page with paste-ready config snippets for Claude Desktop, Cursor, and Continue. Pick your runtime, copy the JSON, done. One thing I wasn't expecting to find: a bunch of the "official" reference servers in modelcontextprotocol/servers are actually archived now (GitHub, Slack, Postgres, SQLite, Puppeteer, Sentry, Brave Search, Google Drive). Most catalog sites I checked still list them as if they're current. I routed every archived one to whatever is still being actively maintained. Microsoft's Playwright instead of Puppeteer, Zencoder for Slack, Brave's own first party server for search, etc. Felt weird that nobody else was doing this. While I was at it I hosted one of them too. agentalmanac.org/s/agentalmanac-time runs on a Cloudflare Worker and exposes get_current_time and convert_time. Drop the snippet into your claude_desktop_config.json and it works. Mostly a proof of concept to see if hosting MCP servers on Workers was even possible. Turns out yes. For anyone curious about the stack: the catalog is plain HTML/JS on Cloudflare Pages with a single servers.json that the detail pages fetch and render client-side. No framework, no database, no build step. The hosted MCP demo is a small Worker using Cloudflare's agents/mcp SDK with a Durable Object for session state. The hosted demo was maybe four hours of work end to end. If you use a server that I'm missing, drop a comment and I'll add it. Also curious whether anyone would actually want to deploy their own server through something like this instead of running it on Railway or Fly. The hosted version is not a real product yet, just feeling out if there's appetite. No signup, no login. JSON feed at /servers.json if anyone wants to build something on top. submitted by /u/madman3063 [link] [comments]

I built a self-hosted memory layer for Claude that runs free on Cloudflare — open source

https://preview.redd.it/touwnxi2z80h1.png?width=1774&format=png&auto=webp&s=b4bf6c2e1f096f692562a2b8b27e72dc2f9cb1c0 Claude forgetting everything between sessions was driving me crazy, so I built a fix. It's a Cloudflare Worker that acts as an MCP server — four tools: remember, recall, list_recent, forget. Claude calls them automatically based on instructions in your system prompt. You set it up once and stop thinking about it. The part I'm most happy with is how recall works. Every note gets vector-embedded using Workers AI (bge-small-en-v1.5) and stored in Cloudflare Vectorize. So when Claude searches your memory, it's matching by meaning, not keywords. Store "users drop off at checkout" and recall it later with "onboarding problems" — it finds it. What I used Claude for building this: Wrote most of the MCP server implementation in TypeScript Helped me work through the Vectorize + D1 architecture Generated the iOS Shortcuts templates and bookmarklet Wrote the README (Claude writing docs for a Claude memory tool felt appropriate) Stack: Cloudflare Workers + D1 (SQLite) + Vectorize + Workers AI. The whole thing runs on Cloudflare's free tier for personal use. One-click deploy button in the repo. Works with Claude Desktop, Claude Code, and claude.ai (via custom connectors). Repo: https://github.com/rahilp/second-brain-cloudflare Happy to answer questions about the implementation — the semantic search piece especially has some interesting tradeoffs worth discussing. submitted by /u/rahilpirani5 [link] [comments]