
JLad
287 posts

JLad
@josh_ladner
Love is to peace, as hate is to war. We need more love in the world. -If you are reading this you are a cyborg like me-


Claude Code now supports agent teams (in research preview) Instead of a single agent working through a task sequentially, a lead agent can delegate to multiple teammates that work in parallel to research, debug, and build while coordinating with each other. Try it out today by enabling agent teams in your settings.json!

Please enjoy this Cheeky Pint / @dwarkesh_sp crossover with @elonmusk. Dwarkesh was most interested in how Elon is going to make space datacenters work. I was most interested in Elon's method for attacking hard technical problems, and why it hasn’t been replicated as much as you might expect. But we got into plenty of topics in this three-hour session. 00:00:23 Space GPUs 00:35:39 Alignment 00:58:48 xAI 01:15:01 Optimus 01:28:03 China 01:40:46 Management 02:16:38 DOGE 02:34:58 Space GPUs redux



On December 8, the Perseverance rover safely trundled across the surface of Mars. This was the first AI-planned drive on another planet. And it was planned by Claude.





WOW!!! If you have semantic memory tied to your UserPromptSubmit hooks, you MUST ALSO include it in your PreToolUse hook. I promise you - it will be an absolute GAME CHANGER. It will put your efficiency levels are over 9,000 (*vegeta voice*). How many times have you sat there, watching Claude code go through an extended workflow, just to notice it start to go down a path you just KNOW will be error filled - and subsequently take it forever to FINALLY figure it out? The problem with relying strictly on the UserPromptSubmit hook for semantic memory injection is the workflow drift from your original prompt. The memories it injects at the initiation of your prompt will be less and less relevant to the workflow the longer the workflow is. Claude has a beautiful thing called thinking blocks. These blocks are ripe for the picking - filled with meaning & intent - which is perfect for cosign similarly recall. Claude thinks to itself, "hmm, okay I'm going to do this because of this", then starts to engage the tool of its choice, and BOOM: PreToolUse hook fires, takes the last 1,500 characters from the most recent thinking block from the active transcript, embeds it, pulls relevant memories from your vector database, and injects them to claude right before it starts using its tool (hooks are synchronous). This all happens in less than 500 milliseconds. The result? A self correcting Claude workflow. Based on my testing thus far, this is one of the most consequential additions to my context management system I've implemented yet. Photos: ASCII chart showing the workflow of the hook, and then two real use-cases of the mid-stream memory embedding actually being useful. If you already have semantic memory setup, just paste this tweet and photos into Claude code and tell it to implement it for you. Then enjoy the massive increase of workflow efficiency :)




We now have 21 participants enrolled in trials worldwide. Check out how our Neuralnauts are driving BCI technology forward. neuralink.com/updates/two-ye…







claude code tip: have it make a sound when it needs your input use the hooks in ~/.claude/settings.json to trigger a sound. terminal-notifier works well for this. just give your terminal notification permission and you're good to go











