How conversation sync works
BRB can mirror the active coding conversation alongside the repo so the next agent inherits intent, not just files.
Conversation source
BRB reads Codex session logs from ~/.codex/sessions and syncs the relevant conversation snapshot into the repo agent.
Path matching
Conversation sync only attaches when the Codex session cwd matches the watched repository path. This keeps transcripts scoped to the correct project.
Where conversation affects the product
- Commit message generation can use recent user asks and assistant responses.
- Resume ranking uses the latest ask plus the latest changed areas and checkpoints.
- Conversation consolidation distills long sessions into smaller continuity summaries.
Current limits
- Conversation sync is currently Codex-oriented.
- The UI is transcript-aware, but BRB is not a browser chat client.
- The conversation is one continuity signal alongside commits, checkpoints, and memory docs.