Urgent.News

What's breaking now, across thousands of outlets.

Tech

When one agent should become several specialists

Keep one agent on the whole task until the work breaks into specialties that need separate context and instructions. Mikiko Chandrasekhar put a practical size on that split: small agents equipped for one to three tasks, each judged on criteria for its own skill set. After the split, log every handoff so you can see who was called, what crossed between them, and what came back. Mikiko…

When a single agent is asked to perform multiple tasks, it is better to split it into several specialized agents. Mikiko Chandrasekhar, Staff Developer Advocate at MongoDB, suggests keeping one agent on a task until it becomes too complex for a single agent to handle. Each specialized agent should be equipped for a small slice of the task, with its own criteria for performance.

Once the task is split, log every handoff between agents to track who was called, what crossed between them, and what came back. This allows for easier debugging and inspection of the system's components. Mikiko treats agents as software products, similar to how software engineering and MLOps practices are handled. She recommends writing different checks for each skill of an agent and comparing them against the job's criteria.

For coding or copilot-style agents, where the output is code, she suggests measuring signals such as accuracy, runtime efficiency, and acceptance rates. Vibe checks are acceptable up to a point, but quantifiable metrics are necessary for improvement. To make agent-to-agent handoffs observable, log the payload that crosses between agents, along with the final answer.

This creates a view of the agentic graph, showing how agents communicate, data passes between them, and tools are called.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Can a Vibe-Coded Healthcare App Be HIPAA-Compliant?

Vibe coding tools can generate a working healthcare application, but that doesn't mean the application is ready to handle protected health information (PHI).

  • Business Associate Agreements (BAAs) necessary when vendors handle PHI
  • Server-side authorization required to prevent unauthorized access to PHI
  • Patient-level auditability mandatory for tracking PHI access and modifications

DNS Change Audit Logs: 5 Custody Checks for Gaming Company Mail

A gaming company's mail migration needs DNS change auditing that preserves who changed each record in searchable logs. It also has two clocks: the moment an authorized engineer changes the MX records…

  • Gaming company migrating mail system
  • 5 custody checks for DNS changes
  • Separate evidence: application events, zone listings, cutover records

Migrating per-machine keys to floating licensing

A floating license pool looks like a server setting: "allow 25 concurrent users instead of 25 named machines." It is not.

  • Floating license pool allows 25 concurrent users without named machines.
  • Dual-mode SDK reads per-key seat.model claim to transition smoothly.
  • Server reconciles old activations into new pool atomically to maintain capacity.

Arize Phoenix CVE-2026-53998: un fallo de cadena de formato con CVSS 10.0 filtra PHOENIX_SECRET sin iniciar sesión

Un fallo de cadena de formato en la consulta applyChatTemplate de Arize Phoenix (CVE-2026-53998, CVSS 10.0, del 16 de noviembre de 2026) permite a cualquiera que alcance una instalación por defecto…

  • Arize Phoenix vulnerability CVE-2026-53998 due to format string injection
  • Allows unauthorized access to PHOENIXSECRET without login
  • CVSS 10.0 rating classifies as critical threat

How to get a software engineering internship

Software engineering internships are some of the most competitive roles students apply for. Big tech companies get thousands of applications for each opening, and most of them open early.

  • Apply to major tech firms early (July-August), then pursue startups (Feb-April)
  • Develop 1-2 substantial projects, host on GitHub with clear README
  • Practice coding problems (50-100) and verbal explanations, apply to diverse employers

How renaming breaks MVVM Toolkit bindings

A CommunityToolkit.Mvvm view-model is mostly code you never wrote. You declare a field and an attribute; a source generator produces the public property, the PropertyChanged plumbing and the command…

  • MVVM Toolkit binding relies on runtime-generated names
  • String names used in property getters/setters, token names for change notifications
  • Recommended approach: keep public properties/commands, rename everything else

More from Wednesday 18 November →