AI Dynamics

Global AI News Aggregator

About

RESEARCH

  • PyTorch trunc_normal_ initialization bugs in LLM training code
    PyTorch trunc_normal_ initialization bugs in LLM training code

    Okay LLM + PyTorch people, trunc_normal_, what the fuck! Many LLM inits use it w/ default cutoffs. It's either not doing anything or it's quite broken due 2 issues. 1. The a/b cutoffs in PyTorch are not in std-devs, they are absolute. So w/ a std=0.02, and -2/2 (default arg) cutoffs that's 100σ!! That is a normal distribution, trun isn't doing anything. 2. There are numerical issues. Even in float32, the truncation produces a handful of -2 (lower cutoff) values, 100σ!! That's incomprehensibly improbable. I doubt a float32 or even float64 algo could even produce it, but clamping a bad float value does. Olmo (@allenai codebases) appear to be one of the few that uses trunc_normal_ and bothered to set the cutoffs properly. It'd be nice to see more train code opened up as a default. We so often only end up with a sanitized version of the inference/fine-tune friendly model these days and may lose details like original init. I've known about #1 for ages, I have an alternate trunc_normal_tf_ implementation in timm for that reason. But I saw those -2's last week when I was debugging something and was a little surprised.

    → View original post on X — @jeremyphoward, 2026-03-30 15:09 UTC

  • llama.cpp reaches 100k stars, local AI movement thriving
    llama.cpp reaches 100k stars, local AI movement thriving

    llama.cpp at 100k stars now that 90% of the code worldwide is being written by AI agents, I predict that within 3-6 months, 90% of all AI agents will be running locally with llama.cpp 😄 Jokes aside, I am going to use this small milestone as an opportunity to reflect a bit on the project and the state of AI from the perspective of local applications. There is a lot to say and discuss and yet it feels less and less important to try to make a point. Opinions about viability of local LLMs are strongly polarized, details are overlooked, the scientific approach is lacking. Arguments are predominantly based on vibes and hype waves. One thing is clear though – local LLMs are used more and more. I expect this trend to continue and likely 2026 will end up being one of the most important years for the local AI movement. I admit that I didn't expect the agentic era to come so quickly to the local LLM space. One year ago, the available models were too computationally expensive for doing long-context tasks. There wasn't an obvious path towards meaningful agentic applications. The memory and compute requirements were huge. Last summer, with the release of gpt-oss, things started to change. It was the first time we saw a glimpse of tool calling that actually works well within the resource constraints of our daily devices. Later in the year, even better models were released and by now, useful local agentic workflows are a reality. Comparing local vs hosted capabilities at a given moment of time is pointless. To try put things into perspective: – We don't need frontier intelligence to automate searches and sending emails – We don't need trillion parameter models to be able to summarize articles or technical documents – We don't need massive GPU data centers to control our home appliances or turn the lights off in the garage I believe that there is a certain level of intelligence we as humans can comprehend and meaningfully utilize to improve our working process. Beyond that level, access to more intelligence becomes unnecessary at best and counterproductive at worst. I also believe that that level of useful artificial intelligence is completely within reach locally and it has always been just a matter of implementing the right software stack to bring it to the end user. With llama.cpp, I am confident that we continue to be on the right track of building that software stack! The llama.cpp project is going stronger than ever. With more than 1500 contributors, the project keeps growing steadily. From technical point of view, I think that llama.cpp + ggml is the only solution that actually makes sense. That is, the software stack must run efficiently on every possible device, hardware and operating system. The technology is too important to be vendor-locked. It has to be developed in the open, by the community, together with the independent hardware vendors. This is the only right way to build something that will truly make a difference in the long run. I won't try to convince you about what is currently and will be possible with local AI. We will just continue to build as usual. I am confident that after the smoke clears and we look objectively at what we have built together, the benefits will be obvious to everyone. Big shoutout to all llama.cpp maintainers. I feel extremely lucky to be able to work together with so many talented contributors. Every day I learn something new and I feel there is so much more cool stuff that we are going to build. Also, I am really thankful that the project continues to have reliable partners to support it! Cheers!

    → View original post on X — @julien_c, 2026-03-30 15:00 UTC

  • Exploring the Mathematical Theory of Mind and Modern AI
    Exploring the Mathematical Theory of Mind and Modern AI

    "The Laws of Thought: The Quest for a Mathematical Theory of the Mind" – explores the quest to use mathematics to describe the ways we think, the ideas behind modern AI systems, and the ways in which they still differ from human minds. Get it at http://
    amzn.to/4rNbszn

    → View original post on X — @kirkdborne

  • Roberta Raileanu Joins RAAIS 2026 Conference in London
    Roberta Raileanu Joins RAAIS 2026 Conference in London

    We're excited to have @robertarail at @raais 2026! Roberta leads open-ended learning at @GoogleDeepMind – from MLGym and MaestroMotif to Toolformer and Llama 3's tool use, her work is shaping what it takes for ai agents to keep acquiring skills. Join us on 12 june in london!

    → View original post on X — @nathanbenaich, 2026-03-30 14:51 UTC

  • CAID: Multi-Agent Asynchronous Coordination for Software Engineering
    CAID: Multi-Agent Asynchronous Coordination for Software Engineering

    Effective strategies for asynchronous software engineering agents. elvis (@omarsar0) NEW research from CMU. (bookmark this one) The biggest unlock in coding agents is understanding strategies for how to run them asynchronously. Simply giving a single agent more iterations helps, but does not scale well. And multi-agent research shows that coordination > compute. A new paper from CMU proves this with a practical multi-agent system. CAID (Centralized Asynchronous Isolated Delegation) borrows proven human SWE practices: a manager builds a dependency graph, delegates tasks to engineer agents who work in isolated git worktrees, execute concurrently, self-verify with tests, and integrate via git merge. CAID improves accuracy over single-agent baselines by 26.7% absolute on paper reproduction tasks (PaperBench) and 14.3% on the Python library development tasks (Commit0). The key insight is that isolation plus explicit integration beats both single-agent scaling and naive multi-agent approaches. For long-horizon software engineering tasks, multi-agent coordination using git-native primitives should be the default strategy, not a fallback. Paper: arxiv.org/abs/2603.21489 Learn to build effective AI agents in our academy: academy.dair.ai/ — https://nitter.net/omarsar0/status/2038627572108743001#m

    → View original post on X — @dair_ai, 2026-03-30 14:42 UTC

  • CAID: Multi-Agent Coordination Improves Coding Task Accuracy
    CAID: Multi-Agent Coordination Improves Coding Task Accuracy

    NEW research from CMU. (bookmark this one) The biggest unlock in coding agents is understanding strategies for how to run them asynchronously. Simply giving a single agent more iterations helps, but does not scale well. And multi-agent research shows that coordination > compute. A new paper from CMU proves this with a practical multi-agent system. CAID (Centralized Asynchronous Isolated Delegation) borrows proven human SWE practices: a manager builds a dependency graph, delegates tasks to engineer agents who work in isolated git worktrees, execute concurrently, self-verify with tests, and integrate via git merge. CAID improves accuracy over single-agent baselines by 26.7% absolute on paper reproduction tasks (PaperBench) and 14.3% on the Python library development tasks (Commit0). The key insight is that isolation plus explicit integration beats both single-agent scaling and naive multi-agent approaches. For long-horizon software engineering tasks, multi-agent coordination using git-native primitives should be the default strategy, not a fallback. Paper: arxiv.org/abs/2603.21489 Learn to build effective AI agents in our academy: academy.dair.ai/

    → View original post on X — @debashis_dutta, 2026-03-30 14:41 UTC

  • NVIDIA Unveils ProRL Agent for Reinforcement Learning of LLM Agents

    NVIDIA AI Unveils ProRL Agent: A Service Infrastructure for Reinforcement Learning of Multi Turn LLM Agents at Scale! #BigData #Analytics #DataScience #AI #MachineLearning #NLProc #LLM #IoT #IIoT #PyTorch #Python #RStats #TensorFlow #Java #JavaScript #ReactJS #GoLang

    → View original post on X — @gp_pulipaka

  • Google’s Paper Assistant Tool Success at ICML 2026
    Google’s Paper Assistant Tool Success at ICML 2026

    Google's Paper Assistant Tool was extremely popular, giving AI feedback on ~4500 submissions prior to the #ICML2026 deadline. Results were positive! 92% of participants said they'd use it again, and 73% rated the feedback as helpful. Read the full blog post for more details: [Translated from EN to English]

    → View original post on X — @thegautamkamath, 2026-03-30 14:21 UTC

  • Basic Mathematical Foundations of AI with Python
    Basic Mathematical Foundations of AI with Python

    Basic Mathematical Foundations of AI — Hands on with Python: https://
    amzn.to/4c0w6pz

    → View original post on X — @kirkdborne