Map a journey with Codex or Claude Code. Follow its screens and branches in the Flows panel or browser viewer, then review product roles, draft test scenarios and quality questions from the same map.
Illustration: a prompt typed into Codex — “Show the checkout flow, including an invalid address and a declined payment.” — produces the checkout flow in the Flows viewer: Shopping bag, Shipping details, an Address valid? decision with an Address needs a fix state that loops back, Payment, Authorize payment, then Order confirmed or Payment declined with a retry loop. The inspector shows the selected step.
From a sentence to a user flow diagram.
Codex reads your description — or your code — and writes a structured flow document. Flows renders it as a graph you can inspect, follow and correct without leaving the conversation.
Typed nodes
Screens, actions, decisions and states — each with a stable ID, an actor and a description. A model of behaviour, not boxes and arrows.
Branches and recovery loops
Every decision has labelled outcomes. Error states loop back to where people recover, so unhappy paths are part of the story.
- ProposedDescribed in the conversationsource.kind: "proposed"
- Inferred from sourceRead from your implementationsrc/checkout/address.ts:42
- ObservedSeen in the running interface1440 × 900 · Playwright
Provenance on every step
Each node says where it came from: proposed in the conversation, inferred from source with a reference, or observed in a running interface.
Screen previews and captures
Proposed screens get lightweight illustrative previews. Implemented screens can use real captures from your app — missing ones are shown as missing, never faked.
Specimens: a node card cycling through the screen, action, decision and state types; a decision whose Valid and Invalid outcomes are highlighted in turn, with the invalid branch looping back to shipping details; a provenance legend for proposed, inferred and observed steps; and a screen card flipping between an illustrative preview and a captured screenshot.
Describe. Graph. Present. Edit.
One loop, entirely inside Codex. The conversation drives the document; the viewer keeps it readable.
Walkthrough: 1, a prompt asking for the checkout flow is typed in the Codex conversation and Flows writes flows/checkout.flows.json. 2, the viewer opens in the Codex browser and the graph appears with labelled connections. 3, fullscreen presentation shows one screen at a time with step details and options on the right, plus Back, Restart and Next below. The example shows a mock payment screen. 4, asking for a declined-payment branch adds a Payment declined state with a retry loop while the rest of the graph stays in place.
- 01
Describe
Ask in plain language, or point Codex at your code. Flows writes a versioned flows.json document in your project.
- 02
Graph
Flows opens beside your Codex conversation, or in the browser viewer: screens, actions, decisions and states with labelled connections.
- 03
Present
Present screens fullscreen, with step details and options on the right. Follow the journey, choose a branch, or go back and restart any time.
- 04
Edit
Ask for a change in the conversation. The document updates and the viewer reloads in place — same IDs, same layout.
Every outcome stays visible.
Loops come back; nothing is hidden in a modal. The happy path, its error branches and the recovery loops live in one graph — read it one layer at a time.
Six steps from the bag to a confirmed order — the path most people take.
The checkout graph: Shopping bag, Shipping details, Address valid?, Payment, Authorize payment and Order confirmed form the happy path. Address needs a fix and Payment declined are error branches. Edit address and Try another method are recovery loops back to Shipping details and Payment.
Give every journey a review plan.
Move from understanding a flow to deciding what to check. Flows prepares test drafts and quality questions from the same map, with links back to the steps and people they concern.
Draft tests from mapped paths
Turn branch choices and endings into scenarios with actions, expected results and prerequisites. Review transition coverage, unreachable steps and recovery loops before preparing a test run.
Connect paths to user needs
Keep the actor, goal and benefit beside the journey. Use cases link user stories to mapped steps and related scenarios, with source references and open questions where evidence is missing.
Plan a quality review
Prepare suggestions for examining comprehension, decisions, recovery, feedback and effort. Explicit output-quality expectations can become review rubrics. These are proposals to investigate, with no scores or research results.
Review each product role
Group flows by user type, inspect permission conditions and their evidence, then filter scenarios and exports by role. Missing or conflicting assignments stay visible for review.
Take the next step in your own tools.
Export functional scenarios as Midscene YAML or JSON, and use cases with quality suggestions as Markdown or JSON. A selected role filters both the review and its export.
Generated scenarios have not been executed. Coverage describes the mapped graph; loops stop at their first return. Role records describe the product’s users and permissions without granting access or verifying security.
Work locally. Share in the cloud when you are ready.
Every flow starts as a file in your repository. Connect an account when your team needs to see it, comment on it or follow how it changes.
@@ "nodes" @@+ { "id": "declined", "type": "state",+ "title": "Payment declined",+ "source": { "kind": "proposed" } }@@ "edges" @@+ { "source": "declined", "target": "payment",+ "label": "Try another method" }Local
Free · no account- Runs on your machine
The plugin serves your flows locally, in the native Codex panel or a loopback browser viewer. No API key, no account.
- A file in your repository
Portable *.flows.json documents keep the graph, product-role evidence, user stories and review hints together. Diff them, review them and commit them with the code.
- Everything in the viewer
Presentation mode, captures, local comments and JSON export for 3 active flows. Archive a flow to free a slot; restore archived flows when a slot is free before opening or exporting them in Flows. Local files are preserved.
MichałYes. Adding it to the retry branch.
Cloud
Optional · 3 flows free- Choose who can view
Share privately with verified email addresses, or separately enable a public link to selected saved flows and current captures. Public links need no sign-in and exclude comments and history.
- Discuss it step by step
Threads on the whole flow or a single step, with verified authors, ready to hand back to your assistant.
- See how a flow changed
With a Pro plan: version history and a before/after comparison, up to 20 previous versions per flow.
- Review without the project
Snapshots retain captured screens, product roles and source hints. The cloud viewer rebuilds scenario and quality drafts from that saved map.
Connecting an account enables private Cloud saving for opened and new flows, including captures. Changes save while the native panel or browser viewer is active. You can turn automatic updates off for each flow; explicit opt-outs are preserved. Free covers 3 cloud flows and 32 MiB; Pro removes the local flow count limit and covers 256 MiB of cloud storage and version history, subject to fair use. Both have no limit on invited viewers. See pricing
Use Codex or Claude Code.
Install Flows in your coding assistant, then ask it to map your project. Local projects and your connected cloud library work together in one plugin.
- Codex
- Claude Code
- Automatic runtime setup
- Direct installation · not listed in public directories
Requires local project access. In Codex desktop, local and cloud flows open in the same panel beside the chat. Claude Code uses the bundled browser viewer when panel support is unavailable. Cursor local import and Windows still need host verification.
Download Flows
One package includes diagrams, captures, product roles, draft scenarios and quality review, plus the connected cloud library. Connect your account to save opened and new flows privately to Cloud by default, with features according to your plan.
Download FlowsKeep the extracted folder in a permanent location. Flows prepares its runtime when needed; first use may require internet access. SHA-256 checksums · Desktop plugin ZIP for direct import.
Install in your assistant
Replace the example path with the extracted folder’s absolute path. Install the same Flows package in each coding assistant you use.
Codex
$ codex plugin marketplace add /absolute/path/to/flows-by-plugin-space-marketplace$ codex plugin add flows@plugin-spaceClaude Code
$ claude plugin marketplace add /absolute/path/to/flows-by-plugin-space-marketplace$ claude plugin install flows@plugin-spaceCursor · local preview
Copy the entire plugins/flows folder to ~/.cursor/plugins/local/flows, including hidden files. Reload Cursor, then check Customize → Skills. Local imports must be allowed by your organization. Verification inside Cursor is pending.
The download uses the macOS/Linux launcher. Windows needs the manual PowerShell setup described in its README.
Ask for a flow
Start a fresh project conversation. In Claude Code you can also use /flows:present-flow.
For updates, replace the extracted folder with the new download, then reinstall in Codex or run claude plugin update flows@plugin-space. Replace earlier recording or local-demo installations with this unified Flows package. Downloads do not update automatically.
Start free. Make room for your team.
Flows is free for 3 active flows on your computer and 3 in the cloud. Pro removes the local flow count limit and gives you more cloud storage. Fair use safeguards apply to cloud activity.
Free
No card · no time limitCreate, capture and present flows on your computer with no account.
On your computer · no account
- 3 active local flows
- Full viewer and presentation mode
- Branches, loops and source references
- Product roles and permission evidence
- Draft scenarios, use cases and quality review
- Local comments, captures and review exports
In the cloud · free account
- 3 cloud flows across all projects
- 32 MiB for snapshots and comments
- Private sharing and team comments
- No limit on invited viewers
Pro
For ongoing teamworkKeep more flows active on your computer and a larger shared library across projects and clients.
On your computer · all features from Free
- Local library without a flow count limit
In the cloud · all features from Free
- Cloud library across projects
- 256 MiB for snapshots and comments
- Version history and before/after comparison
- Up to 20 previous versions per flow
- Choose at any time · cancel renewal anytime
Connect your account in the local plugin to confirm its allowance. Local limits count active flows in the Flows library on your computer, across projects, separately from cloud flows. Archive a flow to free a slot; archiving preserves the local files, and archived flows must be restored when a slot is free before opening or exporting them in Flows.
Free and Pro both include private sharing and team comments with no limit on invited viewers. Updates do not use another flow slot. Version history and comparison require an active Pro plan. Pro includes up to 20 previous versions per flow within its storage allowance; the oldest is removed at that limit. Each snapshot must be under 4 MiB. No automatic overage charges.
After Pro ends, history is locked until Pro is renewed. Choose up to 3 active cloud flows; other saved flows remain read-only. Locally you return to 3 active flows, and nothing is deleted. A new flow requires room within your plan’s limits. Subscriptions are purchased on the account website.
Questions people ask before installing.
Flows by plugin.space is a plugin for Codex and Claude Code that maps user journeys as interactive diagrams with screen captures, product roles and draft test scenarios, built and edited through the conversation with your coding assistant.
How many people can I share a flow with?
Free and Pro have no limit on invited viewers. Invite people by email; each person must sign in with that verified address. All invited viewers can comment on active cloud flows. Storage and discussion limits still apply.
What is Flows by plugin.space?
Flows by plugin.space is a plugin for Codex and Claude Code that maps user journeys as interactive diagrams with screen captures, product roles and draft test scenarios, built and edited through the conversation with your coding assistant. You describe a journey or point at an existing feature; your coding assistant writes a portable flow document and Flows presents it as screens, actions, decisions and states with labelled branches.
Can Flows document an existing flow in my codebase?
Yes. Ask your coding assistant to show an existing feature and the skill inspects the relevant code, records source references on inferred steps, captures real screens where possible and marks what it could not verify. Proposed designs use illustrative previews instead.
Does Flows generate and run tests?
Flows generates draft functional scenarios from the mapped routes, with actions, observable assertions, prerequisites and coverage notes. It includes combinations of branch choices and stops a loop at its first return. It does not run the scenarios or mark tests as passed. Review the drafts and test data, then export Midscene YAML or JSON for use in a separately configured test tool.
What are use cases and quality evals?
Use cases connect user stories and intended outcomes to steps and related functional scenarios. Quality evals suggest questions and tasks for reviewing comprehension, decisions, recovery, feedback, effort or an explicitly mapped output-quality expectation. They retain source labels and missing-evidence questions. They are review proposals, not completed user research, usability findings or assigned quality scores. Export them together as Markdown or JSON.
How do product roles work?
Flows records user types, permission conditions and source evidence for the product you are mapping. The library groups flows by their assigned roles; an audit view links permission claims to affected steps and shows unresolved evidence. Filter functional scenarios, use cases, quality evals and their exports by role. Unassigned or conflicting routes remain unclassified. These records do not grant access to your Flows account or verify that product authorization is secure.
Which tools does Flows work with?
The desktop Flows package combines local project flows and the connected cloud library in one Codex panel. Claude Code uses the same package with a browser viewer when MCP Apps UI is unavailable. Cursor local import and the Windows launcher still need host verification. The separate hosted directory connection reads account flows only and cannot access your computer.
Is Flows free?
Yes. Local use is free with no account, no card and no time limit for 3 active flows: the full viewer, presentation mode, captures, comments and JSON export run on your machine. Cloud saving is optional: Free includes 3 cloud flows and 32 MiB with no limit on invited viewers, free with no time limit and no card needed. Pro costs USD 5 per month plus applicable taxes for a local library without a flow count limit, 256 MiB of cloud storage, no limit on invited viewers and up to 20 previous versions per flow, subject to fair use safeguards, with version history, purchased separately on the account website, never inside the plugin.
How many local flows can I keep?
Free includes 3 active local flows; a connected Pro plan removes the local flow count limit. The limit counts the Flows library on your computer across all projects, separately from cloud flows. Archiving a flow frees an active slot: local files are preserved, and archived flows must be restored when a slot is free before opening or exporting them in Flows. If Pro ends, you return to 3 active local flows and nothing is deleted. The larger local library keeps working offline for up to 7 days after your plan was last confirmed, never past your paid period; changes to your plan apply when you reconnect.
Where are my flows stored?
In your project as readable *.flows.json files, next to the code they describe, so they can be diffed, reviewed and committed in Git. They include mapped roles, stories and test or quality hints. Connecting an optional account also saves opened and newly created flows, with captures and source references, to private Cloud storage by default. Viewers recreate the derived scenarios from that source. Later changes save while the panel or viewer is active, according to your plan. Pro records up to 20 previous versions. You can turn automatic updates off for each flow, save manually or remove a cloud copy.
Does Flows need an API key or a server?
No API key and no server of your own. The plugin bundles a local MCP bridge and a browser viewer served on loopback only; it reuses Node.js 22.13 or newer or downloads a verified runtime on first use. Your coding assistant supplies the model. The optional account library is hosted by plugin.space and requires signing in.
How do I install Flows?
Download flows-by-plugin-space-marketplace.zip, extract it to a permanent location, and register that folder as a marketplace. In Codex run "codex plugin marketplace add /absolute/path/to/flows-by-plugin-space-marketplace" and "codex plugin add flows@plugin-space". In Claude Code use "claude plugin marketplace add /absolute/path/to/flows-by-plugin-space-marketplace" and "claude plugin install flows@plugin-space". The same plugin includes local and cloud features. Replace older recording or local-demo installations, then start a fresh conversation. No npm install is needed. Public directory publication is separate.
Can I share a flow with my team?
With an optional account you can save a private snapshot with its captured screens, grant access to teammates by verified email, discuss the whole flow or a single step, and prepare the open threads as a message for your coding assistant. Owners can separately enable public links for selected saved flows. Private invitations and public links have different access rules.
What does a public link show?
When an owner enables a public flow or project link, anyone with that link can view the selected saved flows and their current captured screens without signing in. The document includes its source references, product roles and permission evidence, user stories and test or quality hints. Later saved updates are visible through the same link. Public links do not expose discussions or retained version history and do not allow content changes. Review the content before enabling a link; disabling it cannot retrieve copies already downloaded.
Own the flow that you’ve built.
Free and local in Codex or Claude Code for 3 active flows. Add an account when you want to share or need more room.
KonradShould we offer a saved card here?