Repository navigation
ContextPort 2.8.0 - Share Context & Reliable Attachments
ContextPort 2.8.0
Share Context
Memory sharing has been redesigned around what ContextPort actually does.
The old Start New Chat workflow is now Share Context.
Choose where to share selected Memory:
- ChatGPT
- Claude
- Gemini
- Grok
- Current Conversation
Selecting an AI provider continues to prepare the Memory context for a new conversation.
Selecting Current Conversation keeps the conversation already open and prepares the selected Memory for the existing Paste Context and Attach Files workflow.
No more leaving the conversation you are already working in just to add Memory.
Cleaner Memory Sharing UI
ContextPort now uses consistent terminology throughout Memory:
Share Context
Share With
Current Conversation
The remaining Start New Chat wording has been removed from the Memory workflow.
Large Developer Source Attachments
ContextPort can now hand off much larger Memory attachments, including Developer Mode source archives.
The previous upload bridge could reject combined attachments above an internal aggregate size boundary.
Attachments are now streamed into the WebView in smaller chunks and reconstructed as complete browser File objects.
This reduces retained memory pressure and allows large ContextPort Developer Sources ZIP archives to reach supported AI providers.
Reliable Attach Files State
Fixed an issue where files successfully attached to an AI conversation but the ContextPort button remained stuck on Attach Files.
ContextPort was waiting for the provider UI to display every full filename before considering the upload successful.
This produced a false failure even when the files had already reached the conversation.
ContextPort now validates the browser file handoff using the exact:
- Filename
- Byte size
- MIME type
Once the browser has accepted the exact staged files, the pending attachment queue is cleared and the button returns to Save Context.
Provider UI detection remains available for paste and drag/drop fallback paths.
Provider UI Drift Detection
ContextPort now monitors the conversation UI structures used by Save Context.
Each provider extractor reports the UI markers it expects and the markers actually found.
ContextPort classifies extraction health as:
Healthy
The expected conversation structure matched. Context saves normally.
Safe Drift
The provider UI changed, but ContextPort still positively identified user and AI turns through a safe fallback.
Context can still save and ContextPort warns once for that UI change.
Unsafe Drift
ContextPort can no longer safely prove both sides of the conversation or detects a blocking challenge/interstitial.
Memory creation is blocked instead of saving questionable context.
The same detected UI change will not repeatedly alert on every Save Context attempt.
Developer Mode can be enabled directly from a drift warning so loaded provider sources can be captured for investigation.
Why This Matters
ContextPort Memory is designed to carry trusted context between AI conversations.
A visible export failure can be fixed.
Incorrect context saved silently into Memory can affect every future conversation that uses it.
ContextPort now validates the conversation boundary, monitors provider UI drift, supports large diagnostic source archives, and verifies attachment handoff before changing application state.
When ContextPort cannot safely prove the context is valid, it does not save it.
Thank you to everyone testing ContextPort on real devices and reporting exact behavior. The Claude exporter fix, provider UI drift monitor, large source attachment work, and attachment state correction all came directly from physical device testing.
Support continued ContextPort development: