Our sessions have been messaging each other for months btw ;)
@nicopreme’s pi-intercom extension makes it easy for one session to pick up where another left off.
Open source Pi packages mean there are multiple ways you can customize Pi. Link to this package and more below.
We’ve been excited to see so many people using and building on Pi.
This week we listened to Scott Gerring from @datadoghq share how he configures Pi for his work.
Start minimal, notice when you hit friction and ask Pi to remove it. Link to full episode below. We recommend!
A senior Anthropic engineer just dropped 15-page PDF on "Graph Engineering and Agent Memory" for multi-agentic systems.
The shift: your agent's memory dies with its context window. A knowledge graph makes it permanent.
Extract → Store → Retrieve → Evolve
Every graph-based memory runs 4 stages:
• Extract: pull entities and typed relations out of raw docs and conversations into structured triples.
• Store: canonical nodes, typed edges, provenance on every fact. One connected graph instead of scattered chunks.
• Retrieve: multi-hop questions become graph traversal. "Who owns what breaks if this ships" is one walk, not six guesses.
• Evolve: the stage everyone under-builds. Facts get validity windows. Nothing is deleted, only marked superseded, so "who owned this in April" still answers.
This 15-page PDF changed how I'm building multi-agent systems today.
Read it now, then explore the article below👇
Matt Pocock just dropped an 18-minute talk at @aiDotEngineer on why software fundamentals matter more than ever in the AI age:
00:00 - Why specs-to-code produces garbage
04:36 - Grill Me: the skill that interrogates your plan before AI writes code
07:21 - Fix verbose AI with a ubiquitous language
09:45 - TDD is your AI's speed limit
12:35 - Deep modules: the codebase structure AI thrives in
15:04 - Design the interface, delegate the implementation
These 18 minutes of software design fundamentals will replace 20 paid AI coding courses.
Watch it, then read the guide on how to make a company AI-native below.
https://t.co/aU4uGollhD
Should AI Engineers read code anymore in 2026? This, apparently is a divisive take, that has folks like Theo, Hashimoto, Primeagen and even uncle bob chiming in.
I predicted this two months ago, and named it the ZL Continuum.
My talk from @aiDotEngineer is covering this debate, and where your attention should go after models drift in capability is live now. Please go take a loook.
Huge thanks for AI Engineer folks for prioritizing the recording as the conversation about this topic caught up.
Every company should have a full stack team of 5 building a product who are banned from directly writing code; they must force the agents to do it. In 2 months they will be your most productive team.
🚀 Maple is now on Windows
File uploads, voice, and the Maple Proxy API, all end-to-end encrypted, backed by verifiable open-source code.
That completes the lineup: web, iOS, Android, macOS, Linux, and Windows. Download it now!