lore daemon

The daemon watches for new AI coding sessions and imports them automatically in real-time.

Commands

Command	Description
`lore daemon start`	Start the daemon
`lore daemon stop`	Stop the daemon
`lore daemon status`	Check daemon status
`lore daemon logs`	View daemon logs
`lore daemon install`	Install as system service
`lore daemon uninstall`	Remove system service

Starting the Daemon

Manual Start

# Start in background
lore daemon start

# Start in foreground (useful for debugging)
lore daemon start --foreground

As a Service (Recommended)

Services start automatically on login and restart on failure.

macOS with Homebrew:

brew services start lore
brew services stop lore
brew services restart lore

Linux with systemd:

lore daemon install    # Install and enable
lore daemon uninstall  # Remove service

Or manage directly:

systemctl --user start lore
systemctl --user stop lore
systemctl --user status lore

Checking Status

lore daemon status

Daemon Status: Running
  PID: 12345
  Uptime: 2 hours, 15 minutes
  Sessions captured: 3

Watching:
  claude-code: ~/.claude/projects/
  aider: (per-project .aider.chat.history.md)
  gemini: ~/.gemini/tmp/

Viewing Logs

# View recent logs
lore daemon logs

# Follow logs in real-time
lore daemon logs --follow

# Show more lines
lore daemon logs --lines 100

Log location: ~/.lore/logs/

How It Works

The daemon:

Watches session directories for all enabled tools
Detects new or modified session files
Parses and imports sessions incrementally
Tracks git branch changes during sessions
Handles file rotations and tool restarts

Sessions are available immediately after creation, no manual import needed.

Daemon vs Manual Import

Feature	Daemon	Manual Import
Real-time capture	Yes	No
Branch tracking	Yes	Snapshot only
CPU usage	Minimal (event-based)	None when idle
Startup	Automatic (service)	Manual

For active development, the daemon provides the best experience. For occasional use, manual lore import is sufficient.

Troubleshooting

Daemon won’t start:

# Check if already running
lore daemon status

# Check for port conflicts
lore daemon logs

# Try foreground mode for debugging
lore daemon start --foreground

Sessions not appearing:

# Verify daemon is watching the right directories
lore daemon status

# Check enabled watchers
lore config get watchers

# Check logs for errors
lore daemon logs

High CPU usage:

The daemon uses event-based file watching with minimal CPU. If you see high usage:

# Check logs for rapid file changes
lore daemon logs --lines 200

# Restart the daemon
lore daemon stop && lore daemon start