Exit Codes

loghop exits with specific codes for different conditions.

Exit Code Reference

Detailed Explanation

0 — Success

The command completed successfully. This includes:

• Session captured and stored
• Handoff created
• Project initialized
• Status query completed

1 — Internal Error

An unexpected error occurred. This is a bug. Please report:

• Command that failed
• Exact error message
• Provider and version
• Log file contents (.loghop/loghop.log)

2 — Usage Error

Invalid command-line arguments or validation failed:

# Missing required argument
loghop handoff show  # Error: handoff ID required

# Invalid option
loghop run --provider invalid  # Error: unknown provider

# Project not a git repo
loghop init  # Error: not a git repository

3 — Timeout

The session reached the timeout limit:

loghop run --timeout 60  # Fails after 60 seconds

Default timeout is 300 seconds (5 minutes). Adjust with --timeout.

10 — Provider Non-Zero

The provider (Claude or Codex) exited with a non-zero status:

loghop run  # Provider exited with code 1

# Check provider logs for details
loghop --verbose run

This usually indicates the provider encountered an error. Check:

• Provider authentication
• Provider logs
• Project configuration

20 — Not Initialized

Project has not been initialized for loghop:

loghop run
# Error: Project not initialized. Run `loghop init` first.

# Fix:
cd your-git-repo
loghop init
loghop run

Using Exit Codes in Scripts

#!/bin/bash
loghop run --provider codex
exit_code=$?

case $exit_code in
    0) echo "Session complete" ;;
    3) echo "Timeout - retrying" ;;
    10) echo "Provider error - check logs" ;;
    *) echo "Unexpected error: $exit_code" ;;
esac

Signal Handling

loghop converts SIGTERM to KeyboardInterrupt internally, which exits with code 130 (128 + 2).

JSON Output with Exit Codes

loghop run --json 2>/dev/null | jq .exit_code

When using --json, the exit code is also included in the JSON envelope.