Delete Agent With Telegram Group

Safely and thoroughly delete an OpenClaw agent and its artifacts. Use when user asks to remove an agent completely, including workspace, agent files under ~/...

Security Scan

The skill is internally coherent: its instructions and included script only touch ~/.openclaw and user-home workspaces (with guards), require explicit confirmations, and do not request credentials or network access.

Purpose & Capability

The name/description (delete an agent and related local artifacts including Telegram routing config) aligns with the included script and SKILL.md: the script edits ~/.openclaw/openclaw.json, cron jobs, agent dir, and optional workspace removal. Nothing requested or included appears unrelated to that purpose.

Instruction Scope

SKILL.md enforces a 3-step destructive gate and instructs a dry-run first; the Python script implements those behaviors. The SKILL.md mentions Telegram group deletion via external browser automation/manual steps but does not include code to perform remote/browser control—this is an out-of-band action that correctly requires separate explicit user consent. Verify any browser automation you run independently.

Install Mechanism

No install spec (instruction-only with a bundled script). No downloads or package installs are performed by the skill, so no install-time code-fetch risk.

Credentials

The skill requests no environment variables, credentials, or config paths beyond standard home-dir file paths. The script only reads/writes files under the user's home (~/.openclaw) and optionally workspaces under the user's home with a claw-* name guard.

Persistence & Privilege

The skill is not always-enabled and does not request persistent system-wide privileges. It does modify only its own OpenClaw config files and writes backups in-place; that is expected for a deletion tool.

Assessment

This skill appears to do exactly what it says: run the dry-run first and inspect its JSON plan; confirm local deletion explicitly; the script will back up openclaw.json and jobs.json before overwriting and will only delete workspaces under your home when the folder name starts with "claw-". It does NOT automatically delete Telegram groups — SKILL.md instructs you to perform browser automation or manual deletion separately and to require an extra confirmation for that step. Before using: (1) run the provided dry-run and review the printed plan, (2) inspect the backup files it creates, (3) verify openclaw.json contents and other data you may want to keep, and (4) avoid running any separate browser automation unless you trust the tooling. If you need higher assurance, open the script yourself to confirm there are no unexpected network calls (there are none) and consider making offline copies of critical files before proceeding.

Delete Agent (Clean)

Permanently remove an agent and its related local config/files.

Safety Rules

• This is destructive. Always require explicit user confirmation.
• Enforce 3-step gate:
  1. run --dry-run,
  2. explicit confirmation for local deletion,
  3. separate explicit confirmation for Telegram browser/session-controlled group deletion.
• Ask user whether to also delete the dedicated Telegram group.
• Never auto-delete Telegram groups without the separate confirmation.
• Prefer script execution for local cleanup (stable, low token).

Inputs

Collect:

• agent_id (required)
• delete_workspace (yes/no)
• delete_telegram_group_config (yes/no; usually yes)
• delete_telegram_group (yes/no; requires explicit confirmation)
• delete_cron_jobs (yes/no; usually yes)

Script-first Commands

Dry-run:

python3 scripts/delete_agent.py --agent-id <agent_id> --dry-run

Execute (after confirmation):

python3 scripts/delete_agent.py --agent-id <agent_id> --yes --delete-workspace --delete-telegram-group-config --delete-cron-jobs

Script Safety Guardrails

• scripts/delete_agent.py validates agent_id format: [a-z0-9-]+.
• It refuses deletion when target paths are outside allowed directories.
• Workspace deletion is allowed only when path is under user home and folder name starts with claw-.
• It creates backup files before writing config changes.

What the script removes

• Agent entry in ~/.openclaw/openclaw.json (agents.list)
• Agent bindings (bindings[] with matching agentId)
• Telegram group routing entries linked by those bindings
  • channels.telegram.groups.<chat_id>
• Agent directory:
  • ~/.openclaw/agents/<agent_id>
• Workspace directory from agent config (if --delete-workspace)
• Cron jobs owned by this agent from ~/.openclaw/cron/jobs.json (if --delete-cron-jobs)

Dedicated Telegram Group Deletion

This skill does not bundle Telegram deletion automation code; it uses external browser automation tooling or manual user actions.

After local script deletion and only if user confirmed delete_telegram_group=yes:

1. Require a separate explicit confirmation: user agrees to browser/session control and irreversible group deletion.
2. Identify dedicated group chat_id from removed bindings.
3. Use browser automation (Telegram Web) to open the group and run Delete Group.
4. In Telegram delete dialog, enable Delete for all members when available, then confirm deletion.
5. Report final group status clearly: deleted / left-only / pending-manual.

Post-step

• Surface backup files created by the script (openclaw.json.bak.*, jobs.json.bak.*) so user can retain recovery points.
• If gateway reload is available, let hot reload apply.
• If not applied, ask for explicit confirmation before restarting gateway, then verify logs.
• Return concise summary with removed items.