/g The Contract Codex ← 返回动态 Catalog

Remote Agent Server Smoke

Deploy an isolated remote agent server and prove event streaming, workspace access, and command execution work.

难度:advanced 分类:devops-runtime 来源:OpenHands remote agent server docs

完整 Prompt(可直接复制)

/goal
GOAL:
Complete Remote Agent Server Smoke for a deployed service: Deploy an isolated remote agent server and prove event streaming, workspace access, and command execution work.

CONTEXT:
- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.
- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.
- Establish a baseline by running or locating evidence for: `remote server smoke run and websocket event evidence`.

CONSTRAINTS:
- Keep the scope limited to this goal; do not expand into unrelated cleanup.
- Do not weaken tests, delete assertions, or mask errors to make verification pass.
- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.
- Do not deploy to production automatically; stop with a verified plan if live credentials are required.
- Keep rollback and health-check evidence attached to the final output.

DONE WHEN:
- The implementation or documentation directly satisfies: Deploy an isolated remote agent server and prove event streaming, workspace access, and command execution work.
- The verification command or evidence path succeeds: `remote server smoke run and websocket event evidence`.
- The final diff is scoped to the relevant files and has no unrelated formatting churn.

VERIFY:
- Run `remote server smoke run and websocket event evidence` or the closest repo-local equivalent if the exact command is not available.
- Capture before/after evidence for the behavior, metric, report, or artifact involved.
- If verification cannot run locally, stop and report the missing dependency instead of guessing success.

OUTPUT:
- Summarize changed files, key decisions, verification output, and remaining risks.
- Include any follow-up that is required for production rollout or human review.

STOP RULES:
- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.
- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.
- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.

来源与证据

原始来源: OpenHands remote agent server docs

证据摘要: Remote Agent Servers package the Software Agent SDK into containers; source: OpenHands remote agent server docs; type: official-workflow; verification: remote server smoke run and websocket event evidence