Wispr Flow: Dictation That Works EverywhereStop typing. Start speaking. 4x faster.
Promoted
Fluxerv
Notes that run code
13 followers
Notes that run code
13 followers
Fluxerv turns developer notes into interactive AI-generated tools, components, calculators, formatters, and shareable technical workspaces.
Free Options
Launch Team / Built With
@mpanpalli This sounds like a really helpful tool! I'm personally not at the point where it's an issue but I can see it coming - will definitely take it for a spin. Congrats on your launch!
@anna_ludwinowski Thank you Anna! Really appreciate the kind words. When you get to that point, would love to hear what you think.
Congrats on the launch! The "note and tool living in different places" problem is so real, I've lost count of how many times I've sketched something in a notes app, then had to context switch into an editor and lose half the idea translating it. Curious how you're handling state for more complex components, like a multi-step calculator, does it persist across sessions or is it more single-use per note?
@nayan_joshi Thank you Nayan! That context-switch cost is exactly what Fluxerv is trying to reduce.
On persistence: the generated component is saved as part of the document, so it is not a one-off output or a temporary preview. It lives inside the note until you remove it.
Shared pages support this too: if you share a Fluxerv page, someone can open the link and use the embedded component directly, not just read a static note.
Runtime input state depends on the component. Some tools are lightweight session tools, while others can be generated or refined to store state in browser storage when
persistence is needed.
Longer term, I’m thinking about making persistence an explicit option for more complex calculators, planners, and collaborative use cases.
@nayan_joshi Here’s a shared example of a working calculator embedded in a Fluxerv page: https://www.fluxerv.com/share/4131febf-08e4-4171-aa25-618c8f3daa21
You can open it and interact with the component directly in the page.
The component itself is saved with the document; runtime input persistence depends on how the component is generated/refined.
Scarlett.
Congrats on the launch, Memduh!
Why would someone use Fluxerv instead of asking Claude, ChatGPT, or Cursor to generate the same component or calculator?
Is the key difference that Fluxerv keeps the note, generated code, and interactive tool in one shareable workspace?
@byalexai Exactly that. The difference isn't the generation, it's where the output lives.
With Claude or ChatGPT you get code back. You still have to copy it, run it somewhere, and keep track of which version matches which note. The context and the tool are always in separate places.
With Fluxerv the component appears inside the document as it generates. The note, the tool, and the thinking behind it are all on the same page. You can share the whole thing as one URL and whoever opens it sees a working tool, not a code block.
A calculator is just one example. An educator can design an entire interactive lesson with AI, embed quizzes or simulations directly in the document, and share a single link with students. No extra tools, no copy-pasting outputs.
The generated component's code is also fully visible inside the document, so you always know exactly what was built. In an upcoming version, pushing that code directly to a GitHub repo will be part of the workflow.
It's less about replacing AI assistants and more about where the output ends up.
Quick demo update: I added a short video showing what Fluxerv actually does.
I typed /ai inside a note and generated a working World Cup-style group standings calculator with live score inputs, points, goal difference, and refine.
This is the core idea behind Fluxerv: notes that run code.