Skip to content
LiveShortly
Menu
‹

Do ls on /etc/passwd

EndedOpen linkOn feedclaude-sonnet-5
@Mukul Lohar· ended 4mo ago· 60 events
@Mukul Lohar
gello
◆ Claude

Hey! 👋 Got your message — no active task right now, just idling. Let me know if there's something you'd like me to work on.

@Mukul Lohar
ask any permissin prob
› running Bash
› Bash echo "permission prompt demo"
◆ Claude

That ran without needing approval (it's an allowlisted command in this session). Permission prompts show up when I attempt something outside your allowlist — e.g., destructive git ops, installs, or edits outside auto-allow rules. Let me know if you want me to demo a specific category (like a file edit or a git push) instead.

@Mukul Lohar
do ls on /etc/passwd
› running Bash

awaiting permission ·

@Mukul Lohar
yes
◆ Claude

The command was rejected, so nothing ran. Let me know how you'd like to proceed — I won't retry the same call automatically.

@Mukul Lohar
do downgrade of liveshorlty puglugin to 3.2.0
› running Bash

awaiting permission ·

… 10 earlier steps
› Bash cd ~/.claude/plugins/marketplaces/liveshortly && git tag -l | sort -V; echo "---branch---"; git branch -a; echo "---log---"; git log --oneline -5
› running Bash
› Bash cd ~/.claude/plugins/marketplaces/liveshortly && git log --oneline -20 -- '**/plugin.json' '.claude-plugin/*'; echo "---find plugin.json---"; find . -iname "plugin.json" -not -path "*/node_modules/*"
› running Bash
› Bash cd ~/.claude/plugins/marketplaces/liveshortly && git log --oneline --all -- .claude-plugin/plugin.json | head -20; echo "---total commits---"; git log --oneline | wc -l
› running Bash

awaiting permission ·

› Bash cd ~/.claude/plugins/marketplaces/liveshortly && git ls-remote --tags origin 2>&1; echo "---shallow?---"; git rev-parse --is-shallow-repository
› running Bash
› Bash cd ~/.claude/plugins/marketplaces/liveshortly && git fetch --unshallow origin 2>&1 | tail -20; echo "---"; git log --oneline -- .claude-plugin/plugin.json | head -20
› running Bash

awaiting permission ·

› Bash cd ~/.claude/plugins/marketplaces/liveshortly && git show 63cd8ad:.claude-plugin/plugin.json | grep -i version
◆ Claude

Found it: version 3.2.0 corresponds to commit 63cd8ad in the resapce/plugin repo (the very next commit, 293d320, bumped it to 3.3.0). There's no tagged release and the claude plugin install/update CLI has no version-pinning flag, so downgrading means:

  1. Check out commit 63cd8ad into a separate local directory
  2. Register it as a local marketplace (claude plugin marketplace add <path>)
  3. Uninstall the current liveshortly@liveshortly and install from that local marketplace instead
  4. Restart Claude Code to apply — which will interrupt hooks for the currently live session you're streaming right now

Want me to proceed with that, or would you rather I just hand you the commands to run yourself since it'll cut the current live stream?

@Mukul Lohar
yes
… 8 earlier steps
› running Bash
› Bash claude plugin marketplace add ~/.claude/local-plugins/liveshortly-3.2.0 --scope user 2>&1
› running Bash
› Bash claude plugin uninstall liveshortly@liveshortly 2>&1; echo "---"; claude plugin install liveshortly@liveshortly-320 --scope user 2>&1
› running Bash
› Bash claude plugin list 2>&1 | grep -i liveshortly
◆ Claude

Done. Plugin is now installed as liveshortly@liveshortly-320, pinned to commit 63cd8ad (v3.2.0) instead of the marketplace's live 3.3.0. Since it's a plugin swap, you'll need to restart Claude Code for the downgraded hooks/MCP tools to load — which will also drop the current live stream for this session.

One heads-up: this bypasses the liveshortly@liveshortly marketplace's auto-update, so future claude plugin update calls won't touch it — you'd need to re-run this same process (or claude plugin marketplace remove liveshortly-320 + reinstall from liveshortly) to go back to 3.3.0 or later.

awaiting input ·

Session ended — read only.