Describe a job or show it once in your browser. FluxIQ turns it into an automation that replays on its own. A model only steps in when something is new, a result looks wrong, or the page has changed, and always within the limits you set.
An animated illustration of the FluxIQ browser extension on an example lead directory. Tell it: you ask in plain words and FluxIQ searches, filters to Calgary, and reads 24 rows. Record it: you do the task once and FluxIQ captures each step as an automation. It adapts: after a redesign moves the Search button, FluxIQ uses AI once to find it, then runs again without AI.
An illustration of the FluxIQ browser extension, which is coming soon.
Routine runs replay saved steps with no model at all. AI is only called for something FluxIQ hasn’t seen before.
Cap how often AI can step in, how many tokens it uses, and what it spends. When a cap is hit, FluxIQ asks you or stops. Your call.
Results are checked on the first runs, then less and less often. Change the Flow and checking starts over.
Fully adaptive, approve every change, or no AI at all. Every repair is logged and can be reverted.
The framework does the thinking and remembering. The extension does the clicking. They pair over a local connection you approve.
Framework · fluxiq 0.7
A TypeScript framework and control panel you run on your own machine. It builds Flows, runs them, checks the results, and repairs what breaks.
Extension · Coming soon
A browser extension, in development, that records what you do, runs Flows on real pages, and pulls data out of lists, page after page.
01 · show
Type what you want done, or record it once in your browser.
02 · build
AI assembles the Flow only from actions FluxIQ actually has. Buying, deleting, or sending always waits for a person.
03 · run
Saved steps run the same way every time, and results get checked until the Flow has earned trust.
04 · repair
When a site changes or a check fails, FluxIQ works out why, proposes a fix, and keeps it only once a full run succeeds.
Where it’s going
FluxIQ’s own tools already run as programs on one framework. Automation Studio, the database manager, and background tasks each have their own screens and APIs.
The goal is for you to describe an outcome and have FluxIQ build the program around it: the interface, the data, the Flows that do the work, and the controls that keep it honest.
“Build me a lead-generation app for commercial roofing companies in Western Canada.”
Pipeline
| Flow | last run | status |
|---|---|---|
| discovery | replay | ok |
| enrichment | replay | ok |
| qualification | checked | ok |
| refresh | repairing | review |
Read the paper
Technical Vision & Architecture · Draft v0.9 · October 2026
How FluxIQ moves work from probabilistic reasoning into reusable, deterministic software, what exists in the code today, and where it goes from here.
Reason when needed. Preserve what works.
Everything is public on GitHub. Here’s what that means today.