Make a hub, or project brain
A hub is a named set of your designs, plus a design of its own that holds what spans them: who is in the effort, how you work together, decisions about process, and ideas that haven't found their design yet. Each design stays its own. The hub is the one thing you share, and the one place to look for the whole.
New to flo2? Start with what flo2 is and connecting your chat app. Everything below works from a chat app, from your own agent, or on your account page.
What a hub is
Say you're designing a ring, a kitchen and a boat, and the same three people are in all of them.
Each is its own design, with its own requirements, decisions and files. A hub called
Family
names the three together. Give it a design of its own and that design becomes the
project brain: the place for we meet on Sundays
, the budget for the year covers all three
,
and somebody look into solar
before anyone knows which design that belongs to.
The list of designs in a hub is flo2's own record, never text in a design. That is what lets flo2 decide who sees what. A hub with no design of its own only groups: it changes no design and nobody's reach.
1 Make one
From your chat app, in your own words:
Use flo2 to make a hub called “Family” with the ring, the kitchen and the boat.
Use flo2 to add the garden to my Family hub.
Use flo2 to take the boat out of the Family hub.
Use flo2 to rename my Family hub to “Home”.
Use flo2 to delete the Family hub.
Naming a hub that doesn't exist makes it. Designs go in and out by name or id. Deleting a hub deletes only the hub: its designs, and its own design if it has one, stay exactly as they are.
From your own agent, it is the same tool, make_or_change_a_hub,
on your account address https://api.flo2.io/mcp.
On your account page, under Your hubs, New hub makes one: a name and a tick beside each design. Change adds, removes and renames; Delete hub is there too. Each hub lists its designs, and says which of them changed since you last looked.
2 Give it a design
A hub needs a design of its own before it can hold anything or be shared. This happens from your chat app or your own agent, not from the account page. Two ways:
Use flo2 to give my Family hub a design.
— a new, empty design, named “Family hub”.Use flo2 to make my “House notes” design the Family hub's own design.
— a design you already own, by its name or id.
The second is for when you already have the project brain: a design where you've been writing the cross-cutting decisions for weeks. Adopting it writes nothing to it. From then on it is the hub's design for everyone, exactly as a new one would be. A hub has one design of its own; asking again answers with the one it has.
For your own agent, the argument is give_it_a_design: true for a new
design, or the name or id of a design you own.
When it's refused, and why
- The hub already has a design. Adopting another over it isn't offered. Delete the hub and make it again, or make a new hub for the design.
- The design is one of the designs in the hub (or in another of your hubs). A hub's own design is never also one of a hub's designs. Take it out first, then give it to the hub.
- The design is already another hub's own design. A design is the own design of one hub at most. Delete that hub first, or give this one another design.
- You don't own it. Only a design you own can become a hub's own design; a design shared with you can't, whatever your role in it. Its owner can give it to a hub of theirs.
- You already have a design named “Family hub”, when asking for a new one. Rename the hub or that design first, so the two can't be confused.
Nothing is changed when a request is refused; the hub's list stays as it was.
3 Share it once
Sharing a hub is sharing its own design, the way you share any design: on your account page, choose the hub's design and invite a person by email, as Can edit or Can view. The invitation says which hub it is. That one invitation reaches every design in the hub.
- Invited to edit, they are a member of the hub's design: they drop ideas and feedback into it, and read every design the hub names. In those designs they are a viewer: they read, and every change is refused, with the hub named.
- Invited to view, they read all of it, the hub's design and every design it names, and write nothing.
- Someone you also gave a design to directly keeps the role you gave them there. The hub never lowers it.
- When you add a design to the hub later, everyone in the hub reaches it at once. Take one out, and they stop reaching it.
- Remove a person from the hub's design and all of it ends, on their next request. Nothing was written to grant the reach, so nothing has to be revoked.
On their account page, a design reached this way says in the Family hub · view only
, and
the hub's own design says which designs it coordinates. In a chat, a design listed this way says
it is reached via the hub.
What each person sees
| Who | What they see and can do |
|---|---|
| You, the owner | Everything you could already reach, and nothing more: your own hub grants you nothing. Only you change the hub's list, give it a design or delete it. A design in your hub you can no longer open is counted, and the account page offers to take it out. |
| Someone who can edit the hub's design | Writes in the hub's design. Reads every design the hub names, as a viewer. Edits a named design only if you also shared that design with them to edit. |
| Someone who can view the hub's design | Reads the hub's design and every design it names. Writes nothing. |
| Someone not in it | Nothing. They don't learn the hub exists. A design you shared with them directly is just that design. |
A system of systems
For something bigger, a system made of systems, the same shape has two tiers. The hub holds
the effort: who is in it, how the parts are worked on, decisions about process. A separate
design holds what no part owns: the seams between systems, budgets that span several designs,
the requirements one system levies on another. Each system stays its own design, and the hub is
how one person reaches all of them. reflow2, the engine behind every flo2 design, has a guide to
working this way: reflow2's hub guide.
In a chat, ask for the hub skill to work across a hub with every fact written in the
design it belongs to.
Good to know
- A person reached through a hub doesn't appear on a design's own sharing page. Nothing is written there: the reach is read from the hub's list on every request, so the sharing page lists only the people you gave that design to directly.
- A chat app that keeps the tool list from when you connected (claude.ai does) shows a tool's old description until you reconnect the connector. The tool works either way.
- A hub's own design is an ordinary design: it has files, a
Connect via the API
link and a sharing page like any other, and it is the one the account page marks as the hub's.
Only you can see your hubs. Anyone you share a hub's design with sees the hub, its design and the designs it names, and nothing else of yours.