Flow is where your team and your agents work the same queue.
Most automation runs beside your work tracker, so what the software did is invisible in the place your team actually looks. Flow puts both in one place: spaces shaped to the work, a hierarchy that matches how you plan, rules about how items move that are actually enforced, and expert agents working items alongside people, under approval.
It is part of the platform rather than something bolted on beside it. Moving a card can start a piece of work, and work that needs a decision has somewhere to put it.
Where triage happens — opens a Studio session automatically
The committed piece of work
A piece a customer will actually see, planned in Studio
The unit someone actually picks up
What It Does
A work tracker that expects agents to be in it.
Spaces you shape, not a fixed mould
Each Space gets its own kinds of item, its own hierarchy and its own set of statuses. Start from one of 3 templates and change any of it afterwards — a support queue and a product backlog do not have to pretend to be the same thing.
How work moves is enforced, not suggested
You decide which moves are allowed, what has to be filled in before an item can make one, and who is permitted to make it. The rule is enforced by the product itself, so nothing arrives in Done by a route nobody sanctioned.
Experts work the item and propose, people commit
Assign an expert agent to a work item and it can propose exactly 4 kinds of change: a comment, an updated field, a new item beneath it, or an attachment. Every proposal waits in an approval queue on the item. Nothing it suggests takes effect until a person applies it.
What an agent may do is enforced, not requested
An expert set up to advise only is refused if it tries to change anything, and the refusal is recorded so whoever asked can see what was attempted and why it was stopped. Instructing a model to behave itself is not a control, so it is not used as one.
A status change can start real work
Set this up on any status and moving an item into it starts a process, carrying the item and its details across. This is the join between the work you track and the work that runs itself: moving a card is a legitimate way to begin.
Customer portals feed the same queue
A Space can publish a service portal. Requests raised there become work items in that Space, so what customers ask for and what your team is doing live in one place, on one set of statuses.
Studio opens inside the item
A kind of item can be tied to a kind of Studio document, so the session is waiting the moment the item is created. The brief, the research and the plan live on the item rather than in a document nobody can find six weeks later.
The Loop
What actually happens when you ask an expert.
This is the whole governance story in one sequence. Note where the agent stops.
- 1You assign an expert to the item
A kind of item can come with its expert already attached, so the right specialist is there from the moment the item exists.
- 2The expert reads the item and works it
It sees the item, its fields, the items beneath it and the discussion on it, and nothing outside that space.
- 3It proposes changes from a fixed list
Comment, update fields, create an item beneath it, add an attachment. Anything beyond those 4 is refused, and the refusal is recorded.
- 4Proposals wait for you
They appear on the item as awaiting approval. An advice-only expert never gets this far, because of how it was set up.
- 5You apply what you want
What you approve becomes a real change on the item, recorded against the run that proposed it.
- 6If it gets stuck, it hands back
An expert that runs out of attempts flags the item into the Attention queue rather than failing quietly.
Spaces & Views
Start from a template, then make it yours.
Intent → Initiative → Feature → TaskThe full delivery hierarchy, with triage on Intent handled in Studio.
Ticket → SubtaskA customer queue running New → Open → Pending → Resolved → Closed.
Epic → Story → Task / BugAgile development with Backlog → In Progress → In Review → Done.
ItemA flat list on To Do → In Progress → Done. Add hierarchy later if you need it.
A board by status, with a limit on how much can sit in each column.
A dense table for filtering and changing many items at once.
The full hierarchy, from the top level down to individual tasks.
Sprint planning, with burndown and how much work is completing.
Everything an agent got stuck on and handed back.
How long work is taking, within one space and across all of them.
Types, statuses, fields, service levels, automations, access, portal.
What it doesn't do
Flow is deliberately narrower than it could be on the agent side, because letting software change your work tracker is not something to hand out casually.
- Agents working elsewhere in Bixie cannot reach into Flow. Nothing outside an item can create one or move it along. Only an expert assigned to an item can propose a change, and only a person can apply it.
- The Flow assistant answers questions and summarises what is in your items. It does not change them.
- Jira works one way only. You can prefill new items from Jira, but nothing is written back to it.
- Standup is built but not yet available in the product.
- Sprint planning covers what is committed and how much is completing. It is not a resource-capacity planner.
See Flow with your own backlog
Bring a real queue. We will set up the space, attach an expert to it, and show you the record of everything the agent proposed and what happened to each suggestion.