Hubs

A hub is a container for memories. Every memory belongs to exactly one hub. Hubs define the boundary for access control, search scope, and team collaboration.

Hub types

Personal hub

Every user gets a personal hub automatically. It's the default destination for all pushes unless you specify otherwise.

• Private by default — only you can see your memories
• Unlimited memories on all plans
• Accessible from any agent or device

Team hub

Team hubs enable shared knowledge across your organization. Create one for your team, project, or company.

# Create a team hub
memax hub create "Platform Team"

# Invite members
memax hub invite alice@company.com --role member
memax hub invite bob@company.com --role admin

# Push to the team hub
memax push -f ./runbook.md --boundary team --hub hub_xyz

Team hub features:

• Shared recall — all members can recall team memories
• Role-based access — admins, members, and read-only roles
• Push routing — optionally require a reason when pushing to team (hub_reason)
• Hub-scoped search — agents can search within a specific hub

Switching hubs

# List accessible hubs
memax hub list

# Switch your active read hub (affects recall results)
memax hub switch hub_xyz

# Check current hub
memax whoami

Hub routing

When you push content, Memax decides where it goes:

1. Explicit hub — --hub hub_xyz sends to a specific hub
2. Boundary hint — --boundary team routes to your default team hub
3. Default — goes to your personal hub

When you recall, Memax searches across all hubs you have access to, ranked by relevance. You can scope recall to a specific hub if needed.