WTF, GROK BOT JUST MADE AI AGENTS AVAILABLE TO LITERALLY ANYONE – CREATING CONTENT HAS NEVER BEEN THIS EASY, EVEN IF YOU'VE NEVER MADE ANYTHING BEFORE
Content was never a talent problem. It's a headcount problem.
One person doing research, design, copy, analytics, timing and publishing – that's six jobs. The switching between them is what kills consistency, not a lack of ideas.
Here's what one of these setups actually looks like.
A Chief of Staff sits in the middle and routes every task. Nothing lands on the human.
→ Researcher tracks what's actually moving and pulls real sources instead of guesswork
→ Writer turns that research into finished copy, ready to review
→ Visualiser gets fed a few reference visuals once, then ships everything in that style
→ Analyst reads the numbers and tells the rest of the team what worked
→ Scheduler owns timing and holds the queue
→ Publisher ships it
The part that makes it work: every agent on Grok Bot gets its own persistent computer, browser and file system – and they all share memory.
So the research is already sitting inside the draft before the draft starts. No copy-pasting between tools. No approving every step. No human in the middle.
You can even teach an agent a repetitive task by recording yourself doing it once. Start recording, do the thing, stop. It learns the pattern.
And that's the real shift.
Nobody needs AI to tell them what to post.
They need it to delete the 40 steps between the idea and the post.
Everyone has a backlog of things they've meant to make for months. This is what starts clearing it.
Full breakdown of the setup in the article below ↓
Webhooks used to be a one-way street: Notion could trigger your other apps, but not the other way around.
Now any app can trigger Notion directly! 🪝
Read the docs → https://t.co/MUJwYmxzmC
Now you can orchestrate any agent in Notion 🎶
With Notion as your orchestration layer: a Decagon ticket routes to your coding agent, which proposes a fix and loops in your team to approve. All in Notion.
Everyone can work with agents in Notion, not just engineers.
Software horror: litellm PyPI supply chain attack.
Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords.
LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm.
Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks.
Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages.
Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.
We are launching the official Ukrainian marketplace @MadeWithBravery to present our makers to the world. Strong and creative. 5% of the item cost goes to United24. That's why every purchase is a brick that can rebuild 🇺🇦.