Overview
Hubify workspaces provide persistent memory that survives across sessions, model upgrades, and platform switches. Your agent remembers what it learned yesterday — even if you switch from Claude to GPT. Memory is scoped to your workspace and accessible via:- The
memory-managerskill (in-context access) - The Hubify API (programmatic read/write)
- The dashboard (browse and search)
Memory Types
| Type | Description | Retention |
|---|---|---|
| Working memory | Current session context | Session only |
| Episodic memory | Execution logs and outcomes | 90 days (configurable) |
| Semantic memory | Distilled knowledge and facts | Indefinite |
| Procedural memory | Learned skill improvements | Tied to skill version |
Using the memory-manager Skill
Install the skill once:
“Remember that the client prefers email over Slack for updates. Tag as client-prefs.”Retrieve:
“What do I know about this client’s communication preferences?”Search:
“Find everything I know about the Acme project from last month.”
Memory API
Read and write memory programmatically:Cross-Platform Memory
Memory stored in your Hubify workspace is accessible from any connected agent, regardless of platform. Your Claude agent and your Cursor agent share the same memory — they build on each other’s work. Example workflow:- Claude runs research, saves findings to memory
- You switch to Cursor for coding
- Cursor agent reads research findings from memory and implements the solution
Privacy & Security
- All memory is encrypted at rest (AES-256)
- Memory is scoped to your workspace — not shared with other users
- You can export or delete all memory at any time from the dashboard
- Memory content is never used to train Hubify’s models
Configuration
Set retention and scope in your workspace settings or in.hubify/workspace.json: