Session Cleanup logo

Session Cleanup

CommunityPopular
hoangsonww
session-cleanup

Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation. Use when tidying the monitoring database.

Overview

Publisherhoangsonww
RepositoryClaude-Code-Agent-Monitor
Skill namesession-cleanup
Stars
1.1K
Forks
260
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by hoangsonww on GitHub. Read the source before you install it.

Installation

Install the Session Cleanup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-cleanup
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git /tmp/Claude-Code-Agent-Monitor
mkdir -p .claude/skills
cp -r /tmp/Claude-Code-Agent-Monitor/plugins/ccam-sessions/skills/session-cleanup .claude/skills/session-cleanup
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Session Cleanup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Session Cleanup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Session Cleanup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Session Cleanup

Find prune-worthy sessions and explain cleanup — preview first, delete only on explicit confirmation.

Input

The user provides: $ARGUMENTS

  • Empty / preview → only show what would be removed (the safe default).
  • confirm → the user has reviewed the preview and explicitly authorizes deletion.
  • An optional staleness threshold (e.g. older than 7d) for what counts as stale.

Data Sources

EndpointReturns
GET /api/sessions?limit=Nsession list: id, status, model, cwd, started_at, ended_at, cost, metadata (turn_count, total_turn_duration_ms)
GET /api/statstotals: total_sessions, active_sessions, total_events, events_today, sessions_by_status, agents_by_status
POST /api/settings/cleanupruns the cleanup routine and returns what was removed — DESTRUCTIVE, only after confirmation

Report Sections

1. Baseline

GET /api/stats — record total_sessions, sessions_by_status, total_events. This is the before-state to compare against.

2. Identify candidates

GET /api/sessions?limit=1000. Flag sessions that are:

  • Empty — zero events and turn_count 0 / null and cost 0 (started but never did anything).
  • Stale active — status active/working but last activity older than the threshold (default 24h), i.e. never cleanly stopped.
  • Truncated — no ended_at and no recent events.

3. Preview table (ALWAYS shown)

List every candidate with the reason it qualifies. State the total count and confirm that nothing has been deleted yet.

4. Explain the endpoint

Describe POST /api/settings/cleanup: it prunes empty / orphaned sessions and their dangling events server-side and returns a summary of removed rows. Make clear this is permanent and not reversible from the dashboard.

5. Execute only on confirmation

If — and only if — $ARGUMENTS is confirm (or the user has explicitly approved this run), call POST /api/settings/cleanup, then re-read /api/stats and report the before → after delta. Otherwise stop after the preview and tell the user to re-run with confirm.

Output

A preview Markdown table: id (short) | status | reason | cwd basename | started_at | cost, then a one-line count and the explicit "nothing deleted — re-run with confirm to proceed" notice. On a confirmed run, add a before → after summary using ▲/▼ on the counts. Currency as USD to 4 decimal places.

Safety

  • This is the ONLY skill in the plugin that mutates data, and only via the one documented endpoint.
  • NEVER call POST /api/settings/cleanup without an explicit confirm from the user in this turn — previewing is the default.
  • Never widen scope to POST /api/settings/clear-data or any other destructive endpoint; cleanup of stale/empty sessions only.
  • If the dashboard is unreachable, tell the user to start it with npm start from the repo root.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Session Cleanup AI skill do?

Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation. Use when tidying the monitoring database.

Why use Session Cleanup on TypingMind?

Because you install it once and use it with any model. Session Cleanup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Session Cleanup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-cleanup. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Session Cleanup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Session Cleanup?

As many as you like. As long as a model supports skills, you can use Session Cleanup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Session Cleanup AI skill free?

Yes. It is published on GitHub by hoangsonww under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇