---
title: "Glossary: Cork blog · Cork"
description: "The words for what goes wrong, and right, when agents share code."
canonical: "https://corkcli.com/blog/c/glossary"
last_updated: "2026-11-14"
---

# Glossary

The words for what goes wrong, and right, when agents share code.

- [Parallel AI coding agents: running several agents on one codebase at once](https://corkcli.com/blog/parallel-ai-coding-agents): Parallel AI coding agents are several coding agents working on one repository at the same time, each on its own task, to finish more work in less time.
- [Multiplayer coding agents: several people and AI agents on one codebase](https://corkcli.com/blog/multiplayer-coding-agents): Multiplayer coding agents means several AI coding agents, often run by several people, working on one codebase at once and needing to stay aware of each other.
- [Landing: rebase, test and push in one step for AI coding agents](https://corkcli.com/blog/landing-rebase-test-push): Landing means getting finished work onto the shared branch in one step: rebase onto everyone else's commits, rerun the tests, then push only if they pass.
- [Coordination layer for AI coding agents: what it is and what it does](https://corkcli.com/blog/coordination-layer-ai-coding-agents): A coordination layer for AI coding agents sits under the tools that run agents and keeps parallel agents aware of each other's changes so the work fits.
- [Blast radius in code: everything a change can break](https://corkcli.com/blog/blast-radius): The blast radius of a code change is the set of callers, dependents, tests and teammates' work that the change can affect, used to judge risk before editing.
- [Agent merge conflict: when parallel AI agents' branches will not merge](https://corkcli.com/blog/agent-merge-conflict): An agent merge conflict is a git merge conflict between branches written by AI coding agents running in parallel, usually found only when the work is combined.
- [Agent handoff: passing work and context from one AI agent to another](https://corkcli.com/blog/agent-handoff): An agent handoff is when one AI coding agent passes unfinished work, findings or decisions to another agent or person, so the next one need not start over.
- [Agent collision: what it is when AI coding agents overwrite each other](https://corkcli.com/blog/agent-collision): An agent collision is when two AI coding agents change the same code, or code that depends on each other, without knowing, so one breaks or erases the other.
- [Agent briefing: the context an AI coding agent gets before it starts](https://corkcli.com/blog/agent-briefing): An agent briefing is the targeted context an AI coding agent gets before it works: signatures, callers, recent changes and notes for the code it will touch.
- [Write gate: a check that holds an AI agent's edit before it lands](https://corkcli.com/blog/write-gate): A write gate checks each file edit an AI coding agent is about to make and holds or blocks it when it would collide with another agent's live work on that code.
- [Semantic merge conflict: changes that merge cleanly but break the code](https://corkcli.com/blog/semantic-merge-conflict): A semantic merge conflict is when two changes merge with no textual conflict but the result is wrong, such as a rename plus new calls to the old name.
- [Semantic lint: catching code that uses a renamed or changed symbol](https://corkcli.com/blog/semantic-lint): Semantic lint flags code that still uses a symbol a teammate or another AI agent renamed, removed or re-signatured, before it becomes a broken build or merge.

[All articles](https://corkcli.com/blog.md) · [Cork in Markdown](https://corkcli.com/index.md) · [llms.txt](https://corkcli.com/llms.txt)

This page in HTML: https://corkcli.com/blog/c/glossary