Slash Command

/syn-health

From syntropic137

First, resolve the API URL:

Popularity

Stars

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/syntropic137:syn-health

Model invocable

No pre-commands

Configuration

Modelsonnet

Referenced Files

Files this command reads when invoked

syntropic137/setup

Tool Access

This command is limited to the following tools:

Bash

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

# /syn-health — API Health Check

First, resolve the API URL:



Detect whether the `syn` CLI is available:



Run the health check:
- If SYN_CLI is set: `$SYN_CLI health`
- Otherwise: `curl -sf "$SYN_API_URL/health"`

If the command succeeds, display the health response.

If it fails (non-zero exit or connection error):
1. Check if Docker is running: `docker info >/dev/null 2>&1`
2. Detect the installation path and check container status:
   
3. If the container exists but API is unhealthy, suggest checking logs:
   - Published path (`~/.syntropic137/`): `docker compose -f ~/.syntropic137/...

Command Content

55 lines · ~482 tokens

Stats

LanguagePython

Stars1

MaintenanceExcellent

Last CommitMay 2, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Actions

/syn-health — API Health Check

First, resolve the API URL:

if [ -n "${SYN_API_URL:-}" ]; then
    SYN_API_URL="$SYN_API_URL"
elif [ -f "$HOME/.syntropic137/.env" ]; then
    _hostname=$(grep '^SYN_PUBLIC_HOSTNAME=' "$HOME/.syntropic137/.env" 2>/dev/null | cut -d= -f2 | tr -d '"' | tr -d "'")
    if [ -n "$_hostname" ]; then
        SYN_API_URL="https://$_hostname"
    fi
fi
SYN_API_URL="${SYN_API_URL:-http://localhost:8137}"

Detect whether the syn CLI is available:

if command -v syn &>/dev/null; then
    SYN_CLI="syn"
else
    SYN_CLI=""
fi

Run the health check:

If SYN_CLI is set: $SYN_CLI health
Otherwise: curl -sf "$SYN_API_URL/health"

If the command succeeds, display the health response.

If it fails (non-zero exit or connection error):

Check if Docker is running: docker info >/dev/null 2>&1

Detect the installation path and check container status:

if [ -f "$HOME/.syntropic137/docker-compose.syntropic137.yaml" ]; then
    docker compose -f "$HOME/.syntropic137/docker-compose.syntropic137.yaml" ps --format "table {{.Name}}\t{{.Status}}" 2>/dev/null
elif [ -f "docker/docker-compose.yaml" ]; then
    docker compose -f docker/docker-compose.yaml -f docker/docker-compose.dev.yaml ps --format "table {{.Name}}\t{{.Status}}" 2>/dev/null
fi

If the container exists but API is unhealthy, suggest checking logs:
- Published path (~/.syntropic137/): docker compose -f ~/.syntropic137/docker-compose.syntropic137.yaml logs
- Source repo: just dev-logs
If no containers are running, suggest starting the stack:
- Published path: npx @syntropic137/setup (interactive menu) or docker compose -f ~/.syntropic137/docker-compose.syntropic137.yaml up -d
- Source repo: just selfhost-up or just dev
If Docker itself is not running, suggest starting Docker Desktop