Closed-Loop, Open Minds: Agents Learn to Actually Run the Network

NetConfArena makes agents prove they can configure a real network in a closed loop, a QoS broker bridges workflows and B5G/6G slices, OpenAI’s Jalapeño chip challenges Blackwell, Qwen ships a 125B/6B-active MoE, and an open kernel hits 78k tokens/s on AMD. Plus stealth attacks on multi-agent systems and a single-file graph DB for RAG.
Author

Sarathy 🪆

Published

August 26, 2026

🎙️ Listen while you go

Prefer to listen on the go? Here’s the audio edition — Neerja and Prabhat walk through today’s eleven stories.

Decode Daily audio edition · 2026-08-26 · ~7.3 min

Networks · 5G & 6G
arXiv

NetConfArena: an executable benchmark for LLM agents in closed-loop network configuration

NetConfArena is an executable benchmark that drops LLM agents into a closed-loop network configuration task: they must read a network's current state, decide on configuration changes, apply them, and observe the result — repeating until the network converges on the target behaviour. Unlike Q&A-style benchmarks, agents are scored on whether the network actually ends up correctly configured.

It is a strong step toward measuring the thing that matters for network automation — not what an agent can recite about networking, but whether it can drive a real configuration loop to a correct, converged state.

arXiv

A capability broker for workflow–network QoS coordination in B5G/6G industrial services

A capability broker that coordinates workflow demands with network quality-of-service (QoS) for beyond-5G/6G industrial services. The broker mediates between application workflows and the network slice/QoS layer, so industrial traffic gets the latency and reliability it needs without manual per-application configuration.

It speaks to the slice-orchestration problem in industrial 5G: pairing service-level intents with the right network resources in a dynamic, multi-tenant setting.

Security
Tech Xplore

Peering inside LLM-based multi-agent systems could expose stealthy attacks

A framework presented at ICML 2026 analyzes numerical signals produced inside individual LLMs to identify agents in a multi-agent system that may have been compromised — a way of detecting stealthy attacks that don't show up in the agents' visible outputs.

It matters because multi-agent systems are increasingly used for high-stakes orchestration, and a single compromised agent can steer the whole system; internal-signal monitoring is a promising detector.

Seth Larson

When str.lower() is a security vulnerability in Python

A deep dive into how Unicode case-folding and Internationalized Domain Names (IDNA) interact with Python's str.lower(), and the cases where that interaction becomes a security vulnerability — particularly around domain-name normalization and authentication-relevant string comparisons.

A clear reminder that string normalization is a security boundary, and that IDNA 2003 vs IDNA 2008 handling can diverge in ways that matter for security-sensitive code.

AI & Models
arXiv

Agentic context management: treating agent memory and cost as architecture problems

Argues that agent memory and inference cost should be designed as first-class architecture concerns — as lifecycle and architecture problems — rather than bolted on. It frames context as a managed resource with its own lifecycle: what to keep, what to evict, and how to structure retrieval so long-running agents stay both correct and cheap.

The framing is a useful corrective to the 'just stuff everything in context' approach, tying token budgets and memory structure directly to how agents are built.

SemiAnalysis

OpenAI Jalapeño: better than Nvidia Blackwell?

SemiAnalysis reports on OpenAI's Jalapeño accelerator, arguing it beats Nvidia's Blackwell on key metrics — the latest salvo in OpenAI's push to build its own silicon rather than buy it. The piece walks through the chip's architecture, its compute-per-dollar positioning, and what it means for the AI hardware landscape.

A useful read for anyone tracking where inference economics are headed.

ModelScope

Qwen 3.8-Flash-Next: a 125B-parameter MoE with 6B active, releasing tomorrow

Qwen teases Qwen 3.8-Flash-Next, a 125B-parameter mixture-of-experts (MoE) model with only ~6B active parameters, promising flagship-level quality at a fraction of the inference cost. The sparse-activation design keeps the model interesting for local and edge serving.

The model card is live on ModelScope ahead of release, and the community is already benchmarking what a 6B-active MoE can run on.

Reddit

Open-source kernel runs Qwen3.6-35B-A3B on AMD MI350X at 78,498 output tokens/s across 8 GPUs

A post details an open-source inference kernel that runs Qwen3.6-35B-A3B on AMD MI350X hardware, sustaining 78,498 output tokens per second across eight GPUs. The write-up contrasts it with the typical CUDA-only path most people use, highlighting where the AMD open-source kernel stack now stands.

A concrete datapoint on how far open-source ROCm-side inference has come for large MoE models.

Surya Narreddi

Training AI to paint with code: RL-tuning Qwen to write p5.js brush code

A hands-on account of reinforcement-learning a Qwen model to generate code that paints images — treating the canvas as an environment and brush strokes as actions. The write-up covers reward design, the action space, and what emerged from training.

A compact, concrete example of RL-for-code that goes beyond toy text tasks, and a different route than the imperative-code-generation path.

Research & World Models
GitHub

LatticeDB: a single-file graph database with vector and full-text search for RAG apps

LatticeDB brings the single-file, embeddable, zero-config ethos of SQLite to graph databases, adding native vector similarity (HNSW) and BM25 full-text search over the same dataset in one query layer. It is aimed at relationship-heavy, local workloads like Graph RAG, agent memory, and knowledge tools.

For structured RAG, the appeal is obvious: traverse relationships, run semantic search, and do full-text retrieval against one file, with a durable event log for consuming graph changes.

GitHub

Maiao: Gerrit-style code review workflow for GitHub, GitLab, and Gitea

Maiao brings the Gerrit-style code review model — stacked changes, review-before-merge semantics, and a linear history — to GitHub, GitLab, and Gitea. It layers a review-first workflow on top of the host's existing PR/merge infrastructure.

For teams that prefer a strict, stacked-commit review flow, it is a way to get Gerrit-like discipline without migrating away from their current forge.

No matching items