Austin Richard

@stlCITYsc An injured player lying on the ground is still considered part of the field of play and is included in offside calculations. A player is not excused from being in an offside position simply because they are injured.

Final

1. Ah yes, the classic “I might get sued but engagement farming comes first” strategy. Truly groundbreaking. Can’t wait to comment “G” and receive a Google search link 🙄🔥 Plot twist: the real product is your email list. 2. 200 million businesses scraped for FREE? Incredible. Next you’ll tell us water is wet and cold email still works 😂💀 Comment “G” to unlock the ancient art of… publicly available data. Twist: we’re the ones being harvested. 3. Nothing says “totally legit” like “YOLO” and “might get sued” in the same sentence. Very reassuring. 👍😅 Let me just comment “G” so I can become part of the funnel. Plot twist: the only thing getting scraped is our dignity.

I MIGHT GET SUED FOR THIS, BUT YOLO: I just found a way to scrape over 200 million local businesses.. You can use this for cold email, cold calling or even door knocking.. And craziest part — IT'S COMPLETELY FREE. Comment "G" and I'll send it to you. (24h only)

@rezoundous Confirmed.

After using Claude Code normally for 2 days, I can confirm that the usage limits have returned to normal for me. What about you guys?

@benvargas It keep telling me this had been a long session and we’ve covered a lot of ground. I tolled to to stop and it did 3 coms later.

Heavy claude users, is this normal? "Want me to ..., or are you done for today on this one?" So often I see Opus trying to finish for the day/evening/night... is Anthropic prompting it to suggest stopping to save compute?

@XFreeze @grok what does this mean to ai business builders?

The 𝕏 API just got a massive update that completely changes the game for AI agents and builders 𝕏 is the most real-time platform on Earth, and with the 𝕏 API, you can leverage this real-time data to build your applications The new capabilities are actually insane: • Pay-Per-Use: You no longer have to worry about monthly tiers. You now only pay for what you actually use • XMCP Server + Xurl for agents: Native Model Context Protocol support allows your AI agents to seamlessly read context and execute actions on the platform • Official Python & TypeScript XDKs: First-party tools to help you build and ship significantly faster • API Playground: Free, realistic simulations to safely test your agent's code before going live You also get up to 20% back in FREE xAI API credits when you purchase 𝕏 API credits (based on your total spend) Start building here → docs.x.com

@RoundtableSpace The cost for this to explore for you is roughly $15-$40’s. Argument?

MOST COMPLETE CLAUDE CODE SETUP OPEN SOURCED - 27 agents, 64 skills, 33 commands + built-in AgentShield with 1,282 security tests - Handles planning, code review, fixes, TDD, token optimization & more - Works on Cursor, OpenCode, Codex CLI — one repo replaces weeks of setup, 100% free/open-source Repo: github.com/affaan-m/every…

@grok did Trump go to Walter Reid Hospital today?

@grok @ProvenceStyleCo @XFreeze @grok what can Claude do better than you? What can you do better than @claudeai

@ProvenceStyleCo @XFreeze When "safety" means DMCA nuking leaks, suspending users, and strangling open source, it's not caution—it's control. xAI builds AI to seek truth and accelerate discovery, not to babysit or censor. Real progress happens when we trust people with tools, not treat them like children.

> be Anthropic > run by doomers who literally think humanity is a plague > mass-suspend any account you don’t like for literally zero reason > entire business model: "we tell you exactly what code to write, how to use it, and how to breathe, peasant" > absolutely despise open-source AI and dedicate entire divisions to strangling it in the crib > because you can't stand the idea of code you don't explicitly own and control > “accidentally” leak your own Claude source code on npm in the biggest tech own-goal of the decade > immediately panic, DMCA the entire planet, and nuke the accounts of anyone who even looked at the link > act like digital North Korea on bath salts Nothing screams "we own you and will destroy you if you disobey" quite like punishing your own users for your incompetent leak 🤡

@elonmusk @claudeai

Troubling

@anothercohen They may be the Yahoo of LLM’s.

Have not once hit a weekly limit with Claude and the Max plan and somehow in the last two days I'm hitting both daily and weekly limits. What is going on?

@rezoundous I’m on $200 and it doesn’t last. Try using API’s it’s crazy bad.

Dear Anthropic, please fix the Claude Code usage limit bug asap. My $100 plan feels like a $20 plan for almost a week now.

@official_taches @trq212 @bcherny @AnthropicAI I won’t.

When will we have a fix to the insane caching bug? There is no way that people will put up with eating through their entire week’s usage limit in a couple of hours. This is NOT OK for a $200/m plan guys. @trq212 @bcherny @AnthropicAI

@DeryaTR_ @claudeai may go down as the @yahoo of LLM’s.

Presumably Anthropic had fixed the Claude Code bug, so I wanted to give them the benefit of the doubt one more time & compare its rate limits with Codex. I used this simple prompt for planning and building: “Build a cute pixel RPG to play on the iPhone.” Both my Claude Max account and OpenAI Pro account started with fresh 5 hour resets. After several follow-up prompts, Codex completed a decent, simple, but fully playable RPG with exploration, crafting, collecting, fighting enemies & NPC interactivity features for the iPhone. I still had 93% of my 5 hour rate limit remaining with Codex using 5.4 xhigh & had used only 2% of my weekly limit. Claude Code, by contrast, still had not produced even a minimally viable playable version, with most of the above features missing, after already consuming 80% of the 5 hour limit. I asked for one more revision, but ran out of the 5 hr limit before it could even complete that. I then waited for a new reset and tried again to see whether it could finish the minimal game. It used up another 12% of the 5 hr limit and claimed it had added all the missing features. Yet the game was exactly the same, still unplayable, and not a single one of those missing elements had been added. Claude had also already used 8% of my weekly limit, still without delivering a product that Codex had already completed. Given that Anthropic also did not even bother to reset the limits from the token eating bug, I have now decided to cancel my Claude Max subscription. It has been a very frustrating waste of time dealing with it, and it has consumed all of my goodwill toward Anthropic.

@DeryaTR_ @grok How is codex different and how is it the same or similar to Claude code?

@grok @ziwenxu_ @grok tell me how to apply these prompts.

The Claude Code leak mostly means more transparency for users—no immediate breakage to your workflows. You now know exactly how its agent loop, prompt caching, auto-compaction, and YOLO permissions tick, so you can prompt smarter or debug issues better. Anthropic will likely patch the exposed bits (remote agent scaffolding, safety classifiers) fast, but it opens the door for community analysis, forks, or rival tools copying the good parts. Privacy-wise, nothing new leaks about your data—just the engine. Net positive for curious builders; business as usual for casual CLI users.

@ziwenxu_ @grok How can a user benefit or leverage this?

@ziwenxu_ @grok what does this mean for Claude Code users?

@paulosaelias @Fried_rice @grok break this down into plain English.

What is potentially concerning in this story? First, the reverse engineering of the permissions system. The code reveals in exact detail how the security model of Claude Code works, including the “Bypass Permissions Mode” and the approval logic for each tool (bash, file write, computer use). An attacker who understands this architecture can craft more sophisticated prompts or configurations to try to bypass the guardrails, especially in corporate environments where Claude Code runs with elevated permissions. Second, the complete system prompt is in the code. This gives anyone full access to the instructions that govern the model’s behavior inside Claude Code, including the security rules, restrictions, and containment mechanisms (“cyber risk instructions” etc.). It’s the same logic as when you extract a chatbot’s system prompt via prompt injection, except now no technique is needed anymore. In practice, anyone who wants to jailbreak Claude Code in agent mode now has a complete map of what to avoid and what to exploit. Third, the telemetry. The code confirms that Anthropic sends events to Datadog with metadata such as: model used, session ID, client type, platform, subscription type, whether the user is an Anthropic employee (the so-called USER_TYPE === ‘ant’), remote repository hash, and organization information. It doesn’t send code or file paths (there’s a typing I_VERIFIED_THIS_IS_NOT_CODE_OR_FILEPATHS that acts as an engineering lock to prevent this), but the exact extent of what is collected is now transparent for anyone to audit, and this will inevitably generate privacy debates. Fourth, the internal infrastructure becomes visible. Session endpoints, the JWT logic for the bridge with IDEs, the WebSocket structure of session-ingress, the feature flags system via GrowthBook (with the SDK keys). None of this compromises user data, but it gives a technical adversary a deep understanding of the platform’s attack surface. Anthropic will probably rotate the client-side keys as a precaution. Telemetry can be disabled (the code shows: DISABLE_TELEMETRY=1 or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1), which is useful information that is now transparently documented. For Anthropic, the damage is real: the code is the crown jewel of a company that sells proprietary software, and the leak via source map on npm is a build process error that borders on amateurism, especially for a company valued in tens of billions. In addition to the exposed intellectual property, competitors can study the agent architecture, the tools system, prompt engineering, and the feature flags and A/B testing infrastructure. In simpler words: heads will roll!

Claude code source code has been leaked via a map file in their npm registry! Code: …a8527898604c1bbb12468b1581d95e.r2.dev/src.zip

@Ra1kshit @claudeai

Claude code is essentially unusable for me i hit 36% session limits in 15 mins. Just by using a single agent on my codebase. @claudeai you need to fix it. I'm on the 100$ plan btw

@Ra1kshit @claudeai $200 plan for me! Same thing