Memory and personas
Understand the context Devboxes retains and the identities it uses in chat.
Memory helps retain relevant context; personas identify how Devboxes participates in chat. Review these settings when a team needs to correct remembered information or change a chat identity.
Organization memory
Open Memory to inspect the organization information available there. A correction creates a new version while retaining the previous version in history. Conflicting claims remain visible until one explicitly supersedes another.
Use a correction to state the current fact clearly. Do not place passwords, access tokens, or other secrets into remembered prose.
Person memory
Person memory belongs to the linked person. Organization owners and admins set the permitted categories but cannot browse its contents through the organization policy view.
The policy can disable person memory or allow the categories shown in the app. Read the available settings before changing what the organization permits.
Personas
Open Personas to inspect the identities used in chat. Owners and admins can review proposed persona splits; owner-only lifecycle actions remain restricted to owners.
Making a persona the default retires the current default for new conversations. Existing session bindings do not switch to the replacement. Read the confirmation before changing the default or retiring a persona.
Read the consequences before retiring a persona or erasing its history. Erasure permanently removes the covered profile revisions and persona-specific memory; it is not the same action as retirement.