Behaviors and memory
Shape how Kosmo works, and keep personal preferences separate from project decisions, constraints, and status.
Behaviors guide how Kosmo approaches a task. Memory carries selected durable context into later conversations. They solve different problems and remain editable.
Behaviors
A behavior is a standing instruction about tone, priorities, and method. Choose it from the composer beside the mode and model controls. Built-in options cover general work, coding, writing, teaching, research, grants, and reviewer responses.
Open Settings → AI → Behaviors to edit a behavior or add your own. A useful behavior is short and specific:
Cite numerical claims and state when the primary source is unavailable.
Preserve my terminology when restructuring a section.
Editing a built-in behavior marks it as modified so you can distinguish your version from the default.
Personal memory
Personal memory stores durable preferences about how Kosmo should work with you. It follows your authenticated account across projects and devices. Examples include your preferred answer style or a recurring accessibility preference.
Personal memory should not contain project findings, collaborator state, unpublished results, or facts that belong to one workspace.
Project memory
Project memory records durable project decisions, constraints, organization, and status. It belongs to the project and helps a new conversation understand the work without copying the full file tree into every prompt.
Kosmo retrieves relevant memory for the current task. It does not blindly include the entire project or every past conversation. Transcript history, personal memory, and project memory are separate stores.
Review project memory when a decision changes or an old constraint no longer applies. Shared project facts stay in the project rather than migrating into a collaborator's personal memory.