-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Add openclaw sessions reset <session-id> subcommand #834
Copy link
Copy link
Open
Labels
Getting StartedUse this label to identify setup, installation, or onboarding issues.Use this label to identify setup, installation, or onboarding issues.NemoClaw CLIUse this label to identify issues with the NemoClaw command-line interface (CLI).Use this label to identify issues with the NemoClaw command-line interface (CLI).enhancementNew feature or requestNew feature or requestpriority: highImportant issue that should be resolved in the next releaseImportant issue that should be resolved in the next release
Metadata
Metadata
Assignees
Labels
Getting StartedUse this label to identify setup, installation, or onboarding issues.Use this label to identify setup, installation, or onboarding issues.NemoClaw CLIUse this label to identify issues with the NemoClaw command-line interface (CLI).Use this label to identify issues with the NemoClaw command-line interface (CLI).enhancementNew feature or requestNew feature or requestpriority: highImportant issue that should be resolved in the next releaseImportant issue that should be resolved in the next release
Problem Statement
There is currently no CLI command to reset a specific session. When a session becomes corrupted (e.g. after a lock failure via the Telegram bridge), the only recovery path is to manually delete .jsonl and sessions.json files from inside the sandbox — which requires knowing the file paths and having sandbox shell access.
Proposed Design
A reset subcommand on openclaw sessions would make this recoverable without manual file system intervention:
Current workaround:
Alternatives Considered
No response
Category
enhancement: feature
Checklist