2mind
A quiet personal memory space with a separate early-access path.
Key capabilities
- Personal memory across sessions
- Local-first context control
- Separate product identity and onboarding
Step-by-step guides
Use cases
Start with the outcome: open a guide, prepare prerequisites, follow the steps and verify the success signals.
01 Complete early-access onboarding and create a personal spaceA local personal space is created with a clear memory policy.
- Audience
- Early-access user
- Outcome
- A local personal space is created with a clear memory policy.
Before you start
- Early-access invitation
- Supported device
- Personal owner profile
Steps
- Open the invitationVerify domain and expiry, then sign in through the provided identity flow.
- Select a local profileConfirm device profile, storage location and encryption state.
- Configure memoryChoose explicit or session-level consent and a clear retention policy.
- Verify the first conversationSave a non-sensitive fact, restart the app and retrieve it.
The fact returns only in the personal owner scope and deletion controls are available.
If the invitation fails, do not register through IAM.Mind; this is a separate product identity path.
02 Save and delete personal memory across sessionsMemory persists across sessions and remains fully owner-controlled.
- Audience
- 2mind user
- Outcome
- Memory persists across sessions and remains fully owner-controlled.
Before you start
- Active personal space
- Memory enabled
- A clear test fact
Steps
- Add a factExplicitly ask to save a fact and verify acknowledgement.
- Start a new sessionAsk about the fact without repeating the original text.
- Open the memory sourceCheck date, scope and source session.
- Delete and retestDelete the item and verify a new session no longer returns it.
After deletion, memory appears neither in the answer nor the source list.
If it reappears, keep the receipt and provide build/device profile to support.
Open detailed manual
Every application screen has a separate page with controls, safe example values, CLI/API alternatives and status-specific recovery steps.
Role of the product
2mind is a separate user product around personal memory and long-lived context. It uses the general local-first principles of IAM.Mind, but retains its own name, onboarding, communication and early-access path.
Main scenario
The user starts with a simple dialogue, then consciously saves important facts, decisions or sources. In subsequent sessions, memory is mixed only in permitted volume. The interface shows which context influenced the response, and allows you to delete an entry without contacting the administrator.
Data Principles
- memory is separated from chat history and model weights;
- each record belongs to a specific owner;
- the source and time of storage are available for verification;
- deletion is confirmed and excludes the entry from future retrieval;
- synchronization is not enabled without explicit user selection.
Communication with IAM.Mind
IAM.Mind - professional local workspace with Chat, Agents, Knowledge, Runs and System. 2mind offers a narrower personal experience. The two products do not combine forms, leads, or user memory.
Status
Access is provided through a separate early-access funnel. Public language is not should present roadmap capabilities as already available production functions.
Verified entry points
- Landing
- https://2mind.one/en/
- Application
- https://2mind.one/
- Portfolio
- https://iamgroup.ru/en/