Plugin Updates

How to update typemux-cc and fix cache issues

Known Claude Code Cache Issue

Claude Code has a known issue where /plugin update does not refresh cached plugin files.

After running /plugin update, you may still see the old version of typemux-cc running because Claude Code serves the plugin from cache instead of the newly downloaded files.

Symptoms of Stale Cache

If you experience any of these after updating:

• New features mentioned in release notes are not available
• Bug fixes don’t take effect
• Log messages show an old version number
• Behavior hasn’t changed despite update command succeeding

You likely have a cached plugin that needs manual clearing.

Manual Cache Clearing Steps

1. Remove cached plugin files

   rm -rf ~/.claude/plugins/cache/typemux-cc-marketplace/
   

   This removes the cached version that Claude Code is serving.

2. Reinstall the plugin

   /plugin install typemux-cc@typemux-cc-marketplace
   

   This downloads fresh plugin files from the marketplace.

3. Restart Claude Code

   Completely quit and restart Claude Code (not just reload window).

Bookmark this page for quick reference next time you update typemux-cc.

Verifying Update Succeeded

After reinstalling and restarting, verify the new version is active:

1. Check Plugin Directory

ls -lh ~/.claude/plugins/cache/typemux-cc-marketplace/

Check the timestamp — it should match when you ran the reinstall command.

2. Check Binary Version

If the plugin includes version info in logs:

# Enable file logging first if not already enabled
mkdir -p ~/.config/typemux-cc
cat > ~/.config/typemux-cc/config << 'EOF'
export TYPEMUX_CC_LOG_FILE="/tmp/typemux-cc.log"
EOF

Restart Claude Code, open a Python file, and check logs:

head -20 /tmp/typemux-cc.log | grep -i version

3. Test New Features

If the update added new features, test them:

# Example: if a new backend was added
echo 'export TYPEMUX_CC_BACKEND="new-backend"' >> ~/.config/typemux-cc/config

Restart Claude Code and verify it works.

Reinstalling After Update (Full Procedure)

If you want to be thorough, follow this complete reinstall procedure:

1. Check current version

   ls -lh ~/.claude/plugins/cache/typemux-cc-marketplace/
   

   Note the timestamp of existing files.

2. Update via Claude Code

   /plugin update typemux-cc@typemux-cc-marketplace
   

   Wait for the command to complete.

3. Clear the cache

   rm -rf ~/.claude/plugins/cache/typemux-cc-marketplace/
   
4. Reinstall

   /plugin install typemux-cc@typemux-cc-marketplace
   
5. Verify fresh files

   ls -lh ~/.claude/plugins/cache/typemux-cc-marketplace/
   

   Timestamp should be newer than before.

6. Restart Claude Code

   Quit Claude Code completely and restart.

When to Manually Clear Cache

You should manually clear cache in these situations:

After Every Update

Recommended: Manually clear cache after every /plugin update to ensure you’re running the latest version.

rm -rf ~/.claude/plugins/cache/typemux-cc-marketplace/ && \
/plugin install typemux-cc@typemux-cc-marketplace

Bug Fixes Not Working

If release notes mention a bug fix but you still see the bug:

1. Clear cache
2. Reinstall
3. Test again

If the bug persists after a fresh install, it may not be fixed yet or you may have a different issue.

After Manual Plugin File Edits

If you manually edited files in ~/.claude/plugins/cache/typemux-cc-marketplace/ for testing:

Always reinstall afterward:

rm -rf ~/.claude/plugins/cache/typemux-cc-marketplace/
/plugin install typemux-cc@typemux-cc-marketplace

Manual edits to cached plugin files are for debugging only. They will be lost on next update.

Unexplained Behavior After Update

If typemux-cc behaves strangely after an update:

1. Clear cache and reinstall (as shown above)
2. Enable trace logging:
   echo 'export RUST_LOG="typemux_cc=trace"' > ~/.config/typemux-cc/config
   echo 'export TYPEMUX_CC_LOG_FILE="/tmp/typemux-cc.log"' >> ~/.config/typemux-cc/config
   
3. Restart Claude Code
4. Check logs for errors:
   grep -i error /tmp/typemux-cc.log
   

Alternative: Local Development Install

If you frequently encounter cache issues, consider using a local development install:

# Clone the repo
git clone https://github.com/K-dash/typemux-cc.git
cd typemux-cc

# Build from source
cargo build --release

# Install as local plugin
/plugin marketplace add /path/to/typemux-cc
/plugin install typemux-cc@typemux-cc-marketplace

# Restart Claude Code

With a local install, you control when to update by pulling from git and rebuilding. No cache surprises.

Update Checklist

Use this checklist every time you update typemux-cc:

• Run /plugin update typemux-cc@typemux-cc-marketplace
• Remove cache: rm -rf ~/.claude/plugins/cache/typemux-cc-marketplace/
• Reinstall: /plugin install typemux-cc@typemux-cc-marketplace
• Verify new timestamp: ls -lh ~/.claude/plugins/cache/typemux-cc-marketplace/
• Restart Claude Code
• Open a Python file and verify type-checking works
• Check logs for any errors: tail -50 /tmp/typemux-cc.log

Downgrading to Previous Version

If an update introduces a regression:

Claude Code plugin system doesn’t support version pinning directly, but you can install from a specific git tag.

# 1. Clone repo and checkout specific version
git clone https://github.com/K-dash/typemux-cc.git
cd typemux-cc
git checkout v0.1.0  # Replace with desired version

# 2. Build
cargo build --release

# 3. Remove marketplace version
/plugin uninstall typemux-cc@typemux-cc-marketplace

# 4. Install local version
/plugin marketplace add /path/to/typemux-cc
/plugin install typemux-cc@typemux-cc-marketplace

# 5. Restart Claude Code

Reporting Update Issues

If you suspect a plugin update problem:

1. Confirm cache is clear:

   ls -lh ~/.claude/plugins/cache/typemux-cc-marketplace/
   

   Timestamp should be recent.

2. Capture logs:

   tail -100 /tmp/typemux-cc.log > typemux-update-issue.log
   

3. Include in report:

   • Output of ls -lh ~/.claude/plugins/cache/typemux-cc-marketplace/
   • Steps you followed to update
   • Log file
   • Expected vs actual behavior