THE AI PULSEMAY 15, 2026EN

The Pulse — May 15, 2026

The signals that entered our radar, organized with sources and context to understand what changed.

Analyze with my AI Send this Pulse on WhatsApp ↗Get the next edition

ModelsAgentsAnthropic

LISTEN TO THIS EDITION

The audio script is ready; narration will appear after voice generation finishes.

01OpenAI (product post)
Codex is now in the ChatGPT mobile app (remote/relay + approvals)
WHY IT ENTERED THE RADAR
This is the “agent era” UX shift: long-running work needs lightweight human checkpoints (approve, redirect, clarify) from anywhere. The key detail is the secure relay model: work stays on your machine, state syncs to phone (diffs/tests/screens/terminal).
SUGGESTED EDITORIAL ANGLE
“The iPhone moment for coding agents: why approvals are the new UI.” Demo a 3-step workflow: start task at desk → approve on phone → review diff later.
Open original source ↗
02Anthropic (engineering/blog)
How Claude Code works in large codebases (agentic search embedding indexes)
WHY IT ENTERED THE RADAR
Anthropic is explicitly arguing that RAG/codebase-embedding indexes become stale at org scale, and that agentic file traversal/grep-style search avoids that failure mode. Also: “harness model” framing (CLAUDE.md, hooks, skills, plugins, MCP, subagents).
SUGGESTED EDITORIAL ANGLE
“Stop asking ‘which model’—start asking ‘which harness’.” Explain the layered setup (CLAUDE.md → hooks → skills → plugins → MCP → subagents) and why it’s the real moat for dev teams.
Open original source ↗
03GitHub repo (Show HN)
whichllm: pick the best local LLM for your hardware (recency + evidence-weighted)
WHY IT ENTERED THE RADAR
The novel bit isn’t “what fits in VRAM” but ranking by merged benchmarks with confidence tags + recency demotion (so 2024 leaderboard artifacts don’t dominate 2026 picks). This is a concrete answer to the “open-source model chaos” problem.
SUGGESTED EDITORIAL ANGLE
“Local LLM shopping is broken—this fixes it.” Frame it as: fit is easy; best is hard. Then explain their scoring philosophy (evidence levels, stale benchmark penalties, MoE active-vs-total params).
Open original source ↗
04Hugging Face model card
Intern-S2-Preview (35B) — scientific multimodal model + “task scaling” + MTP + CoT compression
WHY IT ENTERED THE RADAR
This is an upstream research-y release with a few standout claims:
SUGGESTED EDITORIAL ANGLE
“The next scaling law might be task difficulty, not parameters.” Translate their pipeline into creator terms: better evals + better RL targets + shorter reasoning traces = cheaper inference and better results.
Open original source ↗
05arXiv cs.AI
OpenDeepThink (arXiv) — parallel reasoning with Bradley–Terry aggregation (pairwise comparisons)
WHY IT ENTERED THE RADAR
It’s a clean “breadth scaling” recipe: sample multiple solutions, then rank them via pairwise comparisons aggregated with a Bradley–Terry model (instead of brittle single-judge scoring). They report big gains on Codeforces for Gemini 3.1 Pro.
SUGGESTED EDITORIAL ANGLE
“Why ‘best-of-N’ is evolving into ‘tournament-of-N’.” Explain Bradley–Terry in 60 seconds and pitch it as a general pattern for agent planners: generate → bracket → mutate winners.
Open original source ↗
06arXiv cs.LG (+ code)
Tensor Similarity (arXiv) — weight-based, symmetry-invariant similarity for mechanistic interpretability
WHY IT ENTERED THE RADAR
Most “are these two networks doing the same thing?” measures are either behavior-only (OOD-blind) or basis-dependent (break under weight-space symmetries). This proposes a symmetry-invariant metric for tensor-based models, with empirical tracking on dynamics like grokking/backdoors.
SUGGESTED EDITORIAL ANGLE
“A new lens for catching ‘same model, different disguise’ (and possibly backdoors).” Practical framing: security + interpretability folks want algebraic tools, not just eval prompts.
Open original source ↗
07r/MachineLearning (points to a moderator thread)
arXiv policy enforcement: 1-year ban for “incontrovertible evidence” of unchecked LLM output
WHY IT ENTERED THE RADAR
This will change incentives and workflows for authors using LLMs: citation verification and “LLM meta-comments” become compliance landmines. It’s also a quiet signal that venues are starting to treat “LLM slop” as scientific misconduct-adjacent.
SUGGESTED EDITORIAL ANGLE
“The new academic AI rule: you can use LLMs, but you can’t outsource responsibility.” Give a checklist: reference validation, remove template text, regenerate tables with real numbers, etc.
Open original source ↗

PROMPT.md

I want to analyze this edition of The RegusciLabs Pulse:
The Pulse — May 15, 2026
https://reguscilabs.com/en/blog/pulse/2026-05-15

SIGNALS
1. Codex is now in the ChatGPT mobile app (remote/relay + approvals)
Source: OpenAI (product post)
Original link: https://openai.com/index/work-with-codex-from-anywhere/
Why it matters: This is the “agent era” UX shift: long-running work needs lightweight human checkpoints (approve, redirect, clarify) from anywhere. The key detail is the secure relay model: work stays on your machine, state syncs to phone (diffs/tests/screens/terminal).
Editorial context: “The iPhone moment for coding agents: why approvals are the new UI.” Demo a 3-step workflow: start task at desk → approve on phone → review diff later.

2. How Claude Code works in large codebases (agentic search  embedding indexes)
Source: Anthropic (engineering/blog)
Original link: https://claude.com/blog/how-claude-code-works-in-large-codebases-best-practices-and-where-to-start
Why it matters: Anthropic is explicitly arguing that RAG/codebase-embedding indexes become stale at org scale, and that agentic file traversal/grep-style search avoids that failure mode. Also: “harness  model” framing (CLAUDE.md, hooks, skills, plugins, MCP, subagents).
Editorial context: “Stop asking ‘which model’—start asking ‘which harness’.” Explain the layered setup (CLAUDE.md → hooks → skills → plugins → MCP → subagents) and why it’s the real moat for dev teams.

3. whichllm: pick the best local LLM for your hardware (recency + evidence-weighted)
Source: GitHub repo (Show HN)
Original link: https://github.com/Andyyyy64/whichllm
Why it matters: The novel bit isn’t “what fits in VRAM” but ranking by merged benchmarks with confidence tags + recency demotion (so 2024 leaderboard artifacts don’t dominate 2026 picks). This is a concrete answer to the “open-source model chaos” problem.
Editorial context: “Local LLM shopping is broken—this fixes it.” Frame it as: fit is easy; best is hard. Then explain their scoring philosophy (evidence levels, stale benchmark penalties, MoE active-vs-total params).

4. Intern-S2-Preview (35B) — scientific multimodal model + “task scaling” + MTP + CoT compression
Source: Hugging Face model card
Original link: https://huggingface.co/internlm/Intern-S2-Preview
Why it matters: This is an upstream research-y release with a few standout claims:
Editorial context: “The next scaling law might be task difficulty, not parameters.” Translate their pipeline into creator terms: better evals + better RL targets + shorter reasoning traces = cheaper inference and better results.

5. OpenDeepThink (arXiv) — parallel reasoning with Bradley–Terry aggregation (pairwise comparisons)
Source: arXiv cs.AI
Original link: https://arxiv.org/abs/2605.15177
Why it matters: It’s a clean “breadth scaling” recipe: sample multiple solutions, then rank them via pairwise comparisons aggregated with a Bradley–Terry model (instead of brittle single-judge scoring). They report big gains on Codeforces for Gemini 3.1 Pro.
Editorial context: “Why ‘best-of-N’ is evolving into ‘tournament-of-N’.” Explain Bradley–Terry in 60 seconds and pitch it as a general pattern for agent planners: generate → bracket → mutate winners.

6. Tensor Similarity (arXiv) — weight-based, symmetry-invariant similarity for mechanistic interpretability
Source: arXiv cs.LG (+ code)
Original link: https://arxiv.org/abs/2605.15183
Why it matters: Most “are these two networks doing the same thing?” measures are either behavior-only (OOD-blind) or basis-dependent (break under weight-space symmetries). This proposes a symmetry-invariant metric for tensor-based models, with empirical tracking on dynamics like grokking/backdoors.
Editorial context: “A new lens for catching ‘same model, different disguise’ (and possibly backdoors).” Practical framing: security + interpretability folks want algebraic tools, not just eval prompts.

7. arXiv policy enforcement: 1-year ban for “incontrovertible evidence” of unchecked LLM output
Source: r/MachineLearning (points to a moderator thread)
Original link: https://www.reddit.com/r/MachineLearning/comments/1tdje2d/arxiv_implements_1year_ban_for_papers_containing/
Why it matters: This will change incentives and workflows for authors using LLMs: citation verification and “LLM meta-comments” become compliance landmines. It’s also a quiet signal that venues are starting to treat “LLM slop” as scientific misconduct-adjacent.
Editorial context: “The new academic AI rule: you can use LLMs, but you can’t outsource responsibility.” Give a checklist: reference validation, remove template text, regenerate tables with real numbers, etc.

Help me:
1. Summarize the three most relevant signals.
2. Separate verified facts, provider claims, and editorial inferences.
3. Explain what could change for my company, team, or role.
4. Suggest three concrete actions and one question we should investigate.
5. Cite the original sources and flag any uncertainty.

Before answering, ask about my role, industry, and objective so you can tailor the analysis.

Codex is now in the ChatGPT mobile app (remote/relay + approvals)

How Claude Code works in large codebases (agentic search embedding indexes)

whichllm: pick the best local LLM for your hardware (recency + evidence-weighted)

Intern-S2-Preview (35B) — scientific multimodal model + “task scaling” + MTP + CoT compression

OpenDeepThink (arXiv) — parallel reasoning with Bradley–Terry aggregation (pairwise comparisons)

Tensor Similarity (arXiv) — weight-based, symmetry-invariant similarity for mechanistic interpretability

arXiv policy enforcement: 1-year ban for “incontrovertible evidence” of unchecked LLM output

Continue the analysis where you already work.