Today we are introducing Runway Builders, a program for Seed to Series C startups building the next generation of products and services with generative video and real-time conversational AI at their core. Participating companies receive complimentary API credits, our highest rate limits and access to a private community. Apply and learn more at the links below. [Translated from EN to English]
GENERATIVE AI
-

Claude Code Accidentally Open-Sourced Breaking News
By
–
Breaking!
Claude Code got “open-sourced”… or should I say, accidentally liberated -
Molmo Point: AI Visual Grounding with Precise Spatial Pointing
By
–
Molmo Point: Teaching AI to Ground Language in Precise Visual Locations
— Satya Mallick (@LearnOpenCV) 31 mars 2026
In this episode of Artificial Intelligence: Papers and Concepts, we explore Molmo Point, an extension of multimodal AI that focuses on precise visual grounding enabling models to not just describe images,… pic.twitter.com/z1wpwyHwqUMolmo Point: Teaching AI to Ground Language in Precise Visual Locations In this episode of Artificial Intelligence: Papers and Concepts, we explore Molmo Point, an extension of multimodal AI that focuses on precise visual grounding enabling models to not just describe images, but accurately point to specific regions within them. Instead of treating images as whole scenes, Molmo Point trains models to connect language with exact spatial locations, bringing AI closer to how humans reference and interpret visual information. We break down why visual grounding has been a persistent challenge in vision–language models, how pointing mechanisms improve interaction and understanding, and what this means for applications like robotics, UI automation, and real-world task execution. If you’re interested in multimodal AI, spatial reasoning, or the future of AI systems that can both see and act, this episode explains why Molmo Point represents an important step toward more precise and actionable visual intelligence. Resources: Paper Link: allenai.org/papers/molmopoin… Interested in Computer Vision and AI consulting and product development services? Email us at contact@bigvision.ai or visit us at bigvision.ai
→ View original post on X — @learnopencv, 2026-03-31 13:30 UTC
-
Flowith’s Canvas Unites Humans and AI Agents
By
–
Flowith's Canvas is the first to promise to put humans and AI agents on the same surface, where Claude Code and Codex agents work right inside the same flow!
— 🚨 AI News | TestingCatalog (@testingcatalog) 31 mars 2026
Human X multi-agent 👀 https://t.co/R46srQw4Gz pic.twitter.com/JUwsUdshpJFlowith's Canvas is the first to promise to put humans and AI agents on the same surface, where Claude Code and Codex agents work right inside the same flow! Human X multi-agent
-
OpenAI Codex Codebase Allegedly Leaked on GitHub
By
–
holy shitt, somebody at OpenAI leaked the entire codex codebase.. github.com/openai/codex
→ View original post on X — @arrakis_ai, 2026-03-31 13:27 UTC
-
Mad Max Remake: Fighting Over Claude Credits Instead of Oil
By
–
A remake of Mad Max but instead of oil everyone is fighting over Claude credits.
-

Natural-Language Agent Harnesses: Making AI Agent Control Portable and Inspectable
By
–
Agent harnesses are too restrictive. That's because they're still designed as code. What if the harness itself were written in natural language and interpreted by an LLM at runtime? This research explores the idea. The work introduces Natural-Language Agent Harnesses (NLAHs), a structured natural-language representation that externalizes harness logic as a portable, executable artifact. Instead of scattering control flow across controller code, framework defaults, and tool adapters, NLAHs make contracts, roles, stage structure, state semantics, and failure taxonomies explicit and editable. An Intelligent Harness Runtime (IHR) places an LLM inside the runtime loop to interpret and execute these harnesses directly. Why does it matter? Harness design is increasingly decisive for agent performance, but it's buried in code that's hard to transfer, compare, or ablate. NLAHs make the orchestration layer a first-class scientific object. The practical implication: harnesses become portable across runtimes, composable across tasks, and directly inspectable by humans and models alike. Paper: arxiv.org/abs/2603.25723 Learn to build effective AI agents in our academy: academy.dair.ai/
-

Meta-Harness: Automated System Achieves 6x Performance Improvement
By
–
NEW Stanford & MIT paper on Model Harnesses. Changing the harness around a fixed LLM can produce a 6x performance gap on the same benchmark. What if we automated harness engineering itself? The work introduces Meta-Harness, an agentic system that searches over harness code by exposing the full history through a filesystem. The proposer reads source code, execution traces, and scores from all prior candidates, referencing over 20 past attempts per step. On text classification, it improves over SOTA context management by 7.7 points while using 4x fewer tokens. On agentic coding, it outperforms all hand-engineered baselines on TerminalBench-2, scoring 37.6% versus Claude Code's 27.5%. This is a big deal! Here is why: The harness around a model often matters as much as the model itself. Meta-Harness shows that giving an optimizer rich access to prior experience, not just compressed scores, unlocks automated engineering that beats human-designed scaffolding. Paper: arxiv.org/abs/2603.28052 Learn to build effective AI agents in our academy: academy.dair.ai/
-
Minimax M27 Model Release Announcement and Blog Post
By
–
Blog: minimax.io/news/minimax-m27-…
→ View original post on X — @akshay_pachaar, 2026-03-31 13:07 UTC
-
MiniMax M2.7: First AI That Self-Improves Without Retraining
By
–
The first AI that improves without retraining. (it rewrites its own agent harness) Every developer I know has one thing in common: they obsess over their setup. The terminal, the scripts, the shortcuts. They don't just write code. They constantly refine how they work. The code gets better because the environment gets better. MiniMax just released M2.7, and I think the most interesting thing about it isn't a benchmark number. It's the fact that M2.7 improves its own agent harness. Autonomously. Let's break this down: When you run an AI agent today, it operates inside a "harness." Think of it as the agent's operating environment: the skills it can invoke, the tools it can call, its memory, and the rules it follows. Normally, a human engineer builds this harness, and the agent operates within it. The harness stays fixed. M2.7 treats its harness as something it can rewrite. Here's what the loop looks like: – The agent runs a task and analyzes where things went wrong – It plans changes to its own scaffold: skills, MCPs, memory – It applies those changes, runs evaluations against a benchmark – It compares the results and decides whether to keep or revert – It writes self-criticism into memory so the next round starts smarter Then it loops back and does it again. And again. Think of it like a developer who finishes a project, writes a retrospective, restructures their workflow based on what they learned, and shows up the next day with a better setup. Except the developer here is the model itself. MiniMax ran this self-optimization loop for over 100 rounds internally. Along the way, the model discovered things on its own: it systematically searched for optimal sampling parameters (temperature, penalties), wrote workflow-specific guidelines for itself (like automatically checking for the same bug pattern in other files after a fix), and even added loop detection to avoid getting stuck. No human had to tell it to do any of this. They also tested this in a more controlled setting. They had M2.7 compete in 22 ML competitions from OpenAI's MLE Bench Lite. Each trial ran for 24 hours, fully autonomous. After each iteration, the agent wrote a memory file and performed self-criticism, feeding those insights into the next round. With every round, the ML models it trained achieved higher medal rates. The best run earned 9 gold medals. I've summarized the self-evolving architecture in the graphic below. The reason I find this compelling: this isn't about making a smarter model. It's about making a model that makes itself smarter. The weights never change. What changes is the system around it: better skills, better memory, better workflow rules. And that distinction matters because it means the improvement loop can run continuously without any retraining. We're entering a phase where agents don't just follow instructions. They redesign their own playbook. If you want to learn more, I've shared a link to their official blog post in the next tweet.
→ View original post on X — @akshay_pachaar, 2026-03-31 13:07 UTC
