Dev Environment & Infrastructure for AI Projects

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.

Use Claude Code long enough and you hit a dilemma: a prompt on every command stalls your flow, yet turning them all off with bypass is dangerous. The sandbox breaks that binary by fencing what can be touched at the OS level, so commands run freely inside without prompts while nothing reaches outside. This guide covers the two isolations (filesystem and network), getting started with /sandbox (macOS works out of the box, Linux/WSL2 needs bubblewrap+socat, native Windows is unsupported), auto-allow vs regular mode, configuring settings.json (allowWrite/denyRead, credentials, allowedDomains), how it complements permission modes and rules as a third OS-enforced layer, its limits (un-inspected TLS, Unix sockets), and when to reach for dev containers or VMs. Anthropic reports it cut permission prompts by 84% in internal use.

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.

Claude Code's permission rules let you write allow/ask/deny entries in settings.json to specify, fine-grained, which tools, commands, files, and domains run without asking, prompt every time, or are forbidden. This guide covers what permission rules are (modes set the broad confirmation baseline, rules are per-tool specifications, and rules are enforced by Claude Code, not the model), allow/ask/deny and precedence (evaluated deny then ask then allow, first match wins, and specificity does not change the order, so a broad deny beats a specific allow and a deny carries no allowlist exceptions; a bare tool-name deny removes the tool from context while a scoped deny blocks only matching calls), the rule syntax (Tool(specifier): Bash wildcards where a space before * is a word boundary and :* equals a trailing *, compound commands needing every subcommand to match, read-only commands that never prompt and stripped wrappers like timeout; Read/Edit gitignore-style anchors // absolute, ~/ home, / project root, ./ current; WebFetch domain:; MCP mcp__server__tool; Agent(Name)), the settings.json hierarchy and precedence (managed > CLI > .claude/settings.local.json > .claude/settings.json > ~/.claude/settings.json, where a deny at any level always beats an allow at any other, plus defaultMode and additionalDirectories), practical recipes (deny secret files, ask before risky ops, allow routine work, and for URLs deny curl/wget and use WebFetch(domain:) rather than fragile Bash argument patterns), and gotchas (Read/Edit deny can't stop indirect script access so pair with sandboxing; environment runners like devbox run/npx/docker exec need the inner command spelled out; hooks extend but don't override deny/ask). Based on the official docs as of June 2026.

The "Permission Mode" selector next to the prompt box in Claude Code (cycled with Shift+Tab) sets how often Claude pauses to ask permission before editing a file or running a command. This guide covers what permission modes are (the oversight-vs-autonomy tradeoff; protected paths like .git and .claude are never auto-approved except in bypass), the five modes (Ask permissions = default, reads only auto-approved; Accept edits = acceptEdits, auto-approves edits and common filesystem commands inside your working dir; Plan mode = plan, explores and proposes a plan without editing; Auto mode = auto, a separate classifier blocks dangerous actions while running everything else without prompts; Bypass permissions = bypassPermissions, everything with no checks, isolated environments only) plus the settings-only sixth mode dontAsk, how to switch (Shift+Tab cycles default to acceptEdits to plan, auto and bypass join conditionally, the --permission-mode flag, and defaultMode in settings, with auto honored only in user settings), auto mode in depth (the classifier's allow/block defaults, requirements of Opus 4.6+ or Sonnet 4.6, conversational boundaries honored as block signals, and the 3-consecutive / 20-total block fallback), which mode to use when and safety (bypass has no prompt-injection protection so it's isolated-only; auto is the right answer for everyday prompt fatigue; hooks still run in bypass), and how permission mode relates to the effort setting (permission mode = how much it asks, effort = how hard it thinks). Based on official docs and the live UI as of June 2026.

That "Effort" slider next to the model name in Claude Code — the Faster-to-Smarter dial — sets how much work (thinking, tool calls, and response text) the AI puts into each reply. This guide covers what effort is; the slider's 6 items and labels (the API has 5 levels, low to max, and Claude Code adds its own Ultracode mode; the slider reads Low, Medium, High, Extra, Max, Ultracode, where "Extra" = xhigh and the top effort is "Max" — Ultracode is an add-on, not a step); what saves vs. is session-only (low–xhigh persist, Max and Ultracode are session-only); model support and auto-downgrade (xhigh is limited to Fable 5, Opus 4.8, Opus 4.7, etc.; Opus 4.6 and Sonnet 4.6 have no xhigh and downgrade to high; Claude Code's default is high, xhigh on Opus 4.7, while the API default is high everywhere); how to set it (/effort slider and direct values, /effort auto, /model, --effort, the CLAUDE_CODE_EFFORT_LEVEL env var as highest priority, the effortLevel setting, and skill/subagent frontmatter); a quick-reference table; an in-depth look at Ultracode (a two-layer mode that sends xhigh and has Claude auto-launch multi-agent dynamic workflows, limited to xhigh-capable models and session-only, with how to enable it, when to use it, and cost cautions); and related features (ultrathink, /fast). Based on official docs and the live UI as of June 2026.

You probably assume an LLM has to run in the cloud, but in 2026 running AI entirely inside your own PC — a "local LLM" — is a realistic option. A local LLM means running a model like ChatGPT or Claude directly on your machine instead of in the cloud. The three big draws are privacy (input never leaves your device), zero cost (no API fees), and offline use (works with no internet). The downsides: it is not as smart as the top-tier cloud AI, needs a reasonably capable PC, takes some setup, and has no up-to-date knowledge. This beginner guide covers what a local LLM is (a streaming-vs-downloading analogy), the upsides and downsides, the specs you need and quantization (the GGUF format, with Q4_K_M the go-to that keeps quality while cutting memory to about a quarter; roughly 0.5 GB of memory per 1B parameters at 4-bit), how to start (LM Studio's GUI for beginners, Ollama's CLI for developers — 52 million monthly downloads in Q1 2026), recommended 2026 models (Llama 3.2 7B, Google Gemma 4, Alibaba Qwen3.5, plus DeepSeek and Mistral — all open), and when to use local vs. cloud (local for confidential, high-volume, and offline work; cloud for hard problems). The fastest first step: run one small 3B–7B model in LM Studio.

Environment setup is where every beginner programmer gets stuck. In 2026, generative AI (Claude Code, Codex, Cursor) is genuinely usable for routine infrastructure work — local environment setup, Dockerfile generation, Terraform drafts, CI/CD pipelines. HashiCorp shipped its official Terraform MCP Server in 2026, and Anthropic released Agent Skills so infrastructure expertise can be loaded on demand. But "delegate everything" is a different question: an open 0.0.0.0/0 security group, an SSH key committed to GitHub, a $3,000 month-end AWS bill — all 2026 real incidents. This article splits five safe-to-delegate areas, three "verify-then-trust" risk zones, four human-only areas, a four-step beginner-safe workflow, and the latest 2026 tooling (Claude Code, MCP, Agent Skills) — focused on capability evaluation, not career impact.

Ask Claude Code or ChatGPT about building a web app and you'll almost certainly hear "use Next.js." But that suggestion comes from training-data frequency, not from a judgment about your project. This article unpacks AI's three legitimate reasons (training-data dominance / batteries-included / Vercel deploy ease), explains the JavaScript / React / Next.js relationship, walks a 5-minute decision flow (what to build, SEO, DB, time budget, target host), maps four realistic alternatives (Astro, Vite + React, SvelteKit, HTML + Vanilla) to use cases, lays out the five must-know basics for using Next.js (App Router, Server vs Client Components, file-based routing, env vars, deploy targets), and the three pitfalls beginners hit (use-client everywhere, Vercel lock-in, AI returning outdated Pages-Router code) — all calibrated to May 2026. Second entry in the "AI Recommends..." series after the Docker article.

In February 2026, Anysphere — the company behind Cursor — crossed $2B in ARR, drawing a SaaS revenue curve in the league of OpenAI and Anthropic in just three years. This article covers how Cursor differs from VS Code by embedding AI directly into the rendering layer (sub-100ms Tab completion, 272K-token codebase index, the six core features: Tab / Inline Edit / Composer / Agent / Background Agents / Bugbot), the five concrete differences vs VS Code, side-by-side comparison with four rivals (Windsurf / Zed / Claude Code / GitHub Copilot), the Hobby-free / Pro $20 / Business $40 plan structure, and a decision guide for "who should actually switch" — fact-based as of May 2026.

In summer 2025 a solo developer launched an MCP server called 21st.dev with zero marketing budget and reached $10,000 MRR in 6 weeks. Another developer on Apify Store earns $2,000/month. But of the 12,000+ MCP servers published as of March 2026, fewer than 5% have monetized successfully — the remaining 95% sit in the graveyard of "useful but free." This article lays out, with industry research and real numbers, what separates winners from losers, the 4 revenue models (subscription tiers / usage-based / API-key / freemium), a comparison of the major marketplaces (MCPize 85% rev share / Apify / Glama / Smithery), real-world figures, the 6 failure patterns 95% fall into, the solo developer playbook, enterprise strategy, and a 1-3 year forecast.