- Add withSupermemory wrapper section to OpenAI SDK docs
- Create new Claude Memory Tool integration page
- Replace gpt-4o with gpt-5 across documentation
- Fix normalizePathToCustomId in claude-memory.ts (customId validation)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Improved browser extension memory saving with better content handling and added markdown conversion.
### What changed?
- Enhanced memory content handling in the background script to prioritize different content types (explicit content, highlighted text, markdown, HTML, or URL)
- Added HTML to markdown conversion using TurndownService when saving entire pages
- Improved HTML handling by removing script tags before processing
- Updated the web app to display the saved URL from metadata when available
- Added turndown library and its type definitions as dependencies
### Added streaming support to the Supermemory middleware and improved memory handling in the AI SDK integration.
### What changed?
- Refactored the middleware architecture to support both streaming and non-streaming responses
- Extracted memory prompt functionality into a separate module (`memory-prompt.ts`)
- Added memory saving capability for streaming responses
- Improved the formatting of memory content with a "User Supermemories:" prefix
- Added utility function to filter out supermemories from content
- Created a new streaming example in the test app with a dedicated route and page
- Updated version from 1.3.0 to 1.3.1 in package.json
- Simplified installation instructions in [README.m](http://README.md)d
Removed React Compiler from the project configuration and dependencies.
### What changed?
- Removed `reactCompiler: true` from the experimental options in `next.config.ts`
- Removed `babel-plugin-react-compiler` dependency from `package.json`
- Updated formatting in `next.config.ts` to use consistent indentation and semicolons
### Why make this change?
React Compiler (formerly React Forget) is still in experimental phase and may be causing stability issues or unnecessary complexity in the build process. Removing it simplifies our dependency tree while maintaining full functionality. The PostHog update ensures we're using the latest version with any bug fixes or improvements.
### TL;DR
Added proper semicolons throughout the codebase, improved Twitter import functionality, enhanced memory search results display, and added various icon sizes for the browser extension.
### What changed?
- Added semicolons at the end of statements throughout the browser extension codebase for consistent code style
- Fixed the Twitter import button to only appear on the bookmarks page
- Updated the saveMemoriesToSupermemory function to use the correct action type
- Enhanced the memory search functionality to include related memories in search results
- Added an expandable UI component in the chat interface to display memory search results with details
- Updated the welcome page text to better describe supermemory's capabilities
- Added multiple icon sizes (48x48 to 512x512) for better browser extension display across platforms
- Updated the sign-in button text from "login in" to "Sign in or create account"
- Added turbo flag to the Next.js dev script for faster development
### How to test?
1. Test the Twitter import functionality by visiting the Twitter bookmarks page
2. Verify that the memory search functionality works correctly in chat interfaces
3. Check that the expandable memory results UI displays properly with memory details
4. Confirm that the browser extension icons display correctly at different sizes
5. Verify the sign-in flow with the updated button text
### Why make this change?
This change improves code consistency by standardizing semicolon usage throughout the codebase. It enhances the user experience by making the Twitter import feature more targeted and fixing the memory saving functionality. The expandable memory results UI provides users with more detailed information about their memories, making the search functionality more useful. The additional icon sizes ensure the extension displays properly across different platforms and contexts. Overall, these changes improve both the developer experience through consistent code style and the user experience through enhanced functionality and clearer UI elements.
