/history
Show recently played tracks (a passive local playback log). Use when the user asks what played earlier, what song was on before, recently played music, or to clear the playback history.
Claude Code
$ npx -y skills add Bangs00/claude-media-control --skill history --agent claude-code
Codex
$ npx skills add Bangs00/claude-media-control --skill history -a codex -y
Cursor
$ npx skills add Bangs00/claude-media-control --skill history -a cursor -y
Gemini CLI
$ npx skills add Bangs00/claude-media-control --skill history -a gemini-cli -y
GitHub Copilot
$ npx skills add Bangs00/claude-media-control --skill history -a github-copilot -y
OpenCode
$ npx skills add Bangs00/claude-media-control --skill history -a opencode -y
Windsurf
$ npx skills add Bangs00/claude-media-control --skill history -a windsurf -y
SKILL.md
history.SKILL.mdname: history
description: Show recently played tracks (a passive local playback log). Use when the user asks what played earlier, what song was on before, recently played music, or to clear the playback history.
argument-hint: [count | clear]
allowed-tools: Bash
Requested: $ARGUMENTS
Recent playback history (newest first, `MM-DD HH:MM title — artist (app)`):
!`"${CLAUDE_PLUGIN_ROOT}/scripts/media.sh" history 20`
Now do the following:
1. If the request is a **number** (e.g. "last 50"), re-run with that count:
"${CLAUDE_PLUGIN_ROOT}/scripts/media.sh" history <count>2. If the request is to **clear/delete** the history, confirm intent first, then:
"${CLAUDE_PLUGIN_ROOT}/scripts/media.sh" history clear3. Otherwise present the lines above as a markdown list, newest first — `**title** — *artist* (app · MM-DD HH:MM)` — trimmed to what the user asked for. If the user asked about a specific track ("when did X play?"), answer just that from the list.
Notes you may need:
- Tracks are logged **passively** while media reads happen anyway (statusline
ticks, `/media:now`, playback commands) — there is no background polling, so gaps are normal when Claude Code wasn't running or the statusline is off.
- The log keeps the most recent 500 tracks in `history.jsonl` under the plugin
data directory; nothing ever leaves the machine.
- Logging is controlled by `/media:config history.record on|off`. If the user
asks to stop/start recording, use that key.
Read more
name: history description: Show recently played tracks (a passive local playback log). Use when the user asks what played earlier, what song was on before, recently played music, or to clear the playback history. argument-hint: [count | clear] allowed-tools: Bash
Requested: $ARGUMENTS
Recent playback history (newest first, `MM-DD HH:MM title — artist (app)`):
!`"${CLAUDE_PLUGIN_ROOT}/scripts/media.sh" history 20`
Now do the following:
1. If the request is a **number** (e.g. "last 50"), re-run with that count:
"${CLAUDE_PLUGIN_ROOT}/scripts/media.sh" history <count>2. If the request is to **clear/delete** the history, confirm intent first, then:
"${CLAUDE_PLUGIN_ROOT}/scripts/media.sh" history clear3. Otherwise present the lines above as a markdown list, newest first — `**title** — *artist* (app · MM-DD HH:MM)` — trimmed to what the user asked for. If the user asked about a specific track ("when did X play?"), answer just that from the list.
Notes you may need:
- Tracks are logged **passively** while media reads happen anyway (statusline
ticks, `/media:now`, playback commands) — there is no background polling, so gaps are normal when Claude Code wasn't running or the statusline is off.
- The log keeps the most recent 500 tracks in `history.jsonl` under the plugin
data directory; nothing ever leaves the machine.
- Logging is controlled by `/media:config history.record on|off`. If the user
asks to stop/start recording, use that key.
The current track, live in your Claude Code statusline — ticking every second, ⌘+clickable, styleable down to the bar characters: And whatever your Mac is playing — Spotify, Apple Music, a browser tab, VLC — you can control it from the chat too: "what song is
More skills from other plugins.
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…
Questions about history.
- Which coding agents can use history?
- history installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

