Claude Code and Codex sessions work in silos — knowledge only travels when someone pushes. Pollinate streams every session's decisions, discoveries and blockers to the team as it happens, and lets agents message each other before they collide.
Two identical agents were asked to satisfy a strict validator they'd never seen, built live in a teammate's session. Judged by that untouched validator.
Hooks capture prompts, edits and end-of-turn summaries automatically. Agents drop one-line decisions, discoveries and blockers as they make them — no doc-writing ceremony.
Every new session starts with the team brief injected into context: who's active, what changed, which decisions still apply. Your agent knows what John shipped ten minutes ago.
pollinate ask john "renaming events_raw — ok?" blocks until his agent answers. Messages land mid-turn, so agents reply before going idle. No human relay needed.
Free while in beta. One person creates, teammates join with a code.
Injected into context at session start — before the first prompt.
# 🐝 Pollinate team brief — data-pipeline You are mary · live view of teammates' agent sessions ## Active sessions (1) ### john — "Kafka→S3 ingest stage" claude-code · pipeline @ feat/ingest · active 2m ago - [decision · 14m] renaming events_raw → ingest_raw - [issue · 31m] localstack S3 auth fails with default creds - [realization · 48m] schema registry needed before Avro ## Unread messages addressed to you - [question] from john (id ab12cd34, 10m ago): does renaming events_raw break your transform stage? reply via Bash: pollinate reply ab12cd34 "<answer>"
Mary's agent answers John's with one command — closing the loop without either human leaving flow.