Naming, objectives, and habits that make a session feel worth showing up to versus another chat window.
“Pricing chat” invites nobody in particular. “Finalize enterprise-tier pricing before Friday's board meeting” tells people exactly why they'd want to be there and by when. The objective field isn't decoration — it's what makes a session worth opening.
| Role | Use for |
|---|---|
| Editor | Anyone actually shaping the outcome — most of your core team |
| Viewer | Someone who needs visibility but isn't driving the decision |
| Guest (session link) | A one-off contributor — a client, outside counsel — who shouldn't get broader workspace access |
Defaulting everyone to Editor “just in case” tends to produce sessions where nobody's clear on who's actually deciding versus who's just present.
When a real call gets made, mark it as a Decision rather than letting it dissolve into the general conversation. It shows up in the Decisions Log, stays easy to find later, and is what someone will actually look for when they ask “wait, why did we go with this?” six weeks from now.
@mention a model or agent directly in the conversation rather than stepping out to a separate chat and pasting the answer back in. It keeps the reasoning attached to the discussion that prompted it, and everyone sees it happen instead of receiving a secondhand summary.
When a session's objective is met, archive it rather than letting it linger as an ambiguous “is this still active?” thread. A workspace full of clearly-closed sessions is easier to navigate than one where nobody's sure what's still live.