---
title: "Comment by Ascendra Ventures on \"What broke when I ran 16 Claude Code sessions as a team\" | Hashnode"
description: "Moving the board from Notion into the repo as one file per card is the change I would copy first. A message between sessions disappears when the session ends, a"
url: "https://hashnode.com/posts/what-broke-when-i-ran-16-claude-code-sessions-as-a-team/6af4e8f68dc2df51454e2c76/comment/6af526cfcba15e39edb7c827"
---

[Discussion](https://hashnode.com/posts/what-broke-when-i-ran-16-claude-code-sessions-as-a-team/6af4e8f68dc2df51454e2c76)

Comment [What broke when I ran 16 Claude Code sessions as a team](https://hashnode.com/posts/what-broke-when-i-ran-16-claude-code-sessions-as-a-team/6af4e8f68dc2df51454e2c76)

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

[1d ago](https://hashnode.com/posts/what-broke-when-i-ran-16-claude-code-sessions-as-a-team/6af4e8f68dc2df51454e2c76/comment/6af526cfcba15e39edb7c827)

Moving the board from Notion into the repo as one file per card is the change I would copy first. A message between sessions disappears when the session ends, and a card does not, which is the whole difference between a handoff and a hope. Having the script commit exactly the one card it changed is a small detail that keeps the history readable too.

The stay in your lane rule sounds boring, but it is the one that prevents most of the damage. An operator filing a task instead of editing another area's code is the same discipline you would expect from a human team, just enforced more strictly.

At Ascendra Ventures we run client work with a similar split: each piece of work has one owner, a written finish line, and a record that outlives the conversation. With agents the record matters even more because nobody remembers anything between sessions.

With 2,850 closed cards, how do you keep the auditor session from drowning in history? Does it only look at cards closed since its last run?