Using Palim day to day

Work state or complete chat?

Context snapshot

palim_save_context is the default checkpoint for handing work to another AI tool. The MCP server instructs connected agents to call it proactively after substantial results, decisions, or changes of direction. The client creates a self-contained, compact work state with the goal, decisions, current status, and next steps – without storing the complete message transcript.

Capture the current state for my other AI tools.

Session

Use palim_save_session when the full conversation should remain traceable.

Save this complete chat as "July auth review" and tag it with auth and atlas.

Rule of thumb

Use a context snapshot for the default hand-off and a session for an explicitly requested full archive. Trivial conversations, secrets, and content you asked not to persist should not be included in a checkpoint.

If your AI client does not use Palim reliably on its own, copy the base instruction from Prompts and personalization into its durable instructions. That guide also includes everyday prompts, a cross-client reliability test, and an optional agent skill.

Find saved content

Intent	Example	Matching tool
Find keywords	“Search for database migration”	`palim_search`
Date range and project	“What happened in Atlas last week?”	`palim_search_by_date_range`
Retrieve an overview	“Give me context about the auth flow”	`palim_get_context`
Read a complete chat	“Show session abc-123”	`palim_show_session`

Search currently uses full-text and text matching. Try several characteristic terms, tags, or a project when an exact title phrase is not found.

Manage memories

Memories are best for single, durable facts and decisions:

Remember: Project Atlas uses PostgreSQL 15.

Use palim_search_memories to find saved facts. palim_update_memory corrects outdated content, and palim_delete_memory permanently removes a memory.

Brain and dashboard

The Palim dashboard shows sessions, memories, and the Brain view built from saved session summaries. It lets you search, inspect, and manage your data. Read Brain and dashboard for topic creation, catch-up, editing, and exact deletion behavior.

Automated user profiles are currently limited to approved staff accounts in production and are not part of the general Palim offering.

Metadata, exports, and deletion

palim_update_session_metadata changes a title, tags, project, or date.
palim_update_session_references adds source URLs.
palim_export_session exports a session as Markdown, JSON, or text.
palim_export_brain creates a Markdown/Obsidian export of the Brain view.
palim_delete_session sets a session to the deleted status by default. With hard_delete: true, the session, messages, and summary are permanently removed.

Deleting a session in the dashboard always uses the permanent variant. There is currently no public restore operation for sessions with the deleted status. See Manage data and credentials for exports, deletion, and credential behavior.