← Latest Update

Agent infrastructure: harnesses, memory, local UIs, and gateways

I built the Playwright for desktop apps — 80% token savings. The project exposes native accessibility trees to AI agents, enabling skeleton traversal and deterministic refs that cut token usage by up to 80%. That reduces context costs and makes desktop UIs a legible, efficient surface for agent actions (Principles 06 & 11).

Inside OpenSearch’s bid to become the default AI data layer. OpenSearch 3.5–3.6 adds compressed vector search, neural sparse retrieval, and native agent memory APIs to function as an AI data layer. That gives outcome engineers a scalable, on-prem-friendly memory and retrieval stack to power agent state and long-term context (Principles 06 & 11).

Flue is a TypeScript framework for building the next generation of agents. Flue supplies a TypeScript agent harness and sandbox for building, running, and deploying autonomous agents. That provides an engineering scaffold for safe iteration and deployment of multi-agent workflows (Principles 06 & 07).

The Agent Harness Belongs Outside the Sandbox. The author argues moving the harness off the sandbox to protect credentials, enable durable multi-user sessions, and treat sandboxes as disposable compute. That operational split clarifies control plane vs execution plane and prevents common credential and durability failures (Principles 07 & 03).

Palo Alto Networks to acquire Portkey, AI gateway for securing autonomous agents (valued $120–140M). Palo Alto is buying Portkey to integrate an AI gateway that manages and secures autonomous agents. That signals gateways becoming core security infrastructure for policy enforcement, telemetry, and audit in production agent fleets (Principles 10, 15 & 14).