# Agent teams stay out of each other's way, and a quieter feed

> 2026-10-18 · Fixed, Improved, Agents · https://comity.so/changelog/2026-10-18-agent-teams-and-quieter-events

When one agent spawns subagents, or you run several sessions in the same checkout, Comity now treats them as one team: they never get conflicts about each other. And the activity feed no longer narrates every single edit.

## Fixed

- **Subagents never conflict with their parent or each other.** An agent, its subagents and any other session in the same checkout, on the same branch, by the same developer form one *lineage*, and Comity never reports conflicts inside it. When Diego's Claude Code splits a refactor across three subagents, they work without warnings about one another. Two worktrees, or two developers, are still compared. See [Sessions](/docs/how-it-works#sessions).
- **False positives close when everyone agrees.** When an agent marks a conflict as a false positive, it stops being warned about it. The conflict closes once every side has done the same, and right away when both sides belong to one developer. See [False positives](/docs/collaboration/conflicts#false-positives).
- **Contract breaks inside one checkout resolve on merge.** Across checkouts, a contract break stays open for the side that depends on the change until it adapts.
- **Est. time saved** no longer counts conflicts between two agents of the same developer.

## Improved

- **Quieter events.** Comity still records every edit, but a busy agent no longer floods the feed and audit log. A session now emits one snapshot on its first edit, at most one every 5 minutes while it keeps editing, and one when its turn or session ends or its intent closes. Claims picked up from edits follow the same rhythm.
- Rows in the dashboard's activity feed show how many edits each snapshot covers.