Topic
Agents, context engineering, harness design, MCP, evaluation, token efficiency, and AI-assisted engineering workflows.
Good entry points for this topic before browsing the full archive.
Why AI coding assistant spend needs cloud-style FinOps controls before agent loops, context growth, and workspace credits become a surprise bill.
Why the real engineering surface around agents is the harness of tools, scripts, context, review, and telemetry.
AI coding agents work better when voice, clipboard, screenshots, and MCP tools reduce context friction.
L2 and L3 posts with architecture, reliability, and tradeoff detail.
Evaluating the architectural tradeoffs between turnkey AI coding tools and building an internal AI gateway — with design options, failure modes, and implementation guidance.
How to govern LLM API spend using centralized gateways without slowing down developer velocity, drawing on established cloud cost control patterns.
Why AI coding assistant spend needs cloud-style FinOps controls before agent loops, context growth, and workspace credits become a surprise bill.
AI coding agents work better when voice, clipboard, screenshots, and MCP tools reduce context friction.
An operational playbook for triaging and containing LLM token spend spikes — from alert fire to root cause within 30 minutes.
The highest-starred new open-source projects in April 2026 targeting production-scale AI agent memory, protocol enforcement, and Postgres environment management — what breaks when agents leave single-developer scope.
Token spend behaves differently from compute and storage — it scales with usage and prompt design. Treating it like an engineering cost line, the way you treat a database bill, is how you bring it under control.
Evaluating the architectural tradeoffs between turnkey AI coding tools and building an internal AI gateway — with design options, failure modes, and implementation guidance.
How to govern LLM API spend using centralized gateways without slowing down developer velocity, drawing on established cloud cost control patterns.
Why AI coding assistant spend needs cloud-style FinOps controls before agent loops, context growth, and workspace credits become a surprise bill.
AI coding agents work better when voice, clipboard, screenshots, and MCP tools reduce context friction.
An operational playbook for triaging and containing LLM token spend spikes — from alert fire to root cause within 30 minutes.
Token spend behaves differently from compute and storage — it scales with usage and prompt design. Treating it like an engineering cost line, the way you treat a database bill, is how you bring it under control.
Evaluating the architectural tradeoffs between turnkey AI coding tools and building an internal AI gateway — with design options, failure modes, and implementation guidance.
How to govern LLM API spend using centralized gateways without slowing down developer velocity, drawing on established cloud cost control patterns.
Why AI coding assistant spend needs cloud-style FinOps controls before agent loops, context growth, and workspace credits become a surprise bill.
AI coding agents work better when voice, clipboard, screenshots, and MCP tools reduce context friction.
An operational playbook for triaging and containing LLM token spend spikes — from alert fire to root cause within 30 minutes.
The highest-starred new open-source projects in April 2026 targeting production-scale AI agent memory, protocol enforcement, and Postgres environment management — what breaks when agents leave single-developer scope.
The definitive 2026 reference architecture for autonomous database operations, from detection to multi-agent diagnosis to human-in-the-loop remediation.
The highest-starred new open-source projects in April 2026 relevant to database engineering, infrastructure, and AI tooling — focused on eliminating manual context re-injection across system design, platform automation, and AI memory.
How to combine semantic routing, structured context pruning, and prompt caching to reduce production LLM API costs without degrading application quality.
Why treating AI assistant seats like standard SaaS licenses obscures their true infrastructure cost profile, and how to measure ROI using cloud compute parallels.
How to implement token quotas, chargebacks, and spend controls for AI engineering teams, drawing parallels from cloud database cost management.
Six open-source projects from Q1 2026 that converged on eliminating the manual scaffolding between AI agents and production infrastructure: context management, local cloud testing, and vector retrieval.
Three components AI teams still build by hand — task decomposition graphs, persistent agent workspaces, and path-scored retrieval — each got a breakout open-source release in March 2026 that replaces custom wiring with library calls.
Agentic AI systems can quietly accumulate massive API bills due to compounding context windows, retry loops, and unconstrained workspace parsing.
Practical strategies for managing OpenAI Codex API consumption, workspace credits, and governance across your organization.
A deep dive into model routing rules, context pruning with Graphify, and governing agent API spend.
February 2026's highest-starred new open-source projects connecting AI agents to local infrastructure, Kubernetes clusters, and structured data without cloud API dependencies.
Why traditional SaaS spend models fail for agentic AI, and how platform teams are treating LLM compute like database provisioned IOPS.
The highest-starred new open-source projects in February 2026 — agent-native LLM routing, free AWS local emulation, and cross-platform semantic memory for AI coding agents.
How the Model Context Protocol (MCP) became the networking layer for AI agents, and why monitoring these connections is critical for enterprise security.
The highest-starred new open-source projects in February 2026 — eliminating the context tax that slows AI-assisted code review, infrastructure generation, and database operations.
Why agent harnesses become stale when they overfit today's model weaknesses instead of stable execution contracts.
A reference pattern for keeping large database outputs out of model context by using scripts that summarize evidence before the agent sees it.
Why production agents need discoverable tools and context budgets instead of one giant always-loaded MCP surface.
How to design agent tool surfaces that preserve context budget for reasoning instead of wasting it on tool metadata and raw output.
A reference architecture for making logs, metrics, test output, schemas, and deployment history readable by coding agents.
A practical review pattern where one agent creates a change and specialized agents review risk, rollback, security, and observability.
Why the real engineering surface around agents is the harness of tools, scripts, context, review, and telemetry.
Nine breakout repos across four themes — MCP protocol adoption, agent memory infrastructure, AI-native platform ops, and database automation — that eliminated the hand-built glue code between AI agents and production systems.
Why agentic coding shifts senior engineering work toward decomposition, verification, and operating-model design.
Why monitoring autonomous SRE agents requires tracking tool-call hallucinations, context window saturation, and recursive retry loops, rather than just basic CPU metrics.
A governance model for deciding which database and cloud agent actions require approval and which can run automatically.
Six open-source projects that collectively delivered the missing infrastructure layer for production AI agents: secure sandboxes, deployment platforms, persistent memory, token-efficient encoding, and AI-native storage.
A field note on why agent evaluation should measure verified state changes instead of polished reasoning traces.
Why database and cloud teams need agent eval harnesses that grade outcomes, not persuasive transcripts.
A practical mental model for how coding agents plan, call tools, observe results, and complete infrastructure work without treating the model response as the whole system.
If you log everything and monitor every dimension, your observability bill will eventually exceed your database infrastructure bill. Here is how to fix it.
Three November 2025 breakout projects eliminate the manual infrastructure build that blocks teams from running AI agents in production — covering agent backends, Kubernetes LLM inference, and SQL-driven knowledge retrieval.
October's memory and retrieval breakouts: a structured agent memory framework with benchmarks, a self-hosted cognitive memory engine, and sub-10ms semantic search without a vector database cluster.
Three October breakouts targeting LLM prompt verbosity, parallel agent orchestration, and fragmented hybrid search stacks — all reducing coordination overhead in AI engineering.
Six open-source tools from Q3 2025 that closed the infrastructure gaps blocking AI agents in production: persistent memory, intelligent model routing, and natural language database access.
When AI agents accelerate platform operations versus when they generate unreviewed changes — the permission boundary and audit design that separates useful from risky.
How to connect engineering telemetry with cost telemetry to achieve granular cloud unit economics using FinOps principles and FOCUS standards.
Six Q2 2025 open-source breakouts that closed the gap between AI agents and engineering infrastructure across system design, platform operations, and database tooling.
Self-hosted AI agents become useful only when model quality, tool access, memory, and setup completeness line up.
Running many coding agents only works when git isolation, shared memory, permissions, hooks, and verification are designed as a system.
Three May 2025 open-source projects eliminate the manual scaffolding that blocks every AI agent deployment: orchestration glue, vector database setup, and MCP gateway configuration.
Building a database operations agent requires a workflow framework, production observability, and scalable inference — April 2025 shipped open-source solutions for all three layers simultaneously.
Replacing the translation overhead between business questions and SQL queries requires an architecture that bridges LLM intent parsing with strict execution validation and schema retrieval.
How autonomous AI agents like Bits AI SRE are shifting the database incident workflow from manual dashboard hunting to conversational investigation.
The highest-starred new open-source projects in February 2025 eliminating manual iteration in prompt engineering, infrastructure monitoring, and private data retrieval.
Production AI agent selection should measure quality, retries, tokens, latency, and verification cost per completed task.
How generative AI tools like CloudWatch Investigations shift the operational burden from reading raw dashboards to validating machine-generated hypotheses.
Nine breakout repositories across three themes — agents that operated computers, RAG that grew a graph spine, and databases that finally spoke natively to LLMs — define what actually shifted in the engineering stack in 2024.
Codex mobile turns local agents into remote workflows, but production value depends on deployment, access control, and observability.
The default AI coding setup loads everything into one always-on instruction file. The production alternative is a layered architecture — project memory, task skills, commands, and MCP servers each with a defined load boundary — so context bloat and stale policy stop reaching the model on every turn.
Prompt-level guardrails fail open when the agent misinterprets context. The only boundary that mechanically rejects destructive SQL is the database — dedicated read-only roles, sanitized view schemas, and a network path that application credentials never touch.
Giving an AI coding agent your application's Postgres credentials is the default mistake — the agent inherits every permission the app has. Database-enforced read-only roles, replica routing, query limits, and project-scoped MCP config are the alternative that actually fails closed.
A hosted AI app generator fails when the mobile chat becomes the platform — API keys end up in binaries, execution state blurs with chat, and previews break without artifact handoff. The control-plane architecture that keeps these concerns separated.
Production AI agents work best when coding, files, tools, and knowledge workflows share one governed execution model.
Granting an autonomous AI agent access to your database breaks every assumption of traditional RBAC. How to secure databases against unpredictable, unbounded AI queries.
Stripe's Minions system runs over a thousand AI code reviews weekly using a fork of an open-source agent. The reliability comes from the deterministic pipeline around it, not the model inside.
A production-minded workflow for running Cursor and Aider together without locking engineering practice to one agent.
A practical workflow for separating planning from execution, checkpointing progress in GitHub issues, and resuming multi-phase LLM implementation without context collapse.
Google Research found that independent parallel agents amplify errors 17x compared to centralized orchestrator topologies. Adding more agents to a system with a shared context defect makes it worse, not more resilient.
Chat is request-response; agents are task systems that plan, call tools, iterate, and stop when done. The minimum architecture — loop, tools, bounded memory, stopping conditions — required to make the transition from chat reliable.
Paperclip's zero-human orchestration model — goal-directed agent teams instead of task-by-task prompting — and what that architecture requires from the software and data systems beneath it.
A practical control plane for keeping AI coding sessions on track: separate planning from execution, validate deterministically, reset context aggressively, and isolate parallel work.