Memory
Planned cross-platform memory management and selected history injection.
Memory is the Orbital surface for managing reusable conversation history across platforms.
This surface is on the product roadmap.
Planned Capabilities
Memory is designed to support:
- Cross-platform memory management.
- Multiple memory types.
- Local continuity capsules or equivalent portable memory bundles.
- Selection of thread history for future use.
- Injection of selected history into supported platform conversations.
- Review and control before memory is reused.
Memory Types
Orbital supports more than one memory type because useful continuity has more than one shape. Possible categories include:
- Thread history
- Project context
- User preferences
- Assistant identity or relationship context
- Research notes
- Export packets
Specific memory types appear here as they become available.
Control Principle
Memory injection is explicit. Users can inspect what will be reused, choose when it is used, and understand which platform receives it.
The default posture is not "remember everything everywhere." The default posture is controlled local continuity.
Orbital memory data stays local unless the user chooses to inject selected memory or thread history into a chat platform.