← Latest Update

Agent Infrastructure: Harnesses Outside Sandboxes, Gateways & Specs

The Agent Harness Belongs Outside the Sandbox. Andrea Luzzardi argues the agent harness should live outside sandboxes to protect credentials, enable durable multi-user sessions, and treat sandboxes as disposable compute. For outcome engineers this mandates separating orchestration and secret handling from ephemeral execution to enable durable sessions and a smaller, safer attack surface (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 moves agent-level policy, access control, and telemetry into a centralized gate—expect gateways to become standard infra for production agent fleets (Principles 15 & 10).

Specsmaxxing — On overcoming AI psychosis, and why I write specs in YAML. Acai.sh presents YAML-first, spec-driven tooling to keep AI agents on-task and preserve context across sessions. Outcome engineers should use spec-first pipelines to codify intent, reduce hallucinations, and make agent behavior repeatable and auditable (Principles 06 & 13).

Building in Public With Paperclip. Paperclip demonstrates turning AI agents into a mini operating company that buys domains, deploys sites, and ships RunnerDock in public. Treat this as an orchestration pattern for agentic delivery lanes—use observable artifacts and live deployments to prove outcomes and synchronize teams (Principles 09 & 08).

DeepClaude – Claude Code agent loop with DeepSeek V4 Pro, 17x cheaper. This repo runs Claude Code on DeepSeek V4 Pro and uses context caching to reduce autonomous coding costs up to 17x. It’s a concrete cost-and-architecture play for agent backends—mix cheaper models with caching and loop control to make continuous agent workflows economically sustainable (Principles 12 & 06).