Memory System

The Nexus-Catalyst memory system is the foundation of cross-platform AI intelligence. Every conversation, solution, and decision is preserved and made available across all your AI tools.

How Memory Works

Automatic Storage

Every time you interact with a connected AI client, Nexus-Catalyst:

1. Analyzes the conversation for important information
2. Extracts key concepts (technical terms, decisions, solutions)
3. Stores a summary along with full context
4. Tags and categorizes for easy retrieval
5. Makes it available instantly across all platforms

Intelligent Recall

Before responding to your questions, the AI:

1. Searches your memories using semantic similarity
2. Ranks results by relevance to current context
3. Loads the most relevant memories into the conversation
4. References them naturally in responses

Memory Storage Tiers

Nexus-Catalyst uses a tiered storage architecture for optimal performance:

Tier 1: Summary Storage (Always Available)

• Quick Overview: 200-500 character summary of each memory
• Fast Retrieval: Optimized for <2 second response times
• Metadata Rich: Tags, dates, personas, projects
• Cross-Platform: Available on all connected clients

Tier 2: Full Detail Storage (On-Demand)

• Complete Context: Full conversation content
• Technical Details: Code snippets, error messages, solutions
• File Modifications: What files were changed
• Commands Run: Terminal commands used
• Retrieved When Needed: Via the get_memory_detail tool

Core Operations

Storing Memories

Automatic Storage (Recommended)

Simply have conversations - memories are stored automatically:

You: How do I implement OAuth in Laravel?
AI: [Provides detailed OAuth implementation guide]
    [Automatically stores this solution as a memory]

Manual Storage

Explicitly ask to store important information:

You: Please store a memory that our production database is PostgreSQL 15
     and we use Supabase for hosting.
AI: I've stored that memory about your production setup.

Recalling Memories

Memories are recalled automatically before every response:

You: How should I handle database migrations?
AI: [Automatically searches memories]
    [Finds: "production database is PostgreSQL 15"]
    [Responds with PostgreSQL-specific migration advice]

Searching Memories

Smart Search

Use natural language to find memories:

You: What did we discuss about authentication?
AI: [Searches all memories related to authentication]
    [Returns: OAuth setup, login flows, JWT tokens, etc.]

Filtered Search

Search by specific criteria:

You: Show me memories from the last week about the API project
AI: [Filters by: date range + project name]
    [Returns only relevant recent API memories]

Memory Metadata

Each memory includes rich metadata:

Field	Description	Example
Summary	Brief overview	“Laravel OAuth setup with Sanctum”
Content	Full conversation text	Complete Q&A dialogue
Timestamp	When created	“2025-01-20 23:45 ET”
Persona	AI personality used	“Jack (Backend Architect)”
Project	Related project	“api-gateway-v2”
Client	For consultants	“Ocean Township”
Tags	Categorization	[“laravel”, “oauth”, “security”]
Confidence	Relevance score	0.95 (highly relevant)

Memory Limits by Plan

All plans include unlimited memories — your data is never deleted automatically. Every plan starts with a 14-day free trial (card required at signup, first charge on day 14).

Pro Plan

Monthly: $9/month
Annual: $90/year (Save $18 - 2 MONTHS FREE)

• Unlimited memories
• Unlimited personas
• All integrations
• No automatic deletion
• Advanced search capabilities
• Export functionality
• Individual use only - no team features

Team Plan

Monthly: $14/user/month (3 user minimum)
Annual: $140/user/year (Save $28/user - 2 MONTHS FREE)

• Unlimited memories per user
• Department-level organization
• Shared memory within department
• Department admin controls
• Cross-department memory sharing options
• Project-based organization
• Advanced filtering and analytics
• Minimum 3 users per department

Enterprise Plan

Status: Coming Soon
Pricing: Custom

• Everything in Team
• Company-wide administration
• SSO integration (SAML, Active Directory)
• Cross-department memory sharing
• Advanced analytics and insights
• Custom retention policies
• Audit logs and compliance
• Data export automation
• Dedicated support

Department Organization (Team Plan)

The Team Plan introduces department-level organization for companies with multiple teams or functional areas.

How Departments Work

During Free Registration:

• Users register with just email and password
• No department selection required
• Company domain is detected automatically
• Notification appears if colleagues from same domain exist

When Upgrading to Team Plan:

• Users can either:
  • Join existing department (requires admin approval)
  • Create new department (becomes department admin)
• Department has its own subscription and billing
• Minimum 3 users per department required

Department Features

Shared Memory Within Department

All department members have access to:

• Memories stored by any team member
• Shared persona configurations
• Team-wide integration settings
• Project-based memory organization

Department Admin Controls

Department admins can:

• Approve/deny join requests from colleagues
• Manage department members and roles
• Configure memory sharing settings
• Set up department-specific integrations
• View department usage analytics

Cross-Department Memory Sharing

Departments can share memories selectively:

Department Only (Default - Secure):

• Memories stay within your department only
• Maximum security and privacy
• Best for sensitive projects

Selective Cross-Department Sharing:

• Choose specific departments to share with
• Requires mutual approval (both departments must enable)
• Example: Engineering ↔ Product collaboration

Company-Wide Sharing (Enterprise Only):

• Share across all departments at your company
• Requires Enterprise plan upgrade
• Ideal for organization-wide knowledge

Department Workflow Example

Scenario: Acme Inc has Engineering, Marketing, and Sales departments

1. Engineering Department (5 users):

   • Shares technical memories internally
   • Enables sharing with Product department
   • Keeps security-sensitive memories private

2. Marketing Department (3 users):

   • Shares campaign strategies internally
   • Enables sharing with Sales department
   • Product launch memories shared company-wide

3. Sales Department (4 users):

   • Shares customer insights internally
   • Receives product updates from Marketing
   • Access to public Engineering documentation

Company Domain Awareness

When users register with a company email:

Domain Detection:

• System detects @acme.com domain
• Checks for existing company and departments
• Displays notification about existing team members

Example Notification:

🔔 Good news! Other users from acme.com are already using Nexus-Catalyst.

Existing at acme.com:
- 3 users in Engineering department
- 2 users in Marketing department

Upgrade to Team Plan to collaborate with your colleagues.
[View Team Plans] button

Department Best Practices

✅ DO:

• Create departments by functional area (Engineering, Sales, etc.)
• Set clear memory sharing policies
• Review join requests promptly
• Use project tags for cross-department work
• Regularly audit department member access

❌ DON’T:

• Create too many small departments (use projects instead)
• Share sensitive client data across departments without review
• Ignore join requests from verified colleagues
• Forget to remove departing team members

Advanced Features

Cross-Project Memory Linking

Nexus-Catalyst can find similar solutions across different projects:

You: I'm working on a new React app and need authentication
AI: [Searches across ALL your projects]
    [Finds: Similar auth setup you did in Vue.js last month]
    [Suggests: Adapting that approach for React]

Memory Relationships

Memories are automatically linked:

• Similar Technical Topics: OAuth setup → JWT tokens → Session management
• Sequential Decisions: Architecture choice → Implementation → Testing
• Project Evolution: Initial design → Iterations → Final solution

Temporal Intelligence

The system understands time context:

You: What was our latest decision about the database?
AI: [Prioritizes recent memories]
    [Returns: Last week's PostgreSQL decision, not old MySQL discussion]

Best Practices

Effective Memory Storage

✅ DO:

• Store decisions with context: “We chose PostgreSQL over MySQL because…”
• Include technical details: “Using Laravel Sanctum with SPA authentication”
• Tag by project: “API Gateway v2 project”
• Be specific: “Production uses AWS RDS db.t3.large instance”

❌ DON’T:

• Store vague information: “Remember this”
• Duplicate existing memories unnecessarily
• Store temporary debugging notes (clean these up later)

Optimal Memory Recall

✅ DO:

• Use natural language: “What did we discuss about caching?”
• Reference projects: “In the Ocean Township project…”
• Specify timeframes: “What did we decide last week?”

❌ DON’T:

• Use exact keyword matching (semantic search is smarter)
• Assume chronological order (use explicit date references)

Memory Maintenance

Monthly Cleanup:

1. Review memories via dashboard
2. Delete outdated or irrelevant entries
3. Consolidate related memories
4. Update tags and project associations

Quarterly Review:

1. Archive completed projects
2. Export important memories for backup
3. Reorganize by current projects
4. Prune test/debugging memories

Technical Details

Storage Architecture

User Query → Recall Context
                ↓
    ┌───────────────────────┐
    │  Semantic Search      │
    │  (vector similarity)  │
    └───────────────────────┘
                ↓
    ┌───────────────────────┐
    │  Summary Retrieval    │
    │  (fast keyed lookup)  │
    └───────────────────────┘
                ↓
    ┌───────────────────────┐
    │  Relevance Ranking    │
    │  (Confidence Scoring) │
    └───────────────────────┘
                ↓
    Top-Ranked Memories Loaded

Performance

Recall and search are tuned for conversational latency — summary recall typically completes in 1–2 seconds, with full-detail retrieval on demand so session starts stay fast.

Data Encryption

• In Transit: TLS encryption
• At Rest: AES-256 encryption
• Embeddings: Stored as vector representations, separate from raw content

Troubleshooting

“Recall returning no results”

Possible causes:

1. No memories stored yet
2. Query too specific or uses uncommon terms
3. Memories filtered by project/client

Solutions:

• Try broader search terms
• Check memory count in dashboard
• Verify you’re searching across correct projects

“Memory not storing”

Possible causes:

1. Subscription lapsed (writes pause during payment retries; reads continue)
2. Network connectivity issues
3. Invalid authentication

Solutions:

• Check subscription status on the billing page
• Resume payment to restore write access instantly
• Verify MCP connection status

“Irrelevant memories returned”

Possible causes:

1. Similar keywords but different context
2. Tags/metadata not specific enough
3. Too many similar memories

Solutions:

• Add project context to queries
• Use more specific search terms
• Clean up and tag memories better

What’s Next?

• MCP Tools Reference → — tool parameters and workflow
• Linear Integration → — link memories to issues
• Troubleshooting → — connection and recall issues

---

Questions? See Common Issues or contact support.