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.