Memories

What is a Memory?

A Memory is the basic building block of Memside. It is any piece of context that should remain available for personal reference and, when allowed, for connected AI tools.

That can include a note, task, event, idea, goal, wishlist, Operating Rule, or a checkpoint for work that should continue later.

Each Memory is stored in a structured format so it can be searched, filtered, updated, and reused more reliably than information buried inside long chat history. This helps Memside support continuity across different AI apps and coding tools.

Create a Memory

Creating a Memory is simple:

Sign in to Memside.
Open the Create Memory panel.
Choose the Memory type that best matches the information being saved.
Add the main content in the text area.
Add optional details such as a title, tags, dates, sensitivity, attachments, checkpoint details, or Task Details.
Select Create Memory.

The Memory is saved to the dashboard. It can then be searched, edited, used by connected AI tools, or used later to continue work.

Details to add

The most important field is the main text content. This is where the note, instruction, task details, event description, or other useful context is stored.

Other useful details include:

Title for quick recognition and cleaner search results.
Tags for grouping related Memories.
Sensitivity to control how the Memory can be used.
Occurred date for when something happened.
Due Date when a task or event has a deadline.
Attachments when the Memory needs files, screenshots, or documents.

When creating a Task, Task Details can add structured progress and continuation information. When creating an Operating Rule, Memside shows fields for where the rule applies and how important it is.

Memory types

Memory type helps Memside organize information and show the right fields:

Note for general information, meeting notes, links, research, or saved context.
Task for action items or ongoing work that may need progress, next steps, or checkpoint support.
Event for something tied to a date or time.
Shopping List for items to buy or compare.
Wishlist for things to remember for a later purchase or plan.
Prompt for prompts that should be reused across AI tools.
Idea for early concepts, rough thoughts, or brainstorming.
Goal for a target or outcome to track.
Log for dated entries, progress notes, or records.
Operating Rule for a standing instruction that should apply in relevant AI work.

For most uses, Note and Task cover everyday needs. Use an Operating Rule for a lasting instruction rather than a one-time note.

Task Details

Task Details are optional fields for Task Memories. They are useful when a task needs clearer progress and continuation information instead of looking like a plain note.

Task Details can be enabled while creating or editing a Task. They include:

required Goal and Status fields;
optional Progress, Priority, Assigned To, and up to three ordered Next Steps;
optional Subtasks for separate pieces of work;
an advanced section for parent tasks, dependencies, Operating Rules, blockers, completion criteria, outputs, results, notes, decisions, questions, and references.

Use Task Details when a task needs a clearer working state for later use. Leave them off when the task is simple and the main text is enough.

Operating Rules

An Operating Rule is a standing instruction that Memside can share with connected AI tools when it is relevant.

Use an Operating Rule for guidance that should continue over time, such as writing preferences, workflow rules, project constraints, or repeatable instructions.

Operating Rule fields include:

Rule Title
Instruction Text
Scope Level, such as Global, Workspace, or Project
Scope Reference when the rule belongs to a specific workspace or project
Priority
optional Applies To Modes

This helps the right instructions appear in the right work instead of requiring the same explanation in every fresh AI chat.

Scope Level and Scope Reference

Scope tells Memside where an Operating Rule should apply:

Global applies everywhere and does not need a Scope Reference.
Workspace applies inside one workspace area.
Project applies inside one project area.

For Workspace or Project, Scope Reference identifies the specific place. Use a stable, recognizable name and use the same name consistently.

Generic examples:

Workspace: Personal planning
Project: Home renovation

A Scope Reference is not a Tag or Subject. It helps Memside choose when an Operating Rule applies. It does not group Memories or create a visible Connection.

Checkpoint Preset and Checkpoint Summary

A checkpoint is not a separate Memory type. It is a Note or Task marked with the Checkpoint Preset so the saved state can be used when work continues later.

The checkpoint flow is useful when returning to work without rewriting the same background. A checkpoint can save what has been completed, what matters now, and what should happen next.

Only Note and Task Memories can be marked as checkpoints:

Use a Note for a compact project or session summary.
Use a Task when structured Task Details such as progress and next steps are also needed.

When Checkpoint Preset is enabled, Memside shows a Checkpoint Summary field. Keep this summary short and focused so the next AI session can understand the current state quickly.

Sensitivity levels

Every Memory has a sensitivity setting. Sensitivity controls how the Memory can be used and whether connected AI tools can access it.

Private

Private is the default for most Memories. Use it for normal personal or project context that a connected AI tool may need when asked.

Examples include meeting notes, project decisions, travel plans, or an active task.

Secret

Secret is the strictest setting. Use it for information that should remain inside the Memside app and should not be available through normal AI-sharing flows.

If a connected AI tool needs the Memory later, change its sensitivity to Private or Public first.

Passwords, recovery codes, payment details, and access keys should not be saved in Memside, even as Secret Memories.

Public

Public Memories are still owned by the account holder. They are easier for connected AI tools to notice through lightweight hints. This helps an AI recognize open topics, interests, wishes, or ongoing items that may be relevant. The AI can then open the full Memory when more information is needed.

Public does not make the Memory visible to other users or publish it on the internet.

For example, a laptop shortlist, a wishlist item, or an open research topic can be Public. A connected AI may notice it and offer relevant help.

In short:

Use Private for normal saved context that an AI may need when asked.
Use Secret for app-only information that connected AI tools must not access.
Use Public for open interests or pending items that an AI may be able to help with.

Memside does not currently provide a visible expiry setting for Public Memories.

Attachments

Documents, screenshots, and images can be attached directly to a Memory.

Memside can:

extract text from supported documents;
read text inside images with OCR;
make file content easier to search;
show previews inside the app.

This allows a Memory to include both a written note and its supporting files.

Current limits:

Size: up to 25 MB per file.
Total quota: 500 MB of attachment storage per account.
Formats: common types such as .pdf, .txt, .jpg, .png, and .docx.

Length guidance

There is no need to over-optimize every Memory, but shorter and clearer entries work better for search and AI continuity.

Title: keep it short and recognizable.
Body: there is no strict limit for normal use, but focused text is easier to search and reuse.
Operating Rule Instruction Text: maximum 4,000 characters.
Checkpoint Summary: keep it short and focused.
Task Details: require a Goal and Status when enabled.
Task resume instructions: maximum 500 characters.

For large source material, use attachments or the text importer instead of placing everything in one Memory.

Occurred and Updated dates

These dates mean different things:

Occurred is when something happened or is meant to happen.
Updated is when the Memory was last edited in Memside.

For example, meeting notes written today for a meeting held yesterday can show yesterday as Occurred and today as Updated.

Keeping both dates makes sorting, filtering, and finding context more accurate.

Due Date

The Due Date is optional. It is useful for tasks or events with a deadline, milestone, reminder point, or follow-up date.

Examples include:

a task that must be completed this week;
a renewal or payment date;
an event happening in the future.

Leave the field empty when the Memory is not time-bound.

Tips for useful Memories

A useful Memory is short, specific, and easy to recognize later. Clear titles, useful tags, focused checkpoint summaries, and Task Details only when they add real value make Memories easier to search and reuse.