Today’s edition is political, technical, and a little sobering: In Europe, Aleph Alpha and Cohere could be on the verge of forming a new AI heavyweight. At the same time, Google is pushing the next open model generation onto smartphones with Gemma 4 — and several recent research and community posts show where AI still gets things surprisingly wrong. In short: a lot is moving, but not everywhere with stable direction.

🤝 Aleph Alpha and Cohere: merger with political tailwind

According to a report by heise, Aleph Alpha and Cohere are planning a merger — apparently not only for business reasons, but also with political backing. The German government is said to view the deal as strategically relevant for Germany. That is notable because it could push the European AI market into a new phase: away from many small hopeful contenders, toward a player with more capital, more reach, and likely more negotiating power. For you, that means competition in European enterprise AI could shift noticeably. Aleph Alpha long stood for “sovereignty made in Europe,” while Cohere was known for strong foundation models with a business focus. Together, they would send a message to the market: Europe does not just want a seat at the table in AI, it wants to play the game. Whether this actually becomes a durable champion or just a politically well-packaged marriage with integration problems remains to be seen.
Source: heise

📱 Gemma 4: Google’s AI runs directly on the phone

With Gemma 4, Google is taking an exciting step toward on-device AI: the open model processes text, images, and audio directly on the smartphone — locally, without everything constantly being sent to the cloud. The so-called Agent Skills are especially interesting. They apparently allow the model not only to respond, but also to control tools, such as Wikipedia or interactive maps. This matters because mobile AI starts to feel less like a “chatbot in the browser” and more like genuinely useful everyday assistance. For developers, it opens up new possibilities in privacy, offline functionality, and latency. For users, it’s convenient: faster responses, less data leakage, more device autonomy. The catch remains the usual one: local does not automatically mean error-free, and agentic behavior on a phone can quickly turn into self-confident digital mediocrity. Still, Gemma 4 makes the direction of open models pretty clear.
Source: The Decoder

🔒 MiniMax M2.7: open weights, but not really free

On r/LocalLLaMA, MiniMax M2.7 is drawing attention because the weights are openly available — but the license is extremely restrictive. Commercial use in particular appears to be heavily limited. This is a good reminder that “open weights” does not automatically mean “open source.” In practice, that is an important difference: you may be able to test a model, analyze it, and run it locally, but not simply ship it in a product or deploy it as part of a service. For the community, that is frustrating because the technical progress is visible, but the legal usability is on a short leash. For companies, it means license review is not a side issue, but part of the architecture decision. Otherwise you may build something great — and then not be allowed to sell it because of the fine print. Charming, but not very scalable.
Source: Reddit / LocalLLaMA

🧩 Qwen 3.5: agents need clean templates, not magic

A deep dive from the LocalLLaMA community shows how sensitive tool calling and agent workflows in Qwen 3.5 are to prompt and template setup. The key point: many bugs are not necessarily “model failures,” but the result of unclear Jinja templates, forced prompt injections, or incorrectly assumed XML formats. That sounds technical, but it matters in day-to-day use: if a model is supposed to use tools, it needs clean role and format logic. Otherwise the agent proudly calls a tool — but in a syntax no one understands, least of all the tool itself. The post is a reminder that modern AI systems are not just model weights. Prompt engineering, template design, and infrastructure are at least as important. This is exactly where the “operating system” for agents is emerging right now. And yes: it is less glamorous than a new model name, but much closer to real product quality.
Source: Reddit / LocalLLaMA

🛠️ Tool tip of the day: Cloudflare Browser Rendering for MCP

If you are experimenting with browser automation and agents, it is worth taking a look at Cloudflare Browser Rendering via MCP. The appeal: agents get a remote browser with DevTools support, which makes debugging, web automation, and more complex interactions much more practical. This is especially interesting for prototypes that should not just read websites, but actively operate them. Instead of maintaining a fragile browser setup yourself, you can rely on infrastructure that is specifically built for such workflows. That saves time and nerves — and both are famously scarce in agent projects.

Source: Reddit / LocalLLaMA

🧐 Benchmark warns: multimodal AI prefers guessing to asking

A new benchmark on multimodal models shows an old but still useful problem: when visual information is missing or unclear, models rarely ask for help actively. Instead, they often just guess. That matters for anyone using AI in diagnostic, assistive, or analysis workflows. A system that politely stays silent when uncertain is usually more helpful than one that delivers nonsense with complete confidence. The study also offers some hope: with targeted reinforcement learning, this behavior can apparently be improved. That means “proactive questioning” is not just a UX idea, but a trainable behavior. For production systems, that is an important lever, especially when models work with images, documents, or screenshots.
Source: The Decoder

⚙️ DSPR: bringing physics and forecasting together

With DSPR, another research approach emerges that tackles a classic industrial problem: time-series forecasts should not only be statistically strong, but also physically plausible. This is especially important in industrial environments with changing operating states, delays, and complex interactions. Pure data models often produce strong numbers — until they suddenly generate predictions that make no sense in the real plant. DSPR addresses this with dual-stream approaches and Physics Residual Networks, combining data-driven prediction with physical correction. For you as a reader, this means AI in industry is maturing. The focus is shifting from “can the model predict at all?” to “can I trust that prediction in operation?”. That is often where the real value lies.
Source: arXiv

---

Don’t want to miss any news? Subscribe to the newsletter