pluginslab

Wims — Development skill for Claude Code

Development community

Where Is My Session — find, preview and resume any Claude Code session, from any folder.

How to install Wims

This entry records only its repository, not the path inside it, so there is no exact command to give. Open pluginslab/wims and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Wims does

Where Is My Session — find, preview and resume any Claude Code session, from any folder.

Alternatives in Development

  • Earnings Preview — 财报前预览 — 一致预期对照 + 行业观察指标 + Bull/Base/Bear 三情景 + 催化剂清单 + 预期波幅 6.6k ★
  • Maestro Session Manage — Manage a v3 Session — inspect status/resume-view, review knowledge candidates, complete, archive/unarchive 530 ★
  • Harness Remote — Native-session control plane for Codex, Claude Code, OpenCode, OMP and PI 356 ★

README

wims: where is my session

**Find, preview and resume any Claude Code session, from any folder.**

[![CI](https://github.com/pluginslab/wims/actions/workflows/ci.yml/badge.svg)](https://github.com/pluginslab/wims/actions/workflows/ci.yml) [![npm](https://img.shields.io/npm/v/@pluginslab/wims.svg)](https://www.npmjs.com/package/@pluginslab/wims) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![Node](https://img.shields.io/badge/node-%E2%89%A520-brightgreen.svg)](https://nodejs.org)

You started a Claude Code session about that webhook bug. It was a good session. It was also three days and forty folders ago, and `claude --resume` only lists sessions for the directory you happen to be standing in. So you either remember where you were, or you lose the thread.

`wims` lists **every** Claude Code session on your machine, wherever you started it. Search it, preview it, hit enter, and your shell lands *in that folder* with the conversation resumed.

![wims listing every Claude Code session](assets/wims.svg)

Install

Requires **Node 20+**, and the `claude` CLI to actually resume anything.

From npm

npm install -g @pluginslab/wims

That gives you the `wims-tui` binary. To get the `wims` command that also moves your shell, install the shell function once:

mkdir -p ~/.config/wims
wims-tui --print-shim > ~/.config/wims/wims.sh
echo '[ -f ~/.config/wims/wims.sh ] && . ~/.config/wims/wims.sh' >> ~/.zshrc

Use `~/.bashrc` for bash. For fish, drop it straight into the autoload directory and skip the sourcing line entirely:

wims-tui --print-shim fish > ~/.config/fish/functions/wims.fish

Open a new shell and run `wims`.

Writing the shim to a file is deliberate. `eval "$(wims-tui --print-shim)"` in your rc file also works, but it starts Node on every single shell you open.

From source

git clone https://github.com/pluginslab/wims.git
cd wims
./install.sh
``