Component gallery & roadmap

Flux, every screen and every part

Flux is a calendar-first personal operating system. It opens to a drag-and-drop day with one-minute precision, links every block to the people, places and tools behind it, and compares the day you planned against the day you actually had.

v0.6.0 17 surfaces 78 component files Rendered from the shipped code

What this is, and what it is not

Every frame below is a static reproduction built from Flux's own source: its real tokens, its real Lucide icons, its real strings copied out of the components rather than out of the docs. There is no live app behind this page, no login and no network. Where the code and the documentation disagreed the code won, and each disagreement is listed in the build notes that ship with this site. Components that are placeholders, dead code, or that carry a reproduced bug say so on the card rather than blending in with the ones that work.

Surfaces

17 frames · 1280×800

A surface is a whole place you can be in Flux. Each frame below is rendered at exactly the size a laptop shows it, which means where a page runs past the fold here, it runs past the fold in the product too. Eleven of these are in the main navigation, eight more sit behind a Preview group the app itself marks as unfinished, and the honesty banners you see on some frames are the product's own.

01
Now
The whole product in one screen: what you are on, what is next, and how many of the day's 1440 minutes are left. If Flux has nothing scheduled it falls back to your active focus in Tabatha.
↗
02
Calendar
The workspace. Drag to move, drag to resize, and get argued with when two blocks want the same minute.
↗
03
Planner
Lock the day and Flux keeps an immutable snapshot, then shows it against what actually happened.
↗
04
Context Inbox
Where the AI brings you what it found and waits. Accept, merge, or reject; merging teaches it the alias.
↗
05
Journal
Notes, long-form entries and voice, in three tabs. The notes board saves as you type.
↗
06
Conversations
What was said, who was there, and what it turned into. Imports parse in your browser.
↗
07
People
The people in your system, and a nudge when someone you meant to stay close to has gone quiet.
↗
08
Tabatha
Your live attention board from the sibling product, read into Flux and shown beside the plan.
↗
09
Variables
The five kinds of thing a block can involve. This is the vocabulary the context graph is built from.
↗
10
Insights
Fourteen days of planned against actual, signal against noise, computed from days you really had.
↗
11
Integrations
Four connections that work, eight that do not yet, and a panel that refuses to blur the line.
↗
12
Goals & Systems
A north star, and the goals under it at three timeframes. Starting one creates a real block.
↗
13
Frictions
The four kinds of stuck: problems, decisions, predicaments and constraints.
↗
14
Settings
Seven groups of rules the scheduler later enforces, including a cognitive-style preset that reshapes the defaults.
↗
15
Audit Log
Every sync and every action an agent took for you. It used to be fiction; it is not any more.
↗
16
Login
The only surface outside the app shell. Invite-only, with a waitlist behind it.
↗
17
Admin Gated
Owner-only in the product, and asks for a passphrase here. Every value on it is invented sample data.
↗

No surface matches that filter.

Component library

98 cards · 78 files · 9 categories

Every component under src/components/, grouped by the job it does rather than the folder it sits in, and shown in each state it can actually be in: loading, empty, error, locked, conflicted, drifted. That last part is the point of the exercise. Forcing every component into every state is a thorough test, and it found real bugs, which are labelled on the cards rather than quietly fixed.

Time & Planning
The parts that make Flux a calendar rather than a list: placing a block at a minute, arguing about collisions, and holding you to the plan you locked.
11 components
Context Graph
What turns a calendar into a personal system: capturing who and where a block involved, and letting a human arbitrate what the AI extracted.
8 components
Capture & Journal
Getting a thought out of your head before it evaporates, and turning what you captured into something the system can read.
11 components
Intelligence & Insights
The parts that form an opinion about your day. None of it is load-bearing: every core workflow works with no AI at all.
5 components
Integrations
Flux should not become the only place your work lives. These connect it to what you already use, and are honest about which connections are real.
4 components
Settings & Configuration
Flux has opinions about your day; this is where you argue with them. Most of these store a rule the scheduler later enforces, not a preference.
8 components
Shell & Honesty
The frame around every surface, plus the mechanism Flux uses to tell you how finished the page you are standing on actually is.
11 components
Primitives
The shadcn layer Flux is assembled from. Nearly stock, which is the interesting part: exactly one is customised, and six shipped that nothing imports.
35 components
Admin Gated
An owner-only control plane for the invite gate and the waitlist. Asks for a passphrase, and shows only invented sample data.
5 components

No category matches that filter.

The other half

Flux has a sibling. Tabatha watches attention and focus; Flux interprets the whole life system. Tabatha knows which tab you are on and how long you have really been on it. Flux knows what you meant to be doing and why it mattered. Each works perfectly well alone, and neither is allowed to grow into the other. Tabatha has a gallery like this one, built the same way and looking deliberately nothing like it.