jester/zlh-grind
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify Agent code-server responsibilities

Browse Source
This commit is contained in:
jester 2026-04-16 20:28:27 +00:00
parent 33093fb3c4
commit f044fba546
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Codex/Agent/AGENT_OVERVIEW.md
View File

@ -4,7 +4,7 @@ The Agent is the software that runs inside a ZeroLagHub provisioned container an
For game containers, the Agent is responsible for installing and running the game server, exposing operational controls, reporting status and readiness, supervising crashes, managing console access, and handling local app-aware recovery tasks such as Minecraft backups and restores.
For dev containers, the Agent is responsible for preparing the runtime environment, workspace, user shell, and container-local developer tooling such as code-server.
For dev containers, the Agent is responsible for preparing the runtime environment, workspace, user shell, and container-local developer tooling such as code-server. When code-server is requested, Agent provisioning should install it, start it, verify it, and expose controls for later start/stop/restart operations.
The Agent is intentionally container-local. It should make the workload inside the container reliable and observable, but it should not own platform-level orchestration, billing, portal UX, API product policy, or offsite disaster-recovery strategy.
@ -17,6 +17,7 @@ The Agent is intentionally container-local. It should make the workload inside t
- provide validated file and console operations where supported
- manage local Minecraft backup, restore, and checkpoint behavior
- support dev-container environment setup and local developer tooling
- reconcile requested code-server state during dev provisioning and expose `/dev/codeserver/start`, `/dev/codeserver/stop`, and `/dev/codeserver/restart`
## Current Backup Boundary