ClawHub

Session Rename

v1.0.0

Rename OpenClaw chat sessions by updating the session history store or calling the built-in `sessions.rename` backend path. Use when the user asks to rename,...

⭐ 0· 47·0 current·0 all-time
by@maverick-software
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (rename sessions) matches the instructions: either call the backend sessions.rename or update session_history.displayName in the local history.db. No unrelated env vars, binaries, or external services are requested.
ℹ
Instruction Scope
Instructions include direct filesystem access (searching for history.db and running a Python SQLite update). This is necessary for the stated goal, but searching arbitrary paths or performing DB writes carries risk if executed incorrectly. The SKILL.md warns to confirm instance and to be surgical, which mitigates but does not eliminate that risk.
✓
Install Mechanism
No install steps or external downloads — instruction-only. Nothing is written to disk by an installer, lowering supply-chain risk.
✓
Credentials
The skill requests no environment variables, credentials, or config paths beyond local OpenClaw DB locations. The scope of access (local session DB) is proportional to the purpose.
✓
Persistence & Privilege
Skill is not always-enabled and does not request persistent elevated privileges. It does instruct writing to a local DB, which is appropriate for renaming sessions but should be run only when the target instance is confirmed.
Assessment
This skill appears to do what it says: rename sessions either via the backend API or by directly updating OpenClaw's SQLite history.db. Before using it: prefer the backend sessions.rename method when available; if you must edit the DB, make a backup of history.db first; confirm the correct agent instance and sessionId to avoid accidentally changing other sessions; avoid broad filesystem searches (limit to likely OpenClaw paths) and do not run these edits on remote machines you do not fully trust. If you need higher assurance, request code that uses the built-in backend method instead of direct DB writes.

Like a lobster shell, security has layers — review code before you run it.

latestvk974kbb0tw11pb3be7jf9db9s584q54b

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments