remote-agent-hq-startup

Name: remote-agent-hq-startup
Availability: InStock
Author: tankygranny05

Debug and restart AMS and UI services on remote machines via SSH and tmux.

2|Updated Jan 30, 2026

Search Tags:#tmux #ssh #service startup #remote debugging #ams #agent hq

Ready to run

npx skills add https://github.com/tankygranny05/agent-box --skill remote-agent-hq-startup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: remote-agent-hq-startup
Source: https://github.com/tankygranny05/agent-box/tree/main/agent-box/seed/codex-skills/remote-agent-hq-startup
Command: npx skills add https://github.com/tankygranny05/agent-box --skill remote-agent-hq-startup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses issues with remote Agent HQ services (AMS, UI) not responding, connection errors, or configuration problems, ensuring smooth operation of your agent management infrastructure.

Core Features & Use Cases

Remote Service Debugging: Diagnoses and resolves issues with the Agent Management Server (AMS) and Agent HQ UI on remote machines.
Service Startup: Provides commands to restart AMS and the UI, including necessary environment variable setup and tmux session management.
Use Case: When your Agent HQ dashboard shows "SSE connection lost" or you encounter errors related to ports 8041 or 8037 on your remote server, this skill will guide you through diagnosing and restarting the services.

Quick Start

Use the remote-agent-hq-startup skill to restart the AMS service on the remote machine.

Frequently Asked Questions about remote-agent-hq-startup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix Agent HQ SSE connection lost errors on a remote server?▼

To fix Agent HQ SSE connection lost errors, you must debug and restart the Agent Management Server (AMS) and UI components on the remote machine, resolving any environment variable or port conflict issues causing the failure.

What causes port conflicts on 8041 and 8037 when starting remote Agent HQ services?▼

Port conflicts on 8041 and 8037 occur when previous Agent HQ AMS or UI processes fail to terminate properly, requiring you to kill stale processes and restart the services through an SSH connection.

Do I need tmux and SSH to debug remote Agent HQ AMS services?▼

Yes, you need SSH access to connect to the remote machine and tmux to manage the persistent background processes required for successfully restarting and running the Agent HQ AMS and UI services.

How do I restart the Agent HQ UI and AMS when Vite configuration issues occur?▼

To restart the Agent HQ UI and AMS after Vite configuration issues, establish an SSH connection, verify environment variables, and use tmux to launch fresh service sessions on the remote host.

Are there limitations when resolving environment variable errors for remote Agent HQ services?▼

Limitations include requiring direct SSH access to the remote machine and manual tmux session management, meaning you cannot resolve environment variable errors or restart services without direct terminal access.