Best of Claude CodeApril 2026

  1. 1
    Article
    Avatar of lobstersLobsters·8w

    I used AI. It worked. I hated it.

    A developer with strong anti-genAI views shares their experience using Claude Code to build a certificate generation tool for a learning platform migration. The project succeeded — the Rust/Svelte app is in production — but the process felt miserable. Key observations: TDD with plan-mode kept the model on track, Rust's compile-time safety helped catch hallucinations, a security audit pass found real vulnerabilities (path traversal, timing side-channel in Argon2), and the tool delivered features the author wouldn't have built alone. Despite the functional success, the author warns about the 'human in the loop' problem — the process actively encourages disengagement — and reflects on cognitive dependency, skill atrophy for junior developers, IP theft concerns, and the broader societal harms. The conclusion is nuanced: it works in this narrow domain, the harms still outweigh benefits at scale, but condemning individuals for using it is counterproductive.

  2. 2
    Article
    Avatar of hnHacker News·8w

    The Claude Code Leak

    The accidental leak of Claude Code's source code reveals that the code itself is reportedly low quality, yet the product is beloved. This prompts reflection on five key observations: code quality doesn't determine product success; what matters is what code does, not how it's written; product-market fit trumps implementation details; the copyright situation is ironic given Anthropic's own AI training arguments; and ultimately the leak won't matter because Claude Code's value lies in the seamless integration of model and harness, not the underlying source code. Open-source alternatives like Codex and Gemini CLI haven't captured Claude Code's mindshare, reinforcing that a complete, well-integrated service is what users pay for.

  3. 3
    Article
    Avatar of collectionsCollections·6w

    Claude Code now supports automated routines triggered by schedule, API, or GitHub events

    Anthropic has launched Routines in Claude Code, a cloud-based automation feature currently in research preview for Pro, Max, Team, and Enterprise subscribers. Routines let you configure a task once — with a prompt, repo, and connectors — and have it run automatically on Anthropic's infrastructure without a local machine. Three trigger types are supported: scheduled (hourly/daily/weekly), API (HTTP POST with bearer token), and GitHub events (PRs, pushes, releases, issues). Multiple triggers can be combined on a single routine. Routines run fully autonomously with access to MCP servers, GitHub repos, and environment variables. Daily run limits vary by plan (5 for Pro, 15–25 for Max, 25 for Team/Enterprise) and run against subscription billing rather than API billing. Key caveats include LLM inference latency (2–15s per step), no pre-built OAuth connectors, and the need for careful prompt scoping since routines run unattended. Anthropic positions this as a developer-native alternative to tools like Make.com and n8n, with plain prompts and Git integration instead of a visual node editor.

  4. 4
    Video
    Avatar of bytemonkByteMonk·7w

    Claude's Internal Architecture Revealed | How AI Agents Actually Work

    Anthropic accidentally shipped TypeScript source maps with Claude Code's CLI distribution, exposing the full internal source code. Engineers reverse-engineered the architecture and rebuilt it in Python, then Rust, within 24 hours. The core architecture consists of an agent loop, a tool registry with 20+ tools, a hooks middleware system for safety and observability, a memory compaction mechanism for long sessions, context loading via CLAUDE.md and skills files, and sub-agent spawning for parallel task delegation. Each component maps to familiar distributed systems patterns: the loop is a task queue worker, tools are a service interface, hooks are middleware, memory compaction is log rotation, and sub-agents are worker nodes.

  5. 5
    Article
    Avatar of ubqa4zl8noglmlpvdnr79Prince Kumar·8w

    Claude code become open source?

    Claude Code's internal source was accidentally leaked via a source map file, exposing ~500K lines of TypeScript. Following DMCA takedowns of mirrors, the community responded by creating Claw Code — a clean-room reimplementation of Claude Code's architecture written in Python and Rust. The project recreates the agent tools, query engine, and orchestration without copying proprietary code, making it a legitimate open-source alternative. It quickly became one of the fastest-growing repos on GitHub.

  6. 6
    Article
    Avatar of phProduct Hunt·8w

    Baton: Orchestrate your AI coding agents

    Baton is a desktop app for orchestrating multiple AI coding agents in parallel. Each agent runs in its own git-isolated workspace, with smart notification badges to flag which agents need attention. It supports Claude Code, Codex, OpenCode, and any terminal-based agent. Features include diff review, file browsing, codebase search, and a built-in MCP server that lets agents spawn new agents. Built by a developer who needed a single unified interface to manage multiple agents without constant window-switching.

  7. 7
    Article
    Avatar of freecodecampfreeCodeCamp·8w

    AI Tools for Developers –

    A freeCodeCamp course covering AI tools for developers, including GitHub Copilot, Anthropic's Claude Code, and Gemini CLI for AI pair programming and agentic terminal workflows. Also covers OpenClaw for locally hosted open-source AI automation and CodeRabbit for AI-driven pull request analysis. The course is 1.5 hours and available on YouTube.

  8. 8
    Article
    Avatar of kilo-ai-blogKilo Blog·6w

    Anthropic Doesn’t Want Your Subscription Anymore

    Anthropic has updated Claude Code's usage policies to bar businesses from using subscription plans, pushing enterprises to API-based pricing. The author argues this was inevitable since flat-fee inference was always an unsustainable subsidy — one developer tracked $15,000 in API-equivalent usage on an $800 subscription. The shift will likely cause a period of shadow IT as developers use personal accounts for work, before companies migrate to usage-based API pricing. Once on API pricing, the logic of staying locked to a single model provider weakens, accelerating a move toward model-agnostic, multi-provider inference strategies. The post concludes with a pitch for Kilo, a model-agnostic AI platform built for this new reality.

  9. 9
    Article
    Avatar of codropsCodrops·7w

    Building the Maxima Therapy Website: React, GSAP, and Dabbling with AI

    A behind-the-scenes case study of building the Maxima Therapy website, a highly interactive and illustrated site for a neurodivergent support organization. The stack includes React Router, Sanity CMS, Cloudflare Pages, GSAP with ScrollTrigger, Lenis smooth scroll, Lottie animations, Matter.js physics, and Tailwind CSS. Key technical highlights include a draggable SVG carousel with Lottie animations, canvas-based composite layering for scroll-reactive backgrounds, physics-based rope interactions using Matter.js, SVG morphing with GSAP's MorphSVG plugin, and a mouse-driven water ripple effect generated with Claude Code. The post also reflects honestly on AI-assisted development: Claude Code accelerated tedious tasks like SVG optimization, TypeScript typing, and CMS block generation, but occasionally produced inconsistent results and created a sense of losing control over the codebase when used for larger features.

  10. 10
    Video
    Avatar of webdevcodyWeb Dev Cody·5w

    Can Opus 4.7 Refactor NextJs to Tanstack Start?

    An experiment using Claude Code's max effort level to refactor a production Next.js app (with tRPC) to TanStack Start. The author walks through the full process: setting up the prompt, running a 28-minute planning session that consumed ~33% of a 5-hour session budget, iteratively fixing errors (config issues, React SSR incompatibilities, auth migration from NextAuth to Auth.js v5, S3 bucket port mismatches), and ultimately getting the app running locally with 103 file changes. Key takeaways include keeping refactoring scope narrow, running security audits on auth/middleware changes post-refactor, and setting up a staging environment before merging to production.

  11. 11
    Article
    Avatar of claudeClaude·6w

    Redesigning Claude Code on desktop for parallel agents

    Anthropic has redesigned the Claude Code desktop app to support parallel agentic workflows. Key additions include a new sidebar for managing multiple concurrent sessions across repos, drag-and-drop workspace layout, an integrated terminal and file editor, a faster diff viewer, expanded preview support for HTML and PDFs, and SSH support extended to Mac. Three view modes (Verbose, Normal, Summary) let users control how much detail they see. The app now streams responses in real time and has parity with CLI plugins. Available to Pro, Max, Team, and Enterprise plan users and via the Claude API.

  12. 12
    Article
    Avatar of minersThe Miners·7w

    Stop Putting Best Practices in Skills

    A data-driven investigation into why best practices should live in CLAUDE.md rather than Claude Code skills. The author ran 51 multi-turn evals across 4 configurations (Superpowers, plain skills, CLAUDE.md, CLAUDE.md+hint) and found that plain skills are only invoked 6% of the time in multi-turn sessions, while CLAUDE.md guidelines are always in context. The key insight: skills and CLAUDE.md are both just prompts — the difference is reliability of delivery. Superpowers works not because of skills but because its SessionStart hook front-loads instructions, achieving 66% invocation. The recommendation is clear: put coding standards, TDD rules, and debugging protocols in CLAUDE.md (100% presence, no activation gap), and reserve skills for on-demand procedural recipes like scaffolding or migrations.

  13. 13
    Article
    Avatar of v7balm8y0o32yjz1hhf5aFabian Letsch·4w

    Many Coding Agents. One Codebase. How?

    Managing coding agent instructions across multiple tools (Claude Code, Cursor, Copilot, Codex, Gemini, Pi) in a shared codebase is surprisingly unsolved. AGENTS.md is the closest thing to a standard, but Claude Code doesn't support it natively — requiring a workaround using its @-import syntax. Per-user local instruction files also lack a unified standard, forcing developers to maintain separate files in different locations for each tool. The post calls out the fragmentation and lack of community discussion around this problem, ending with an open question about how others are handling it.

  14. 14
    Article
    Avatar of metalbearMetalBear·6w

    What Happens After AI Writes the Code

    AI coding agents introduce 'assumption bugs' — errors based on unverified premises about the real environment (queue message formats, env var names, DB schema) that only surface when code runs against actual dependencies. The typical workflow means these bugs are caught hours later in CI. A 'remocal development' approach, using a tool like mirrord, lets the locally running service connect to a real remote Kubernetes staging cluster in real time, so AI agents can observe failures immediately after generating code, fix them, and push with confidence. mirrord handles shared staging safety via HTTP traffic filtering, database branching, and queue splitting.

  15. 15
    Article
    Avatar of developwithandroidAndroid Developers·8w

    Essential Claude Code Skills for Mobile Developers

    A curated list of Claude Code skills tailored for mobile developers working with iOS, Android, and Kotlin Multiplatform. Claude Code skills are packaged folders of instructions and scripts that teach the AI agent specialized tasks via a SKILL.md file. The post covers installation (global vs. project-level), then walks through recommended skills including Swift Development, iOS Mobile Design, iOS App Builder, SwiftUI agent skill, Android Development, Android Kotlin Development, Mobile Android Design, Jetpack Compose Expert, and a KMP Abstraction Guide — each linked to its repository or marketplace page with a brief description of what it teaches Claude to do.

  16. 16
    Video
    Avatar of designcourseDesignCourse·6w

    The 2 Biggest Ways my UI/UX Workflow has Changed

    A UI/UX designer shares how their workflow has shifted with AI tools. Instead of starting in Figma from scratch, they now use Claude Code for initial vibe-design prototyping, then use Figma MCP to generate multiple design variations quickly. The designer picks the best option, refines colors and layout manually in Figma, then feeds the result back to Claude Code to implement in live code. The workflow produced a working floating modal panel with filtering and search in minutes, without writing any code directly. The author positions AI as a junior designer that handles iteration while the human designer handles refinement and creative judgment.

  17. 17
    Article
    Avatar of mtlynchMichael Lynch·8w

    Claude Code Found a Linux Vulnerability Hidden for 23 Years

    Nicholas Carlini, a research scientist at Anthropic, used Claude Code to discover multiple remotely exploitable heap buffer overflows in the Linux kernel, including one that had gone undetected for 23 years. The vulnerability exists in the NFS driver: when a lock request is denied, the server writes a response of up to 1056 bytes into a 112-byte buffer, allowing an attacker to overwrite kernel memory. The discovery required minimal human oversight — a simple shell script looped Claude Code over every source file in the kernel asking it to find vulnerabilities. Carlini has found hundreds more potential bugs but lacks the time to validate and report them all. The rapid improvement of LLMs at vulnerability discovery signals a coming wave of security bug disclosures.

  18. 18
    Video
    Avatar of t3dotggTheo - t3․gg·8w

    I got DMCA'd by Anthropic (not a joke)

    A developer recounts receiving a DMCA takedown notice from Anthropic on GitHub, affecting their fork of the official Claude Code repository — a fork containing only a one-word change. The DMCA was part of a mass takedown targeting 8,100 repositories, which turned out to be a miscommunication between Anthropic and GitHub. Anthropic quickly retracted the notice for all repos except those mirroring the actual leaked source code. The author ultimately partially defends Anthropic, crediting their transparent crisis communications, while strongly criticizing their decision to keep Claude Code closed source as the root cause of the entire situation.

  19. 19
    Article
    Avatar of agents_digestAgentic Digest·5w

    Kimi K2.6 lands as a real open-source coding agent, GitHub Copilot closes signups

    Kimi K2.6, a 1T-parameter MoE open-source model from Moonshot AI, launched with strong benchmark scores (80.2% SWE-Bench Verified) and ships in Fireworks, OpenCode, and HuggingChat. GitHub Copilot paused new signups for Pro, Pro+, and Student plans as agentic workflows blew past flat-rate cost assumptions, with Opus models being tiered up. Anthropic silently cut Claude Code's prompt cache TTL from 1 hour to 5 minutes in April, causing significant cost spikes for developers in sustained agentic sessions. Claude Desktop was found to silently install a browser bridge granting broad access without user consent. Other notable items include Cursor 3's shift to parallel agent orchestration, a $5B Amazon-Anthropic deal expansion, an MCP STDIO RCE disclosure affecting ~200K servers, and OpenAI losing three senior executives in one day.

  20. 20
    Video
    Avatar of youtubeYouTube·7w

    Andrej Karpathy Just 10x’d Everyone’s Claude Code

    Andrej Karpathy shared a method for building personal LLM-powered knowledge bases using Claude Code and markdown files. The approach involves feeding raw documents (PDFs, articles, transcripts) to Claude Code, which automatically organizes them into a structured wiki with relationships, indexes, and backlinks — stored as plain markdown files viewable in Obsidian. This eliminates the need for vector databases or embedding pipelines for small-to-medium scale knowledge bases (up to hundreds of documents). The tutorial walks through setting up a vault, ingesting content via the Obsidian Web Clipper extension, and querying the resulting wiki. It also compares this approach to traditional semantic search RAG, noting the wiki approach is simpler and cheaper at small scale but doesn't scale to millions of documents.