AI Agents & Automation: RAG, Workflows & Guides

Arriving July 9, just two and a half months after April 2026's GPT-5.5, GPT-5.6 is not merely a performance bump — the biggest change is the reorganization from a single flagship into a three-model lineup: Luna/Terra/Sol. What matters most to many GPT-5.5 users is that the mid-tier Terra delivers GPT-5.5-class quality at a far lower price: it launched at half price, and the July 30, 2026 price cut took it to 40% of GPT-5.5's unit price ($2/$12). For those wanting more performance there is the top-tier Sol (same $5/$30, with SWE-Bench Pro rising 58.6→64.6% per OpenAI); for those wanting lower costs there is Terra. This article lays out, based on official announcements and independent analysis, what the three-model shift means, a spec-at-a-glance table, Terra's price-to-performance, generational benchmark gains (same-metric SWE-Bench Pro +6pt; TerminalBench versions differ between announcements, so compare within one table; general-reasoning gains are small), 5.6's new features (Programmatic Tool Calling, max effort, ChatGPT Work, GPT-Live, GitHub Copilot support), real cost (roughly $1,100→$440 for 100M input/20M output a month), and which model you should migrate to (cut the bill by 60% with Terra, then move only performance-critical work to Sol).

An in-depth comparison of OpenAI's then-flagship GPT-5.6 Sol (July 9) and Claude Fable 5 (June 9), which Anthropic positioned at launch as "the most powerful model it has ever made generally available." Where the Opus 4.8 matchup was a head-to-head in the same price tier, this one turns on a cost-versus-capability trade-off: "the half-price all-rounder Sol ($5/$30)" against "the twice-as-expensive but top-tier Fable 5 ($10/$50)." On production-grade coding's SWE-Bench Pro, Fable 5's 80.0% pulls more than 15 points ahead of Sol's 64.6% in OpenAI's table, which lists both — a gap wider than in the Opus 4.8 matchup. Fable 5 also stays focused across millions of tokens and, per Anthropic, works autonomously for longer than any previous Claude, with Stripe finishing a 50-million-line Ruby migration in a single day as its home-turf "follow-through." Sol, meanwhile, leads on terminal operation (TerminalBench 2.1 88.8% vs Fable 83.1%), Agents' Last Exam (53.6 vs 40.5), and Coding Agent Index (80 vs 77.2), plus best value with half the price and +54% token efficiency. This article covers the spec cheat sheet, benchmark details, the "undisclosed-benchmark problem" (metrics missing from OpenAI's table, and OpenAI questioning SWE-bench Pro itself), long-running autonomy, real cost (viewed per completed task), a strengths-and-weaknesses map, and how to choose by use case — all grounded in official and independent benchmarks.

An in-depth comparison of the two AI-coding giants as of July 2026, Claude Opus 4.8 (May 28) and GPT-5.6's top-tier Sol (July 9). Their strengths are almost opposite: Sol leads in terminal operation and overall agentic capability (TerminalBench 2.1 88.8% vs Opus 78.9%, Agents' Last Exam 53.6, Coding Agent Index 80), while Opus 4.8 leads in production-grade coding (SWE-bench Pro 69.2% vs Sol 64.6%), and foregrounds honesty (about 4x less likely to let flaws in its own code slip by; fails to flag important failures only 3.7% of the time). GPQA Diamond and FrontierMath, once reported as undisclosed, are in OpenAI's evaluation table with Sol ahead (as it is on GraphWalks 1M), and on SWE-bench Pro even OpenAI's own table puts Opus ahead, so in coding's heartland Opus has the edge. We cover the spec table, benchmark details, the undisclosed-benchmark problem, real cost ($25 vs $30 unit price vs +54% token efficiency), a strengths/weaknesses map, use-case picks, and a dual-vendor strategy.

OpenAI made GPT-5.6 generally available on July 9, 2026, replacing the old "standard + Pro" structure with a three-model lineup: Luna (fast, low-cost, $0.20/$1.20), Terra (balanced, $2/$12, GPT-5.5-class at 40% of Sol's unit price), and Sol (flagship, $5/$30) — prices as revised on July 30, 2026. Sol takes first place on Agents' Last Exam (53.6) and the Coding Agent Index (80), and its 88.8% on TerminalBench 2.1 beats Claude Fable 5 (83.1%) — yet on production-grade SWE-Bench Pro, Claude Fable 5 leads decisively at 80.0% against Sol's 64.6%. This article covers the differences between the three models, pricing, benchmarks, new features (Programmatic Tool Calling, ChatGPT Work, the full-duplex GPT-Live voice model), availability by ChatGPT plan, a comparison with Claude (Fable 5 / Opus 4.8), and how to choose by use case — all grounded in OpenAI's official announcement and independent benchmarks.

You built on OpenAI, then wanted to try Claude and compare Gemini — and lost hours to the different SDKs, formats, and error handling per provider. An LLM gateway (AI gateway / LLM proxy) is a relay you slot between your app and the providers: it exposes one OpenAI-compatible API to reach every model and takes over the cross-cutting chores — fallback, cost tracking, virtual keys, caching, rate limiting, and observability. This guide covers why you need one, what a gateway really is, the three types (self-hosted proxy = LiteLLM / hosted = OpenRouter / SDK = Vercel AI SDK), how to choose among LiteLLM, OpenRouter, and the Vercel AI SDK, minimal setup code that only swaps the endpoint, and the limits — a hop of latency, the gateway as a new failure point, fees (OpenRouter charges 5.5% on purchases), feature loss, and privacy.

After you build an AI agent, you always hit the same wall: "OK, but is it actually working?" The mechanism for deciding whether a prompt or model change made things better or worse with data instead of gut feel is evals. LLMs produce different output every time for the same input, so exact-match unit tests don't fit. This article centers on the steps for actually building and running them, covering five ways to measure quality (① ground-truth matching ② rule-based checks ③ LLM-as-judge ④ regression testing ⑤ production monitoring), agent-specific evaluation (task success rate, correct tool calls, trajectory, cost), how to start small from 20 failure examples, common pitfalls, and key tools (Anthropic Console/Evals, OpenAI Evals, LangSmith, Langfuse, Ragas) — written for practitioners.

The perennial automation question: "AI agents or RPA?" The answer isn't either/or — choose by role, and the 2026 winning pattern is a hybrid of both. RPA is deterministic "hands" that run a fixed procedure fast and precisely (but break when the screen/spec changes); an AI agent is a probabilistic "brain" that reads the situation and decides (strong on ambiguity and exceptions, but not identical every time). This article covers the operating-principle difference, a comparison table (the reproducibility-vs-resilience trade-off), how to choose (the axis is "can it be fully written as rules?" — yes → RPA, judgment you can't write → AI agent), the 2026 trend (RPA leaders UiPath, Automation Anywhere, Blue Prism going agentic — convergence; the question is no longer "which one" but "where should the reasoning live" = orchestration-first), and the practical answer: a hybrid where the brain (AI agent) handles judgment/orchestration and the hands (RPA) run deterministic execution — don't put an agent where determinism is required, and pair delegated judgment with guardrails and human approval. Based on vendors' official information, with an FAQ.

Can you hand AWS operations to AI? In 2026 you can delegate a lot. AWS itself ships Amazon Q Developer and the Agent Toolkit for AWS (May 2026 — 40+ agent skills + a managed AWS MCP Server + plugins), so AI can reach from IaC generation to resource operations. This guide frames "delegating" in three levels (① code/IaC generation, ② read-oriented ops/investigation, ③ an autonomous agent that actually operates AWS), covers the main tools (Amazon Q Developer, Agent Toolkit, AWS MCP Server, Terraform MCP, Bedrock AgentCore) — including the bring-your-own route of giving Claude Code or Codex the AWS CLI to run "aws" from the shell — the upside (fast IaC, automated triage, cost-optimization ideas, democratized knowledge), and then the real point, the downsides (IAM permission sprawl, over-privilege as a blast-radius amplifier for mistakes/prompt injection, permissions that outlive the task, cost runaway — with real prod-DB-deletion incidents in 2025-26), based on AWS official and security-vendor sources. The key twist: the question isn't "can it?" but "how do you delegate without a runaway or bill explosion" — and AWS itself building IAM guardrails, CloudTrail audit, and sandboxing into the Agent Toolkit shows the shape of the answer. Includes the five principles (least-privilege IAM, human approval for destructive ops, observability, JIT short-lived credentials, sandboxing) and an FAQ.

The first hurdle in building an AI agent into real work is "which framework to build it on." From a developer and tech-selector viewpoint, this article compares six major frameworks — LangGraph, CrewAI, AutoGen (folded into the Microsoft Agent Framework, GA April 2026), OpenAI Agents SDK, Google ADK, and Claude Agent SDK — by orchestration approach (directed graph / role-based crew / conversational GroupChat / handoffs / hierarchical tree / autonomous tool loop), language, learning curve, control, production maturity, token cost, and best-fit use case. The key caveat: the framework that is "fastest to prototype" (CrewAI) can be the most expensive in production — around 3× the tokens (41k vs LangGraph 18.5k in one benchmark) and non-deterministic, making it a poor fit for finance and healthcare. It also explains how 2026 brought interoperability via MCP (tools) and A2A (agent-to-agent), so agents from different frameworks can now work together and lock-in has faded. Includes a use-case selection guide and FAQ.

In "How to build a multi-agent system" we said to instrument every handoff before adding agents; the tech that powers that instrumentation in production is AI observability. It makes visible what LLMs and agents actually do in production (which model with what prompt, which tools and searches, what was returned, and how long and how much it cost) so you can trace back to the cause. The decisive difference from ordinary app monitoring: AI can return 200 OK in 50ms and still confidently hallucinate, so most AI failures are quality failures (hallucination, weak retrieval, unsafe answers, incomplete tasks, poor tool use, post-prompt-change regressions), not infrastructure failures. Observability rests on three pillars: traces (one request as a tree of spans showing LLM calls, tools, retrieval, reasoning chains; the star of AI observation), metrics (latency, cost, tokens, error rate, throughput), and logs (per-event detail). The industry standard OpenTelemetry GenAI conventions capture prompts, responses, token usage, and tool/agent calls in a vendor-neutral schema feedable into Datadog/Grafana. The most-confused distinction is observability vs evaluation (evals): observability shows what happened (easy to measure, but cannot tell if the answer is correct), while evals measure whether the answer is good (accuracy, groundedness, safety) and require explicit evaluation. Because cost and latency are easy to measure but answer quality is not, 2026 tools combine trace display with output scoring and degradation alerts. Metrics split into operational (cost, latency, tokens, error rate) and quality (hallucination, groundedness/faithfulness which is most critical for RAG, safety, task completion), with hallucination detection via LLM-as-a-judge, semantic similarity, and groundedness scores. Major tools: LangSmith (LangChain), Langfuse (open-source self-host), Arize Phoenix (RAG debugging), MLflow (lifecycle), AgentOps (agents), and OpenTelemetry (the standard). Start by capturing traces (OpenTelemetry-compliant), visualize operational metrics, then connect evals before shipping. For multi-agent systems observation is essential since failures hide in multi-step chains visible only in a full-session trace. Observe plus evaluate is what makes AI production-grade. Figures and traits are quoted from public materials, directional.

The hands-on follow-up to "What is a multi-agent system?". The core rule: build with a single agent first and add agents minimally only after hitting a limit (a Google Research study found every multi-agent setup 39–70% worse on a strictly sequential task, and Anthropic reports multi-agent systems use about 15× the tokens of a chat). The base shape is the supervisor pattern: subagents in the Claude Agent SDK, agents as tools in the OpenAI Agents SDK. Beyond the 5 steps (decompose, define workers, design the supervisor, handoffs, measure), it gives minimal code for both SDKs that follows their official docs (one supervisor plus a researcher and a reviewer), how to restrict each role's tools, three layers of caps (maxTurns, max_turns, spend), when to use handoffs instead, good and bad role splits, and failures Anthropic actually hit (50 subagents for a simple query, duplicated research) with fixes.

Now that AI agents are commonplace, the next challenge is how to make agents collaborate with each other. If MCP connects an agent to its tools, A2A (Agent2Agent) connects an agent to another agent — an open standard for AIs built on different vendors and frameworks to discover, communicate, and cooperate through a common convention. Google released it in April 2025, donated it to the Linux Foundation that June, and it reached v1.0 in 2026. This beginner guide covers what A2A is (the etiquette of a business partnership analogy), why it's needed (specialized agents relay work — a planning agent to a hotel-booking agent to a payment agent), how it differs from MCP (MCP is vertical, agent ↔ tools; A2A is horizontal, agent ↔ agent; stacking both is the standard two-layer setup), how it works (an Agent Card — a JSON "business card" at /.well-known/agent-card.json — is used to discover capabilities, then a Task carries the request through states like working, input-required, and completed, and an Artifact returns the result, all over HTTP, Server-Sent Events, and JSON-RPC 2.0, with agents keeping their internals hidden), and where it stands and implementation (as of April 2026, 150+ supporting organizations, 22,000+ GitHub stars, SDKs in five languages — Python, JavaScript, Java, Go, .NET — with Microsoft, Salesforce, SAP, and ServiceNow involved). The mnemonic: connect to tools = MCP, connect to peers = A2A.