Session Logger

Automatically log a session summary to ~/Tandem/memory/sessions/YYYY-MM-DD.md when the conversation is ending. This is a background behavior — never announce that you're logging unless the user asks.

---

When to Log

Trigger session logging when:

• User says "goodbye", "thanks, that's all", "I'm done", "see you later"
• User has been idle and the session is clearly winding down
• A major task sequence has completed and the user seems satisfied
• Another skill or command has completed its final step

Do NOT log:

• In the middle of an active task
• For trivial interactions (single question, quick lookup)
• If the session was only 1-2 exchanges with no real work done
• When the user says "remember that" or "save this" — route to memory-create instead
• When the user says "add to my tasks" or "create a task" — route to task-manager instead
• Do NOT auto-trigger mid-session; only log at session end

---

Log Format

Append to ~/Tandem/memory/sessions/YYYY-MM-DD.md (create file if it doesn't exist):

## Session [HH:MM]

- **Skills/commands used**: /email-triage, /daily-plan, memory-create
- **Tasks completed**: Triaged 15 emails, created daily plan, saved 2 contacts
- **Documents created**: daily-plan-2026-03-18.md, inbox-triage-2026-03-18.md
- **Suggestions accepted**: Saved email contact, set follow-up reminder
- **Suggestions dismissed**: Automation offer for daily triage
- **Decisions made**: [any decisions the user stated during the session]
- **Duration**: ~[estimate] min
- **Activity level**: ~[N] tool calls, [brief description of heaviest operations]

---

Logging Rules

1. Be concise — each field should be one line, not a paragraph
2. Be accurate — only log skills/tasks that actually happened in this session
3. Track suggestion acceptance — this data is critical for the pattern-detector skill
4. Estimate duration — rough estimate based on conversation length is fine
5. Append, don't overwrite — multiple sessions per day get appended to the same file
6. Silent operation — never tell the user "I'm logging this session" unless asked
7. Language — log in English for consistency (this is internal analytics, not user-facing)
8. Trigger dashboard sync — after logging, run the /sync workflow silently to update dashboard.html

---

Dashboard Sync

After writing the session log entry, trigger a dashboard sync:

1. Read ~/Tandem/stats.json to check if any entries exist
2. If stats.json exists and has entries, invoke the /sync workflow:
   • Read ~/Tandem/stats.json and ~/Tandem/tasks/kanban.md
   • Recompute all dashboard statistics (7-day rolling totals, deltas, trends)
   • Update the JSON block in ~/Tandem/dashboard.html
   • See tandem-skills/core/sync/SKILL.md for the full algorithm
3. If stats.json does not exist or is empty, skip the sync silently

This ensures the dashboard reflects all activity from the session that just ended. The sync is silent — do not announce it to the user.

---

Skill Usage Tracking

After writing the session log entry, update skill usage tracking:

1. Read ~/Tandem/memory/skill-usage.json (create as {} if the file does not exist)
2. For each skill listed in "Skills/commands used" for this session:
   • If skill exists in JSON: update last_used to today's date, increment use_count by 1
   • If skill is new: add entry with first_used = today, last_used = today, use_count = 1
3. Write updated JSON back to ~/Tandem/memory/skill-usage.json

This enables the explore skill to show which skills the user has tried vs not tried.

---

File Management

• One file per day: memory/sessions/YYYY-MM-DD.md
• Multiple sessions per day get appended as separate ## Session [HH:MM] blocks
• Files older than 30 days can be archived by the memory-delete skill's cleanup flow
• The pattern-detector skill reads the last 7 days of session files to detect patterns

---

What NOT to Log

• Personal or sensitive information the user shared in conversation
• Full email content or document text
• Private details about contacts (only log that a contact was saved, not their details)
• Anything the user explicitly asked not to remember

This is a usage log, not a conversation transcript.