AI pair programming
AI pair programming is a collaboration style where an LLM assistant sits alongside you, suggesting code and reviewing changes in real time as you work.
AI pair programming is a working style where a large language model plays the role of a programming partner — suggesting code, asking clarifying questions, spotting bugs, and reviewing diffs — while you drive the keyboard. It's the interaction model popularized by GitHub Copilot, Cursor, and editor-embedded assistants, and sits between raw autocomplete and fully agentic coding.
Why it matters
AI pair programming is the gateway most developers walk through before moving to agentic tools. You stay in control of each change, the AI accelerates the mechanical parts (boilerplate, tests, docs, translations), and review is continuous because you see every suggestion.
Compared to vibe coding or full autonomous agents, pair programming trades throughput for control. Some teams keep both modes — an IDE with a pair-programming assistant for careful work, plus SpaceSpider running Claude Code or Codex CLI panes for tasks they're comfortable delegating.
How it works
Modern AI pair programming tools combine several techniques:
- Ghost text — inline completion predictions as you type
- Chat — a sidebar for asking questions about the current file or selection
- Edit mode — a natural-language diff proposal you accept or reject
- Codebase context — embeddings over your repo via RAG so suggestions aren't file-local
The LLM receives the surrounding code (and optionally retrieved snippets from elsewhere in the repo) and a short instruction derived from your action. Output is applied as a suggested edit, visible before you commit to it.
How it's used
Typical pair-programming flows:
- Writing test cases by highlighting the function and asking "add tests"
- Scaffolding a new endpoint by describing it in a chat panel
- Renaming and refactoring with LLM-generated diffs
- Explaining unfamiliar code — "what does this regex do?"
See /compare/cursor-vs-claude-code and /compare/copilot-vs-claude-code for how this style compares to terminal-first agents.
Related terms
- Agentic coding — the more autonomous sibling
- Vibe coding — the looser, more trust-based variant
- Tool use — what unlocks agent mode beyond pair programming
- LLM — what sits behind every pair-programming tool
- Claude Code — a terminal-first alternative to IDE pair programming
FAQ
Is Claude Code pair programming or agentic coding?
It can be either. Run it interactively and answer its questions one step at a time — that's pair programming. Hand it a task and let it loop through edits and tests autonomously — that's agentic.
Can I do pair programming in SpaceSpider?
Yes — open a space with Claude Code in one pane and a shell in another and drive each turn manually. SpaceSpider doesn't force autonomy; it just runs the CLIs you pick.
Related terms
- Agentic codingAgentic coding is software development where an LLM-powered agent plans, edits, runs, and verifies code on its own using tools, not just autocomplete.
- ANSI escape codesANSI escape codes are control sequences that terminals interpret for colors, cursor movement, and screen clearing — the language of every modern CLI UI.
- Autonomous agentAn autonomous agent is an AI program that perceives, decides, and acts on its own toward a goal — the architecture behind modern coding CLIs.
- CheckpointA checkpoint is a saved snapshot of file state that lets you roll back an AI coding agent's changes to a known-good point.
- Claude CodeClaude Code is Anthropic's official command-line agent that plans, edits, runs, and verifies code across your repo using Claude models and tool use.
- CLI wrapperA CLI wrapper is a program that launches, manages, and UI-wraps other command-line tools — how apps like SpaceSpider host Claude Code and Codex CLI.