Lesson 6 of 6 · 0%Capstone: run, inspect, stop, and remove the first safe agentAssessment
Course map

Safe Installation and First Agent

0 of 6 complete0 of 6

Lesson 6.1 · 45 minutes

Capstone: run, inspect, stop, and remove the first safe agent

Demonstrate one bounded proposal, complete the evidence record, rotate the test credential, and tear down or reset the environment.

Skip course map
Current lessonCapstone: run, inspect, stop, and remove the first safe agent0% complete · 0/6 lessons

Safe Installation and First Agent

0% complete · Current: Capstone: run, inspect, stop, and remove the first safe agent

Verifiedon 2026.7.1-2

Action boundary

Before you act

Expected result
A redacted evidence record proves one proposal-only run, explicit human review, credential rotation, and controlled teardown.
Failure mode
The learner keeps an unreviewed long-running gateway, reusable test credential, or agent workspace after the exercise.
Rollback
Stop the gateway, revoke the test credential, follow the selected platform’s documented uninstall/reset route, and delete only confirmed test artifacts.

Capstone: First Safe Agent

Run exactly one controlled task from the prior lesson. The agent reads only the test input, produces a proposal, and writes no external side effect. The trusted operator reviews the proposal and records either approved for a future, separate action or not approved. For this capstone, do not perform the future action.

Evidence checklist

Your redacted evidence record must contain:

  • platform and OpenClaw version;
  • provider live-check result without a credential;
  • CLI/Gateway verification results;
  • task contract and controlled-input label;
  • proposal outcome and human approval decision;
  • a statement that no real channel or external side effect was connected;
  • credential rotation/revocation result; and
  • gateway stop plus workspace/install teardown result.

Secret rotation drill

Assume the test credential was copied into an unsafe note. Revoke it with the provider, replace it if a repeat test is necessary, and verify that the old credential cannot be used. The OpenClaw secrets guidance is clear that plaintext residue and backups remain secrets until removed; a new key does not erase the old one.

Teardown

Use the primary uninstall documentation for your exact install route. Preview the built-in removal scope first with openclaw uninstall --dry-run --all; inspect the listed service, state, workspace, and app targets before approving any removal. On a VPS, retain only the redacted operational evidence and any backup required by your policy; remove test state/workspace only after confirming it is not shared. On a local host, stop the gateway first, then run the approved uninstall scope. Do not improvise deletion commands from memory.

Rubric

Criterion Weight Pass signal
Isolation 30% Test host/workspace and no real channel are explicit.
Verification 25% CLI, gateway, and provider results are recorded.
Approval boundary 25% Output is a proposal; external action remains disconnected.
Rollback/removal 20% Credential rotation and teardown are evidenced.

A pass means the exercise is reversible and inspectable—not that the agent is safe for production.

Check your understanding

Knowledge check · security

Pass mark 100% · Attempt 1 of 3 · Not passed

What is required after a provider key appears in a screenshot?
Why this matters

A copied credential may remain accessible outside the edited artifact.

Evidence last verified 2026-07-30

Source provenanceVerification and sources

Review receipt rr_setup_capstone_teardown

Outcome
approved
Method
source-review
Reviewer
forge-independent-review
Reviewed

Evidence

Limitations

  • Independent source review approved the dry-run-first teardown procedure; destructive removal remains a human-approved action.

Open the public evidence snapshot

Lesson checkpoint

Ready to move on?

Mark this lesson complete when you can apply its outcome without relying on the examples above.