About Services Tools Blog Contact us

Folder Workflow Despatcher

A browser form saves a brief and its uploads into a dated job folder, and a helper program on a desktop computer hands that folder to the Cursor editor.

  • Agentic Workflows
  • Professional services
  • Pipeline
  • Product
  • Local/private
  • 2026

The problem

Repeat jobs depended on someone remembering the folder layout, the procedure and which tool to open. The brief and the files ended up in different places from the record of the run. So the next repeat of a job started with a search.

What it does

Each workflow has its own form. Submitting it creates a dated input folder holding the brief and the uploads. A helper program on a desktop computer, started from a signed-in session, takes waiting jobs one at a time and runs them through Cursor. Finished jobs go into an output folder with the record of the run.

Outcomes

  • Every submission gets a dated folder with the brief and the files together.
  • Only one job runs at a time, and a marker stops two helpers clashing.
  • A job can be seen moving from waiting to running to filed.
  • The next repeat of a workflow uses the same form.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

Weekly note

Harbour Wren
Brief
Attach hours.csv
Despatch
  1. Write the brief
  2. Create the dated folder
  3. Queue the job
  4. Take the worker lock
  5. File the output
Attach the hours file, then submit.

Standing report

Brief
Attach figures.csv
Despatch
Attach the figures, then submit.

Desktop worker

Lock free
Queued

Nothing waiting

Running

No job holds the lock

Filed
September close

2026-10-03-harbour-wren-weekly-note-september-close

output folder
This poll
The worker only runs from a logged-in desktop session.

How it works

  1. List the workflows and the form defined for each one.
  2. Submit the brief and the files into a dated input folder.
  3. The helper program marks itself busy and looks for waiting jobs.
  4. It runs one job at a time through Cursor.
  5. Finished jobs move to an output folder with the record of the run.

Pipeline

flowchart LR
  A[Form] --> B[Dated folder]
  B --> C[Queue]
  C --> D[Desktop worker]
  D --> E[Cursor run]
  E --> F[Output folder]