Articles
Every Aftergradient guide in one place: setting up Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and Antigravity, adding MCP servers and skills, writing CLAUDE.md and AGENTS.md files, and choosing between tools and plans.

MCP stdio vs Streamable HTTP: which transport to use
Choose stdio for a client-owned local process and Streamable HTTP for a separately managed network service.

Google Jules vs Antigravity: cloud tasks or local agents?
Compare Google Jules and Antigravity by execution environment, review flow, permissions and best-fit tasks.

Claude Code compact: context checks and continuation
Use /context and focused /compact prompts, then verify the saved work and source details before continuing.

GitHub Copilot custom agents: .agent.md files and tools
Set up GitHub Copilot custom agents with .agent.md files, scoped tools, precedence and CLI invocation.

Best MCP servers for Cursor, with mcp.json setup
Best MCP servers for Cursor: GitHub, Playwright, Context7, Supabase and more, with each vendor's mcp.json config.

Cursor student discount: current options and renewal rules
Cursor's old student discount is closed. See free access, academic credits and existing-plan renewal rules.

Claude Code sandbox: files, network and strict mode
Claude Code sandbox limits for files and networks, strict mode, retries and the tools outside its boundary.

CLAUDE.md vs AGENTS.md: which file each coding agent reads
Claude Code now reads AGENTS.md when no CLAUDE.md exists. Here is what Codex, Copilot, Cursor and Gemini CLI read.

Codex CLI vs Codex app vs IDE extension: which surface to use
What the Codex CLI, the Codex app in the ChatGPT desktop app and the IDE extension each do, and when to pick each.

Where Claude Code stores sessions, settings and memory
Claude Code keeps sessions in ~/.claude/projects/ for 30 days, settings in settings.json files and memory per repo.

GitHub Copilot CLI: install, sign in and tool approvals
GitHub Copilot CLI setup from GitHub's docs: install, sign in, plan mode, -p prompts and safe tool approvals.

Gemini CLI in VS Code: Companion Setup and Diff Review
Connect Gemini CLI to VS Code, inspect editor context and review changes through the Companion extension.

GitHub Copilot AI credits: plans, reset and legacy requests
GitHub Copilot AI credits by plan: what uses them, when they reset, and why premium requests are now mostly legacy.

Claude Desktop vs Claude Code: which workspace fits the job?
Claude Desktop and Claude Code share a model family but organise work differently. Here is the practical split.

Example CLAUDE.md files for Bun, Python and React
Adapt real CLAUDE.md files from Anthropic's Bun, Python and React projects, with sourced commands and pitfalls.

Serve Claude Code as MCP: Setup and Limits
Run Claude Code as a local stdio MCP server, configure the client and keep approvals at the client boundary.

Cursor rules: .mdc files, AGENTS.md and scope
Choose between .cursor/rules, AGENTS.md and user rules, and check when Cursor actually includes your instructions.

Codex: dangerously skip permissions and safer modes
The exact Codex bypass flag, what it removes, and how to run unattended jobs while keeping a sandbox.

Global CLAUDE.md: personal instructions across projects
Global CLAUDE.md: file location, personal preferences, project scope and checks for loaded instructions.

What are Claude skills? SKILL.md, loading and where they run
Claude skills are folders of instructions, scripts and resources that Claude loads only when a task calls for them.

Claude skills marketplace: where to find and install skills
Where the Claude skills marketplace lives: Claude Code plugin marketplaces, /plugin install and claude.ai skills.

Claude Code skills: SKILL.md, locations, frontmatter and install
Claude Code skills are SKILL.md folders Claude loads when relevant or you run as /skill-name. Where they go and how.

How to update Gemini CLI: npm, Homebrew, npx and channels
Update Gemini CLI with npm install -g @google/gemini-cli@latest or your package manager's command, then check gemini -v.

Codex hooks: hooks.json, config.toml, events and exit codes
Codex hooks run commands at events like PreToolUse and Stop, set in hooks.json or the hooks table of config.toml.
Each guide answers one job and states the tool version or documentation date it reflects. Commands and limits come from the vendor’s own docs and are linked next to the claim. For prices, see the plans tracker; for servers and skills, the MCP directory and skills directory.
