Shared Memory

What is Shared Memory?

Shared Memory is like a team bulletin board for your digital twin. When someone adds information to Shared Memory, everyone using the same digital twin can benefit from it.

Simple way to think about it:

User Memory = Your personal notes (only you see them)
Shared Memory = Team notes (everyone sees them)

Your twin also keeps Long-term Memory — what it picks up on its own as you talk. It works alongside this, and does not replace it.

How It Works

Adding to Shared Memory

A twin admin can add information for the whole team:

Prompt

Remember for the team: All pull requests require two approvals before merging

The digital twin stores this, and now everyone on the team gets consistent guidance about code reviews.

Writing to Shared Memory is an admin capability. If a regular member asks the twin to “remember for the team,” the fact is saved to their own personal memory instead — it won’t reach other members. Every member’s conversations still read Shared Memory automatically.

Using Shared Memory

When someone asks a related question later, the digital twin automatically uses the shared information:

Prompt

How many approvals do I need for my pull request?

Response

According to your team's guidelines, all pull requests require two approvals before merging.

Real-World Examples

Development Teams

What to store:

Coding standards and style guides
Approved libraries and frameworks
Code review requirements
Deployment procedures

Example:

“Remember for the team: We use TypeScript for all new projects, React 18 for frontend, and require ESLint checks to pass before commits.”

Now every developer gets consistent guidance without having to repeat these standards.

Documentation Teams

What to store:

Style guide preferences
Template structures
Terminology standards
Brand voice guidelines

Example:

“Remember for the team: API documentation should always include authentication examples and use professional but friendly language.”

Every writer now produces consistent documentation.

Support Teams

What to store:

Common troubleshooting steps
Escalation procedures
Product knowledge
FAQ responses

Example:

“Remember for the team: For billing issues, always verify the customer’s last payment date and subscription tier before troubleshooting.”

All support agents follow the same process.

Educational Institutions

What to store:

Course policies
Grading rubrics
Resource lists
Institutional guidelines

Example:

“Remember for all users: Late assignments lose 10% per day, maximum 3 days late.”

All students and instructors get consistent policy information.

Shared Memory vs User Memory

Aspect	User Memory	Shared Memory
Who sees it	Only you	Everyone on your team
Who adds it	You (or Pria, automatically)	Twin admins
What to store	Your preferences, your projects	Team standards, shared knowledge
Example	”I prefer concise responses"	"Our team uses TypeScript”
Persistence	Personal entries follow you; entries made inside a twin stay with that twin	Stays with this digital twin

Both kinds of memory are given to the digital twin as context — your personal preferences and the team’s shared standards work together, so you can still customize your experience while following team standards.

Who can edit what

Every shared entry records who added it. Authors can always edit or delete the shared entries they created themselves; editing or removing entries added by someone else requires edit rights on the Digital Twin. Personal memories that were never created inside the twin can’t be turned into shared ones. Admins can also manage shared entries outside of chat: open the Memory panel (avatar menu → Memory) to browse, search, edit, share, and delete entries directly. Regular members see only their own personal entries in that panel — shared entries work for them in conversation without appearing there.

Managing Shared Memory

Any member can view shared memory in conversation; the update and remove prompts below apply to twin admins.

View What’s Stored

Ask your digital twin:

Prompt

Show me everything in shared memory

or search for specific topics:

Prompt

What coding standards are stored in shared memory?

Update Information

Prompt

Update the shared memory: Change our React version requirement to 18.2

Remove Outdated Information

Prompt

Remove the old deployment procedure from shared memory

Best Practices

Start with the essentials

Add your team’s most important standards first—things everyone needs to know.

Be specific

“Use TypeScript for new projects” is better than “Use good practices.”

Keep it current

Review shared memory periodically to remove outdated information.

Don't over-store

Only add information that truly benefits the whole team. Personal preferences belong in User Memory.

Technical Details for Administrators

Storage Architecture

Shared Memory uses key-value storage organized by namespaces:

namespace/key_name → {
  value: "stored data",
  description: "purpose and context",
  created: timestamp,
  shared: true
}

Tool-Based Access

Reading shared memory:

get_from_memory("technical_stack", "true")  // Search by namespace
get_from_memory("typescript", "true")       // Search by keyword
get_from_memory("", "true")                 // Get all shared parameters

Writing to shared memory:

set_in_memory([
  {
    key_name: "primary_language",
    key_value: "TypeScript",
    key_description: "Primary language for all new projects",
    key_namespace: "technical_stack"
  }
], "true", "false")

Namespace Organization

Organize parameters into logical categories:

company_standards — Organization-wide policies
technical_stack — Approved technologies
compliance_rules — Regulatory requirements
documentation_standards — Writing conventions

Assistant Integration

Reference shared memory in Assistant instructions:

Before reviewing code:
Retrieve standards: get_from_memory("technical_stack", "true")
Check code against stored standards
Flag violations with specific references

Batch Operations

Store multiple parameters at once:

set_in_memory([
  {key_name: "lang", key_value: "TypeScript", key_namespace: "tech_stack"},
  {key_name: "framework", key_value: "React 18", key_namespace: "tech_stack"},
  {key_name: "testing", key_value: "Jest + RTL", key_namespace: "tech_stack"}
], "true", "false")

Digital Twin Capabilities

Files

Assistants

Memory

Settings & Account

What is Shared Memory?

How It Works

Adding to Shared Memory

Using Shared Memory

Real-World Examples

Shared Memory vs User Memory

Who can edit what

Managing Shared Memory

View What’s Stored

Update Information

Remove Outdated Information

Best Practices

Storage Architecture

Tool-Based Access

Namespace Organization

Assistant Integration

Batch Operations

​What is Shared Memory?

​How It Works

​Adding to Shared Memory

​Using Shared Memory

​Real-World Examples

​Shared Memory vs User Memory

​Who can edit what

​Managing Shared Memory

​View What’s Stored

​Update Information

​Remove Outdated Information

​Best Practices

​Storage Architecture

​Tool-Based Access

​Namespace Organization

​Assistant Integration

​Batch Operations

What is Shared Memory?

How It Works

Adding to Shared Memory

Using Shared Memory

Real-World Examples

Shared Memory vs User Memory

Who can edit what

Managing Shared Memory

View What’s Stored

Update Information

Remove Outdated Information

Best Practices

Storage Architecture

Tool-Based Access

Namespace Organization

Assistant Integration

Batch Operations