Kagi

Kagi AI

Kagi AI

Kagi AI

Kagi AI

Kagi AI

Kagi AI

Kagi AI

Kagi AI

Kagi AI

Kagi AI

thing i wish i'd known about ai tools when i started using them seriously a year ago

the biggest unlock wasn't the model getting better. it was me getting better at knowing when to use which tool. year-ago me: opened chatgpt for everything because it was the first tab. asked it questions, got mediocre answers, accepted them, moved on. now me: actually thinks about which tool fits the task. claude for writing and reasoning. perplexity (used to, less now) or kagi for "find me a source." cursor for code. notebooklm for synthesizing across many documents. chatgpt voice for thinking-out-loud. granola for meeting notes. each one has a specific role. this sounds obvious typed out. it wasn't obvious when i was just starting. i thought i was supposed to find The One Tool and master it. turns out the skill is matching tool to task. the tools are mostly fine. the user choosing the wrong tool is most of why outputs are bad. second thing: don't trust any tool that doesn't show its work. perplexity citations matter. claude saying "i'm not certain about this" matters. tools that just confidently produce output with no provenance are dangerous if you're going to act on the output. early on i trusted everything equally. now i grade tools by how clearly they show me what they don't know. third thing: the cheap subscriptions add up faster than you think. i ran the math at one point — what i spent in my first year of "trying ai tools" was more than what i'd have paid a human freelancer to do the things i was trying to automate. would have been faster, too. AI tools have a real cost-benefit math and it's not always in your favor, especially early when you're still figuring out what works. if i'd known those three things a year ago, i'd have wasted less money and gotten better outputs sooner. posting in case it helps anyone earlier in the curve. submitted by /u/Honest-Purchase-9113 [link] [comments]

Claude Code's source code appears to have leaked: here's what we know

Anthropic appears to have accidentally revealed the inner workings of one of its most popular and lucrative AI products, the agentic AI harness Claude Code, to the public. A 59.8 MB JavaScript source map file (.map), intended for internal debugging, was inadvertently included in version 2.1.88 of the @anthropic-ai/claude-code package on the public npm registry pushed live earlier this morning. By 4:23 am ET, Chaofan Shou (@Fried_rice), an intern at Solayer Labs, broadcasted the discovery on X (formerly Twitter). The post, which included a direct download link to a hosted archive, acted as a digital flare. Within hours, the ~512,000-line TypeScript codebase was mirrored across GitHub and analyzed by thousands of developers. For Anthropic, a company currently riding a meteoric rise with a reported $19 billion annualized revenue run-rate as of March 2026, the leak is more than a security lapse; it is a strategic hemorrhage of intellectual property.The timing is particularly critical given the commercial velocity of the product. Market data indicates that Claude Code alone has achieved an annualized recurring revenue (ARR) of $2.5 billion, a figure that has more than doubled since the beginning of the year. With enterprise adoption accounting for 80% of its revenue, the leak provides competitors—from established giants to nimble rivals like Cursor—a literal blueprint for how to build a high-agency, reliable, and commercially viable AI agent. Anthropic confirmed the leak in a spokesperson’s e-mailed statement to VentureBeat, which reads: “Earlier today, a Claude Code release included some internal source code. No sensitive customer data or credentials were involved or exposed. This was a release packaging issue caused by human error, not a security breach. We're rolling out measures to prevent this from happening again.” The anatomy of agentic memory The most significant takeaway for competitors lies in how Anthropic solved "context entropy"—the tendency for AI agents to

Kagi Small Web