How this command is triggered — by the user, by Claude, or both
Slash command
/claude-remember:statusThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Check the claude-remember session logging status: 1. Read the configuration from ~/.claude-logs/config.json (if it exists) to show current settings 2. List the 5 most recent session markdown files from ~/.claude-logs/sessions/ (check today's date folder first) 3. Query the SQLite database at ~/.claude-logs/sessions.db to count total sessions and messages 4. Report any per-project overrides from .claude-remember.json in the current directory Display a summary showing: - Whether logging is enabled - Log directory location - Database location and stats (total sessions, messages, tool calls) ...
Check the claude-remember session logging status:
Display a summary showing:
npx claudepluginhub davidshq/claude-remember/assist-logsQueries the context-inject hook log to show what knowledge and milestones are being injected into Claude Code sessions. Supports --limit and --search filters.
/statusShows CLAUDE.md (or AGENTS.md) memory sync status: pending changes count, last sync time, file locations, and config settings. Offers /auto-memory:calibrate if pending.
/CLAUDEDisplays recent activity log from claude-mem context in auto-generated <claude-mem-context> section, listing actions or 'No recent activity'.
/ralph-statsShows Ralph Wiggum loop session history and statistics from logs, filtered by last N, project, outcome, active status, or all.