TensorPM v1.10.0-beta.2 (Beta)

Changelog - v1.10.0-beta.2

New Features

Microsoft 365 connector

TensorPM can now connect to Microsoft 365 work and school accounts through
Microsoft Graph. This adds a first-class path for teams that keep their project
communication in Outlook and Microsoft calendars.

What Changed:

• New Microsoft 365 connector in the connector setup flow
• Secure Microsoft sign-in with OAuth and MSAL
• Mail sync through Microsoft Graph, alongside the existing email connector
• Microsoft 365 connector status is visible in the project connector overview
• Admin-consent guidance is included for organizations with restrictive
  Microsoft tenant policies
• Tokens are stored locally on the device; TensorPM never stores a Microsoft
  password

User Benefit:
Connect TensorPM to a Microsoft work account without IMAP setup. Project mail
can flow into the same intake pipeline users already know, with a setup flow
that matches enterprise Microsoft environments.

Calendar-aware TensorPM agent

The TensorPM agent can now work with Microsoft 365 calendars when calendar
access is enabled for a project connector.

What Changed:

• New optional calendar capability for Microsoft 365 connectors
• Calendar access uses incremental Microsoft consent for calendar permissions
• The agent can inspect real calendar availability before suggesting dates
• The agent can prepare new calendar events or changes to existing events
• Calendar proposals appear directly in chat with event details and an
  "Approve & Apply" action
• TensorPM applies calendar changes only after explicit user approval
• Failed calendar updates can be retried from the proposal state

User Benefit:
Ask the agent to find a meeting slot, prepare a project review, or adjust an
event without manually checking the calendar first. TensorPM keeps the final
write under user control, so calendar changes are never silently pushed.

Graph reply threading for mail

Mail replies created through the agent now use the Microsoft Graph reply path
for Microsoft 365 messages.

What Changed:

• Reply drafts are associated with the original Microsoft 365 message
• Sent replies stay in the correct mail conversation where Graph metadata is
  available
• Mail and calendar agents share the same connector availability model, so
  tools appear only when the project actually has the required connector role

User Benefit:
AI-assisted mail replies fit back into the original Outlook conversation
instead of becoming detached follow-up messages.

Project creation from prompts and documents

The welcome/onboarding flow can now create a project from a description,
attached documents, or both at the same time.

What Changed:

• Add documents directly in the first project creation screen
• Combine a written project description with PDFs, Word files, spreadsheets, or
  other supported documents
• See selected documents, token usage, and token-limit feedback before
  generating the project
• Remove or add more documents before starting generation
• Document-only project creation is supported when the files already contain
  enough context
• The project generation prompt now receives both the typed description and the
  extracted document context

User Benefit:
Start from real project material instead of a blank form: upload a brief,
proposal, protocol, or spreadsheet, add a short instruction if needed, and let
TensorPM build the initial project context from both sources.

Independent panel and dashboard chats

The AI panel chat and dashboard chat now maintain separate active chat
surfaces.

What Changed:

• Panel and dashboard chat selection are tracked independently
• Streaming state, cancellation, rate-limit banners, and background updates are
  associated with the correct chat instance
• Chat selection persists per project, so reopening a project restores the
  right conversation surface
• Background chat events no longer take over the visible chat unexpectedly

User Benefit:
Use the dashboard assistant and the side panel assistant without losing context
or having one surface interrupt the other.

Improvements

Connector architecture prepared for more integrations

• Connector handling now uses a registry-style abstraction for connector types,
  roles, credentials, intake sources, and availability checks
• IMAP email and Microsoft 365 mail share more of the same intake path
• Connector credentials are handled through a dedicated service
• Project-scoped connector roles make it clearer which tools are available for
  each project

User Benefit:
Microsoft 365 lands as a real connector family, not a one-off integration. This
keeps setup, status, intake, and future connector capabilities more consistent.

Calendar proposal safety

• Calendar create and update requests are stored as local proposals first
• The approval system blocks calendar writes unless the user approved the exact
  proposal
• Repeated apply attempts are guarded so a proposal is not applied twice
• Calendar Graph errors are shown on the proposal state
• The calendar agent cannot bypass the chat approval step

User Benefit:
The agent can help with scheduling, but users stay in control of the real
calendar.

Better chat attachment handling

• Chat file attachments received a visual and interaction refresh
• PDF attachments can be opened in a lightweight chat preview
• Attachment validation now recognizes additional document file types
• Chat input tests cover the updated attachment behavior

User Benefit:
Files attached to AI conversations are easier to inspect and harder to send in
an invalid state.

Window and chat state resilience

• Window state is saved and restored more deliberately
• Chat streaming events are routed by chat instance, reducing stale or
  cross-surface updates
• Cancelled streams clean up their callbacks more reliably
• Rate-limit messages stay attached to the chat instance that caused them

User Benefit:
TensorPM feels steadier during long AI runs, window restores, and multi-chat
workflows.

Bug Fixes

• Fixed cases where dashboard and panel chat state could interfere with each
  other during streaming, cancellation, or background updates
• Fixed Microsoft Graph token refresh handling so a Graph operation can retry
  once after a 401 with a fresh token
• Fixed connector availability checks so mail and calendar tools are hidden
  when the current project has no active matching connector
• Fixed calendar update handling so empty or whitespace-only updates do not
  produce invalid Graph patch requests
• Fixed calendar proposal failure handling so rejected Graph writes mark the
  proposal as failed with a visible error
• Fixed onboarding generation paths so document-only and prompt-plus-document
  project creation both reach the project generator correctly

Internal Quality

• Added unit coverage for Microsoft OAuth descriptors, token cache handling,
  OAuth service behavior, Graph request handling, and connector IPC
• Added tests for Microsoft 365 mail sync, ingest, connector configuration, and
  built-in connector registration
• Added calendar service, calendar agent, calendar executor, proposal storage,
  and calendar approval tests
• Added an integration test that verifies calendar proposals cannot reach
  Microsoft Graph before user approval
• Added onboarding and wizard tests for document-backed project creation
• Added chat state and chat selection storage tests for independent chat
  surfaces
• Added a developer smoke script for Microsoft sign-in flows

Notes

• This release supersedes v1.10.0-beta.1. The beta.1 tag was created, but the
  GitHub release workflow did not complete because the CI typecheck process ran
  out of memory on the runner.
• Microsoft 365 calendar support is opt-in per connector. Users must enable the
  calendar capability before the TensorPM agent can access calendar data.
• Organizations with strict Microsoft tenant policies may require an IT admin to
  grant admin consent before users can connect TensorPM.
• Calendar delete operations are not included in this release. The new calendar
  capability covers reading availability, creating events, and updating events.
• This release includes a local database migration for calendar event proposals.
• The release typecheck now runs with a larger Node heap to avoid CI runner
  out-of-memory crashes during the TypeScript check.

---

Release Info

• Version: 1.10.0-beta.2
• Release Date: 2026-06-13
• Previous Version: 1.10.0-beta.1
• Type: Patch (Beta) Release