Guides: running AI coding agents as a team

Practical, workflow-level guides to running AI coding agents: in parallel, in worktrees, with your issue tracker, and with your whole team in the loop.

• How to Add the Linear MCP Server to Claude CodeConnect Linear to Claude Code in one command: add https://mcp.linear.app/mcp over HTTP, authenticate with /mcp, and drive issues from your terminal.
• Agent sessions are the new pair programmingJuniors used to ramp by pairing with seniors. Now the judgment worth learning lives in AI agent sessions. How to make watching real sessions a team practice.
• Your coding agent says the tests passed. Here is how to verify it.An agent's summary of its own work is a claim, not evidence. Map each claim (tests passed, bug fixed, build works) to the artifact that proves it.
• AI Code Review Noise: When Accurate Comments Are Not NecessaryAI code review noise is accurate but unnecessary comments. How to filter it: severity thresholds, blocking vs non-blocking rules, and a written product contract.
• Running AI Coding Agents on Client Work: A Playbook for AgenciesHow agencies and dev shops run coding agents across client projects: isolation per client, showing live work to non-technical clients, and keeping AI costs out of your margin.
• AI Coding Agents for Product Managers: Preview, Comment, SteerHow product managers preview and steer AI coding agents: prompt-to-app prototyping, preview deployments with comments, and live previews that reach the agent.
• Running AI Coding Agents With Your Own KeysWhat bring-your-own-keys means for AI coding agents: subscription logins vs API keys vs platform credits, per-user vs shared keys, and options for teams.
• Always-On Coding Agents: Where Should They Actually Live?An always-on coding agent needs a machine that never sleeps. Compare a kept-awake laptop, a VM you own, and vendor sandboxes like Codex cloud, honestly.
• The Best AI Coding Tools for Team Collaboration in 2026Ranked: the AI coding tools that let teams build with code agents together in 2026, judged on shared live sessions, steering rights, isolation, and pricing.
• The Best Cloud Coding Agents in 2026, ComparedThe cloud coding agents worth using in 2026: Claude Code on the web, Codex cloud, Cursor cloud agents, Copilot coding agent, Jules, Devin, and AQ, compared honestly.
• Build vs Buy: Should Your Team Build Its Own AI Coding Harness?Ramp's in-house agent made build-vs-buy a live question. Most of the advantage comes from where the harness runs, not who built it. How to decide in 2026.
• Can a Coding Harness Get Your Account Banned? Credential Custody, ExplainedYes: reusing subscription OAuth inside third-party coding tools triggered real bans in 2026. Whose credentials your harness holds, and how to stay safe.
• How to Carry Context Between Claude Code and CodexWhat actually transfers when you switch between Claude Code and Codex mid-task: repo state and instruction files move, sessions do not. The reliable handoff recipe.
• Claude Code Agent Teams vs Parallel Worktree SessionsWhat Claude Code agent teams are, how the shared task list works, what teams cost in tokens, and when plain parallel worktree sessions are the better choice.
• The Coding Agent Harness Directory (August 2026)A directory of coding agent harnesses as of August 2026: lab CLIs, open-source harnesses, parallel-agent desktop apps, cloud platforms, and what shut down.
• Conductor Alternatives for Windows and Linux DevelopersConductor is a Mac-only app as of August 2026. How Windows and Linux developers get the same parallel-agent workflow: Emdash, Claude Code Desktop, DIY, and AQ.
• How to Connect Linear to Codex with the Linear MCP ServerConnect Linear to Codex in one command: codex mcp add linear --url https://mcp.linear.app/mcp, sign in with OAuth, and drive Linear issues from your terminal.
• DeepSeek V4 Pro for Coding Agents: What to KnowDeepSeek V4 Pro went GA on August 13, 2026: open MIT weights, 1M context, big agentic gains, and a first-party price increase days later. The full picture.
• Designers Building With AI Coding Agents: The 2026 GuideHow designers build working software with AI coding agents in 2026: prompt-to-app tools, agent CLIs in the real codebase, and preview-driven feedback loops.
• Executable Specs as Guardrails for AI Coding AgentsHow executable specs (BDD scenarios, failing tests, spec files) steer AI coding agents, how agents game them, and what still needs human judgment.
• How to Get Notified When Your Coding Agent Finishes or Needs YouSet up alerts for when a coding agent finishes or waits on input: Claude Code notification hooks, the terminal bell, Codex notify, tmux flags, and phone push.
• How to Get Your Whole Team Building with AI AgentsA rollout playbook for engineering leads: pilot in the open, make sessions visible, set a review policy, standardize the environment, measure quality.
• Git Worktrees for AI Coding Agents: The Isolation StandardA git worktree gives each AI coding agent its own working directory and branch from one repo. Here is how to use them, the gotchas, and how to automate them.
• GLM-5.3 for Coding Agents: What to KnowZ.ai released GLM-5.3 on August 14, 2026: same base as GLM-5.2, all gains from post-training, record open-model benchmark claims, and weights due in two weeks.
• Grok 4.6 for Coding Agents: What Changed and How to Run ItGrok 4.6 shipped August 12, 2026 as a post-training upgrade aimed at long-running agents. Benchmarks, pricing, early caveats, and how to run it with your team.
• How Many Coding Agents Can One Developer Actually Run?Most developers plateau at two to four concurrent coding agent sessions. The ceiling is attention and review bandwidth, not compute. Here is how to raise it.
• How to Choose a Coding Harness in 2026Choosing a coding harness comes down to four questions: model access, how much harness you want, how the pairing performs on your repo, and who sees the work.
• How to Resume and Search Claude Code SessionsClaude Code saves every conversation. Resume with --continue or --resume, search the session picker, catch up with /recap, and know when transcripts expire.
• How to review an AI coding session, not just the diffHow to review an AI coding agent's session: preserve the brief, keep the transcript retrievable, check five layers, and put a second person on agent PRs.
• How to Run Claude Code From Your PhoneThree ways to drive Claude Code and other coding agents from a phone: official remote-control features, a DIY SSH and tmux stack, or a phone-native IDE like Lunel.
• How to Run Multiple Claude Code AccountsRun multiple Claude Code accounts with separate config directories (CLAUDE_CONFIG_DIR), per-OS-user logins on shared machines, and per-user accounts for teams.
• How to Safely Run AI Coding Agents on Your Own ReposRun AI coding agents on your own repositories safely: least-privilege tokens, branch protection, isolated git worktrees, secrets hygiene, and real PR review.
• One Repo, Many Agent CLIs: Keeping AGENTS.md and CLAUDE.md in SyncMake AGENTS.md the single source of truth for Codex, Cursor, and OpenCode, bridge Claude Code with an import or symlink, and stop instruction drift.
• How to Keep Claude Code Running After You Close Your LaptopClosing your laptop kills any Claude Code session tied to it. Here is how tmux, mosh, VS Code Tunnels, Claude Code Routines, and AQ each solve persistence, as of July 2026.
• How to Keep Codex Running After You Close Your LaptopClosing your laptop kills a local Codex CLI session, and codex resume only restores the transcript. Here is how tmux, mosh, Codex cloud, and AQ each keep work going.
• Keeping Secrets and Production Data Out of Coding Agent PromptsWhat actually leaves your machine when a coding agent runs, and the four layers that keep secrets and production data out of prompts.
• From Linear Issue to Agent-Built PR: A Working WorkflowA Linear coding agent workflow: label an issue ai-task, a workspace appears for the team, a human starts the agent, and the PR is tracked back to the issue.
• How to Manage Claude Code Sessions Across a TeamClaude Code sessions live on one machine, under one account. How teams manage them anyway: naming conventions, worktree isolation, persistence, visibility, and handoff.
• How to review Claude Code sessionsWhere Claude Code stores session transcripts, how to export and resume them, what a second reviewer can and cannot reach, and workarounds that close the gap.
• Reviewing Pull Requests From AI Agents Without DrowningHow to review AI agent PRs without drowning: review the run, not just the diff, use live previews to check behavior, and keep every PR small and rebased.
• Rolling out session review: a playbook for engineering leadersA leader's playbook for making AI agent sessions reviewable by policy: when a second person is required, how to keep it lightweight, and what to measure.
• How to Run Claude Code on a Cloud VMProvision a small Linux VM, install Claude Code, sign in over SSH, and keep sessions alive with tmux. A complete setup guide with hardening and costs.
• How to Run Multiple AI Coding Agents in ParallelRun Claude Code, Codex, and other agent CLIs in parallel: one isolated git worktree per task, separate ports and data, and sessions that outlive your laptop.
• How to Run Multiple Claude Code Sessions in ParallelThe fastest way to run multiple Claude Code sessions in parallel: one git worktree per task locally, or one isolated workspace per task on a platform.
• Self-Hosted AI Coding Agent Setup: A Step-by-Step GuideStep-by-step self-hosted AI coding agent setup: VM sizing, SSH and Tailscale, installing Claude Code and Codex, headless login, and tmux persistence.
• Self-Hosted AI Coding Agents: Your Options in 2026Self-hosting an AI coding agent means owning the execution environment, not the model. Compare OpenHands, Cursor, Warp Oz, a plain VM with tmux, and AQ.
• How to Share a Claude Code Session With Your TeamClaude Code share links are read-only. To share a live session, use tmux over SSH or a multiplayer workspace where teammates join the same terminal and preview.
• How to Share a Dev Environment with Your TeamTwo ways to share a dev environment: commit the recipe (devcontainer.json, Nix) or share the running instance (Live Share, tmux, a team server). How to pick.
• Shared AI pair programming: pairing when one side is an agentHow to pair program when one side is an AI coding agent: the human navigates, the agent drives, and the session stays visible to a second human. Full guide.
• The session review checklistA copy-paste checklist for reviewing AI coding sessions: concrete reviewer questions across five layers, from the original brief to the running result.
• What AI Code Review Can and Cannot CatchAI code review catches mechanical bugs and known vulnerability patterns. It cannot observe runtime behavior, unstated intent, or its own biases. Here is the line.
• Why Parallel Claude Code Sessions Collide, and What Actually Fixes ItParallel Claude Code sessions collide on files, ports, databases, and branches. The fix is a ladder: worktrees, per-session resources, locks, then visibility.