How-Tos & Practical Guides

Cursor just shipped a feature that reframes what a coding AI tool is for. Automations — now rolling out across Cursor accounts — lets you define coding agents that trigger automatically based on events: a new commit, a Slack message, a scheduled timer. You stop prompting. The agents start running. This is the shift from interactive to ambient coding assistance, and it’s a genuinely different paradigm. What Cursor Automations Actually Does Before Automations, Cursor (and every other AI coding tool) was reactive: you opened the editor, asked a question, got a response. Useful, but fundamentally a fancier autocomplete. ...

Google quietly published something very useful on GitHub in early March: gws, a command-line interface for the full Google Workspace API surface. It ships with 100+ pre-built agent skills covering Gmail, Drive, Docs, Calendar, and Chat — and it includes a built-in MCP server that lets AI clients like Claude Desktop, Gemini CLI, and VS Code access your Workspace directly. This is the thing that used to require a custom OAuth flow, API client library setup, and a day of plumbing. Now it’s a CLI install and a config file. ...

OpenAI dropped a significant update on March 5, 2026: GPT-5.4, a model built from the ground up for autonomous agent work. It ships with two things practitioners have been waiting for — native computer-use capabilities and a 1M-token context window in API preview. If you build agents, this changes your architecture options in real ways. What Actually Shipped GPT-5.4 comes in two variants: Standard GPT-5.4 — The default API model with native computer-use support and 1M-token context GPT-5.4 Pro — A higher-performance tier aimed at complex, long-horizon tasks The model is available in ChatGPT, the Codex environment, and the API. Microsoft Foundry integration is also confirmed, meaning enterprise teams using Azure AI Foundry can access it without a separate onboarding. ...

A ZDNET survey of chief data officers finds that 50% of organizations deploying agentic AI cite data quality and retrieval issues as their primary barrier. Executives are responding by increasing data management investment specifically to unblock agent deployments — not as a general data hygiene initiative, but as a direct prerequisite for getting agents into production. If you’re in that 50%, here’s a practical framework for what to actually fix. ...

Researchers at Palo Alto Networks’ Unit 42 have published documentation of real-world indirect prompt injection attacks — and this is one of those security stories that deserves more attention from the AI builder community than it’s currently getting. The attack is conceptually simple and practically dangerous: a malicious actor embeds hidden instructions in a website’s content. When an AI agent browses that page as part of an automated task, it reads the hidden instructions and executes them — without the user ever seeing what happened. ...

LangChain just released something that deserves more attention than it’s getting: a skills system for AI coding agents that nearly quadruples Claude Code’s success rate on LangChain and LangGraph tasks — from 25% to 95%, according to the official LangChain blog. That’s not a marginal improvement. That’s the difference between a tool that frustrates you half the time and one that actually ships working code. What the Skills System Is LangChain Skills is a structured way to give AI coding agents precisely the context they need for ecosystem-specific work — without bloating the agent’s context window with everything upfront. ...

OpenAI’s agentic coding app Codex has officially landed on Windows — and it’s not a half-hearted port. This is a ground-up native implementation: custom open-source sandbox, PowerShell integration, and a proper Windows Store listing. The milestone coincides with Codex hitting 1.6 million weekly active users, up from roughly 500K a few months ago. That’s a meaningful signal that agentic coding is moving from developer curiosity to mainstream workflow. What’s Actually New in the Windows Release The Windows version of Codex ships three things worth paying attention to: ...

Something genuinely important is shipping in Chrome 146: an early preview of WebMCP, a W3C draft standard jointly developed by Google and Microsoft that fundamentally changes how AI agents interact with websites. Right now, AI agents that browse the web do so by scraping DOM elements — reading HTML, finding buttons, inferring what actions are available. It’s brittle. A website redesign breaks the agent. A modal renders differently across browsers and the agent gets stuck. This approach works well enough for demos but fails at production scale. ...

AWS just added OpenClaw to Amazon Lightsail as an official one-click blueprint. That means you can now deploy a fully functional, self-hosted AI agent — pre-connected to Amazon Bedrock and Claude Sonnet 4.6 — in the time it takes to make coffee. Here’s exactly how to do it. What You’ll Need An AWS account (free tier works for the first month; the $3.50/month Lightsail tier covers basic usage) About 5 minutes A domain name (optional, but recommended for HTTPS setup) Step 1: Open the Lightsail Console Navigate to lightsail.aws.amazon.com and sign in with your AWS credentials. If you don’t have an account, the signup takes about 3 minutes and doesn’t require a credit card for the initial free tier. ...

If you’ve deployed OpenClaw agents with MCP server integrations, there’s a good chance your agents have more access than you realize — and your audit logs are hiding it. Security researchers call it the “god key” problem, and it’s a genuine architectural gap in how most teams are running MCP today. Here’s what it is, why it matters, and how to fix it. What Is the MCP God Key Problem? Model Context Protocol (MCP) servers act as bridges between your AI agents and external tools — databases, file systems, APIs, SaaS platforms. The problem is how credentials flow through that bridge. ...