Rules & automatic organization

Describe where a kind of file belongs, once, and Picketdesk files it there from then on — on your command, on a schedule, or the moment it lands on the desktop.

You write the rules Picketdesk never crows before you do: a desktop with no rules stays exactly as you arranged it, and the Documents / Pictures / Downloads examples are there to edit rather than to obey — they arrive switched off, waiting for you to point them somewhere. Turn one on and it goes to work immediately, on what is already on your desktop and on everything that arrives next.

Anatomy of a rule

A rule combines:

How rules behave:

Example rule set:

RuleEffect
png, jpg + name contains screenshot → Screenshots Every new screenshot files itself.
pdf, docx, xlsx → Documents Office files head to a Documents picket.
zip, iso, dmg, older than 90 days → Archive A sweep tucks stale files away. Age and size are extra gates, not criteria of their own — a rule still needs extensions or a name fragment, or it matches nothing.
mp4, mkv, at least 500 MB → Big videos Heavy files become easy to spot and clean up.

Running the rules

Quick ways to make rules

A new rule also sweeps what is already there A rule does not only route files that arrive later: the next rescan offers it every unclaimed item on your desktop. So when you make a quick rule and matching files are already sitting there, Picketdesk says how many and asks first — “Move 38 .pdf file(s) here now, and new ones from now on”. Dismiss the popup and no rule is created. Without that question the sweep landed on the next rescan, minutes later and triggered by something unrelated, which read as the app moving files on its own.

Suggestions — analyzed locally

Self-cleaning pickets

Right-click a regular picket → Automation… → Enable self-clean. Choose 1–3,650 days and Recycle Bin or Folder, review the summary, then Save automation. Edits are not applied until saved. A sweep runs every 10 minutes in the primary desktop-controlling instance. Safe mode and isolated --profile instances skip self-clean, including its membership-age updates, and so does a read-only session (the one the warning box at launch describes): the layout it shows is not your saved one. Every expired file is logged (source → destination) to picket.log.

An item counts as old only when all three of its clocks are past N days: its last-modified time, its created time (a fresh copy of an old file is a new file — Explorer's copy keeps the old modified date), and the time the sweep first saw it in this picket (a same-drive move keeps both file dates, so only the membership age catches “moved an old file in yesterday”). A file you just dropped in is never swept on the first pass; items that predate this rule age from the first sweep after updating.

With your configuration kept in another folder (Settings → Move configuration to another folder…), a self-clean policy runs only once this PC has approved exactly it — its days and its destination, the Recycle Bin included — because anyone who can write that folder could otherwise set one. A policy you save here is approved as you save it, and moving the configuration approves the ones you already had. One that arrived through the folder is skipped (nothing is moved or recycled) and a notification says so once per launch: Automation… → Save automation on that picket allows it. If your configuration was already in another folder before this version, your own policies count as having arrived that way too: save each one once on each PC.

It only ever moves files that sit directly on your desktop; folders are skipped. A collection item that lives in one of your own folders — including a folder sitting on the desktop — is shown by the picket but never recycled or archived by the timer.

Every sweep is undoable. The toast names the first file and where it went — “Self-clean: “report.pdf” and 2 more → D:\Archive — tray → Undo last action” — and that one tray entry takes the whole sweep back. (Ctrl+Z in a picket does too, but the sweep runs on a timer and leaves no picket focused; pressed on the desktop, Ctrl+Z goes to Explorer and undoes your own last file operation instead.) Archived files are renamed home and re-filed into the picket they left, recycled ones come back from the Recycle Bin. A file whose desktop name has been taken by something else since is left where it is rather than written over it. The undo stack is session-only and 20 steps deep, so picket.log remains the record for anything older.

Archiving preserves files already at the destination, including one created during the move. It takes a numbered name such as report (2).pdf, and undo follows that name. A failed copy never removes a destination it did not create.

A destination on another drive works (the file is copied, then the original removed); the desktop itself is refused as a destination. The destination must be a full folder path on this PC, like D:\Archive: a folder name alone, a %USERPROFILE%\… path, C:Archive, a \\server\share path or a mapped network drive is refused when you save, because most of those would have landed inside Picketdesk's own program folder. Quotes from Explorer's “Copy as path” are removed, and the panel shows the path as stored. One an older version saved is refused by the sweep too, with the items left in the picket and a toast saying so once. If an item can't be moved — the destination folder can't be created, the file is held open, or the destination was inside a Desktop folder that OneDrive's folder backup has since moved and is no longer there (it is not re-created in the old place; the next launch re-links it once it has arrived, see Recovery) — it stays in its picket, hidden as before: picket.log names the reason, a toast says so once, and that item is left alone until the destination changes or the next start. The sweep never asks a question: recycling on the timer ignores Explorer's “display delete confirmation dialog” preference. It never deletes anything permanently either: when Windows would delete a file for good rather than recycle it (that drive has no Recycle Bin, the bin is off for it, or the file is bigger than the bin takes), the question Windows asks is answered No before it appears, the file stays in its picket, hidden, and a toast says why once — that item is left alone until the next start. Move such a file yourself, or give the picket a Folder destination.

Quick capture

Ctrl+Shift+N opens a note box anywhere: jot, then Ctrl+Enter saves it to your desktop as a Markdown file. Esc (or Alt+F4) closes the box and keeps what you typed for the next Ctrl+Shift+N; only a save empties it. Your rules route it like any other new file — a md → “Notes” rule gives you an instant inbox. Notes are named Note YYYY-MM-DD HH-MM.md on your local clock; a second one in the same minute becomes Note … (2).md, preserving existing files even if another app creates the name during capture. If the desktop cannot be written, the box comes back with your text, a retry message and a toast; clearing the box discards the draft and the message with it. While a save is pending, reopening shows the draft read-only with Saving…; another Ctrl+Enter cannot submit it twice.

Driving Picketdesk from launchers & scripts

While Picketdesk is running, a second picket-app.exe with a flag forwards the action to the live instance and exits — the standard channel for PowerToys Run, AutoHotkey, Stream Deck, or Task Scheduler:

FlagDoes
--toggleHide / show all pickets.
--peekToggle peek-over (pickets above every window).
--page "Gaming"Switch to a saved page (fuzzy match, snapshot first).
--palette "pin Work"Run one command-palette verb; the result shows as a toast.
--search "invoice -t pdf"Open the search overlay pre-filled.
--triageOpen the overlay straight into Inbox triage.
--new-picketCreate an empty picket.

The set is closed on purpose: no launcher flag accepts a file path or a command line, and none deletes anything. What a stray process spawning Picketdesk can reach is what you can do by hand: --page and --palette move desktop items into and between pickets (filing an item hides its desktop icon, as always), and loading a page opens the programs that page lists — at once only if this PC approved them for that page, otherwise after a box asks you. Each of those is undone the usual way (Ctrl+Z, the snapshot taken before a page loads). A second launch with no flags simply re-shows your pickets, as it always has — or, when there is no picket to show, opens the welcome box that offers to create one.