claude-code-tools 0.2.0__py3-none-any.whl → 1.0.6__py3-none-any.whl

claude_code_tools-0.2.0.dist-info/METADATA

@@ -1,495 +0,0 @@
-Metadata-Version: 2.4
-Name: claude-code-tools
-Version: 0.2.0
-Summary: Collection of tools for working with Claude Code
-License-File: LICENSE
-Requires-Python: >=3.11
-Requires-Dist: click>=8.0.0
-Requires-Dist: fire>=0.5.0
-Requires-Dist: mcp>=1.13.0
-Requires-Dist: rich>=13.0.0
-Provides-Extra: dev
-Requires-Dist: commitizen>=3.0.0; extra == 'dev'
-Description-Content-Type: text/markdown
-
-# claude-code-tools
-
-A collection of practical tools, hooks, and utilities for enhancing Claude Code
-and other CLI coding agents.
-
-## Table of Contents
-
-- [🎮 tmux-cli: Bridging Claude Code and Interactive CLIs — "playwright for the terminal"](#tmux-cli-bridging-claude-code-and-interactive-clis)
-- [🚀 Quick Start](#quick-start)
-- [🎮 tmux-cli Deep Dive](#tmux-cli-deep-dive)
-- [🚀 lmsh (Experimental) — natural language to shell commands](#lmsh-experimental)
-- [🔍 find-claude-session — search and resume Claude sessions](#find-claude-session)
-- [🔍 find-codex-session — search and resume Codex sessions](#find-codex-session)
-- [🔐 vault — encrypted .env backup & sync](#vault)
-- [🔍 env-safe — inspect .env safely without values](#env-safe)
-- [🛡️ Claude Code Safety Hooks — guardrails for bash, git, env, files](#claude-code-safety-hooks)
-- [🤖 Using Claude Code with Open-weight Anthropic API-compatible LLM Providers](#using-claude-code-with-open-weight-anthropic-api-compatible-llm-providers)
-- [📚 Documentation](#documentation)
-- [📋 Requirements](#requirements)
-- [🛠️ Development](#development)
-- [📄 License](#license)
-
-<a id="tmux-cli-bridging-claude-code-and-interactive-clis"></a>
-## 🎮 tmux-cli: Bridging Claude Code and Interactive CLIs
-
-> **Note**: While the description below focuses on Claude Code, tmux-cli works with any CLI coding agent.
-
- ![tmux-cli demo](demos/tmux-cli-demo-short.gif)
-
-Consider these scenarios:
-
-You're using Claude Code (CC) to build an interactive script. The script prompts 
-for user input, but CC can't respond to prompts.
-
-You want Claude Code to debug using pdb, stepping through code line by line.
-
-You need your CLI code agent to launch another instance of the same OR different 
-CLI code agent, AND interact with it, not as a hidden sub-agent, 
-but as a visible session you can monitor (as shown in gif above).
-
-**tmux-cli enables these workflows** by giving Claude Code programmatic control 
-over terminal applications.
-
-For those new to [tmux](https://github.com/tmux/tmux/wiki), it's a terminal 
-multiplexer that lets you create and manage multiple terminal sessions. The key 
-benefit for our purposes is that tmux is scriptable and allows sending keystrokes 
-to specific panes or sessions programmatically.
-
-**Important**: You don't need to learn tmux-cli commands. Claude Code will handle 
-all the interactions automatically. Just tell CC what you want to do, and it will 
-use tmux-cli behind the scenes.
-
-**Think Playwright for terminals** - Terminal automation for AI agents.
-
-**Works anywhere**: Automatically handles both local tmux panes and remote sessions.
-
-<a id="quick-start"></a>
-## 🚀 Quick Start
-
-```bash
-# Install from PyPI (recommended)
-uv tool install claude-code-tools
-
-# Or install the latest development version from GitHub
-uv tool install git+https://github.com/pchalasani/claude-code-tools
-```
-
-This gives you:
-- `tmux-cli` - The interactive CLI controller we just covered
-- `find-claude-session` - Search and resume Claude Code sessions by keywords
-- `find-codex-session` - Search and resume Codex sessions by keywords
-- `vault` - Encrypted backup for your .env files
-- `env-safe` - Safely inspect .env files without exposing values
-
-<a id="tmux-cli-deep-dive"></a>
-## 🎮 tmux-cli Deep Dive
-
-### What Claude Code Can Do With tmux-cli
-
-1. **Test Interactive Scripts** - CC can run and interact with scripts that 
-   require user input, answering prompts automatically based on your instructions.
-
-2. **UI Development & Testing** - CC can launch web servers and coordinate with 
-   browser automation tools to test your applications.
-
-3. **Interactive Debugging** - CC can use debuggers (pdb, node inspect, gdb) to 
-   step through code, examine variables, and help you understand program flow.
-
-4. **Claude-to-Claude Communication** - CC can launch another Claude Code instance 
-   to get specialized help or code reviews.
-
-Claude Code knows how to use tmux-cli through its built-in help. You just describe 
-what you want, and CC handles the technical details.
-
-For complete command reference, see [docs/tmux-cli-instructions.md](docs/tmux-cli-instructions.md).
-
-### Setting up tmux-cli for Claude Code
-
-To enable CC to use tmux-cli, add this snippet to your global
-`~/.claude/CLAUDE.md` file:
-
-```markdown
-# tmux-cli Command to interact with CLI applications
-
-`tmux-cli` is a bash command that enables Claude Code to control CLI applications 
-running in separate tmux panes - launch programs, send input, capture output, 
-and manage interactive sessions. Run `tmux-cli --help` for detailed usage 
-instructions.
-
-Example uses:
-- Interact with a script that waits for user input
-- Launch another Claude Code instance to have it perform some analysis or review or 
-  debugging etc
-- Run a Python script with the Pdb debugger to step thru its execution, for 
-  code-understanding and debugging
-- Launch web apps and test them with browser automation MCP tools like Puppeteer
-```
-
-Incidentally, installing the Puppeteer MCP tool is easy:
-
-```bash
-claude mcp add puppeteer -- npx -y @modelcontextprotocol/server-puppeteer
-```
-
-For detailed instructions, see [docs/tmux-cli-instructions.md](docs/tmux-cli-instructions.md).
-
-<a id="lmsh-experimental"></a>
-## 🚀 lmsh (Experimental)
-
-Natural language shell - type what you want in plain English, get an editable command.
-
-```bash
-# Direct usage - translate, edit, execute, then enter interactive mode
-$ lmsh "show me all python files modified today"
-find . -name "*.py" -mtime 0  # <-- Edit before running
-
-# Or interactive mode
-$ lmsh
-lmsh> show recent docker containers
-docker ps -n 5  # <-- Edit before running
-```
-
-**Features:**
-- Rust-based for instant startup (<1ms binary load time)
-- Translates natural language to shell commands using Claude Code CLI
-- Commands are editable before execution - full control
-- Preserves your shell environment
-
-**Note:** Requires Claude Code CLI (`claude` command) to be installed. The translation adds ~2-3s due to Claude Code CLI startup.
-
-**Installation:**
-```bash
-# Install from crates.io (easiest, requires Rust)
-cargo install lmsh
-
-# Or build from source
-cd lmsh && cargo build --release
-cp target/release/lmsh ~/.cargo/bin/
-# Or: make lmsh-install
-```
-
-See [docs/lmsh.md](docs/lmsh.md) for details.
-
-<a id="find-claude-session"></a>
-## 🔍 find-claude-session
-
-Search and resume Claude Code sessions by keywords with an interactive UI.
-
-### Setup (Recommended)
-
-Add this function to your shell config (.bashrc/.zshrc) for persistent directory
-changes:
-
-```bash
-fcs() {
-    # Check if user is asking for help
-    if [[ "$1" == "--help" ]] || [[ "$1" == "-h" ]]; then
-        find-claude-session --help
-        return
-    fi
-    # Run find-claude-session in shell mode and evaluate the output
-    eval "$(find-claude-session --shell "$@" | sed '/^$/d')"
-}
-```
-
-Or source the provided function:
-```bash
-source /path/to/claude-code-tools/scripts/fcs-function.sh
-```
-
-### Usage
-
-```bash
-# Search in current project
-fcs "keyword1,keyword2,keyword3"
-
-# Search across all Claude projects  
-fcs "keywords" --global
-fcs "keywords" -g
-```
-
-### Features
-
-- Interactive session selection with previews
-- Cross-project search capabilities
-- Automatic session resumption with `claude -r`
-- Persistent directory changes when resuming cross-project sessions
-
-Note: You can also use `find-claude-session` directly, but directory changes
-won't persist after exiting Claude Code.
-
-For detailed documentation, see [docs/find-claude-session.md](docs/find-claude-session.md).
-
-Looks like this -- 
-
-![fcs.png](docs/fcs.png)
-
-<a id="find-codex-session"></a>
-## 🔍 find-codex-session
-
-Search and resume Codex sessions by keywords. Usage is similar to `find-claude-session` above, but works with Codex session files instead.
-
-### Key Differences from find-claude-session
-
-- Searches `~/.codex/sessions/` (organized by YYYY/MM/DD directories)
-- Extracts metadata from `session_meta` entries in Codex JSONL files
-- Resumes sessions with `codex resume <session-id>`
-
-### Usage
-
-```bash
-# Search in current project only (default)
-find-codex-session "keyword1,keyword2"
-
-# Search across all projects
-find-codex-session "keywords" -g
-find-codex-session "keywords" --global
-
-# Limit number of results
-find-codex-session "keywords" -n 5
-
-# Custom Codex home directory
-find-codex-session "keywords" --codex-home /custom/path
-```
-
-### Features
-
-- **Project filtering**: Search current project only (default) or all projects with `-g`
-- Case-insensitive AND keyword search across all session content
-- Interactive session selection with Rich table display
-- Shows project name, git branch, date, line count, and preview of last user message
-- Automatic session resumption with `codex resume`
-- Cross-project session support with directory change prompts
-- Reverse chronological ordering (most recent first)
-- Multi-line preview wrapping for better readability
-
-<a id="vault"></a>
-## 🔐 vault
-
-Centralized encrypted backup for .env files across all your projects using SOPS.
-
-```bash
-vault sync      # Smart sync (auto-detect direction)
-vault encrypt   # Backup .env to ~/Git/dotenvs/
-vault decrypt   # Restore .env from centralized vault
-vault list      # Show all project backups
-vault status    # Check sync status for current project
-```
-
-### Key Features
-
-- Stores all encrypted .env files in `~/Git/dotenvs/`
-- Automatic sync direction detection
-- GPG encryption via SOPS
-- Timestamped backups for safety
-
-For detailed documentation, see [docs/vault-documentation.md](docs/vault-documentation.md).
-
-<a id="env-safe"></a>
-## 🔍 env-safe
-
-Safely inspect .env files without exposing sensitive values. Designed for Claude Code and other automated tools that need to work with environment files without accidentally leaking secrets.
-
-```bash
-env-safe list                    # List all environment variable keys
-env-safe list --status           # Show keys with defined/empty status  
-env-safe check API_KEY           # Check if a specific key exists
-env-safe count                   # Count total, defined, and empty variables
-env-safe validate                # Validate .env file syntax
-env-safe --help                  # See all options
-```
-
-### Key Features
-
-- **No Value Exposure** - Never displays actual environment values
-- **Safe Inspection** - Check which keys exist without security risks
-- **Syntax Validation** - Verify .env file format is correct
-- **Status Checking** - See which variables are defined vs empty
-- **Claude Code Integration** - Works with protection hooks to provide safe alternative
-
-### Why env-safe?
-
-Claude Code is completely blocked from directly accessing .env files - no reading, writing, or editing allowed. This prevents both accidental exposure of API keys and unintended modifications. The `env-safe` command provides the only approved way for Claude Code to inspect environment configuration safely, while any modifications must be done manually outside of Claude Code.
-
-<a id="claude-code-safety-hooks"></a>
-## 🛡️ Claude Code Safety Hooks
-
-This repository includes a comprehensive set of safety hooks that enhance Claude
-Code's behavior and prevent dangerous operations.
-
-### Key Safety Features
-
-- **File Deletion Protection** - Blocks `rm` commands, enforces TRASH directory
-  pattern
-- **Git Safety** - Advanced git add protection with:
-  - Hard blocks: `git add .`, `git add ../`, `git add *`, `git add -A/--all`
-  - Speed bumps: Shows files before staging directories (e.g., `git add src/`)
-  - Commit speed bump: Warns on first attempt, allows on second
-  - Prevents unsafe checkouts and accidental data loss
-- **Environment Security** - Blocks all .env file operations (read/write/edit),
-  suggests `env-safe` command for safe inspection
-- **Context Management** - Blocks reading files >500 lines to prevent context
-  bloat
-- **Command Enhancement** - Enforces ripgrep (`rg`) over grep for better
-  performance
-
-### Quick Setup
-
-1. Copy the hooks configuration from `hooks/settings.sample.json` 
-
-2. Add the hooks to your global Claude settings at `~/.claude/settings.json`:
-   - If the file doesn't exist, create it
-   - Copy the "hooks" section from settings.sample.json
-   - Replace `/path/to/claude-code-tools` with your actual path to this repository
-   
-   Example ~/.claude/settings.json:
-   ```json
-   {
-     "hooks": {
-       // ... hooks configuration from settings.sample.json ...
-     }
-   }
-   ```
-
-### Available Hooks
-
-- `bash_hook.py` - Comprehensive bash command safety checks
-- `env_file_protection_hook.py` - Blocks all .env file operations
-- `file_size_conditional_hook.py` - Prevents reading huge files
-- `grep_block_hook.py` - Enforces ripgrep usage
-- `notification_hook.sh` - Sends ntfy.sh notifications
-- `pretask/posttask_subtask_flag.py` - Manages sub-agent state
-
-For complete documentation, see [hooks/README.md](hooks/README.md).
-
-<a id="using-claude-code-with-open-weight-anthropic-api-compatible-llm-providers"></a>
-## 🤖 Using Claude Code with Open-weight Anthropic API-compatible LLM Providers
-
-You can use Claude Code with alternative LLMs served via Anthropic-compatible
-APIs, e.g. Kimi-k2, GLM4.5 (from zai), Deepseek-v3.1. 
-Add these functions to your shell config (.bashrc/.zshrc):
-
-```bash
-kimi() {
-    (
-        export ANTHROPIC_BASE_URL=https://api.moonshot.ai/anthropic
-        export ANTHROPIC_AUTH_TOKEN=$KIMI_API_KEY
-        claude "$@"
-    )
-}
-
-zai() {
-    (
-        export ANTHROPIC_BASE_URL=https://api.z.ai/api/anthropic
-        export ANTHROPIC_AUTH_TOKEN=$Z_API_KEY
-        claude "$@"
-    )
-}
-
-dseek() {
-    (
-        export ANTHROPIC_BASE_URL=https://api.deepseek.com/anthropic
-        export ANTHROPIC_AUTH_TOKEN=${DEEPSEEK_API_KEY}
-        export ANTHROPIC_MODEL=deepseek-chat
-        export ANTHROPIC_SMALL_FAST_MODEL=deepseek-chat        
-        claude "$@"
-    )
-}
-```
-
-After adding these functions:
-- Set your API keys: `export KIMI_API_KEY=your-kimi-key`,
-  `export Z_API_KEY=your-z-key`, `export DEEPSEEK_API_KEY=your-deepseek-key`
-- Run `kimi` to use Claude Code with the Kimi K2 LLM
-- Run `zai` to use Claude Code with the GLM-4.5 model
-- Run `dseek` to use Claude Code with the DeepSeek model
-
-The functions use subshells to ensure the environment variables don't affect 
-your main shell session, so you could be running multiple instances of Claude Code,
-each using a different LLM.
-
-<a id="documentation"></a>
-## 📚 Documentation
-
-- [tmux-cli detailed instructions](docs/tmux-cli-instructions.md) - 
-  Comprehensive guide for using tmux-cli
-- [Claude Code tmux tutorials](docs/claude-code-tmux-tutorials.md) - 
-  Additional tutorials and examples
-- [Vault documentation](docs/vault-documentation.md) - 
-  Complete guide for the .env backup system
-- [Hook configuration](hooks/README.md) - Setting up Claude Code hooks
-
-<a id="requirements"></a>
-## 📋 Requirements
-
-- Python 3.11+
-- uv (for installation)
-- tmux (for tmux-cli functionality)
-- SOPS (for vault functionality)
-
-<a id="development"></a>
-## 🛠️ Development
-
-### Setup
-
-1. Clone the repository:
-   ```bash
-   git clone https://github.com/username/claude-code-tools
-   cd claude-code-tools
-   ```
-
-2. Create and activate a virtual environment with uv:
-   ```bash
-   uv venv
-   source .venv/bin/activate  # On Windows: .venv\Scripts\activate
-   ```
-
-3. Install in development mode:
-   ```bash
-   make install      # Install tools in editable mode
-   make dev-install  # Install with dev dependencies (includes commitizen)
-   ```
-
-### Making Changes
-
-- The tools are installed in editable mode, so changes take effect immediately
-- Test your changes by running the commands directly
-- Follow the existing code style and conventions
-
-### Version Management
-
-The project uses commitizen for version management:
-
-```bash
-make patch  # Bump patch version (0.0.X)
-make minor  # Bump minor version (0.X.0)  
-make major  # Bump major version (X.0.0)
-```
-
-### Contributing
-
-1. Fork the repository
-2. Create a feature branch (`git checkout -b feature/amazing-feature`)
-3. Make your changes
-4. Test thoroughly
-5. Commit your changes (commitizen will format the commit message)
-6. Push to your fork
-7. Open a Pull Request
-
-### Available Make Commands
-
-Run `make help` to see all available commands:
-- `make install` - Install in editable mode for development
-- `make dev-install` - Install with development dependencies
-- `make release` - Bump patch version and install globally
-- `make patch/minor/major` - Version bump commands
-
-<a id="license"></a>
-## 📄 License
-
-MIT

claude_code_tools-0.2.0.dist-info/RECORD

@@ -1,22 +0,0 @@
-claude_code_tools/__init__.py,sha256=CT_2W9O4WI9FzVRSv2aWi3GUcT26f2XEaWEPlJzZmhc,89
-claude_code_tools/codex_bridge_mcp.py,sha256=0roYm3YgEFB6y2MvGovzHyY7avKtire4qBtz3kVaYoY,12596
-claude_code_tools/dotenv_vault.py,sha256=KPI9NDFu5HE6FfhQUYw6RhdR-miN0ScJHsBg0OVG61k,9617
-claude_code_tools/env_safe.py,sha256=TSSkOjEpzBwNgbeSR-0tR1-pAW_qmbZNmn3fiAsHJ4w,7659
-claude_code_tools/find_claude_session.py,sha256=zHPIGcq8Af1IRAGd0BTfjLWQngxy7zMzYuSeWfnsVR0,24201
-claude_code_tools/find_codex_session.py,sha256=gx2QK001QHrVNRpV8_-wjCSGwpK-YAosyRMO5ltaXyU,15583
-claude_code_tools/tmux_cli_controller.py,sha256=5QDrDlv3oabIghRHuP8jMhUfxPeyYZxizNWW5sVuJIg,34607
-claude_code_tools/tmux_remote_controller.py,sha256=eY1ouLtUzJ40Ik4nqUBvc3Gl1Rx0_L4TFW4j708lgvI,9942
-docs/cc-codex-instructions.md,sha256=5E9QotkrcVYIE5VrvJGi-sg7tdyITDrsbhaqBKr4MUk,1109
-docs/claude-code-chutes.md,sha256=jCnYAAHZm32NGHE0CzGGl3vpO_zlF_xdmr23YxuCjPg,8098
-docs/claude-code-tmux-tutorials.md,sha256=S-9U3a1AaPEBPo3oKpWuyOfKK7yPFOIu21P_LDfGUJk,7558
-docs/dot-zshrc.md,sha256=DC2fOiGrUlIzol6N_47CW53a4BsnMEvCnhlRRVxFCTc,7160
-docs/find-claude-session.md,sha256=fACbQP0Bj5jqIpNWk0lGDOQQaji-K9Va3gUv2RA47VQ,4284
-docs/lmsh.md,sha256=o2TNP1Yfl3zW23GzEqK8Bx6z1hQof_lplaeEucuHNRU,1335
-docs/reddit-post.md,sha256=ZA7kPoJNi06t6F9JQMBiIOv039ADC9lM8YXFt8UA_Jg,2345
-docs/tmux-cli-instructions.md,sha256=hKGOdaPdBlb5XFzHfi0Mm7CVlysBuJUAfop3GHreyuw,5008
-docs/vault-documentation.md,sha256=5XzNpHyhGU38JU2hKEWEL1gdPq3rC2zBg8yotK4eNF4,3600
-claude_code_tools-0.2.0.dist-info/METADATA,sha256=5brLd-Ya8_bGL6fm_Ee35I6eFvr3trzm-HRGK4V4ed8,16925
-claude_code_tools-0.2.0.dist-info/WHEEL,sha256=qtCwoSJWgHk21S1Kb4ihdzI2rlJ1ZKaIurTj_ngOhyQ,87
-claude_code_tools-0.2.0.dist-info/entry_points.txt,sha256=rAHzNUN7b_HIRbFlvpYwK38FG6jREYWaO0ssnhAVPrg,287
-claude_code_tools-0.2.0.dist-info/licenses/LICENSE,sha256=BBQdOBLdFB3CEPmb3pqxeOThaFCIdsiLzmDANsCHhoM,1073
-claude_code_tools-0.2.0.dist-info/RECORD,,