1 control agent api and remote service runner
forgejo-actions edited this page 2026-07-13 19:45:35 +00:00

Control-Agent API And Remote Service Runner

The control agent exposes a remote service-runner API for health, readiness, service status, logs, start, stop, and restart actions.

Purpose

Use this page when operating services through a remote agent instead of the local Control Panel process. The agent is useful for remote orchestration, but it is not a full replacement for the panel dependency workflow.

Required Inputs

The agent needs workspace root configuration, AETHER_AGENT_TOKEN bearer auth when enabled, service definitions, build configuration, and bounded log capture settings.

Procedure

Check /health and /ready before service actions. Use /v1/services to inspect service state. Start, stop, restart, and log endpoints require the correct bearer token when configured. The agent can build before launch and keeps runtime state in memory.

Failure Modes

Invalid workspace roots, missing bearer tokens, build failures, log buffer limits, and remote dependency gaps can make agent actions fail even when local panel actions would work.

Verification

Confirm readiness, service status, and recent logs after every remote action. For build-before-launch failures, inspect agent logs and service binary paths before retrying.