EP Finance Autopilot
EP Finance Autopilot works through the review queue so you do not have to. It suggests; you approve. It never changes a figure on its own.
This page documents EP Finance Autopilot 0.1.7.
Published by ElmsPark Studio.
Requirements
Section titled “Requirements”- PageMotor 0.9b or later
- EP Finance, which holds the ledger this plugin reads and writes
- EP Finance Importer, which owns the review queue this works through
- EP Email if you want the weekly digest
What it will and will not do
Section titled “What it will and will not do”How it suggests
Section titled “How it suggests”History first. If you have categorised the same payee the same way three times, that is a better signal than anything a language model will tell you, and it costs nothing. An AI provider is used only where configured, and only where history has nothing to offer.
The weekly digest
Section titled “The weekly digest”Once a week you get an email listing what is waiting, with a one-tap approve link per item. Those links are signed and single-use, so one cannot be reused or altered to approve something else.
Learning from your corrections
Section titled “Learning from your corrections”When you correct a suggestion, the plugin proposes a rule. A rule is not switched on until you have accepted it three times, so a one-off does not become a standing instruction. Once a month it reviews the rules it has and reports any that have stopped matching reality.
Knowing whether it is any good
Section titled “Knowing whether it is any good”There is a scoreboard: how often its suggestions were accepted, and how that is trending. If the accuracy is poor you will see it rather than having to sense it.
Driving it conversationally
Section titled “Driving it conversationally”The same loop is exposed to any connected AI client, so you can work through the queue by talking to it instead of clicking. The same rule applies there: it suggests, you approve.
Changelog
Section titled “Changelog”- Fixes stored keys and passwords reading as empty after a PageMotor 0.11.3 or 0.11.4 update. After the core update, every secret this plugin had encrypted at rest came back blank, so anything that needed it failed with an authentication error until the value was typed in again. Nothing was deleted: the encrypted value was still in the settings row, but PageMotor 0.11.3 moved the site secret that opens it, and this plugin was still looking in the old place. It now finds the secret in both places, so an existing value opens again without re-entry, and a value that was re-entered in the meantime keeps working and is moved back under the site secret.
- If you updated PageMotor and then re-entered a key or password, there is nothing to do. If you updated and have not re-entered it, this release restores it on the next page load.
- Works with PageMotor 0.11.3 and stays compatible with earlier releases. PageMotor 0.11.3 changed how a plugin declares its API and MCP actions, and a plugin that still uses the old declaration has every one of its actions silently dropped from the registry on that version. This release declares its actions in the shape the running PageMotor expects, so an AI connected over API or MCP keeps every action whether the site is on 0.11.3 or on an earlier release.
- Actions are now grouped into families, so a connected AI that looks up one action is shown its siblings.
Released 1 September 2026.
- Some of this plugin’s actions used to appear as their own entries in the tool list of any connected AI client. That surface is reserved for PageMotor itself, so those entries have been removed.
- Nothing became unreachable and nothing else changed. Every action still works exactly as before through PageMotor’s own dispatch, with identical responses. Only a caller that had been invoking one of those names directly is affected, and it should dispatch through PageMotor instead.