Lesson 60 · Build with customers

What did our coding agents decide, and how do I continue?

Read the history. Carry the context forward.

1 min 31 s8 stepsLesson 5 of 8 in Build with customers

You’ll be able to

  • Find and read coding agent sessions
  • Review signals and session visibility
  • Continue with the right context

Read the docs

Synced from docs.buildbetter.ai

The help pages for this lesson, kept up to date. Read them here without leaving the lesson.

Agent Sessions
What gets captured, where it's stored, and how to resume on any machine.
ZeroShot (CLI) Overview
A single bb binary that captures every coding-agent session and lets your team resume them anywhere.
BuildBetter CLI
Use the bb command line tool to connect local AI coding sessions to BuildBetter

Transcript

You can now review what your coding agents did, see their decisions and continue with context.

On the Build surface, open Agent Sessions. Search prompts, transcripts, repositories or branches.

Open All providers to narrow to Codex, Claude Code or Cursor. Visibility and association filters help you find the right session.

Open a session. Transcript shows the conversation and tool events. The sidebar keeps the repository, branch and commit with it.

Signals highlights extracted evidence, like a verification failure or migration risk. Review the evidence before acting on it.

You can rename the title when you have edit access. Open Visibility to review Workspace or Private access.

Continue with context lets you ask in BuildBetter or open Codex, Claude or Cursor. The handoff carries the session context.

On a project, open Agent sessions. Sessions link automatically when their branch matches a pull request on that project.

On an account, open Agent Sessions. Find an uploaded session here, or review sessions already associated with that customer.

Next up, choose reports for your customer success team.