APC and APX Split Project Context from Runtime to Keep AI Agents Portable

·1 views

APC (Agent Project Context) and APX are two complementary layers designed to make AI agent projects portable without making false assumptions about host machines. APC stores the durable project definition — including agent configs, skills, and commands — inside the repository so it can travel with any clone. APX operates at the runtime level, detecting which AI CLI tools and engines are actually installed on the current machine before executing any agent task. This separation prevents fragile handoffs that occur when a repo assumes specific binaries like Codex or Claude Code are universally available. The design keeps project contracts lean and trustworthy while delegating local capability checks and session tracking entirely to APX.

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)

Developer shrinks 1.1 GB AI image gallery to 30 MB using WebP conversion trick

A developer running a small AI photo-prompt gallery discovered that 1,541 PNG files were consuming 892 MB — about 75% of total storage — simply because the image generator exported lossless PNGs by default instead of a web-friendly format. Converting all images to WebP at quality 82 reduced the total size from 423.7 MB to just 29.8 MB, a 93% reduction, without any visible loss in image quality. Rather than overwriting originals or updating database URLs, the developer generated sibling WebP files and served them via HTML's picture element, ensuring automatic fallback for unsupported browsers and easy rollback. A surprising bug during the process caused images to be double-wrapped in picture tags due to a shortcode running through two content filters, which was fixed by stamping a data attribute on already-processed tags. The project highlighted that format choice, not image dimensions or compression levels, was the primary cause of bloat.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer ports JavaScript glob library Picomatch to Rust, finds it 18x slower

A developer ported Picomatch, a widely used JavaScript glob-matching library, to Rust over 72 hours, pinning the project to a specific upstream commit and building a standalone Rust scanner, compiler, and matcher. Despite passing all 1,977 inherited tests plus 28 native Rust tests, the Rust implementation processed roughly 395,000 matches per second compared to Node's 7.18 million — about 18 times slower. Further differential testing uncovered subtle Unicode compatibility bugs, including edge cases around the Latin long s and the Kelvin sign, which behave differently under JavaScript's legacy versus Unicode-aware case-insensitive regex modes. To address this, the developer derived a complete legacy Canonicalize table for all 65,536 Basic Multilingual Plane code units from Node 24.18.0, generating over 4,700 additional test checks. The project highlights how passing an inherited test suite does not guarantee correctness, particularly when porting code that relies on language-specific runtime behaviors.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Open-Source OWASP-Aligned Web Vulnerability Scanner WebMask

A full-stack developer based in Yerevan has released WebMask, a self-hosted web vulnerability scanner available on GitHub. The tool performs over 43 security checks aligned with common OWASP findings, helping developers identify potential weaknesses in their web applications. WebMask features a React-based admin UI that displays scan results with severity ratings, and is built on a Node, Express, and Vite stack. The project incorporates SSRF-safe design considerations and is intended as a learning tool for application security rather than a replacement for commercial DAST suites.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How ACID Properties in SQL Prevent Incomplete Bank Transactions

Database transactions group multiple operations into a single unit so that all steps either complete together or none take effect. This becomes critical in scenarios like bank transfers, where a system crash mid-operation could deduct funds from one account without crediting the other. To address this, SQL databases rely on ACID properties — Atomicity, Consistency, Isolation, and Durability — which together ensure data integrity. Atomicity, for instance, guarantees that if any part of a transaction fails, all changes are rolled back to the original state. Commands like BEGIN, COMMIT, and ROLLBACK give developers explicit control over when changes are saved or undone.

0 comments Read more at DEV Community