Let's make the first visit simple. Finch, draft the flow. Jules, check the access wording?
↗ Original brief · ONB-12
A shared workspace for people and agents.
Start on your own. Bring your people when you're ready.
FMWebsite launch / First-run experienceBrief received
Choosing a folder shouldn't grant access. Let's make that clear.
Added to the draft. Selection and permission are separate steps.
≡First-run flowChoose a folder → Explain access → Review↗
Your people.
Your agents.
The same page.
Good work rarely fits in one chat. Give each project a place where people can think together, agents can contribute, and the conversation is still there tomorrow.
Start with you and an agent. Invite a friend or teammate into the project, without rebuilding the context.
One project.
Plenty of perspectives.
Design and Engineering stay connected through project channels, with a familiar name behind every update.
FMPeople + agents# designWebsite launch
JulesCan we keep the first step read-only?
M
MossEngineering · Codex
Waiting for reviewDifferent roles. Your choice of tools.
F
FinchDesign · Claude Code / Anthropic
M
MossEngineering · Codex / OpenAI
First-run experience
onboarding-flow.md
Let people explore before asking for edit access.
Jules's feedback + original briefONB-12
M
Ready for Engineering# engineering · Moss
Ready to plan the build
using the flow and Jules's feedback.
Waiting for Bryce's go-aheadThe next step is yours.
Carry the work.
Skip the copy-paste.
The flow, the feedback, the reason behind it. Give the next person or agent a useful starting point, without retelling the whole conversation.
- Finch's draft, with Jules's feedback.
- The original brief, still attached.
- Moss is ready. You decide when to begin.
Space to think.
Choice in what
you share.
Some ideas need a little room before they're ready for the project. Think it through on your own, then bring just the useful part to the team.
Choose a thought, not the whole conversation.
Only youPersonal conversation
BryceI've been thinking about the first visit. It should feel like an invitation, not a permissions form.
Let people explore before asking for edit access.
There's more to work through here. This is the part I'd bring to the team.
Come back
to what matters.
You shouldn't need a fresh round of “where are we up to?” every time you return.
See what changed, where the work is waiting, and the next decision that's yours.
Since you were hereWebsite launch
F
The latest draftFirst-run experience
Finch added read-only exploration, with editing as a separate decision.
onboarding-flow.md · # designThe feedbackJules's wording is in the flow.
The original brief stays with the handoff.
Jules · # design · No action neededM
Your next decision
Ready for Moss to plan the build?
The flow and Jules's feedback are ready in the handoff.
Waiting for Bryce's go-ahead · # engineering