rename-session
Skill4 starsChanged 5 months agoMITView on GitHub
Rename or auto-generate a friendly label for an OpenClaw-style session by editing sessions.json directly. Supports random labels (zh/en with locale auto-detect), multi-agent auto-detection, listing sessions, retry with verification, and XDG-compliant history storage. 适用场景:在 OpenClaw / 任何兼容的 session 管理体系中给会话起名/改名/换花名/重命名 session/给会话加 label。
2 other projects use a version of this.
Adopted by
Most recently taken up by
- FooJiaYin/dev-skillstheir own version, first seen Sep 24, 2026
- Castrozan/claude-code-flaketheir own version, first seen Jan 22, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- FooJiaYin/dev-skills★ 2same name
- Castrozan/claude-code-flake★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- agent-avatar-managerSkill
- agent-team-meshSkill
- claw-memory-managerSkill
- codex-thread-repairSkill
- collective-memorySkill
- copy-my-profileSkill
- hello-envSkill
- init-hooksSkill
- multica-squad-load-balancerSkill
- multica-squad-onboardSkill
- openviking-projectsSkill
- recover-codex-project-chatsSkill
- session-recoverySkill
- subagent-timeout-configSkill
- token-slimSkill
- workspace-git-setupSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 100
All randomized output uses standard Python random (no external deps).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
rename-session
- Version: 1.0.0
- License: MIT
- Author: Evan Song · github.com/Songhonglei
- Repository: https://github.com/Songhonglei/better-agent-skills
Minimal, zero-dependency tool to rename a session label in
<agents-root>/<agent>/sessions/sessions.json (OpenClaw-style layout).
Quick start
# List all sessions under the only agent under ~/.openclaw/agents/
python3 scripts/rename_session.py --list
# Rename a session with a literal label
python3 scripts/rename_session.py agent:main:main "My new session name" --agent main
# Auto-generate a random label (auto-detects language from $LANG)
python3 scripts/rename_session.py agent:main:main --random --agent-name Ashley
# Force Chinese label
python3 scripts/rename_session.py agent:main:main --random --lang zh --agent-name Ashley
# Force English label
python3 scripts/rename_session.py agent:main:main --random --lang en --agent-name AshleyCLI
| Flag | Description | Default |
session_key | Session key, e.g. agent:main:main | required (unless --list) |
new_label | New literal label | required unless --random |
--random | Auto-generate a random label | false |
--list | List all session keys under the agent and exit | false |
--lang zh|en | Language for --random vocabulary | auto-detect from $LC_ALL/$LC_MESSAGES/$LANG, fall back to en |
--agent-name <name> | Agent display name used in random label | Ashley |
--agent <id> | Agent ID. Auto-detected when only one exists | auto |
--root <path> | Agents root | $RENAME_SESSION_ROOT or ~/.openclaw/agents |
Configuration via environment
| Env var | Purpose | Default |
RENAME_SESSION_ROOT | Override agents root | ~/.openclaw/agents |
XDG_DATA_HOME | Where history is stored | ~/.local/share |
History file: $XDG_DATA_HOME/rename-session/history.json (keeps last 10
labels to avoid immediate repeats when using --random).
Random label format
<scene><agent-name><mood-emoji><state-word><state-emoji>Example outputs:
zh:春光明媚Ashley🌸元气满满💻en:March Breeze Ashley🌸 Energized💻
70% of the time the scene is month-aware (e.g. March produces spring words).
Exit codes
| Code | Meaning |
| 0 | Success (rename verified or list completed) |
| 1 | Failure (3 retries exhausted, missing session, or file errors) |
| 2 | Bad CLI arguments |
Failure reasons
| Output | Explanation |
sessions.json not found at ... | Agent does not exist or has no sessions yet |
session key '...' not found | The specified session key does not exist |
File permission issues | Cannot write to sessions.json |
Disk is full or read-only | Filesystem write blocked |
Another process is continuously modifying sessions.json | Concurrent writers; retry later |
Notes
- Changes take effect immediately in the file; refresh the session list in your client to see the new label.
- Multi-agent: when more than one agent is detected under the root,
--agent <id>is required. - All randomized output uses standard Python
random(no external deps).
See references/TESTING.md for the test plan.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.