Skip to content

v1.5.5

Choose a tag to compare

View all tags
@CCimen CCimen released this 12 Jan 22:34
· 274 commits to main since this release
v1.5.5
4442655
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release Notes — v1.5.5

✨ Settings & Maintenance TUI (New Feature)

A new interactive Settings & Maintenance screen, accessible via the s key from the dashboard, providing a visual interface for system maintenance and configuration management.

TUI Navigation

Key Action
s Open Settings & Maintenance from dashboard
↑/↓ or j/k Navigate actions
←/→ or h/l Switch categories
Enter Execute action
p Preview affected paths and sizes
? Show help panel
Esc Go back / Close panels

Maintenance Actions

Action Risk Tier Description
Clear cache Safe ✓ Remove regenerable cache files
Clear contexts Changes State Clear recent work contexts
Prune containers Changes State Remove stopped Docker containers
Prune sessions Changes State Remove old sessions (keeps recent 20)
Reset exceptions Destructive Clear all policy exceptions
Delete all sessions Destructive Remove entire session history
Reset configuration Destructive Reset to defaults (requires setup)
Factory reset Very Destructive ☠ Remove all SCC data

Risk-Tiered Confirmation System

Actions are categorized by risk level with appropriate confirmation safeguards:

  • Tier 0 (Safe): No confirmation required
  • Tier 1 (Changes State): Simple Y/N confirmation
  • Tier 2 (Destructive): Y/N confirmation with impact preview
  • Tier 3 (Factory Reset): Type FACTORY RESET to confirm (case-insensitive)

CLI Commands

Command Description
scc reset Interactive maintenance hub (TTY mode)
scc reset --cache Clear regenerable cache files
scc reset --contexts Clear recent work contexts
scc reset --sessions Prune sessions (30d, keep 20)
scc reset --all Factory reset (everything)
scc config paths Show file locations, sizes, and permissions

🐛 Bug Fixes

Plugin Container Isolation

Fixed a critical issue where plugins installed inside containers caused errors on the host Claude instance.

Root cause: SCC wrote plugin settings to workspace/.claude/settings.local.json, causing host Claude to see container-only plugins and fail with "Plugin not found in marketplace" errors.

New behavior:

  • Marketplace materials still sync to workspace (container needs bind-mount access)
  • settings.local.json is not written to workspace (prevents host leakage)
  • Plugin settings are injected directly into container HOME (/home/agent/.claude/settings.json) after startup
  • Follows VS Code DevContainers pattern where container config stays container-local

✅ Result: scc plugins on host shows only host plugins; scc plugins in container shows team-specific plugins. No cross-contamination.

TUI & UX Fixes

  • Esc key handling: Added double-escape support for macOS terminal quirk
  • Factory reset confirmation: Now case-insensitive ("factory reset" works)
  • TTY error after setup: Fixed by passing all ctx.invoke parameters explicitly
  • Risk badge rendering: Fixed to use Rich Text objects for proper styling
  • Info panel: Fixed to properly render Text objects instead of markup strings

📦 Installation Update

Recommended installation method:

uv tool install scc-cli

Alternative (if you don't have uv):

pip install scc-cli

What’s Changed

  • feat(settings): add Settings & Maintenance TUI with UX polish — #70
  • fix: inject plugin settings to container HOME to prevent host leakage — #71
  • chore: bump version to 1.5.5 and update installation docs — #72

Full Changelog: v1.5.4...v1.5.5

Assets 2
Loading