# 1.0.22

- Link: https://blog.curbsoftware.com/changelog/v1-0-22/
- Published: 2026-09-02T14:00:00+00:00
- Author: curbsoftware

## Summary

PressedMail 1.0.22 rebuilds the AI settings screen around one provider and four

tools, stops calendar invitations going out through the site’s mail server, andgives
administrators a way to act on accounts that no longer match their domainpolicy.

## Added

 * Every AI tool now has its own card: turn it on, choose its model, and edit the

system prompt it runs on. Give tagging a small fast model and summaries a
stronger
one; the Composer card edits all eight of its writing prompts. Everyprompt has a
Reset to default.

 * A single switch that turns AI off for the whole site. Off means off: the

features stop running, not just stop appearing in settings.

 * The connected accounts list reports how many accounts are on domains the

managed-domain policy does not allow, and offers to remove them behind a
confirmation
that names the exact number.

## Changed

 * The AI provider is configured once, at the top of the tab, and every tool uses

it. The data-use notice appears there once instead of on each tool.

 * Google Gemini is no longer a separate provider. Sites configured for it are

moved to Gemini’s OpenAI-compatible endpoint automatically, with the same API
key,
and keep working.

 * The WordPress email settings now ask one question with two answers instead of

presenting an unlabelled checkbox, and say plainly that PressedMail inboxes
are 
unaffected either way.

 * Phishing detection is switched on with the other AI tools. Its security policy

stays on the Security tab.

## Fixed

 * Tag and signature capabilities reported a maximum and a remaining count for

limits that do not exist in any edition. Nothing was ever restricted, so the
payload
now simply says what you can do.

 * “Test Provider” called a working provider invalid when the model spent its

whole reply budget on reasoning before writing an answer. It now says so.

 * Auto-tagging reported a successful run that applied no tags when the real

cause was a refused request. The reason is reported instead.

 * Anthropic models could not be used at all. Every request carried a sampling

parameter that current Claude models reject outright, so the call failed
whichever
model was chosen.

 * Saving the AI provider overwrote every tool’s chosen model with the

assistant’s, so a cheaper model picked for tagging disappeared on the next
save.

 * Calendar invitations went out through the site’s SMTP server while carrying

the organiser’s address, a domain that server is not authorised for. They now
leave
through the organiser’s own mailbox, like every other message sent froman inbox.

 * Diagnostics showed “Managed by WordPress.org” on Pro and never asked the

licence server for the latest version, so the number it displayed was always
the
version already installed.

## Upgrade Notes

 * No action is required. AI stays in whatever state it was in: sites that had

tools switched on keep them switched on.

 * A site configured for Google Gemini keeps working on the same API key. Its

provider now reads as OpenAI Compatible.

 * Removing accounts on disallowed domains is always a deliberate action. Nothing

is deleted on save, and an account on an allowed domain whose server settings
have
drifted is never offered for removal.
