v2.2.2

OutlookAI v2.2.2 — Settings apply to every user

Settings now saves for every user on the machine. The model, reasoning effort, write tools and admin password are saved in C:\ProgramData\OutlookAI\config.xml, and each user picks them up the next time Outlook starts.

• Settings used to also save a copy in the %APPDATA%\OutlookAI\config.xml of whoever was signed in, and that copy kept overriding later changes for that user (for example a model you switched everyone to, or a new admin password). The ProgramData file now wins over those copies, so nobody needs their model reset.
• Settings opens on what's saved now and saves only what you change (for write tools, only the tools you switched on or off), so two admins (or two Outlook windows) don't undo each other's changes.
• When the saved model has retired, Settings shows its replacement but saves it only if you pick it in the list and click Save AI Settings.
• A failed or interrupted save leaves the previous settings intact, and Settings says so instead of showing "Saved.". Unchecking every write tool now stays that way when Settings is reopened.
• After the first Settings save, the ProgramData file holds all five of these settings. To change one by hand, edit that file, not C:\Program Files\OutlookAI\config.xml.
• If Settings rejects your admin password after updating, use the one in C:\ProgramData\OutlookAI\config.xml.
• If you ever go back to a version before v2.2.2, the old per-user copies override again; delete them first.

Also fixed

• A 32-bit Outlook now reads C:\Program Files\OutlookAI\config.xml (it looked in Program Files (x86)).
• The installer grants Authenticated Users access to C:\ProgramData\OutlookAI by SID, so it also works on non-English Windows, and warns if that fails.

v2.2.1

OutlookAI v2.2.1 — Updates keep your settings; "None" effort is now "Auto"

Installs and updates keep your settings. This applies to the update to v2.2.1 itself, because the in-app updater runs the new installer.

• C:\Program Files\OutlookAI\config.xml stays exactly as it was, and is still backed up to C:\ProgramData\OutlookAI\Backups first. Hand-set values such as <MaxBulkExportRows>, <VoiceModel>, <Model> and <ModelCatalogClientVersion> now survive updates. A missing <CodexAuthPath> is added.
• Servers still on a v1 (Claude-era) config get the v2 template, with the admin password carried over. A fresh install, or a reinstall after uninstalling, carries over the admin password, model and client-version pin from the newest backup, as before.
• If an install stops partway (for example, antivirus blocks a file), config.xml is still in place, and running the installer again keeps it. A config.xml that isn't valid XML, or that can't be changed (read-only), is left as it is with a warning, and the install carries on.
• Per-user settings (%APPDATA%\OutlookAI\config.xml, written by Settings → Save) are no longer renamed away on every install or update. Only v1 (Claude-era) per-user files are retired. A per-user file overrides the server defaults for that user, including the admin password in effect when it was saved. Delete it to put the user back on the server defaults, for example after changing the admin password.

The "None" reasoning effort is now called "Auto". It always meant "send no effort and let the model use its default" (medium today), not "no reasoning". Configs that say None keep working and show as Auto. Settings still saves it as None in config.xml, so servers still on an older version read it the same way. In the chat panes, the first entry in the effort list is now "(from Settings)", which uses the effort saved in Settings.

v2.2.0

OutlookAI v2.2.0 — Update Models

New: Settings → AI Behavior → Update Models. The model list and each model's reasoning efforts now come from the model catalog ChatGPT publishes for your account. New OpenAI models and effort levels show up without an OutlookAI release.

• Uses your existing ChatGPT sign-in. The list is cached in C:\ProgramData\OutlookAI\models.json and shared with every user on the server, with a per-user fallback in %LOCALAPPDATA%\OutlookAI\models.json. Other users pick it up the next time Outlook starts; open task panes refresh their effort lists right away.
• ChatGPT only lists models that the current Codex CLI supports, so the refresh identifies as the latest Codex release (looked up on GitHub). If api.github.com is blocked, pin a version with <ModelCatalogClientVersion> in C:\Program Files\OutlookAI\config.xml. Installs and updates keep that pin.
• Only efforts the API accepts are offered. Catalog-only modes such as Codex's ultra are filtered out. The GPT-6 and GPT-5.6 models get a new Max effort.
• GPT-5.5 retires 2026-10-14. Settings shows the retirement date next to the model. After that date, requests move automatically to the announced replacement (gpt-5.6-sol) until you pick a new model. A model that is merely missing from ChatGPT's list is never treated as retired.
• A reasoning effort that the selected model doesn't accept is now omitted (server default) instead of failing the request.
• The built-in list has been refreshed to the models ChatGPT accounts can use today: gpt-6-astra, gpt-6-sol, gpt-6-luna, gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna and gpt-5.5. Removed: gpt-5.5-pro, gpt-5.4, gpt-5.4-mini, gpt-4.1-mini, gpt-4.1-nano and gpt-5.3-codex.
• Updates keep the model already set in config.xml. A fresh install uses the top model in ChatGPT's list.

After updating: Settings → AI Behavior → Update Models → pick a model (GPT-5.5 retires Oct 14) → Save AI Settings.

v2.1.3

OutlookAI v2.1.3

Maintenance release: bulk-export polish, a new export column, and a fixed CI release pipeline. No breaking changes; upgrade via Settings -> Updates -> Check Now -> Install Update.

Fixes & improvements

• Bulk export respects the 10,000-row cap. outlook_export_search_results now shares a single row-cap constant with the interactive outlook_export_excel path, so a high admin-set MaxBulkExportRows can no longer produce a workbook larger than the interactive tool permits. (#12)
• New folder export column. Bulk search-result exports can now include the folder each message lives in. (#12)
• Reliable release CI. The release workflow is now publish-only/verify-only: it validates that a published release is well-formed (both assets present + SHA256 matches its sidecar) instead of attempting a VSTO build the GitHub runner can't perform. (#9)

Internal

• Documented the count/search consistency window in the bulk-export tool (accepted by design). (#12)
• Serialized the Config-mutating test classes to remove a parallel-test race. (#12)
• Tests: 633 -> 636.

Full changelog: v2.1.2...v2.1.3

v2.1.2

OutlookAI v2.1.2 - complete bulk exports + search truncation feedback.

Fixes / features

• No more silently-truncated exports. outlook_search_messages now reports total_matches and truncated, so the assistant knows when a result was capped (hard cap 100) instead of silently exporting a subset. This is what caused an attorney to "hit the cap" on a large export in v2.1.1.
• New complete-list Excel export. When you ask for "all" / "every" / "a list of" / "a spreadsheet of" matching messages, the assistant uses a new server-side tool that counts the true total and collects up to a configurable ceiling (default 2,000 rows) in one pass, then tells you "exported N of M" so nothing is silently dropped. Columns: subject, from, to, received_at, snippet, has_attachments.
• Admin-tunable ceiling via MaxBulkExportRows in the global config.xml (default 2000).

Install

1. Download OutlookAI-v2.1.2-RDS-Deploy.zip below. Right-click -> Properties -> Unblock before extracting.
2. Verify integrity (optional): (Get-FileHash OutlookAI-v2.1.2-RDS-Deploy.zip -Algorithm SHA256).Hash should match OutlookAI-v2.1.2-RDS-Deploy.zip.sha256.
3. Extract anywhere on the RDS host; run Install-OutlookAI.ps1 elevated. Or use the in-app updater: Settings -> Updates -> Check Now -> Install Update.

Note

Built locally on the dev box; the CI release workflow is still blocked by issue #9 (windows-2025 runner has no Office, so VSTO COMReference can't resolve). Same publishing flow as v2.1.0 / v2.1.1.

Commit: 2d60958
SHA256: 58fc961b3e5a39122bf463300c0000ca1f57c3ce2873532d62bbe61aa3e06803

v2.1.1

OutlookAI v2.1.1 — first update test of the in-app updater shipped in v2.1.0.

Fixes

• UNC export failure on RDS with redirected Documents. ExportPathResolver now detects UNC and falls back to %LOCALAPPDATA%\OutlookAI\Reports (always machine-local, always writable). Previously every export under a UNC-redirected Documents folder was hard-rejected with "UNC paths are not permitted." See #2 / #4.
• Admin settings did not propagate to other users on the RDS. Added a C:\ProgramData\OutlookAI\config.xml shared-admin-defaults layer between the server-authoritative global config and the per-user AppData override. When the admin (on the RDS) saves "ReasoningEffort = Medium" (or any user-tunable field), all users on the host pick that up as their default on next launch. Per-user override still works for any user who wants their own value.

Install (manual via running v2.1.0 Settings -> Updates -> Install Update)

Click Check Now in v2.1.0's Settings -> Updates section. You should see "Update available: v2.1.1". Click Install Update, accept UAC, watch the installer. Outlook closes; reopen and verify Current: v2.1.1.

Install (fresh install or manual)

1. Download OutlookAI-v2.1.1-RDS-Deploy.zip below.
2. Verify integrity (optional): (Get-FileHash OutlookAI-v2.1.1-RDS-Deploy.zip -Algorithm SHA256).Hash should match the contents of OutlookAI-v2.1.1-RDS-Deploy.zip.sha256.
3. Extract anywhere on the RDS host. Right-click the ZIP -> Properties -> Unblock before extracting.
4. Run Install-OutlookAI.ps1 from the extracted folder, elevated.

Note

Built locally on the dev box; CI release workflow is still blocked by issue #9 (windows-2025 runner has no Office, so VSTO COMReference doesn't resolve). Same workflow as v2.1.0.

Commit: d8ee686
SHA256: 912af614bfce49ef810fd4f4ff72dd28feaba1710ffe68796f0072463514d866

v2.1.0

OutlookAI v2.1.0 — first release with in-app updater.

What's new

• Settings -> Updates section: check for new releases, see current/latest version, install with one click (UAC + RDS confirmation dialog).
• New Services/Updates/ namespace: UpdateManifest, SemVer, VersionComparator, GitHubReleaseClient, UpdateDownloader, UpdateInstaller, UpdateHistoryLog, UpdateStartupReconciler.
• version.json baked into the deploy ZIP and copied into the install dir so the add-in knows its own tag.
• ThisAddIn.Startup reconciles the in-progress sentinel against the installed tag (clears on success or after 30 min staleness).

Install

1. Download OutlookAI-v2.1.0-RDS-Deploy.zip below.
2. Verify integrity (optional): (Get-FileHash OutlookAI-v2.1.0-RDS-Deploy.zip -Algorithm SHA256).Hash should match the contents of OutlookAI-v2.1.0-RDS-Deploy.zip.sha256.
3. Extract anywhere on the RDS host.
4. Run Install-OutlookAI.ps1 from the extracted folder, elevated. Outlook will be closed for ALL users on the RDS during install.

Note

This release was built locally on the dev box rather than on CI. The release.yml workflow tried to build on a windows-2025 runner but failed because that runner image doesn't have Microsoft Outlook installed, so the project's COMReference entries for the Outlook/Office type libraries don't resolve. Future releases will use a fixed workflow.