mr-greet¶

Your AI session butler and context coach

Mr-greet provides the /hello command that starts every F3L1X session. It checks ecosystem health, extracts blockers from doc-u-me, identifies missing context, and gives you a comprehensive briefing before you start working—ensuring nothing falls through the cracks.

What It Does¶

Mr-greet is what runs when you use the /hello command. It:

1. Greets you - Friendly session start message
2. Checks services - Verifies essential realms are running
3. Surfaces blockers - Extracts incomplete tasks from your docs
4. Finds context - Identifies relevant previous work
5. Lists next steps - Shows prioritized work ready to begin

Think of mr-greet as your briefing officer—giving you everything you need to know before the meeting starts.

Key Capabilities¶

Session Health Check¶

• Service Verification: Ping Herald, PostgreSQL, Redis, doc-u-me
• Port Availability: Check all essential ports are accessible
• Dependency Status: Verify all critical services healthy
• Failure Reporting: Show which services need to be restarted

Blocker Dashboard¶

• Doc-u-me Integration: Pull all unchecked "- [ ]" items
• Priority Sorting: Show high-priority blockers first
• Related Context: Link blockers to relevant documentation
• Action Items: Extract specific next steps

Context Recovery¶

• Recent Sessions: Show last 3 session summaries
• Project Status: Display current project name and description
• Related Realms: List which realms you were working with
• File History: Show recently modified files in current project

Session Initialization¶

• Codebase Snapshot: Option to generate repomix for current project
• Git Status: Show uncommitted changes and branch info
• Environment Check: Verify Python, dependencies, configuration
• Workspace Setup: Prepare for productive coding session

Accessing mr-greet¶

Command Line¶

# Start new session with full greeting
/hello

# Or manually:
"C:/Users/felix/Desktop/F3L1X Tech/active/mr-greet/venv/Scripts/python.exe" \
  "C:/Users/felix/Desktop/F3L1X Tech/active/mr-greet/manage.py" greet --start-services

Web Dashboard¶

URL: http://127.0.0.1:8078

The mr-greet dashboard shows:
- Session greeting and briefing
- Current blockers
- Service status
- Recent context
- Quick action buttons

Greeting Types¶

Mr-greet adapts to context:

Common Use Cases¶

Use Case 1: Start Daily Work Session¶

Goal: Begin day knowing everything important

/hello

Mr-greet outputs:
- "Good morning! System status: ✅ All services healthy"
- "4 blockers from previous sessions" (shows list)
- "Last work: Supabase authentication (2026-02-16)"
- "Ready to continue or start new task?"

Use Case 2: Resume After Long Break¶

Goal: Rebuild context after time away

/hello

Mr-greet outputs:
- Full service health check
- All unchecked tasks across ecosystem
- Links to relevant documentation
- Suggests high-priority blockers to tackle first

Use Case 3: Recover from Session Crash¶

Goal: Understand what was happening when system failed

/hello

Mr-greet outputs:
- "Last session crashed (2026-02-17 14:32)"
- "Was working on: Feature X in realm Y"
- "Partially completed: Task A, Task B"
- "Auto-saved state recovered"
- Jumps to last known working point

Use Case 4: Check Blockers Before Starting Work¶

Goal: Know what's preventing progress

Dashboard shows:
- High-priority blockers (red): Dependencies, missing info
- Medium blockers (yellow): Nice-to-have optimizations
- Low blockers (blue): Future improvements

Important Notes¶

Blocker Extraction¶

Mr-greet reads your ACTIVITY_LOG.md and extracts:

## 2026-02-17 (Session 42) - Build Feature X

### Next Steps
- [x] Email confirmation working (COMPLETED - disappears)
- [ ] SMTP setup for production (APPEARS AS BLOCKER)
- [ ] Rate limiting on login (APPEARS AS BLOCKER)

Only documents in active/{realm}/ACTIVITY_LOG.md are scanned.

Don't put activity logs in:
- docs/sessions/ - Legacy dead storage (never scanned)
- ~/.claude/ directories - Not part of F3L1X infrastructure
- Random markdown files - Doc-u-me won't find them

Session Greeting Format¶

Mr-greet generates consistent briefings:

═════════════════════════════════════════════════
  F3L1X Daily Briefing - 2026-02-17 08:45:00
═════════════════════════════════════════════════

✅ SYSTEM STATUS
   Herald:     healthy (8014)
   PostgreSQL: healthy
   Redis:      healthy
   Doc-u-me:   healthy (8005)

⚠️  ACTIVE BLOCKERS
   [HIGH]  SMTP credentials needed (waiting for Felix)
   [HIGH]  Database migration pending
   [MED]   Static files not optimized

📋 RECENT CONTEXT
   Last session: 2026-02-16 18:30 - "Supabase integration"
   Working realm: herald
   Recent files: models.py, views.py, settings.py

🎯 RECOMMENDED NEXT STEPS
   1. Provide SMTP credentials (unblocks email feature)
   2. Run: python manage.py migrate
   3. Optimize static files performance

═════════════════════════════════════════════════

Service Start Options¶

Mr-greet can start services automatically:

# Start with auto-start services (recommended)
/hello --start-services

# Check health without starting services
/hello --check-only

# Full system rebuild
/hello --full-reset

Troubleshooting¶

Services show as down but are actually running¶

Symptom: Health check shows red for service you know is running
Fix: Service may not be responding on expected port, check with: netstat -an | grep 8014 (replace 8014 with realm port)

Blockers not appearing in greeting¶

Symptom: You know there are incomplete tasks but they don't show
Fix: Activity logs must be in active/{realm}/ACTIVITY_LOG.md, not docs/sessions/ or random folders

"SMTP credentials missing" blocker won't clear¶

Symptom: Blocker keeps appearing even though you think it's done
Fix: Mark as complete in ACTIVITY_LOG.md with "- [x]" and run /hello again

Session greeting takes too long¶

Symptom: /hello command hangs or is very slow
Fix: Service health check may be timing out, try --check-only to skip service startup

Context shows wrong project¶

Symptom: Greeting shows context from different project
Fix: Check git branch, may be in wrong directory, verify pwd matches expected project

Related Realms¶

• doc-u-me - Mr-greet queries for blockers and context
• worker-bee - Provides health status for service checks
• herald - Verified as running during health check
• All active realms - Checked for service status

Further Reading¶

• Session Protocol Standards
• Activity Log Best Practices
• Blocker-Driven Development