tunacode-cli 0.0.76__tar.gz → 0.0.76.1__tar.gz

{tunacode_cli-0.0.76 → tunacode_cli-0.0.76.1}/.github/workflows/publish.yml

@@ -71,5 +71,3 @@ jobs:
           TWINE_USERNAME: __token__
           TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
         run: python -m twine upload dist/*
-
-      

tunacode_cli-0.0.76.1/CLAUDE.md

@@ -0,0 +1,132 @@
+
+### Workflow
+Make this repository perfectly optimized for you and future instances of Claude working with it. Implement the following structure and instructions precisely:
+
+### Directory Structure
+
+```
+claude/
+├── metadata/
+│   ├── dependency_graphs/
+│   ├── file_classifications.json (implementation vs. interface)
+│   └── intent_classifications.json
+├── semantic_index/
+│   ├── function_call_graphs.json
+│   ├── intent_mappings.json
+│   └── type_relationships.json
+├── debug_history/
+│   ├── error_solution_logs.json (categorized by component and error type)
+│   └── context_and_versions.json
+├── patterns/
+│   ├── canonical_patterns/
+│   ├── empirical_interface_patterns/
+│   └── reliability_metrics.json
+├── cheatsheets/
+│   └── component_cheatsheets.md (quick-reference guides, known pitfalls, Claude-specific behaviors)
+├── qa/
+│   ├── solved_problems/
+│   ├── context_logs/
+│   └── reasoning_docs/
+├── debug_history/
+│   └── debug_sessions.json (error→solution pairs, context, code versions)
+├── docs_model_friendly/
+│   ├── component_purpose.md
+│   └── component_relationships.md
+├── delta_summaries/
+│   ├── api_change_logs.json
+│   ├── behavior_changes.json
+│   └── reasoning_logs/
+└── memory_anchors/
+    ├── anchors.json (UUID-based anchors with semantic structure)
+
+To perfectly optimize this repository for you and future instances of Claude working with it, implement the following explicit instructions:
+
+1. **Claude-specific Metadata Directory**
+   - Maintain normalized metadata about the codebase, including dependency graphs, file types (implementation/interface), and intent classifications.
+
+2. **Semantic Code Indexing**
+   - Create a semantic index with intent classification and pre-analyzed semantic relationships.
+   - Document detailed function-to-function call graphs and intent mappings.
+
+3. **Debug History Database**
+   - Log all debugging sessions explicitly, including error-solution pairs, context, code versions, and categorization by component/error type.
+
+4. **Pattern and Industry Database**
+   - Provide canonical implementation patterns and empirical interface examples.
+   - Include explicit reliability metrics for assessing robustness.
+
+4. **Component-specific Cheat Sheets**
+   - Create quick-reference guides documenting common operations, pitfalls, edge cases, and Claude-specific behaviors clearly.
+
+5. **Queries-and-Answers Database**
+   - Store solved queries explicitly indexed by component, file, error type, with context and detailed reasoning.
+
+6. **Claude-specific Model-Friendly Documentation**
+   - Include clear, explicit documentation on component purposes and relationships optimized for Claude.
+
+7. **Delta Summaries**
+   - Clearly document semantic change logs, highlighting API changes, behavior shifts, and reasoning behind these changes.
+
+7. **Explicit Memory Anchors**
+   - Embed special "memory anchor" comments with UUID-based identifiers and semantic structure for easy and precise future reference.
+
+Implementing these changes ensures an optimized, efficient, and highly actionable Claude-specific repository structure for current and future Claude interactions
+
+- **CRITICAL: WORKTREE REQUIREMENT** - When user requests a worktree, you MUST:
+  1. Create the worktree with `git worktree add -b branch-name ../dirname`
+  2. If access is blocked, immediately ask: "I cannot access the worktree directory. Should I: a) Work in a subdirectory instead, b) Use a branch in the main directory, or c) Another solution?"
+  3. NEVER proceed without a worktree if user specifically requested one
+
+- before any updates make a git commit rollback point, clearly labeled for future agents
+
+- the clear outline of the objective MUST be established before we begin ANY coding, do not under any circumstance begin any updates untill this is clearly understood, if you have any ambiuguity or quesiton, the user can be brought in or use best practises
+
+- pre-commit hooks can NOT be skipped, you will be punished for skipping the
+
+
+- grep documentation and .claude as needed BOTH of these have a README.md that ahs a direcoty map, you MUST read these before any bigger grep or context searches
+
+- in general gather as much context as needed, unless specified by the user
+
+- this is the most important part of this prompt: Synthesis context aggressively and heuristically AS NEEDED ONLY You can deploy the appropriate subagent for complex tasks agents list below
+
+### Documentation
+
+- update the documents @documentation and in .claude after any update.
+
+- use the subagent tech-docs-maintainer to update the documentation you MUST instruct the subagent to keep doc updates short you will be PUNISHED for not telling the documentation agent to keep it to only the most distilled information
+
+- always follow best practices with git commits naming and gh cli workflows
+
+- commit frequently
+
+- always be on the side of safety, if you have any question consult the user
+
+### Python Coding Standards
+
+- always use the .venv
+- Use type hints (PEP 484) for all function signatures
+- Prefer f-strings (PEP 498) over %-formatting or .format()
+- Use pathlib.Path instead of os.path for filesystem operations
+- Structure imports: stdlib → third-party → local (PEP 8)
+- Use dataclasses (PEP 557) for simple data containers
+- Prefer context managers (with) for resource handling
+- Use structural pattern matching (PEP 634) for complex
+- run ruff frequently for both linting and formatting
+
+### Testing
+
+- "hatch run test" command for testing suite
+
+- anytime a new feature or refactor is done, we MUST find or make the golden/character test FIRST as a baseline standaard BEFORE starting, under no circumstance are you to NOT follow this TDD pattern
+
+- if a test for a feature does not exist you MUST create one FIRST to capture current behavior
+
+
+
+
+## Available Agents:
+
+1. **bug-context-analyzer** - Investigates precise context around bugs without suggesting fixes
+2. **code-synthesis-analyzer** - Analyzes recent code changes to identify issues needing fixes
+3. **documentation-synthesis-qa** - Creates comprehensive docs via multi-agent orchestration

{tunacode_cli-0.0.76 → tunacode_cli-0.0.76.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tunacode-cli
-Version: 0.0.76
+Version: 0.0.76.1
 Summary: Your agentic CLI developer.
 Project-URL: Homepage, https://tunacode.xyz/
 Project-URL: Repository, https://github.com/alchemiststudiosDOTai/tunacode
@@ -75,6 +75,27 @@ pip install tunacode-cli
 
 For detailed installation and configuration instructions, see the [**Getting Started Guide**](documentation/user/getting-started.md).
 
+## Quickstart
+
+```bash
+# 1) Install
+pip install tunacode-cli
+
+# 2) Launch the CLI
+tunacode --wizard   # guided setup (enter an API key, pick a model)
+
+# 3) Try common commands in the REPL
+/help        # see commands
+/model       # explore models and set a default
+/plan        # enter read-only Plan Mode
+```
+
+Tip: You can also skip the wizard and set everything via flags:
+
+```bash
+tunacode --model openai:gpt-4.1 --key sk-your-key
+```
+
 ## Development Installation
 
 For contributors and developers who want to work on TunaCode:
@@ -87,13 +108,13 @@ cd tunacode
 # Quick setup (recommended)
 ./scripts/setup_dev_env.sh
 
-# Or manual setup
-python3 -m venv venv
-source venv/bin/activate  # On Windows: venv\Scripts\activate
-pip install -e ".[dev]"
+# Or manual setup with UV (recommended)
+uv venv
+source .venv/bin/activate  # On Windows: .venv\Scripts\activate
+uv pip install -e ".[dev]"
 
 # Verify installation
-python -m tunacode --version
+tunacode --version
 ```
 
 See the [Hatch Build System Guide](documentation/development/hatch-build-system.md) for detailed instructions on the development environment.
@@ -102,6 +123,42 @@ See the [Hatch Build System Guide](documentation/development/hatch-build-system.
 
 Choose your AI provider and set your API key. For more details, see the [Configuration Section](documentation/user/getting-started.md#2-configuration) in the Getting Started Guide. For local models (LM Studio, Ollama, etc.), see the [Local Models Setup Guide](documentation/configuration/local-models.md).
 
+### New: Enhanced Model Selection
+
+TunaCode now automatically saves your model selection for future sessions. When you choose a model using `/model <provider:name>`, it will be remembered across restarts.
+
+**If you encounter API key errors**, you can manually create a configuration file that matches the current schema:
+
+```bash
+# Create the config file
+cat > ~/.config/tunacode.json << 'EOF'
+{
+  "default_model": "openai:gpt-4.1",
+  "env": {
+    "OPENAI_API_KEY": "your-openai-api-key-here",
+    "ANTHROPIC_API_KEY": "",
+    "GEMINI_API_KEY": "",
+    "OPENROUTER_API_KEY": ""
+  },
+  "settings": {
+    "enable_streaming": true,
+    "max_iterations": 40,
+    "context_window_size": 200000
+  },
+  "mcpServers": {}
+}
+EOF
+```
+
+Replace the model and API key with your preferred provider and credentials. Examples:
+- `openai:gpt-4.1` (requires OPENAI_API_KEY)
+- `anthropic:claude-4-sonnet-20250522` (requires ANTHROPIC_API_KEY)
+- `google:gemini-2.5-pro` (requires GEMINI_API_KEY)
+
+### ⚠️ Important Notice
+
+I apologize for any recent issues with model selection and configuration. I'm actively working to fix these problems and improve the overall stability of TunaCode. Your patience and feedback are greatly appreciated as I work to make the tool more reliable.
+
 ### Recommended Models
 
 Based on extensive testing, these models provide the best performance:

{tunacode_cli-0.0.76 → tunacode_cli-0.0.76.1}/README.md

@@ -27,6 +27,27 @@ pip install tunacode-cli
 
 For detailed installation and configuration instructions, see the [**Getting Started Guide**](documentation/user/getting-started.md).
 
+## Quickstart
+
+```bash
+# 1) Install
+pip install tunacode-cli
+
+# 2) Launch the CLI
+tunacode --wizard   # guided setup (enter an API key, pick a model)
+
+# 3) Try common commands in the REPL
+/help        # see commands
+/model       # explore models and set a default
+/plan        # enter read-only Plan Mode
+```
+
+Tip: You can also skip the wizard and set everything via flags:
+
+```bash
+tunacode --model openai:gpt-4.1 --key sk-your-key
+```
+
 ## Development Installation
 
 For contributors and developers who want to work on TunaCode:
@@ -39,13 +60,13 @@ cd tunacode
 # Quick setup (recommended)
 ./scripts/setup_dev_env.sh
 
-# Or manual setup
-python3 -m venv venv
-source venv/bin/activate  # On Windows: venv\Scripts\activate
-pip install -e ".[dev]"
+# Or manual setup with UV (recommended)
+uv venv
+source .venv/bin/activate  # On Windows: .venv\Scripts\activate
+uv pip install -e ".[dev]"
 
 # Verify installation
-python -m tunacode --version
+tunacode --version
 ```
 
 See the [Hatch Build System Guide](documentation/development/hatch-build-system.md) for detailed instructions on the development environment.
@@ -54,6 +75,42 @@ See the [Hatch Build System Guide](documentation/development/hatch-build-system.
 
 Choose your AI provider and set your API key. For more details, see the [Configuration Section](documentation/user/getting-started.md#2-configuration) in the Getting Started Guide. For local models (LM Studio, Ollama, etc.), see the [Local Models Setup Guide](documentation/configuration/local-models.md).
 
+### New: Enhanced Model Selection
+
+TunaCode now automatically saves your model selection for future sessions. When you choose a model using `/model <provider:name>`, it will be remembered across restarts.
+
+**If you encounter API key errors**, you can manually create a configuration file that matches the current schema:
+
+```bash
+# Create the config file
+cat > ~/.config/tunacode.json << 'EOF'
+{
+  "default_model": "openai:gpt-4.1",
+  "env": {
+    "OPENAI_API_KEY": "your-openai-api-key-here",
+    "ANTHROPIC_API_KEY": "",
+    "GEMINI_API_KEY": "",
+    "OPENROUTER_API_KEY": ""
+  },
+  "settings": {
+    "enable_streaming": true,
+    "max_iterations": 40,
+    "context_window_size": 200000
+  },
+  "mcpServers": {}
+}
+EOF
+```
+
+Replace the model and API key with your preferred provider and credentials. Examples:
+- `openai:gpt-4.1` (requires OPENAI_API_KEY)
+- `anthropic:claude-4-sonnet-20250522` (requires ANTHROPIC_API_KEY)
+- `google:gemini-2.5-pro` (requires GEMINI_API_KEY)
+
+### ⚠️ Important Notice
+
+I apologize for any recent issues with model selection and configuration. I'm actively working to fix these problems and improve the overall stability of TunaCode. Your patience and feedback are greatly appreciated as I work to make the tool more reliable.
+
 ### Recommended Models
 
 Based on extensive testing, these models provide the best performance:

{tunacode_cli-0.0.76 → tunacode_cli-0.0.76.1}/documentation/README.md

@@ -4,7 +4,7 @@ Project documentation for tunacode.
 
 ## Directory Structure
 
-```
+```text
 documentation/
 ├── agent/                  # Agent architecture and workflows
 │   ├── TOOLS_WORKFLOW.md
@@ -12,6 +12,8 @@ documentation/
 │   └── main-agent-architecture.md
 ├── configuration/         # System configuration docs
 │   ├── config-file-example.md
+│   ├── config-flow-diagram.md
+│   ├── config-touch-points.md
 │   ├── local-models.md
 │   └── logging-configuration.md
 ├── development/          # Development practices
@@ -21,7 +23,8 @@ documentation/
 │   ├── hatch-build-system.md
 │   ├── performance-optimizations.md
 │   ├── publishing-workflow.md
-│   └── prompt-principles.md
+│   ├── prompt-principles.md
+│   └── streaming-text-prefix-fix.md
 │── user/                 # user guides
     │── getting-started.md
     │── commands.md
@@ -41,3 +44,4 @@ General project documentation for features, architecture, and best practices.
 - [Configuration File Example](configuration/config-file-example.md) - Complete example of `~/.config/tunacode.json` with all available settings.
 - [Local Models Setup](configuration/local-models.md) - Guide for using local models with LM Studio or any OpenAI-compatible API.
 - [Performance Optimizations](development/performance-optimizations.md) - Major performance improvements and optimization strategies.
+- [Streaming Text Prefix Fix](development/streaming-text-prefix-fix.md) - Technical documentation for the streaming text truncation fix.

tunacode_cli-0.0.76.1/documentation/configuration/config-flow-diagram.md

@@ -0,0 +1,65 @@
+graph TD
+    %% Configuration Sources
+    A[User Config File<br/>~/.config/tunacode.json] --> B[load_config()]
+    C[CLI Arguments<br/>--model, --key] --> D[CLI Override Logic]
+    E[Environment Variables<br/>OPENAI_API_KEY, etc.] --> F[Environment Setup]
+    G[Default Config<br/>src/tunacode/configuration/defaults.py] --> H[Config Merging]
+
+    %% Loading and Validation
+    B --> I[SHA-1 Fingerprint Check]
+    I --> J{Config Changed?}
+    J -->|No| K[Use Cached Config]
+    J -->|Yes| L[JSON Validation]
+    L --> M[Merge with Defaults]
+    D --> M
+    M --> N[Configuration Validation]
+
+    %% Configuration Distribution
+    N --> O[StateManager.session.user_config]
+    O --> P[Export Environment Variables]
+    P --> Q[Agent Configuration]
+    O --> R[Tool Configuration]
+    O --> S[Model Selection Logic]
+    O --> T[MCP Server Setup]
+
+    %% Runtime Updates
+    U[/model command] --> V{Has 'default' keyword?}
+    V -->|Yes| W[set_default_model()]
+    V -->|No| X[session.current_model only]
+    W --> Y[save_config()]
+    Y --> A
+    X --> Z[Session Only - NOT PERSISTED]
+
+    %% Tool-Specific Config Paths
+    R --> AA[tool_ignore list]
+    R --> BB[ripgrep settings]
+    R --> CC[tool_strict_validation]
+    AA --> DD[Tool Filtering]
+    BB --> EE[Search Tool Config]
+    CC --> FF[Parameter Validation]
+
+    %% Agent Setup Flow
+    Q --> GG[System Prompt Loading]
+    Q --> HH[Tool Initialization]
+    Q --> II[Model Client Setup]
+    S --> II
+
+    %% Configuration Persistence Issues
+    JJ[Setup Wizard] --> KK[Interactive Config Changes]
+    KK --> LL[save_config() called]
+    LL --> A
+
+    MM[Runtime Model Switch] --> X
+    NN[Runtime Setting Change] --> OO{Explicit save?}
+    OO -->|No| PP[Lost on Exit]
+    OO -->|Yes| Y
+
+    %% Potential Issue Points
+    style Z fill:#ffcccc
+    style PP fill:#ffcccc
+    style X fill:#ffcccc
+
+    %% Legend
+    QQ[Legend:]
+    RR[Red boxes = Config not persisted]
+    SS[Normal boxes = Config persisted]

tunacode_cli-0.0.76.1/documentation/configuration/config-touch-points.md

@@ -0,0 +1,21 @@
+## Configuration Touch Points
+
+### Loading & Validation
+- `src/tunacode/utils/user_configuration.py:33-58` - Main config loading
+- `src/tunacode/configuration/defaults.py:11-38` - Default values
+- `src/tunacode/core/setup/config_setup.py` - Setup wizard & validation
+
+### Distribution Points
+- `src/tunacode/core/setup/coordinator.py` - Setup orchestration
+- `src/tunacode/core/setup/environment_setup.py:29-49` - Env var export
+- `src/tunacode/core/agents/agent_config.py:45-67` - Agent configuration
+
+### Runtime Updates
+- `src/tunacode/cli/commands/implementations/model.py:162-170` - Model switching
+- `src/tunacode/utils/user_configuration.py:89-97` - Config persistence
+- Session state in `StateManager.session.user_config`
+
+### Tool Configuration
+- `src/tunacode/tools/base.py:23-41` - Tool schema validation
+- `src/tunacode/services/mcp.py:61-108` - MCP server config
+- Individual tool settings in `settings.ripgrep`, `tool_ignore`, etc.

{tunacode_cli-0.0.76 → tunacode_cli-0.0.76.1}/documentation/development/hatch-build-system.md

@@ -7,7 +7,7 @@ TunaCode uses [Hatch](https://hatch.pypa.io/) as its build system and developmen
 ## Installation
 
 ```bash
-pip install hatch
+uv install hatch
 ```
 
 ## Common Commands
@@ -15,64 +15,65 @@ pip install hatch
 ### Development
 
 ```bash
+# Create virtual environment with UV
+uv venv
+
 # Install development dependencies
-hatch run install
+source .venv/bin/activate && uv pip install -e ".[dev]"
 
 # Run the application
-hatch run run
+source .venv/bin/activate && tunacode
 
 # Start development mode
-hatch run dev
+source .venv/bin/activate && tunacode
 ```
 
 ### Testing
 
 ```bash
 # Run test suite
-hatch run test
+source .venv/bin/activate && pytest
 
 # Run tests with coverage
-hatch run coverage
+source .venv/bin/activate && pytest --cov=src/tunacode
 
 # Test specific Python version
-hatch run py310:test
-hatch run py311:test
-hatch run py312:test
+source .venv/bin/activate && python3.10 -m pytest
+source .venv/bin/activate && python3.11 -m pytest
+source .venv/bin/activate && python3.12 -m pytest
 ```
 
 ### Code Quality
 
 ```bash
 # Lint and format code
-hatch run lint
+source .venv/bin/activate && ruff check . && ruff format .
 
 # Check without modifying
-hatch run lint-check
+source .venv/bin/activate && ruff check . && ruff format --check .
 
 # Type checking
-hatch run typecheck
+source .venv/bin/activate && mypy src/
 
 # Security analysis
-hatch run security
+source .venv/bin/activate && bandit -r src/ -ll
 
 # Dead code analysis
-hatch run vulture
-hatch run dead-code-check
-hatch run dead-code-clean
-hatch run dead-code-report
+source .venv/bin/activate && python -m vulture --config pyproject.toml
+source .venv/bin/activate && python -c "print('Running comprehensive dead code analysis...')"
 ```
 
 ### Building & Publishing
 
 ```bash
 # Build distribution packages
-hatch build
+source .venv/bin/activate && python -m build
 
 # Clean build artifacts
-hatch run clean
+source .venv/bin/activate && python -c "import shutil, pathlib; dirs=['build', 'dist']; [shutil.rmtree(d, ignore_errors=True) for d in dirs]; print('Cleaned build artifacts')"
 
 # Publish to PyPI
-hatch publish
+source .venv/bin/activate && twine upload dist/*
 ```
 
 ## Environment Management
@@ -113,36 +114,38 @@ All Hatch configuration is in `pyproject.toml`:
 
 | Old Command | New Command |
 |------------|-------------|
-| `make install` | `hatch run install` |
-| `make test` | `hatch run test` |
-| `make lint` | `hatch run lint` |
-| `make build` | `hatch build` |
-| `make clean` | `hatch run clean` |
-| `make coverage` | `hatch run coverage` |
-| `make vulture` | `hatch run vulture` |
+| `make install` | `source .venv/bin/activate && uv pip install -e ".[dev]"` |
+| `make test` | `source .venv/bin/activate && pytest` |
+| `make lint` | `source .venv/bin/activate && ruff check . && ruff format .` |
+| `make build` | `source .venv/bin/activate && python -m build` |
+| `make clean` | `source .venv/bin/activate && python -c "import shutil; dirs=['build', 'dist']; [shutil.rmtree(d, ignore_errors=True) for d in dirs]"` |
+| `make coverage` | `source .venv/bin/activate && pytest --cov=src/tunacode` |
+| `make vulture` | `source .venv/bin/activate && python -m vulture --config pyproject.toml` |
 
 ## Troubleshooting
 
-### Command not found
+### UV not found
 
-Ensure hatch is installed:
+Install UV for faster package management:
 ```bash
-pip install --upgrade hatch
+curl -LsSf https://astral.sh/uv/install.sh | sh
 ```
 
-### Environment issues
+### Virtual environment issues
 
-Reset environments:
+Recreate virtual environment:
 ```bash
-hatch env prune
+rm -rf .venv
+uv venv
+source .venv/bin/activate && uv pip install -e ".[dev]"
 ```
 
 ### Build errors
 
 Clean and rebuild:
 ```bash
-hatch run clean
-hatch build
+source .venv/bin/activate && python -c "import shutil; dirs=['build', 'dist']; [shutil.rmtree(d, ignore_errors=True) for d in dirs]"
+source .venv/bin/activate && python -m build
 ```
 
 ## Advanced Usage