Session history and mob ROI

Every MobSession is saved as a durable record your team can revisit: who steered, what shipped, and what it cost. From that record you can open an ROI report that shows why the mob was worth it.

Preview. This is in early access and rolling out to teams.

Live now vs. early access

During a session you already see the live transcript, who is steering, and the running cost per turn.

The early-access part is what happens after the session ends. The transcript, contributors, files, pull requests, time, and cost get written to a saved record. That record drives a report view in your account, plus exports you can hand to people who were never in the session.

What a saved session captures

Each record includes:

• Full transcript. Every prompt and response, in order.
• Contributors and who steered. Which experts joined, and who was driving at each point.
• Files changed. Every file the mob touched.
• Pull requests opened. Links to the PRs the work produced.
• Time and cost. Total wall-clock time and dollar cost.
• Accomplishment summary. A plain-language recap of what the mob set out to do and what it finished.

Open a session weeks later and the whole story rebuilds itself, no one's memory required.

The ROI report

The report answers one question: was bringing these experts together worth it, and at what price? It pulls the saved record into a single view.

A report highlights:

• Outcomes. What got fixed and shipped, tied back to the pull requests that delivered it.
• Contributors. The experts who took part, and how the work passed between them.
• Cost and time. Total spend and time, so the value is concrete.
• Summary. A short narrative, ready to share upward.

View reports in your account under session history. They export too, so you can attach one to a wrap-up, a review, or a budget conversation.

How teams use it

• Show the value of a mob. Several experts, a fixed window, a known cost, a concrete set of shipped changes.
• Justify the spend. Time and cost sit next to the outcomes, so finance and engineering leaders see the ROI in one place.
• Onboard and review. A saved transcript with files and PRs is a ready-made walkthrough of how a hard problem got solved.
• Keep a paper trail. Decisions and changes don't get lost when a session closes.

Where to find it

• Browse saved sessions at /account/sessions.
• Open any session to view its report, then export it from the report page.

Related

• Attribution explains how contributors and steering are tracked across a session.
• Audit and compliance covers how durable session records support your audit needs.