TensorPM v1.36.0
Changelog - v1.36.0
π New Features
Clear Four-Level Priorities
Action-item priorities now use four explicit levels β Low, Medium, High, and
Urgent β plus None for items that have not been prioritized yet.
What Changed:
- β Pick a named level instead of estimating a number on a 1β100 scale
- β Use the same levels in list, board, priority, filter, sorting, AI, MCP, and sync workflows
- β Keep unprioritized work separate from genuinely low-priority work
- β Preserve existing priorities by converting their former numeric bands automatically
User Benefit:
Priorities are faster to set, easier to discuss, and consistent wherever an action item appears.
ποΈ Improvements
Transparent AI Usage and Billing
The AI Activity view now explains model usage and billing independently instead of hiding token
counts behind a subscription or TensorPM tier label.
- Token counts remain visible for TensorPM AI, subscriptions, your own API keys, and failed calls
that already consumed tokens - Each activity shows whether it used TensorPM credits, a provider subscription, your own key, or
a local model - Cached input and reasoning usage are identified more clearly
- Tool calls use readable, localized names and distinguish active work from completed work
- Multi-model operations select the primary user-facing model more reliably
Gemini 3.7 Flash
Google AI connections and the TensorPM AI fallback now use Gemini 3.7 Flash in place of Gemini
3.6 Flash. Existing unsupported saved model selections fall back to the current provider catalog.
More Reliable Briefing Refreshes
Overlapping manual project-briefing requests now remain coordinated until every request has
finished. A scheduled check-in can no longer start in the gap created when an older cancelled
request settles before the newer request, preventing duplicate AI cost and stale content from
overwriting the requested briefing.
π Bug Fixes
Priority Sync and Migration Safety
- Invalid or future priority levels received from a synced workspace are safely cleared instead
of causing the complete action item to be rejected - Older clients continue to receive the preserved numeric priority representation
- Priority migrations keep sync timestamps and existing orphan diagnostics intact
- The migrated schema is validated against a fresh installation using real SQLite transactions
Priority Interaction Coverage
The Electron regression suite now exercises the actual priority level picker, its lock state, and
level-based sorting instead of the retired numeric input.
π Security
Document parsing now resolves to the patched PDF.js runtime used by TensorPM. Production
dependencies have no known high-severity audit findings at release time.
π Notes
- Existing action-item priorities are migrated automatically; no manual cleanup is required.
- Shared workspaces remain compatible with clients that still use the previous priority format.
- The first request after updating an AI provider may rebuild its prompt cache once.
π Release Info
- Version: 1.36.0
- Release Date: 2026-08-17
- Previous Version: 1.35.7
- Type: Minor Release