Macaulay Culkin was paid $4,500,000 for Home Alone 2. His father picked every role, his parents fought over his fortune in court, and on the day of the custody trial his dad just disappeared. In the video below, a 20-year-old Culkin tells Barbara Walters about the first message his father sent him in 4 years. His father, Kit, travelled with him from set to set and picked every project. Mac says he never read a single one of the scripts for his 14 films. They learned the lines the night before, he shot them, and the cycle repeated. At his peak he was reportedly making $8,000,000 per film. At home, he says, he and his brother slept on the couch. At 14 his parents split, and he quit acting. A public custody battle followed. His mother said his father was drunk and abusive. Kit denied it. Mac had his parents' names taken off his trust fund, reportedly worth $15–20 million. On the day of the custody trial, his father just didn't show up. No note, no goodbye. 4 years later, a telegram arrived on Mac's opening night: "You will, as always, be wonderful. Dad." In 2025 Culkin said they hadn't spoken in 30 years. Would you forgive a parent who only reached out once you were famous again, or is that where family ends?

Dan Bilzerian told Joe Rogan he beat one man for $54,000,000 at poker, over 8 to 9 months. Some of poker's best players still think the money came from his father. In the video below, he tells Rogan how the games worked, and what he was on while he played. He says it started in college. He sold 3 guns for $750, turned it into $10,000 on a gambling boat, and had $187,000 at the Bellagio 3 weeks later. By 2012, he says, he was playing private heads-up games against billionaires. At one point he had $18,000,000 on the table. One hand alone, he says, was worth $14 to 15 million. The man reportedly on the other side: billionaire Alec Gores. Pros later said Gores lost over $40,000,000 to him. Doug Polk publicly asked him to prove it. His theory: the money came from Dan's father, Paul Bilzerian, a former corporate raider who went to prison. Bilzerian denies it. He says he only got a trust fund at 35, years after the poker money. Poker pro Chance Kornuth backed part of the story. He says he coached Bilzerian for the Gores game, played at $5,000/$10,000 blinds. Gores has never confirmed the numbers. Poker genius, or trust-fund kid with a great story?

Apple's $3,499 headset never shows you the room. Everything you see is a camera picture, streamed to the screens within 12 ms. I wanted to see how that works, and found a Vision Pro you can take apart. Lift the glass, pull it into layers, turn the lenses round to face you. What it shows: > 12 cameras, 5 sensors and 6 mics feed one chip, R1. The M2 next to it just runs the apps > the 2 screens are micro-OLED, each about the size of a postage stamp, 23 million pixels between them > behind each lens a ring of infrared lights and cameras watches your eyes. Invisible in real life, drawn red here > fans pull air in underneath and push it out the top The trick: the free anatomy skill makes Claude Code write the real numbers as a small model first, then draw every part from it and check every frame in headless Chrome. Built by @elvar_official. Press the steps yourself in the first reply ↓

This is f*cking insane. Every kid who watches F1 should get to play with this. An F1 wheel you can drive, pull off the car and crack open, one button press per step. I always wondered what drivers actually do with all those buttons, so I went through it myself. > through a chicane, 3 pulls on the right paddle go from 5th to 8th while the shift lights sweep green, red, blue > under braking the left paddle clicks back from 8 to 4, and one yellow button turns on the pit limiter > pull the red collar and the whole wheel slides off the column, so the driver can climb out > then it splits into layers down to the board. About 1.3 kg, mostly carbon fibre 20-25 controls on one wheel, every part drawn in code with Claude Code and the free anatomy skill. Made by @elvar_official, try it yourself in the first reply 👇 Build your own in the article below

Opus 5.5 is a beast at motion design but... give it one link and it becomes a full mechanical animation studio • real 3D engines where every part is modeled and moves on its own • cinematic exploded views with smooth camera moves down to every bolt • cutaways and airflow you can follow through the whole engine I asked for a turboprop teardown. this is render #3 send this to your Claude: mechanica-atlas.vercel.app

I gave Claude Code one folder and 5 free repos. 20 minutes later I had 3 agents planning, coding and reviewing each other. someone mapped 300+ open-source agent tools on one page. most people bookmark it and never open it again. hand Claude Code one folder and 5 repos from that list, and it stops being a chatbot. it plans, splits the work between agents, remembers, runs code in a sandbox and logs every step. here's the whole stack: > make a folder called AGENTS, open Claude Code in it, add a CLAUDE.md with one rule: "plan first, run code only in the sandbox, log every step" > install Ollama, run ollama pull qwen3. a local model for the cheap subtasks. $0 per token, nothing leaves your laptop > pip install crewai, then crewai create crew research. tell Claude to give it 3 roles: planner, coder, reviewer > pip install mem0ai. now the crew remembers your project between sessions instead of starting from zero > pip install e2b-code-interpreter (free key). every piece of code the agents write runs in a sandbox, not on your machine > pip install agentops. one line in the script and you see every step, every tool call, every error 20 minutes of setup, and you have a crew instead of a chat window. all the repos: -> github.com/ollama/ollama -> github.com/crewAIInc/crewAI -> github.com/mem0ai/mem0 -> github.com/e2b-dev/E2B -> github.com/AgentOps-AI/agent… bookmark this and test asap

this sh*t is unreal. your second brain can work the night shift now, on Grok Bot's own computer, with your laptop closed three bots, three jobs: the collector files every link, PDF and voice note you drop into raw/ and never touches the original the writer turns it into wiki pages and links every page back to where it came from the checker wakes up on a nightly routine and hunts contradictions and stale pages → you wake up to one morning page: what came in, what changed, what looks wrong → two sources disagree: it flags you instead of quietly picking one → nothing new about a page for a month: it gets a "needs a fresh source" tag chat memory keeps summaries. files keep exactly what you wrote no page gets saved without three things: > what it says > which file proves it > the last night it was checked paste this into Grok Bot: "Build me a second brain with three bots. Collector saves every source to raw/ and never edits it. Writer keeps wiki/ updated with a source link on every page. Checker runs every night at 3am, finds contradictions and stale pages, and sends me one morning summary. Ask me before deleting or sending anything. Show me the folder structure first and wait for my ok." give it one project for a week before you hand it your whole life the full 7-step build is in the article below ↓

THIS IS GETTING F*CKING DANGEROUS You can run 20 Claude Code agents at the same time and put a second model on top that checks every word they write. None of them gets away with making stuff up You open the terminal: - 20 agents reading your files at once - Every claim checked against the source before it's saved - Anything without a real quote gets sent back - Everything lands in plain markdown folders The trick is the split: Opus does the work, a cheaper Haiku only decides if the claim is actually in the source. The loop keeps running until every claim passes This used to be a week of reading. Now it's two markdown files and one prompt Same Second Brain + agent swarm setup everyone keeps sharing. Full breakdown below ↓

It is becoming f*cking dangerous: Claude Code can turn a flat 2D drawing into a 3D part you edit with one number ok I did not expect CAD to be next no CAD license. one open-source Python library and a prompt give it a dimensioned drawing of a bracket. it reads every measurement, writes the part as code and keeps each dimension as a named parameter change hole_pitch from 40 to 55 and the whole part rebuilds around it my favorite part: the drawing didn't give the wall thickness. it stopped and asked instead of making one up the setup: → pip install cadquery (free parametric CAD in Python, exports STEP and STL) → open Claude Code in an empty folder → drop the drawing in as a PNG or PDF → paste this: "Turn this drawing into a parametric CadQuery model. 1. Extract every dimension, unit and constraint into a table, with where each one sits on the drawing. Mark anything missing or ambiguous and ask me before you use it. 2. Write part.py with every dimension as a named parameter at the top. No hardcoded numbers in the geometry. 3. Use a separate subagent to check the model against the drawing: overall size, hole positions, hole diameters, and that the result is one valid closed solid. 4. Export part.step and part.stl, plus report.md with each dimension, its value and pass or fail. 5. Show me how to change one parameter and rebuild." start with a simple part you can measure by hand passing these checks means the geometry matches the drawing. it says nothing about strength or how the part holds up under real load watch a flat drawing become an editable part below ↓

Holy sh*t. Grok Bot can watch you do a task for 10 minutes and turn it into a job that runs every night with the laptop closed i've done the same 7-tab morning research by hand more times than i want to admit. the fix was one button and 5 rules teach → review → add rules → test → approve → schedule the official docs are blunt: a taught task is only a draft skill. the demo never shows it what to do when something breaks so before night 1, give it the rules the demo missed: → source is down: report it, never reuse yesterday's data → data is stale: flag it and stop → send, delete, publish or buy: draft it and wait for my yes → step half done: say exactly which part finished → retry only if running it twice changes nothing then one test run, and check it stopped at the approval point. a test run does real work limits worth knowing: > up to 50 routines per bot > schedules at least 5 minutes apart > last 20 runs kept per routine > delete a routine and there's no undo Teach it once. Write the rules. Sleep. Paste this into Grok Bot right after you teach it, the full build is in the article below: "Review the skill you just learned from my demo: [TASK NAME] 1. List every step and how it could fail: missing source, stale data, login wall, duplicate, rate limit 2. For each failure write one rule: if [problem] then [action] 3. Put every send, delete, publish or purchase behind my approval 4. Run one test, stop at the first approval, show me the result Do not schedule anything until I confirm"