Skip to content

ContextPort 2.10.3

Choose a tag to compare

@DeerSpotter DeerSpotter released this 12 Jul 16:30
· 96 commits to main since this release
46f5a6e

ContextPort 2.10.3

Save Context Restored for ChatGPT and Claude

This release restores reliable conversation saving for ChatGPT and Claude and introduces custom naming when creating a new Memory.

What’s New

Custom Memory Names

When selecting Save as New Memory, ContextPort now:

  • Extracts and validates the conversation before creating the Memory.
  • Uses the existing AI chat title as the default Memory name.
  • Lets you replace the title with a custom name.
  • Provides a Use Chat Name button to restore the original detected title.
  • Prevents empty or whitespace-only Memory names from being saved.
  • Creates no Memory when the naming screen is canceled.

Adding a revision to an existing Memory continues to preserve the established Memory name.

ChatGPT Save Context Fixes

  • Restored authenticated conversation retrieval for current ChatGPT sessions.
  • Added support for the current access-token authorization flow.
  • Improved extraction of structured ChatGPT message content.
  • Preserved authenticated session cookies during conversation retrieval.

Claude Save Context Fixes

  • Added support for Claude’s current conversation and response containers.
  • Preserved compatibility with older Claude page layouts.
  • Improved message discovery inside supported shadow-root content.
  • Continued requiring verified user and assistant messages before saving.

Reliability Improvements

  • Provider extraction logic has been separated into smaller, maintainable modules.
  • Conversation validation remains fail-closed to prevent incomplete or incorrectly identified page content from being saved.
  • Existing Gemini, Grok, and DeepSeek Save Context behavior remains supported.

Version

  • Version: 2.10.3
  • Build: 82
  • Minimum iOS version: iOS 16

Installation

Download the unsigned IPA from the GitHub Actions artifacts and sign or install it using your normal iOS deployment method.