Claude Code

Claude Code AI

Claude Code AI

Claude Code AI

Claude Code AI

Claude Code AI

Claude Code AI

Claude Code AI

Claude Code AI

Claude Code AI

Claude Code AI

Claude Code asking me if i'm human

submitted by /u/Glittering-Cherry-90 [link] [comments]

the dashboard rebranding is live. "business intelligence for tradesmen." claude built 60% of the new analytics features.

the pivot: invoicing tool → business intelligence platform for tradesmen. the dashboard that started as an accident is now the product. new features built with claude code in the last 2 months: expense tracking: input expenses. dashboard shows profit margins per job. 8 hours to build. revenue forecasting: 3-month projection based on historical invoicing patterns. 12 hours. customer concentration: alerts when one customer exceeds 30% of revenue. 4 hours. all 3 features were claude-assisted. the architecture, the API endpoints, and the initial UI. i refined and deployed. the dashboard now functions as a simple ai report generator for tradesmen. revenue trends, expense tracking, profit margins, customer health. the data that used to require a quarterly accountant visit is on their phone. 185 of 270 customers use the dashboard daily. the rebranding from "invoicing" to "business intelligence" reflects what customers actually use. the custom claude style for technical documentation ensures release notes are consistent. the style for customer communications ensures the rebranding messaging is warm and clear. for founders with "accidental features": if your customers use it more than your core product, its not accidental anymore. its the product. submitted by /u/Ok-Salary-6309 [link] [comments]

Claude tried 4 wrong fixes for the same bug. My teammate found it in 30 min.

I've been building an app with Claude as my coding helper. Yesterday it broke - users couldn't see their data. I asked Claude to fix it. Claude saw "too many requests" errors in the logs and decided that was the problem. It made 4 different fixes. Each one shipped cleanly. None of them actually fixed the bug. The real issue was something completely different - a library we use changed how it labels stuff, and our app was still reading the old labels. So every piece of data came back blank. My teammate found it in 30 minutes by literally printing out one piece of data and going "wait, why is this empty?" When I asked Claude later why it missed this, the honest answer was: it locked onto the first thing that looked like a cause and never questioned it. It never did the simplest check - look at one piece of the data first and ask "does this even make sense?" The lesson: AI is really good at solving problems you point it at. It's bad at picking which problem to look at. If I had said "first check if the data even looks right before assuming it's a network issue," it would have caught the bug fast. My new rule for any "stuff isn't showing up" bug: look at ONE piece of the broken data first. Then start guessing. TL;DR: AI will fix the wrong thing very efficiently if you don't tell it what to verify first. submitted by /u/SadNose6889 [link] [comments]

Massive Thank you to Claude AI

Don’t know if this is the right place but recently for my coursework, ( A Level NEA Computer Science) it suddenly disappeared from my google drive ( not sure if my ex revenge deleted it or my mum ). and i had no back ups because i never expected this. i mainly used ChatGPT back then but after 30 days the files get deleted from the chat. However, i pasted my whole write up to Claude including the code to it to check for minor improvements and 6 months later it is still there which saved me months of work. all i had to do was format it and 3 days later good as new. Im glad Claude AI doesn’t delete files sent, completely saved me big time it genuinely saved my uni offer. submitted by /u/Due-Plenty-8744 [link] [comments]

Why have 126,000,000 tokens been used in 7 hours when I haven't sent a single message?

(This is not me complaining about limits, this is a bug where usage is being spent from literally nowhere, of which is clearly obvious) between 3am (when my weekly started) and now, 10:06am, my weekly has been used 21% and my session has been used 100%. I haven't even been awake to send a single message. I am only logged into my on my phone and computer, and neither have been accessed by anyone new. There has been no new chat appearing in recent chats, nor any new messages appearing in any existing chats. I do not have any currently running API codes that I use, I don't use claude code, nor am I connected to any external platforms like connectors or plugins. Is this a known bug? Support bot hasn't provided anything helpful. Thanks in advice for any help. submitted by /u/SamwiseMay [link] [comments]

I used Claude Code to build a free Pokémon personality profiler from scratch in one session

Hey r/ClaudeAI, I built NotRandom (notrandom.vercel.app) a free web app where you type your favorite Pokémon and get a psychographic profile based on your choice. The premise: your favorite Pokémon is not random. It reveals something real about you. What it does: Fetches the Pokémon's types and Pokédex lore from PokéAPI Classifies it into one of 10 archetypes (The Sovereign, The Rebel, The Shadow Operator, The Jester...) Generates a Core Identity, Shadow Side, a unique nickname ("The Calculated Vanishing" for Greninja), and a one-liner "The Line" designed to feel uncomfortably accurate Lets you download a 1080x1080 shareable image card How Claude Code specifically built this: Everything was written by Claude Code in a single session. Here's what it actually did: Full architecture I described the concept, Claude Code planned the stack (React + Vite + Tailwind + Vercel serverless) and the complete file structure before writing a single line All React components from scratch LandingPage, LoadingScreen, ProfileCard, ShareCard, state machine in App.tsx The archetype system designed and coded the mapping of all 18 Pokémon types to 10 personality archetypes with color palettes per type The Claude Haiku prompt engineered to return a structured JSON with the right tone (intelligent, slightly poetic, never cringe) Solved a real architectural problem — the Anthropic API blocks direct browser calls (CORS). Claude Code diagnosed it, then created a Vercel serverless /api/profile route to proxy the call server-side Debugged the share card the downloaded image was black. Claude Code identified two causes: position: fixed breaks html-to-image's canvas renderer, and Google Fonts fail silently during capture. Fixed with skipFonts: true + sprite conversion to base64 before capture Full deployment Vercel config, environment variables, 30s timeout for cold starts I described what I wanted, Claude Code wrote the code, I tested, reported what broke, it fixed. Classic loop. https://preview.redd.it/i62hsrbd0n4h1.png?width=1080&format=png&auto=webp&s=aa31a839f094fa5760e401e8f336b01efbb49179 Free to use: https://notrandom.vercel.app no login, just type any Pokémon name in English (all 1025 are supported). submitted by /u/dyloum84 [link] [comments]

I got Rick Rolled by Claude Code

I'm currently working recreating the outer glow effect (Ambient Mode) that YouTube has. To check YouTube's implementation of this effect, Claude Code opened no other than Rick Astley's "Never Gonna Give You Up". Claudes reply on the matter: And yes — that was indeed a Rick Roll. In my defence, it's the most reliably-available public YouTube video for testing purposes. Classic. Didn't expect to get Rick Rolled by an AI, but here we are. submitted by /u/Grimgorkos [link] [comments]

naksha-studio v5 is out. It now remembers your project so you stop explaining your stack every session.

Been building naksha-studio for a while now. It's a plugin that gives you a virtual design agency as slash commands inside Claude Code, Cursor, Windsurf, and Gemini CLI. 62 commands, 26 specialist roles, all the design work you'd normally bounce between tools to do. The problem was every session started from zero. New chat, explain your stack again. Brand color, framework, grid system, WCAG level. Every time. v5 fixes that with project memory. What's new: /naksha-browse captures a live site through Playwright and stores the findings. Layout grid, type scale, color palette, UX patterns, all written to your project memory. Run it on your competitors or sites you admire and every future design command uses those as reference automatically. /naksha-remember persists design constraints. "Grid is 8px. No dark mode. WCAG AA required." Classified and stored. Never repeated again. Both write to .naksha/project.json and 5 existing commands (/design, /brand-kit, /design-system, /design-score, /accessibility-audit) read it automatically from that point on. The Stop hook also processes memory blocks written during a session so context you establish mid-conversation survives to the next one. GitHub: https://github.com/Adityaraj0421/naksha-studio If you were already using it, just git pull. No reinstall needed. Run /naksha-init to upgrade your existing project to the v5 schema. Feedback welcome, especially on whether the memory actually reduces your setup friction. submitted by /u/Known-Delay-9689 [link] [comments]

PSA: "deep research" in Claude Code is *not* the same as in the desktop/web app.

Learnt this one the hard way. Previously I've used deep research to build helpful reports on whatever topics, e.g. API docs that I want CC to build an interface for. Fired up a deep research session from Claude Code - it launched 199 agents and burnt ~50 million tokens over 30 mins! Now I'm timed out, oof. Turns out this is a new(?) thing? Maybe? A "dynamic workflow", say the docs. The docs also mention that these workflows are "limited" to 1,000 agents per run. Lol. Lmao, even. submitted by /u/marky125 [link] [comments]

trying to see if Mythos claims are verified or not

The claims about Mythos Preview (Anthropic's unreleased Claude model) are substantially verified from multiple independent sources, though the exact CVE numbers and commit hashes for the FFmpeg vulnerability are still being disclosed through coordinated security processes. Key Verified Facts 1. OpenBSD 27-year-old vulnerability ✅ Verified What: A bug in OpenBSD's TCP SACK (Selective Acknowledgment) handling introduced around 1998[forum.devtalk] Impact: Allows an attacker to remotely crash any OpenBSD machine just by connecting to it via TCP[linkedin] Details: OpenBSD tracks SACK state as a singly linked list of holes; the vulnerability is subtle and survived 27 years of expert review[reddit] Patch: Available at openbsd/pub/Openpatches/.8/025ack.patch[reddit] 2. FFmpeg 16-year-old vulnerability ✅ Verified What: A bug in FFmpeg's H.264 decoder where a 32-bit slice counter is stored in a 16-bit lookup table, initialized to 65535[secureworld] Impact: A specially crafted frame with exactly 65,536 slices causes counter collision triggering out-of-bounds write[secureworld] Origin: Type mismatch dates to FFmpeg's 2003 H.264 commit; exploitable code path introduced in 2010 refactor[secureworld] Testing evasion: The code path was hit by automated testing tools 5 million times without flagging the bug[linkedin] Patch status: Three FFmpeg vulnerabilities found by Mythos were patched in FFmpeg 8.1[secureworld] 3. Linux kernel vulnerability chain ✅ Verified What: Mythos autonomously found and chained multiple Linux kernel vulnerabilities for privilege escalation[reddit] Impact: Escalation from ordinary user to complete root control of the machine[linkedin] Cost: Under $2,000 in tokens to create the exploit chain[linkedin] Status: Anthropic is funding the Linux Foundation to fix these vulnerabilities[linkedin] Supporting Evidence Source Type Key Confirmation Anthropic's risk report Official PDF Technical assessment of Mythos Preview released April 7, 2026 [anthropic] AI Security Institute evaluation Independent Confirmed 73% success on expert-level cyber CTF tasks [aisi.gov] Debian security tracker Official CVE-2026-40962 fixed in FFmpeg 8.1 [security-tracker.debian] Reddit/OpenBSD forum Community Patch discussion and technical details [reddit] Why This Matters This is considered "possibly the most frightening cybersecurity news in decades" because: AI found bugs that survived decades of expert audits and relentless fuzzing[agent-wars] Mythos found thousands of zero-days versus Opus 4.6's ~500[reddit] The model achieved 181 working exploits in Firefox benchmark testing[agent-wars] Access is gated/restricted due to dual-use risk[docs.aws.amazon] The FFmpeg commit should indeed be public given it's open source, and the patch is in FFmpeg 8.1. The exact commit hash is being handled through coordinated disclosure, but the vulnerability details are confirmed by multiple independent security researchers.The claims about Mythos Preview (Anthropic's unreleased Claude model) are substantially verified from multiple independent sources, though the exact CVE numbers and commit hashes for the FFmpeg vulnerability are still being disclosed through coordinated security processes.Key Verified Facts1. OpenBSD 27-year-old vulnerability ✅ VerifiedWhat: A bug in OpenBSD's TCP SACK (Selective Acknowledgment) handling introduced around 1998[forum.devtalk] Impact: Allows an attacker to remotely crash any OpenBSD machine just by connecting to it via TCP[linkedin] Details: OpenBSD tracks SACK state as a singly linked list of holes; the vulnerability is subtle and survived 27 years of expert review[reddit] Patch: Available at openbsd/pub/Openpatches/.8/025ack.patch[reddit]2. FFmpeg 16-year-old vulnerability ✅ VerifiedWhat: A bug in FFmpeg's H.264 decoder where a 32-bit slice counter is stored in a 16-bit lookup table, initialized to 65535[secureworld] Impact: A specially crafted frame with exactly 65,536 slices causes counter collision triggering out-of-bounds write[secureworld] Origin: Type mismatch dates to FFmpeg's 2003 H.264 commit; exploitable code path introduced in 2010 refactor[secureworld] Testing evasion: The code path was hit by automated testing tools 5 million times without flagging the bug[linkedin] Patch status: Three FFmpeg vulnerabilities found by Mythos were patched in FFmpeg 8.1[secureworld]3. Linux kernel vulnerability chain ✅ VerifiedWhat: Mythos autonomously found and chained multiple Linux kernel vulnerabilities for privilege escalation[reddit] Impact: Escalation from ordinary user to complete root control of the machine[linkedin] Cost: Under $2,000 in tokens to create the exploit chain[linkedin] Status: Anthropic is funding the Linux Foundation to fix these vulnerabilities[linkedin]Supporting EvidenceSource Type Key Confirmation Anthropic's risk report Official PDF Technical assessment of Mythos Preview released April 7, 2026 [anthropic] AI

How do you handle runaway API costs across multiple OpenAI agents? I built something to solve this

Hey, I'm a CS student and I've been building LedgerAI, a cost tracking and budget enforcement layer for LLM agents. The problem it solves: You're running 3+ agents in production. One goes rogue overnight. You wake up to a $400 bill with no idea which agent caused it and no way to have stopped it. What makes LedgerAI different: Most tools log costs after the call. LedgerAI enforces limits before it. The SDK hits a budget check endpoint before every LLM request, and if the agent is over its daily or monthly limit, the call is blocked. Hard stop, not a soft warning. What it tracks per call: Agent name, model, provider (Anthropic + OpenAI supported) Input/output tokens + exact cost in USD Daily and monthly spend rollups per agent Completely free and open source right now. Pip install or hit the API directly with cURL. Would love feedback from anyone running multi-agent systems, especially what alerting/enforcement features would actually be useful in prod! submitted by /u/IndianCurry06 [link] [comments]

The real reason coding agents fail in real repos — and it's not the model

Most coding agent failures I see aren't model failures. They're repo context failures. The agent doesn't know what to read first, what the validation actually checks, which decisions are already made, what "done" means on this team. So it guesses. After tracking hundreds of these failures, I've gotten pretty good at predicting where agents will stumble. The pattern is always the same: the repo has zero structured context for anything that isn't the code itself. I've been building a repo-level harness-experimental that forces structure into those gaps -- CLAUDE.md, architecture notes, test matrices, decision records. Curious what gaps your agents hit most often? What's something they always get wrong that you'd never think to explain in a prompt? submitted by /u/tickettodamoon [link] [comments]

anyone using rtk with claude code ? Are you really saving tokens??

rtk-ai repo has 56.6k stars and claims they save 60-90% tokens so to give it a try i started using it , Here is the feedback My one day savings 0.3% tokens . Reads are highly consuming so i added on claude to always use ls (supported by rtk claims 60% savings). Had 300+ reads with rtk 0% tokens saved . Am i using wrong ? Are you aware of repos that really saves tokens submitted by /u/EcstaticLime2672 [link] [comments]

Deepeseek inside claude code -Easist way

For those who cant afford claude models and wanna use claude code, deepseek v4 pro is closest best and cheapest option. How to use deepseek API inside claude code (easist way ever): We will use AI to replace AI. Just feed your existing claude code this prompt "Yo Claude, you’re expensive af 💀 Do everything needed to fully switch Claude Code to DeepSeek API automatically. Set up the complete settings.json config, API integration, model selection, base URL, env variables, testing, debugging, and optimization for low cost + strong coding performance. Use this DeepSeek API key: "sh......................" Make it fully working, minimal, and production ready." Thats it! Thank me later! submitted by /u/Agreeable-Pen-9763 [link] [comments]

I built a local mission control for Claude Code — it auto-stops when you hit your budget

Been using Claude Code heavily and kept running into the same problem — sessions would run long with no visibility into cost until it was too late. No built-in way to set a hard stop at $5 or 10k tokens. So I built AgentFleet — a local web UI that wraps Claude Code (and Codex) with: - Live terminal streaming in the browser via xterm.js so you can watch what the agent is doing in real time - Automatic session stop when you hit a USD or token budget limit - Session history persisted to local SQLite so you can review what happened after a session ends - Works with any shell command, not just Claude Code Everything runs locally — no cloud, no accounts, no data leaving your machine. It's an MVP so there are honest limitations (token count is estimated, PTY sessions don't separate stdout/stderr). But the budget enforcement works and has already saved me from a few runaway sessions. Repo: https://github.com/akhilsinghcodes/agents_fleet Happy to answer questions about how the PTY streaming or budget enforcement works under the hood. submitted by /u/mahsin09 [link] [comments]