REFLUX
Sign in Contact sales Request demo

0.5    -  Changelog

Visible distillation train

Reflux's default showpiece workflow now rebuilds a multi-column Aspen Plus train in the foreground, step by step. It starts from verified PSE/LAP24 chemistry, clears the flowsheet, places three RadFrac columns, connects feed, recycle, product, pump, and letdown valve paths, then runs and saves a reusable backup case.

This is still a deterministic demo path, but it is much closer to the product shape Reflux is aiming at: an engineer can watch native simulator work happen, inspect the transcript, and review the produced case instead of trusting a hidden script.

Reviewed runs
Visible T5 distillation Saved visible_t5_distillation_demo.bkp
Reset active worksheet Blank sheet confirmed before build
Viewport refresh pass PFD redraw, zoom full, ribbon compensation
Aspen Plus foreground build
Blocks 3 columns + pump
Mode Visible Real Run
Output Saved .bkp
The changelog preview mirrors the foreground simulator behavior without embedding a fragile screenshot.

What's included

  • Seed-backed chemistry so the visual build starts from a known-good case.
  • Foreground Aspen Plus progress for block, stream, connection, configure, run, and save steps.
  • Viewport hardening that keeps the PFD drawing surface in frame during the demo.

0.4    -  Changelog

Visible execution for simulation studies

Reflux now presents simulator work as a sequence of reviewed, visible steps: reading case files, planning the change, producing generated helpers, running the simulation, and summarizing the output.

The simulator remains the source of truth, while the agent's work becomes inspectable enough for process teams to trust before anything meaningful is changed.

Transcript opened Aspen Plus case drafted reviewed plan created FLASH, FEED, VAPOR, LIQUID ran simulation saved generated backup and summarized products

What changed

  • Reviewed tasks can change the visible plan, files, and report state.
  • Generated files are exposed as separate reviewable artifacts.
  • Preview panes highlight the exact rows and sections being discussed.
Read the article ->

0.4    -  Changelog

Request access flow for early teams

Early Reflux usage is routed through a lightweight request flow so simulation teams can share context before anyone touches a real simulator workflow.

The same access request nudge now appears from product-like demos, CLI prompts, and contact calls to action. That keeps curiosity in the page while making the next step explicit.

What changed

  • Prompt demos reveal a request-access message after a user enters text.
  • The contact page collects role, company, email, use case, and message details.
  • The flow works on a static site without adding a backend dependency.
Read the article ->

0.3    -  Changelog

Reviewed plans before simulator changes

The workflow now emphasizes a review gate before meaningful simulator actions, so teams can approve intent before execution. Reflux frames every edit as a plan, then requires an explicit confirmation point before native case mutation.

That gives reviewers a plain-language record of the intended engineering change and keeps prompt interpretation separate from simulator state changes.

Why it matters

  • Plan fingerprints bind approval to the exact executable plan.
  • Dry runs can validate shape, template choice, and output warnings first.
  • Process teams get a review artifact that matches the saved simulator work.
Read the article ->

0.3    -  Changelog

Workflow context for repeatable studies

Reflux examples now describe reusable engineering paths instead of one-off scripts, which better matches how teams repeat and audit studies across adapters.

The public surface connects context collection to reviewable plans, deterministic template paths, simulator adapters, and future changelog automation from merged, user-facing product work.

What's next

  • Keep filtering public notes to merged work tagged changelog or user-facing.
  • Continue expanding the Aspen Plus, HYSYS, Aveva Pro II, and GWB adapter surfaces without coupling their models.
  • Use human review before publishing generated changelog drafts.
Read the article ->