Agent Markup Language lets developers compose AI agents as reusable JSX components

·1 views

A new open-source SDK called Agent Markup Language (AML) enables TypeScript developers to build multi-agent AI workflows using a JSX-based component model similar to React. Instead of manually managing thread orchestration, prompt assembly, and execution order, developers define specialist agents as composable functions with props and children. Child agents run in sequence, with their outputs automatically injected into parent agent prompts, reducing boilerplate glue code. AML integrates with OpenAI's Codex SDK and supports conditional logic, nested children, and session-based follow-up queries. The approach aims to make complex AI pipelines easier to read, maintain, and reuse across projects.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Server-Side WebAssembly Gains Ground as Lightweight Alternative to Containers

WebAssembly, traditionally a browser-based binary format, is increasingly being deployed on server infrastructure through a standard called WASI, which allows Wasm programs to safely interact with host system resources. Unlike traditional containers that bundle operating system files and can occupy hundreds of megabytes, WebAssembly binaries contain only compiled application logic, often weighing just a few megabytes and starting in under a millisecond. A software engineer experimenting with Rust-based backend services on a server-side Wasm runtime found the cold-start performance significantly better than conventional approaches, enabling hundreds of isolated tasks on modest hardware. However, the ecosystem remains immature, with debugging tools, database drivers, and telemetry libraries still being adapted for the Wasm environment. Experts suggest WebAssembly is unlikely to replace containers across all enterprise workloads but shows strong promise for high-density, low-latency, and event-driven use cases.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Mozilla Contributor Fixes 5-Year-Old Firefox Bug That Trapped Amazon in Top Sites

A Mozilla open-source contributor has resolved a long-standing Firefox bug, first reported on Bugzilla, where users were unable to remove Amazon.com from the browser's New Tab Top Sites grid despite repeated attempts. The bug stemmed from how Firefox categorizes Top Sites — distinguishing between visited history, pinned sites, and default curated tiles — with Amazon persisting as a default entry regardless of user action. The contributor initially proposed blocking the URL upon deletion, but Mozilla engineers pushed back, noting this would silently alter user settings without clear consent. Guided by a second reviewer, the contributor identified the root cause through targeted logging and implemented a more precise fix that respects user intent. The resolution was submitted as part of DEV Community's Summer Bug Smash challenge, powered by Sentry.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

CamBridge streams Mac webcam to iOS Simulator for real camera testing

CamBridge is a new open-source tool that solves the lack of real camera hardware in the iOS Simulator by streaming a Mac's webcam feed over localhost. It consists of two components: a Mac menu bar app that captures and broadcasts JPEG frames via TCP, and a Swift package called CamBridgeKit that provides a drop-in replacement for AVCaptureSession. Developers can use the same code path for both the Simulator and physical devices, with no simulator-specific branching required. The tool is MIT licensed and available on GitHub, with Android Emulator support already planned as the next milestone.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

A Practical 90-Day Reliability Roadmap for Newly Formed SRE Teams

Site reliability engineer Dr. Samson Tanimawo has outlined a structured 90-day plan designed to help new SRE teams establish credibility and build lasting reliability practices. The plan begins with observation — studying existing systems, reviewing post-mortems, and identifying the top five reliability problems ranked by engineering time lost per week. Early weeks focus on quick, visible wins such as removing flaky alerts or automating repetitive runbooks, while avoiding large overhauls like rewriting deployment pipelines. Mid-phase work introduces foundational elements including SLOs, error budget dashboards, and a lightweight weekly reliability review. The final phase aims to institutionalize ongoing programs — such as post-mortem tracking and quarterly leadership reviews — so reliability work continues even when team members are unavailable.

0 comments Read more at DEV Community