Use SLB and CAAM for safety and account management.
Safety First
AI agents are powerful but can cause damage if misused. The Dicklesworthstone stack includes two safety tools:
SLB
Two-person rule for dangerous commands
CAAM
Agent authentication switching
SLB: Simultaneous Launch Button
SLB implements a "two-person rule" for dangerous commands. Just like nuclear launch codes require two keys, SLB requires two approvals before executing risky operations.
When to Use SLB
rm -rf /git push --force origin mainDROP DATABASE productionkubectl delete namespace prodSLB Commands
CAAM: Coding Agent Account Manager
CAAM enables sub-100ms account switching for subscription-based AI services (Claude Max, Codex CLI, Gemini Ultra). Swap OAuth tokens instantly without re-authenticating.
Token Management
Backup and restore OAuth tokens for each tool
Instant Switching
Switch accounts in under 100ms via symlink swap
Multi-Tool Support
Works with Claude, Codex, and Gemini CLIs
Profile Backup
Save profiles by email for easy restoration
CAAM Use Cases
CAAM Commands
Integration with Agents
Both SLB and CAAM integrate with Claude Code, Codex, and Gemini:
# Example: Dangerous command triggers SLB$ claude "delete all test files"> SLB: This command requires approval> Waiting for second approval...> Run 'slb approve req-123 --session-id <sid>' from another session# Example: Switch Claude accounts for a project$ caam activate claude work@company.com> Activated profile 'work@company.com' for claude> Symlink updated in 47ms$ claude "continue the project"> Using profile: work@company.com
Best Practices
SLB Best Practices
CAAM Best Practices
Quick Reference
SLB
$ slb pending$ slb run <cmd> --reason ...$ slb approve <id> --session-id ...$ slb status <id>CAAM
$ caam ls [tool]$ caam backup <tool> <email>$ caam activate <tool> <email>$ caam status [tool]