
Game changer: started using `$ npx @anthropic-ai/claude-code` to fire up Claude Code in the terminal… and the absurd token usage limits are GONE. Been prompting hard for almost 2 hours and my current session is only at 27%. We are SO back!
m-ret
1.9K posts


Game changer: started using `$ npx @anthropic-ai/claude-code` to fire up Claude Code in the terminal… and the absurd token usage limits are GONE. Been prompting hard for almost 2 hours and my current session is only at 27%. We are SO back!

Update: Socket has found 121 more compromised npm package artifacts across 84 package names, including 64 UiPath artifacts. Combined w/ TanStack, the current known total is 205 affected npm package artifacts across enterprise automation, AI/MCP, auth, workflow, and dev tooling.

There's an entirely different world out there



i spent the entire day keeping my laptop lid open so my AI agents could run brought portable chargers, tethered to my phone for internet, the whole deal finally, when i got home, i opened my laptop to see the work they'd done nothing had happened because Claude was waiting for permission to open the project folder this is the future of work






If you wanna switch to @Cloudflare Email Sending today, here's my prompt for you, as always I'm unaffiliated, not paid, not sponsored, but I like it, make sure you remove the space before the .com in the API url I added to avoid it becoming a link in this tweet: # Prompt: Migrate transactional email to Cloudflare Email Service Paste this into Claude Code (or Cursor, or any agent) running inside your project. --- I want to migrate this codebase's outbound email from its current provider (Postmark / SES / Resend / SendGrid / Mailgun / etc.) to Cloudflare Email Service (public beta, launched April 2026). Help me do this carefully. ## Context: what Cloudflare Email Service is A new transactional email API from Cloudflare. Endpoint: ``` POST https://api.cloudflare .com/client/v4/accounts/{ACCOUNT_ID}/email/sending/send Authorization: Bearer {API_TOKEN} Content-Type: application/json ``` Request body: ```json { "to": "user@example.com", // string OR array of strings "from": "no-reply@yourdomain.com", // string OR {"address":"x@y","name":"Display"} "subject": "...", "html": "
...
", // optional "text": "...", // optional (one of html/text required) "cc": ["..."], // optional, array "bcc": ["..."], // optional, array "reply_to": "...", // optional, single string "headers": {"List-Unsubscribe": "<...>"} // optional, e.g. for newsletters } ``` Success response: HTTP 200 + `{"success":true,"result":{"delivered":[],"queued":[],"permanent_bounces":[]}}`. Failure: non-200 OR `success:false` OR non-empty `permanent_bounces`. Always check all three. Pricing: $5/mo Workers Paid plan + 3,000 emails free + $0.35 per 1k after. Roughly 5× cheaper than Postmark. No batch send endpoint — loop single sends. ## Steps you should follow ### 1. Verify prerequisites with me Before writing any code, ask me to confirm: - I have a Cloudflare Workers Paid plan ($5/mo) - I've onboarded my sender domain(s) in Cloudflare dashboard → Email → Email Sending → Onboard Domain (this auto-adds SPF/DKIM/DMARC + cf-bounce MX records) - I have an API token with `email_sending:write` scope (created at dash.cloudflare.com/profile/api-to… → Custom Token) - I have my Cloudflare account ID Don't proceed until you have these. ### 2. Recommend a domain reputation strategy Most apps should split senders across 2-3 subdomains so spam complaints on one don't drag down deliverability on others: - `mail.

networking as activity is mostly cope. e.g. the conference circuit, the warm intros, the moving to sf discussions or whatever, oh & the “grabbing coffee” economy.. all of this is overwhelmingly negative selection esp with vc (lol). the ppl worth knowing are usually too busy doing the thing to be farmable, & the ppl available to be networked w/ are available cuz they have literally nothing better going on. do the work, then publish it loudly enough that the right ppl can find you w/o you having to chase. one way broadcast > two way schmoozing. this is why x matters a ton now more than ever before.




