Session Check

---
name: session-check
description: Use when loading a built plugin in a harness session to check it — the command per harness and the setup each one needs first.
---

# Session check

Build first with `cargo xtask build`; each command loads what `dist/` holds.

| Harness | Command |
| --- | --- |
| Claude Code | `claude --plugin-dir dist/claude-code` |
| Claude Code, installed with its companions | `claude plugin marketplace add ./dist/claude-code`, then `claude plugin install tightship@tightship`, once the catalogs `DietrichGebert/ponytail`, `ayghri/i-have-adhd`, and `blader/humanizer` are added |
| Cursor | `agent --plugin-dir dist/cursor`, an interactive CLI session |
| Antigravity CLI | `agy plugin validate dist/antigravity-cli --strict` |

## Setup per harness

- **Claude Code** under `--plugin-dir` has no vault option: export `CLAUDE_PLUGIN_OPTION_VAULT_FOLDER`
  before `claude`. Its companions are enabled in the user settings, so `--setting-sources project` disables
  the plugin for a missing dependency; keep them and pass
  `--settings '{"enabledPlugins":{"tightship@tightship":false}}'`, so an installed copy stays off.
- **Cursor**'s `agent` runs from PowerShell with `$env:SHELL = $null`.
- **Antigravity CLI**: `agy plugin install` writes into the adopter's own config, and on Windows needs
  `hooks.windows.json` moved over `hooks.json` first, as `install.ps1` does.