pynchy-opslisted

# Pynchy Ops The pynchy service runs on `pynchy-server` over Tailscale. SSH: `ssh pynchy-server`. ## Auto-deploy: Never Restart Manually Pynchy self-manages. Two mechanisms trigger automatic restarts: 1. **Git changes on `main`** — the polling mechanism detects new commits, pulls, and restarts (with container rebuild if source files changed). 2. **Config file changes** — editing `config.toml`, `litellm_config.yaml`, or other settings files triggers an automatic restart. Edit the file and wait ~30–90s. **Do not manually restart containers or the service.** This includes `docker restart`, `systemctl restart`, and direct container management (`docker kill/stop/rm`). Manual restarts bypass lifecycle management and can leave things in a bad state. Only use manual commands when the service is unhealthy and needs fixing. See [references/server-debug.md](references/server-debug.md) for diagnostic steps. ## Quick Status Check **Preferred: the `/status` endpoint.** Single command that returns everything: ```bash # On pynchy-server directly: curl -s http://localhost:8484/status | python3 -m json.tool # Remotely (via Tailscale): curl -s http://pynchy-server:8484/status | python3 -m json.tool ``` Returns JSON with: `service` (uptime), `deploy` (SHA, dirty, unpushed), `channels` (slack/whatsapp connected), `gateway` (LiteLLM health, model counts), `queue` (active containers, waiting groups), `repos` (per-repo worktree status — SHA, dirty, ahead/behind, conflicts), `messages` (in