The infrastructure for artificial intelligence is consolidating rapidly, concentrating both capability and control among a narrowing set of actors while creating new vulnerabilities for those outside that circle. The Army's decision to funnel 120 procurement actions into a single $20 billion Anduril contract exemplifies this trend in defense spending, where consolidation of capability into fewer hands has become the default procurement strategy. Meta's reported 20 percent workforce reduction alongside massive capital expenditure on AI infrastructure reveals the underlying economics: the cost of building dominant infrastructure is so high that companies must cut headcount elsewhere to justify the burn. OpenAI is moving aggressively into the transaction layer through new app integrations, positioning itself to observe and influence user behavior at scale, while North Korean operatives demonstrate how the same tools can be weaponized to impersonate workers and drain European companies. Users trust AI-generated summaries at rates approaching 40 percent despite a documented 60 percent hallucination rate, creating asymmetric risk for those relying on these outputs without verification.
Software engineering research reflects this consolidation from a different angle: the field has moved from treating agents as a research question to treating them as an engineering problem that requires scaffolding. Repositories like agency-agents and superpowers ship with built-in personality, processes, and deliverables, moving multi-agent systems from conceptual territory into applied methodology. Specialized tools handle context management through file system paradigms while others bind natural language to physical hardware actuators. The decisive shift is architectural: capability and tooling are decoupling from each other, with plugin ecosystems becoming the distribution model for agent capabilities. Fine-tuning and multi-agent coordination are now engineering problems, not research frontiers. Yet the research literature simultaneously documents fundamental gaps in practical effectiveness: patch overfitting detection fails against random baselines in realistic settings, frontier agents cannot match instruction-tuned models at post-training tasks, and sentiment analysis varies strongly within individuals. The field is building production systems while the underlying evaluation rigor remains contested.
Developers on GitHub have internalized both the consolidation and the gaps. The repositories gaining traction are those solving concrete production problems: headless browsers designed for agent interaction rather than retrofitted tools, dataset quality infrastructure, autonomous research loops, and output control mechanisms. The pattern across all three domains is identical: whoever builds infrastructure that touches users or controls interfaces accumulates leverage, data flows, and margin. Builders with direct user contact consolidate power. Everyone else either cuts costs to fund someone else's advantage or gets exploited by the tools they cannot fully trust or control.
Grant Calloway
No lab headlines.
Context. Microservice architectures are widely adopted for building scalable cloud-native systems, enabling independent deployment, fine-grained service composition, and operational elasticity. Problem. Despite growing interest in sustainable software, research on energy efficiency in microservices spans operational, infrastructural, and architectural perspectives, but these are typically addressed in isolation. Existing studies focus on optimisation techniques or measurement approaches, with limited synthesis of how energy efficiency is considered, measured, and addressed at the architectural level. Goal. This study synthesises research on energy-efficient microservices by examining where energy efficiency is considered, how it is measured, and which architectural solutions have been proposed. Method. We conduct a systematic literature review following Kitchenham's guidelines, screening publications from four major digital libraries through a six-stage process with backward and forward snowballing, resulting in 40 primary studies. Results. Energy efficiency is predominantly addressed at runtime through monitoring, scheduling, and resource management, while design-time integration remains limited. Measurement practices are largely infrastructure-oriented and rely on model-based estimation and coarse-grained monitoring. Conclusion. Energy efficiency in microservices is primarily treated as an operational optimisation problem rather than a lifecycle-spanning architectural concern, highlighting the need for earlier architectural integration and improved measurement practices.
Reusing embedded software functions across products is economically valuable but technically difficult: the same functionality implemented for two different microcontroller platforms can be entirely incompatible at the hardware level, even when the functions score above 0.90 cosine similarity and both pass SonarQube quality checks. Static analysis tools were designed to measure code quality, not hardware-domain compatibility, and have no model of peripheral interfaces, hardware abstraction layer (HAL) dependencies, or register-map constraints. This paper presents a domain-aware retrieval-augmented generation (RAG) pipeline for embedded C software reuse detection that addresses the hardware-compatibility gap directly. The pipeline enriches each function by extracting its existing inline comments, call-graph context, and a project README before embedding it with eight backbone models (MiniLM, MPNet, BGE, E5, GraphCodeBERT, OpenAI text-embedding-3-small, LLaMA 3 8B, StarCoder2 3B) acting as feature extractors. Four hardware-compatibility validators---covering peripheral token overlap, parameter count parity, call-graph dependency overlap, and structural branching pattern---filter candidates directly in the retrieval stack. Evaluated on six public embedded C software projects (184 functions, 4,815 above-plateau pairs), the pipeline reveals that SonarQube produces a 93.6% false-positive rate as a reuse filter, with 83.5% of failures caused by hardware-environment mismatches that static analysis cannot detect. Manual verification of 40 rejected pairs confirms 97.5% validator accuracy, and a diagnostic rule-injection variant identifies the dominant failure categories (McNemar chi-squared~=~294.0, p~$<$~0.001).
Agentic AI is increasingly used to coordinate planning, implementation, review, and testing in software development, yet it often offers limited transparency into its decisions and interactions. Many such systems also assume that users can effectively guide the AI's decisions and validate its outputs. This assumption poses a particular challenge for novices, who must simultaneously learn how agentic AI works, how to collaborate with it effectively, and how to evaluate its outputs critically. To address this challenge, we present \textit{AgentForge}, an immersive learning system in which novices take on one of four software-engineering roles: Task Planner, Patch Author, Code Reviewer, or Test Runner, within a multi-agent code-repair workflow. In each practice session, the novices perform their chosen role while AI agents perform the remaining three. Through role-based scaffolding and metacognitive support, AgentForge clarifies role-specific responsibilities, makes agent coordination and intermediate artifacts visible, and encourages novices to monitor and evaluate their decisions. In a study with 37 novice developers, participants achieved high task-completion rates with AI-agent support. However, interaction demands differed significantly across practices: the Code Reviewer practice required more interaction turns, reroutes, and completion time ($p_{\mathrm{adj}} = .004$) and was perceived as the most challenging. Participants nevertheless reported significant gains in their understanding of software repair and agent collaboration ($p_{\mathrm{adj}} < .001$). These findings suggest that AgentForge can help novices develop practical software-engineering skills while learning to collaborate with agentic AI more critically and effectively.
Fine-tuned code models often behave as domain specialists and can degrade sharply under distribution shift: in our clone-detection setting, a model trained on same-language clones drops 71\% F1 on cross-language clones, while multi-task training falls to 0.151 F1 on unseen AI-generated clones. Our companion study shows that post-hoc model merging can address this fragmentation, achieving 93\% of multi-task performance without training data while generalizing 4$\times$ better to unseen clone types. However, no practical tool exists that lets SE researchers diagnose checkpoint compatibility, merge specialists, validate results on SE benchmarks, and export models for deployment. We present \textbf{MergeSE}, an open-source CLI and web tool for training-free model merging of HuggingFace encoder checkpoints. While motivated by OOD generalization in clone detection, MergeSE supports SE classification workflows more broadly through a built-in registry of nine task types, including vulnerability detection, defect prediction, and code-smell detection. MergeSE provides five operations: \textit{tasks}, \textit{inspect}, \textit{merge}, \textit{evaluate}, and \textit{export}. It supports five merging algorithms, including TIES, DARE-TIES, Wudi, PCB, and averaging; detects cross-task classification-head mismatches; produces seedable deterministic outputs; and includes bundled benchmark samples for smoke-test reproduction. A full merge of two 124M-parameter checkpoints completes in under 5 seconds on CPU. End-to-end validation confirms that MergeSE-produced checkpoints match reference implementations and recover cross-domain performance from domain-specific specialists. The tool is available online at https://mergese.usask.ca, and the development repository is at https://github.com/srlabUsask/MergeSE.
Source code summaries have traditionally been evaluated from a human developer's perspective, with quality determined by how closely they resemble developer-written references and how well they align with human preferences. But this overlooks a growing reality: LLM-based tools and agents increasingly consume code summaries as inputs for software engineering (SE) tasks, and what makes a summary useful for a consuming agent on a task remains largely unexplored. To bridge this gap, we propose SONAR, a reference-free framework that evaluates source code summaries along four dimensions: Correctness, Abstraction, Conciseness, and Fluency. Rather than optimizing for a pre-written "gold standard", SONAR introduces a novel code regeneration-based approach that uses a summary to regenerate code and leverages that reconstruction as a quality signal of the summary. This provides an empirical grounding that requires neither a reference summary nor the subjective judgment of humans or LLMs. We evaluate SONAR's dimensions on their ability to influence LLM performance across four downstream SE tasks. We find that Correctness, followed by Abstraction, significantly correlates with LLM performance, with correlations up to 14X higher than the best baseline. Conciseness and Fluency, though widely valued by human developers, remain mostly insignificant to an LLM consumer, suggesting that what makes a summary useful is task- and consumer-dependent. Through a large-scale evaluation of 11 popular LLMs using SONAR, we further identify the strengths and weaknesses of different models across each quality dimension, while offering insights to facilitate future research on task-aware summarization.
The growing diversity of code clone types, from syntactic copies to cross-language semantic clones to AI-generated duplicates, has created a fragmentation crisis in clone detection. Current deep learning detectors are domain specialists that degrade significantly outside their training distribution, with F1 drops exceeding 70% across domains. Deploying multiple specialized models is impractical, yet training a single cross-domain detector requires simultaneous access to all training data. To address this, we investigate model merging, a family of post-hoc techniques that operate solely on trained checkpoints. We evaluate parameter merging with five task-vector methods, architecture merging via greedy layer stitching, and cross-tokenizer alignment across four code models, three benchmarks, and twelve configurations. Same-base TIES merging creates effective cross-domain detectors, validated across two model families and three random seeds, reaching 0.865 combined F1 on UniXcoder, 93% of multi-task performance without any training data at the merging step. WUDI achieves the highest in-distribution combined F1 at 0.899, but TIES generalizes better to unseen AI-generated clones, making it our recommended method. Cross-base merging yields only marginal and high-variance gains across all five methods, indicating that task vector compatibility through a shared pre-trained base is the binding factor for effective merging. Merged detectors also outperform zero-shot code LLMs on GPTCloneBench at lower inference cost and generalize up to 4x better than multi-task training to unseen AI-generated clones, suggesting a trade-off between in-domain performance and OOD robustness. This work provides one of the first systematic empirical studies of model merging for software engineering and a practical recipe for building cross-domain clone detectors.
Composite score across coding, math, and reasoning
| # | Model | Score | tok/s | $/1M |
|---|---|---|---|---|
| 1 | Gemini 3.1 Pro Preview | 57.2 | 120 | $4.50 |
| 2 | GPT-5.4 | 57 | 84 | $5.63 |
| 3 | GPT-5.3 Codex | 54 | 68 | $4.81 |
| 4 | Claude Opus 4.6 | 53 | 57 | $10.00 |
| 5 | Claude Sonnet 4.6 | 51.7 | 61 | $6.00 |
Agentic coding on real-world software engineering tasks
| # | Model | Score |
|---|---|---|
| 1 | Claude Code | 52.9% |
| 2 | Junie | 52.1% |
| 3 | Claude Opus 4.6 | 51.7% |
| 4 | gpt-5.2-2025-12-11-xhigh | 51.7% |
| 5 | gpt-5.2-2025-12-11-medium | 51.0% |
OpenViking is an open-source context database designed specifically for AI Agents(such as openclaw). OpenViking unifies the management of context (memory, resources, and skills) that Agents need through a file system paradigm, enabling hierarchical context delivery and self-evolving.
Official, Anthropic-managed directory of high quality Claude Code Plugins.
Dimensional is the agentic operating system for physical space. Vibecode humanoids, quadrupeds, drones, and other hardware platforms in natural language and build multi-agent systems that work seamlessly with physical input (cameras, lidar, actuators).
Fully automatic censorship removal for language models
OpenRAG is a comprehensive, single package Retrieval-Augmented Generation platform built on Langflow, Docling, and Opensearch.
Firmament Autopilot Embedded System
ARIS ⚔️ (Auto-Research-In-Sleep) — Claude Code skills for autonomous ML research: cross-model review loops, idea discovery, and experiment automation via Codex MCP
An AI framework for generating and modding osu! beatmaps for all gamemodes from spectrogram inputs.
Fine-tuning & Reinforcement Learning for LLMs. 🦥 Train OpenAI gpt-oss, DeepSeek, Qwen, Llama, Gemma, TTS 2x faster with 70% less VRAM.
Collect some World Models for Autonomous Driving (and Robotic, etc.) papers.