rafal-fryc lets you pass a workflow around like a document

A built or customised workflow can now be saved to a file and loaded into another Mike instance, no shared account required.

workflowintegration

The pitch is portability. If your team has tuned a workflow and another team, environment, or organisation wants it, rafal-fryc's change lets you hand it over as a small file the way you'd email a Word doc. Today the only way to share is through the existing email flow, which this leaves untouched and simply adds a second channel alongside.

Three pieces make it work:

  • Export: every workflow in the list gets a download control that writes the whole thing - its title, type, practice area, prompt, and any column setup - out to a file.
  • Import: a new control at the top of the page opens a file picker and recreates the workflow under whoever uploads it, as a fresh copy they own.
  • Guardrails: a strict checker rejects a junk or malformed file and tells you what went wrong on the spot, rather than quietly importing garbage.

Deliberately, nothing touches the server or the database. The file is just inert data, so there are no cross-account permission questions to worry about.

So what Anyone running Mike across multiple teams or clients gets a clean way to standardise and reuse workflows without wiring up shared logins.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?