Reminder... before Trump... Reps had an extremely narrow path to presidency. Trump broke the blue wall. MAGA is the way, but need support from establishment, which it doesn't give... so establishment needs to go. MAGA.
Someone just open sourced a complete AI agency and it hit 50K GitHub stars in under two weeks.
It's called The Agency.
And it's not a prompt template.
It's 147 specialized AI agents across 12 divisions -- engineering, design, marketing, product, QA, support, spatial computing, each with its own personality, workflow, and deliverables.
Here's what you actually get:
→ 147 agents across 12 divisions, each with unique voice and expertise
→ Works natively with Claude Code, GitHub Copilot, Gemini CLI, Cursor, OpenCode, and more
→ One-command install for any supported tool
→ Agents have defined missions, success metrics, and production-ready code examples
→ Full modding support -- build and contribute your own agents
→ Interactive installer that auto-detects your dev environment
→ Conversion scripts for every major agentic coding tool
→ Lua-style Markdown templates with YAML frontmatter
Here's the wildest part:
Most people use AI like a generalist intern. One model doing everything from writing copy to debugging code.
This repo structures AI like an actual company. Specialized roles. Clear responsibilities. Defined workflows between agents.
It started as a Reddit thread. Now it has 50K+ stars, 7.5K forks, and contributions from developers around the world.
Greg Isenberg called it out. It hit 10K stars in 7 days.
This is what the future of AI-assisted development actually looks like.
50K+ GitHub stars. 7.5K forks. 147 agents. 12 divisions.
100% Open Source. MIT License.
(Link in the comments)
🚨 WOW! Looks like the U.S. Park Police are using PLAINCLOTHES informants to catch people screwing with the sealant in the reflecting pool
This woman has just been DETAINED after being caught.
Keep your hands off the freaking sealant, losers.
Claude Code creator:
"Loops are as big a step as move from source code to agents. Loops - step from agents to the next thing.
30% of my code is fully written by loops right now."
in a 40-minute fireside chat, Boris Cherny reveals his actual working setup.
Loops + dynamic workflows + routines, and more.
Watch the full episode, then read the article on loop engineering below.
Broken Legs, Body Full of Shrapnel — He Still Got Every Man Out - Maj. James Capers, Jr. The First Black Marine Officer Nominated for the Medal of Honor Just Got It
Anthropic pays $750,000+ a year for engineers who can build LLM architectures from scratch. Stanford taught the entire thing in 1 hour lecture & released it for free.
Bookmark & watch this today before someone takes it down and read this article below
Andrej Karpathy: "90% of Claude's mistakes come from missing context, not a weak model."
41% mistake rate without a CLAUDE.md. 11% with the 4-rule baseline. 3% with the 12-rule version below
here are the 12 rules senior engineers settled on:
1. think before coding: state assumptions, don't guess. the model can't read your mind, stop hoping it will
2. simplicity first: minimum code, no speculative abstractions. the moment you let Claude add "for future flexibility," you've added 200 lines you'll delete next quarter
3. surgical changes: touch only what you must. don't let it improve adjacent code, that's how PRs blow up
4. goal-driven execution: define success criteria upfront, loop until verified. without them Claude either loops forever or stops too early
5. use the model only for judgment calls: classification, drafting, summarization, extraction. NOT routing, retries, status-code handling, deterministic transforms. if code can answer, code answers
6. token budgets are not advisory: per-task 4000, per-session 30000. by message 40 of a long debug, Claude is re-suggesting fixes you rejected at message 5
7. surface conflicts, don't average them: two patterns in the codebase? pick one. Claude blending them is how errors get swallowed twice
8. read before you write: read exports, callers, shared utilities. Claude will happily add a duplicate function next to an identical one it never read
9. tests verify intent, not just behavior: a test that can't fail when business logic changes is wrong. all 12 of Claude's tests can pass while the function returns a constant
10. checkpoint every significant step: Claude finished steps 5 and 6 on top of a broken state from step 4. nobody noticed for an hour
11. match the codebase conventions: class components? don't fork to hooks silently. testing patterns assumed componentDidMount, hooks broke them without surfacing
12. fail loud: "completed successfully" with 14% of records silently skipped is the worst class of bug. surface uncertainty, don't hide it
what actually compounds instead of the next framework:
- the CLAUDE.md file as institutional memory across sessions
- eval-driven changes, not vibe-driven
- checkpoints over speed
- explicit conflicts over silent blending
- discipline over framework, every time
- one repo, one rules file, no exceptions
you don't need a better AI
you need better context engineering
complete playbook below ↓
Marco Rubio jokes about UFC Freedom 250
Cage on White House lawn.
"The president's threatening to leave it permanently... Maybe we'll just host weekly fights between people in politics and settle our scores that way."
Will you be watching the UFC fights today?
“At my direction, the United States Southern Command delivered a swift and lethal kinetic strike to successfully execute Niño Guerrero, the infamous leader of Tren De Aragua, one of the most bloodthirsty Terrorist Organizations on Planet Earth.” - President DONALD J. TRUMP 🇺🇸
Elon just created 4,400 millionaires in a single day.
400 of them are now worth over $100 million.
These aren't VCs. They're SpaceX employees, and the list includes welders, technicians, and cafeteria staff, because for two decades the company paid every level of the workforce in stock instead of higher salaries.
Juan Hernandez immigrated from Mexico and took a $28 an hour contractor welding job in 2015. He says he didn't even know what SpaceX was. The company gave him a $10,000 equity grant and let him buy more shares through payroll deductions. That stake is now worth $880,000.
Trevor Hise's parents wanted him to take a stable job at General Electric. He picked SpaceX instead, stayed 12 years, and accumulated over 100,000 shares. At the $135 listing price that's $13.5 million. He's 37 and semiretired. His words: "The magnitude of this has been ridiculous."
The most telling detail came before the listing. Over 100 employees quietly banded together and negotiated a group wealth management deal covering up to $5 billion, because none of them had ever needed a wealth manager before.
Software IPOs have minted millionaires for 30 years. This is the first one where the money went to the factory floor.
what is agent looping
for the last two years we prompted agents one task at a time. that is starting to change
instead of asking an agent to build the landing page and then driving every step yourself, you set up a loop that handles discovery, planning, the work, checking, and iterating until the goal is met
looping is a setup you build. almost any agent harness can run it, it just depends on how you wire it up
at its simplest, looping is one agent working on itself:
> researches
> drafts
> checks the draft against a goal
> fixes what is weak
> runs that cycle again until the work clears the requirements
you are not prompting each step anymore. the agent repeats the cycle for you
the bigger version is a fleet looping. you give an orchestrator agent a goal, it breaks the goal into pieces, hands each piece to a specialist agent, and those specialists hand smaller jobs to their own subagents
the whole tree keeps looping through discovery, planning, execution, and verification until the goal is met
one agent looping is like a person redoing their own draft. a fleet looping is a whole team running a project end-to-end
you create a goal, and the system runs the loop until it finishes within the reqs you set
open and closed looping:
OPEN LOOPING is exploratory. it still has conditions and a goal, but you give the agent or the fleet a wide space to move in. it can try different paths, discover things, build something you did not fully spec out
this is the exciting end, it is what Peter and others are doing, and tbh it is where I want to spend more time
the catch is cost, an open loop with real room to explore burns an insane amount of tokens. for the 90 percent of people without an unlimited budget it is not runnable yet, and pointed at projects with a loose standard it turns into a slop machine
CLOSED LOOPING is bounded. a human designs the end-to-end path first:
> clear goal
> defined steps
> an eval at each step
> a point where it stops or hands back to you (and feeds back performance data)
the agents still loop, but inside framework you built. it gets better every run because each pass feeds the next, and it runs on a normal budget because the path is tight.
for most marketing work, closed is the one that pays off today.
> the orchestrator owns the goal
> the specialists own the steps
> the subagents do the narrow work
> an eval gate make sure its not slop
Claude Code's creator said something that stopped me cold:
"I don't prompt Claude anymore. I write loops — and the loops do the work. My job is to write loops."
Most developers are still crafting the perfect prompt.
The person who built the tool moved past prompting entirely.
In 30 minutes Boris reveals his actual daily Claude Code setup.
Claude Code + loops + dynamic workflows.
Worth more than any $500 vibe-coding course.
Watch it.
Then read this - everything you need to know about loops to actually apply what he says ↓
Bookmark both. This is your weekend.
Google has published a paper that might end the transformer era.
For the last 7 years, every major AI, ChatGPT, Claude, Gemini, has been built on the exact same architecture: The Transformer.
But Transformers have a fatal flaw.
To remember context, they have to process every single word against every other word. It’s called quadratic complexity. As your prompt gets longer, the compute cost explodes.
The alternative is the old-school RNN (Recurrent Neural Network). RNNs are incredibly cheap and fast, but they have a fixed memory size. If you give them a long document, they get amnesia.
Until today.
Google researchers published Memory Caching: RNNs with Growing Memory.
And it fixes the biggest bottleneck in AI.
Instead of an RNN having a fixed, rigid memory that constantly overwrites itself, Google gave it a "save" button.
The technique allows the RNN to cache checkpoints of its hidden states as it reads.
The memory capacity of the RNN can now dynamically grow as the sequence gets longer.
They built four different variants, including sparse selective mechanisms where the AI actively chooses exactly which checkpoints matter most.
The results rewrite the rules of efficiency.
On long-context understanding and recall-intensive tasks, these new Memory-Cached RNNs closed the gap with Transformers.
They achieved competitive accuracy without the explosive, quadratic compute cost. It perfectly bridges the gap between the cheap efficiency of an RNN and the massive capability of a Transformer.
We have spent billions scaling Transformers because we thought they were the only way an AI could remember a long conversation.
But Google just proved we don't need to process the whole history every single time.
We just needed a smarter cache.
Medicaid's "home health aide" program is being used as foreign aid. All the big Bhutanese advocacy groups are linked to home health firms. Medicaid company owners have affiliated charities that funnel profits abroad. Ohio Medicaid is funding a school system in Nepal!
Bhutanese are described as greedier and more cunning than Somalis. Huge numbers have their own Medicaid firms. In Ohio alone, just people with the Bhutanese last name of Adhikari have been paid $350M – a tenth of the GDP of their country. Much is sent back there.