QuickFlow
A folder of workflow files a colleague can run right without reading them first.
Free right now. No account, no card
Preview
1 interface design, then a screenshot of it running. Drag, scroll or use the arrows.
Free while we’re in preview
Get QuickFlow
A folder of workflow files a colleague can run right without reading them first.
The Mac button is for Apple Silicon. On an older Intel Mac, get this one instead.
One file, both ways. Double-click it for the window. Run the same file from a command prompt with arguments and it behaves as the command-line tool, because the engine is inside it. Nothing else to download and nothing to keep beside it.
Early preview. The window has been built and run, but not yet on a real Windows PC or Mac, so expect rough edges. The engine underneath it is fully tested.
- One file, no installer
- Runs on your machine, offline
- Source code published below
Free while in preview. It isn’t signed yet, so Windows or macOS will ask you to confirm the first time you open it. here is exactly what to click. At launch, QuickFlow is included in every plan along with the rest of the range.
Declared inputs, checked before anything runs
A workflow is one JSON file in a shared directory. It declares its parameters (string, int, bool or enum) with types, defaults, allowed values and whether each is required, then lists its steps in order. quickflow describe onboard-teammate prints all of that, so somebody who has never opened the file still knows what it wants.
Supply the wrong type, a value outside an enum, or a --set key the workflow doesn’t declare, and QuickFlow reports every problem at once and exits before a single step executes.
No shell, anywhere
Each step is handed to the operating system as an explicit argument vector: the command, plus each argument as its own element. QuickFlow never joins strings into a command line and never invokes sh, bash or cmd.exe. A parameter value of ; touch /tmp/pwned ; reaches the program as one argument containing exactly those characters. The quoting in dry-run output is cosmetic.
run is a dry run until --apply. An applied run appends one JSON line to a ledger with the resolved parameters, every step’s final argv, per-step status and exit code.
That ledger is append-only but not tamper-evident, and parameter values land in it verbatim. Don’t pass a password or token as a parameter yet.
Questions about QuickFlow
What does QuickFlow do?
QuickFlow keeps your team's jobs in one shared folder. A job carries its own name, the answers it needs from whoever runs it, and the list of things it does — so somebody who has never seen it can still run it correctly. Running one always shows you everything it is about to do first, and nothing happens until you say so. Every real run is written down.
Will QuickFlow delete my files?
QuickFlow does not change your files itself. It runs the command you gave it when a rule matches, so what happens to a file is whatever that command does. Try a new rule against a copy first. Without an explicit go-ahead it only lists what it would run.
Does QuickFlow send anything over the internet?
No. There is no network code compiled into QuickFlow at all, nothing in the binary can open a socket. 88 of the 100 programs here are like that.
Does QuickFlow run on a Mac?
Yes. There are builds for Apple Silicon and for Intel Macs, as well as for Windows and Linux, one file each, with no installer and nothing to uninstall.
Is QuickFlow free?
Yes, while Techlosoft is in preview: no account, no card, and nothing switched off. Later it is part of a plan covering all 100 programs rather than sold on its own, and anything you download now carries on working.
Reading on the job itself
- How to run something automatically when a file appears in a folder Wait for the file to stop changing before you act on it. A watcher that fires the moment a file appears wil...
Advanced & technical details Command-line builds, source code, checksums and a recorded session, for developers and IT teams
A working CLI prototype of the shared workflow library: workflows are templates with declared, type-checked parameters, so a colleague can run one correctly without reading its internals, and every applied run is appended to an audit ledger. Steps execute via an explicit argv and never through a shell — verified that values like “; touch …”, “$(…)” and backticks arrive as literal strings and execute nothing. Approval gates and secret handling are on the roadmap.
Recorded session
Naming status
Working name only — brand verdict **RENAME** (High). Collision: QuickFlow. Rename before launch.
What it draws on
Existing paid software whose best ideas shaped this program: PhraseExpress, Macro Express Pro, Jitbit Macro Recorder, ClipboardFusion Pro.
Command line
There is nothing extra to install. The program you download is the command-line tool as well: give it arguments instead of double-clicking it and it runs as one, with its output on your terminal. The standalone builds below are the same engine on its own, for machines where you would rather not ship a window at all.
quickflow 1.0.0 - shared, parameterised workflow library with a run ledger
USAGE
quickflow list --library <dir> [--json]
quickflow describe <name> --library <dir> [--json]
quickflow run <name> --library <dir> [--set key=value ...] [--apply]
[--ledger <run.jsonl>] [--json]
quickflow validate --library <dir>
quickflow help | -h | --help
COMMANDS
list List every workflow in the shared library with its parameters.
describe Show one workflow in full: parameters and steps.
run Validate parameters, substitute them into each step, then run.
DRY RUN BY DEFAULT - nothing executes without --apply.
validate Report every structural problem in the library at once.
FLAGS
--library <dir> Directory of workflow .json files (required).
--set key=value Supply a declared parameter. Repeatable.
--apply Actually execute the steps. Without it, run is a dry run.
--ledger <path> Append the run record to this JSONL file (default
<library>/quickflow-ledger.jsonl). Applied runs only.
--json Machine-readable output.
SAFETY
Steps run via an explicit argv (command plus argument list). Parameter values
are never passed through a shell, so metacharacters such as ; $() and
backticks are delivered to the command as literal text.
EXIT STATUS
0 success 1 usage error, validation failure, or a failed stepRecorded from the shipped binary, not written by hand.
Source
Every file the program is built from:
console.go · console_test.go · guided.go · main.go
SHA-256 checksums · build instructions & scope notes · full build plan