tunacode-cli 0.1.24__tar.gz → 0.1.28__tar.gz

tunacode_cli-0.1.28/.claude/JOURNAL.md

@@ -0,0 +1,278 @@
+# Claude Journal
+
+## 2026-01-07: Renderer Unification
+
+Unifying the 8 tool renderers in `src/tunacode/ui/renderers/tools/` to eliminate duplication via a shared base class and registry pattern.
+
+### Completed:
+- Created `base.py` with `BaseToolRenderer[T]` ABC and `ToolRendererProtocol`
+- Extracted shared helpers: `truncate_line`, `truncate_content`, `pad_lines`
+- Added registry pattern: `@tool_renderer`, `get_renderer`, `list_renderers`
+- Migrated `list_dir.py` to use `BaseToolRenderer` (199 -> 149 lines)
+- Created documentation at `docs/ui/tool_renderers.md`
+
+### Architecture Decisions:
+- Module-level singleton renderer instances (not created per-call)
+- Render functions remain the public API (backward compatible)
+- `@tool_renderer` decorator for self-registration
+- Helpers are standalone functions, not methods
+
+---
+
+## 2026-01-07: Local Mode Context Optimization
+
+### Problem:
+- System prompt + tool schemas used ~3.5k tokens before any conversation
+- Each file read could use 2000 lines (~20k tokens)
+- With 10k context, only ~6.5k left for conversation
+- LLM APIs are stateless - system prompt sent every turn
+
+### Solution:
+
+**1. Minimal System Prompt**
+- `LOCAL_TEMPLATE` in `templates.py` - only 3 sections: AGENT_ROLE, TOOL_USE, USER_INSTRUCTIONS
+- `local_mode: true` setting triggers minimal template
+
+**2. Minimal Tool Schemas**
+- Reduced from 11 tools to 6 (bash, read_file, update_file, write_file, glob, list_dir)
+- 1-word descriptions ("Shell", "Read", "Edit", etc.) - saves ~1k tokens
+
+**3. Aggressive Pruning**
+- LOCAL_PRUNE_PROTECT_TOKENS: 2,000 (vs 40,000)
+- LOCAL_PRUNE_MINIMUM_THRESHOLD: 500 (vs 20,000)
+
+**4. Tool Output Limits**
+- LOCAL_DEFAULT_READ_LIMIT: 200 lines (vs 2,000)
+- LOCAL_MAX_LINE_LENGTH: 500 chars (vs 2,000)
+- LOCAL_MAX_COMMAND_OUTPUT: 1,500 chars (vs 5,000)
+
+**5. Response Limit**
+- local_max_tokens: 1000 - caps model output per turn
+
+### Token Budget (Local Mode):
+| Component | Tokens |
+|-----------|--------|
+| System prompt | ~1,100 |
+| Guide file | ~500 |
+| 6 tools (minimal) | ~575 |
+| **Total base** | **~2,200** |
+
+With 10k context: ~7.8k available for conversation.
+
+### Key Insight:
+LLM APIs are stateless. Every request sends: system prompt + tool schemas + full conversation history. Model has no memory - re-reads everything each turn.
+
+### Key Files:
+- `src/tunacode/core/limits.py` - Centralized limit configuration
+- `src/tunacode/core/prompting/templates.py` - LOCAL_TEMPLATE
+- `src/tunacode/core/prompting/local_prompt.md` - Condensed prompt
+- `src/tunacode/core/compaction.py` - Dynamic prune thresholds
+- `src/tunacode/constants.py` - Local mode limit constants
+
+---
+
+## 2026-01-06: Local Model Support
+
+### Task: Add local model support to tunacode
+
+### Completed:
+- Created condensed system prompt at `src/tunacode/prompts/local_model_prompt.txt` (~500 bytes vs 34KB full prompt)
+- Added `local_model: true/false` setting in config defaults
+- Modified `load_system_prompt()` to use condensed prompt when `local_model=true`
+- Added cache invalidation for `local_model` setting in `_compute_agent_version()`
+- Skip AGENTS.md loading for local models to save tokens
+- Created `fallback_executor.py` for models that output tool calls in text (e.g., `<tool_call>` tags)
+- Updated `node_processor.py` to detect and execute fallback tool calls
+- Passed `agent_ctx` through the call chain for result injection
+- Tested with multiple local models via LM Studio/vLLM
+
+### Notes:
+- Qwen2.5-Coder-14B supports native OpenAI tool calling format
+- Smaller models (0.6B-1.7B) output `<tool_call>` tags in content - fallback parser handles this
+- llama.cpp uses KV cache efficiently (LCP similarity) so repeated prompt not re-computed
+
+---
+
+## 2026-01-08: Config Restoration & Local Mode Docs
+
+### Task: Restore pre-local-mode config and document local mode setup
+
+### Completed:
+
+**1. Config Backup Discovery**
+Found three config variants in `~/.config/`:
+- `tunacode.json` - was set to local mode (grok-code-fast-1, 10k context)
+- `tunacode.json.bak` - MiniMax-M2.1, 200k context, no local mode
+- `@tunacode.json` - Gemini 3 Pro via OpenRouter
+
+**2. Restored Config**
+- Restored `~/.config/tunacode.json` from `.bak` (MiniMax config)
+- Settings: `minimax:MiniMax-M2.1`, 200k context, `guide_file: AGENTS.md`
+
+**3. Created Local Mode Example**
+- Created `docs/configuration/tunacode.local.json.example`
+- Documents all local mode settings:
+  - `local_mode: true`
+  - `local_max_tokens: 1000`
+  - `context_window_size: 10000`
+  - `OPENAI_BASE_URL: http://127.0.0.1:8080/v1`
+  - `guide_file: CLAUDE_LOCAL.md`
+
+### Key Files:
+- `~/.config/tunacode.json` - user config (restored to MiniMax)
+- `docs/configuration/tunacode.json.example` - standard example
+- `docs/configuration/tunacode.local.json.example` - NEW: local mode example
+
+### Notes:
+- Local mode uses condensed prompts and minimal tool schemas for small context windows
+- The `.bak` file preserved the pre-experimentation state - good backup hygiene!
+- User was testing local models, now back to cloud (MiniMax)
+
+---
+
+## 2026-01-08: Syntax Highlighting for Tool Renderers (Branch: ui-model-work)
+
+### The Mission:
+Make tool outputs pretty! All those ugly plain text viewports were a crime against NeXTSTEP aesthetics. Time to add syntax highlighting everywhere.
+
+### Completed (Commit 9db8e92):
+
+**1. Created `syntax_utils.py` - The Shared Foundation**
+- `EXTENSION_LEXERS` - 60+ file extension → lexer mappings
+- `get_lexer(filepath)` - Get pygments lexer from file path
+- `syntax_or_text(content, filepath)` - Render highlighted or plain
+- `detect_code_lexer(content)` - Heuristic code detection (shebangs, JSON, Python/JS patterns)
+- `SYNTAX_THEME = "monokai"` - Consistent theme everywhere
+
+**2. Created `write_file.py` - New Renderer!**
+- Was missing entirely - now shows syntax-highlighted preview of written content
+- Green "NEW" badge in header, file stats
+
+**3. Updated 8 Existing Renderers:**
+
+| Renderer | What Changed |
+|----------|-------------|
+| `read_file` | Syntax highlighting by file extension, built-in line numbers from Syntax component |
+| `grep` | Cyan file paths, yellow `reverse` highlighted matches, styled line numbers with `│` |
+| `glob` | Files colored by type: Python=bright_blue, JS=yellow, JSON=green, etc. Dir path dim, filename bold |
+| `list_dir` | Tree chars dim, directories bold cyan, files colored by lexer type |
+| `bash` | Smart detection: `git diff`→diff lexer, JSON commands→json lexer, labeled stdout/stderr |
+| `web_fetch` | URL-based detection (raw.githubusercontent.com, .json, /api/), content heuristics |
+| `research` | New "Code" section with syntax-highlighted examples from `code_examples` field |
+| `update_file` | Already had Syntax("diff") - unchanged, the OG |
+
+**4. Updated `__init__.py`:**
+- Added `write_file` renderer to exports
+- Added syntax utility functions to `__all__`
+- Better docstring explaining the 4-zone pattern
+
+### Key Design Decisions:
+- `syntax_or_text()` returns `RenderableType` - graceful fallback to `Text()` for unknown extensions
+- File-type coloring consistent across `glob`, `list_dir`, `grep` (same color = same type)
+- Bash output detection is conservative - only highlights when confident
+- Research viewport prioritizes findings over code (code is supplementary)
+
+### Files Modified:
+```
+src/tunacode/ui/renderers/tools/
+├── __init__.py        (exports + docstring)
+├── syntax_utils.py    (NEW - shared utilities)
+├── write_file.py      (NEW - renderer)
+├── read_file.py       (syntax highlighting)
+├── grep.py            (styled matches)
+├── glob.py            (colored paths)
+├── list_dir.py        (styled tree)
+├── bash.py            (smart detection)
+├── web_fetch.py       (URL/content detection)
+└── research.py        (code examples)
+```
+
+### What's Left on This Branch:
+- Other UI model work (the branch name suggests more to do)
+- Unstaged: `.claude/JOURNAL.md`, `CLAUDE.md`, research docs, config example
+
+### Commands:
+```bash
+uv run ruff check src/tunacode/ui/renderers/tools/  # All checks pass
+uv run python -c "from tunacode.ui.renderers.tools import list_renderers; print(list_renderers())"
+# ['bash', 'glob', 'grep', 'list_dir', 'read_file', 'research_codebase', 'update_file', 'web_fetch', 'write_file']
+```
+
+### Fun Fact:
+We went from 0 syntax-highlighted viewports to 8 in one session. The `update_file` renderer was the lonely pioneer - now it has friends!
+
+---
+
+## 2026-01-08: The Great Panel Width Debugging Adventure (Branch: master)
+
+### The Problem:
+Tool panels were narrower than agent panels. User showed screenshot - `read_file` panel was ~50 chars wide while `agent` panel was full width. Classic NeXTSTEP violation!
+
+### The Red Herring (What We Thought):
+Initially believed the issue was `width=TOOL_PANEL_WIDTH` (50 chars) on `Panel()` calls. Spent time:
+- Removing `width=TOOL_PANEL_WIDTH` from 7 Panel() calls in `panels.py`
+- Removing it from `search.py`, `update_file.py`, `app.py`
+- Cleaning up unused imports
+
+But panels were STILL narrow after restart. User called me out: "stop being lazy, dig deeper"
+
+### The Actual Root Cause (The AHA Moment):
+
+**Textual's `RichLog.write()` has its OWN `expand` parameter that defaults to `False`!**
+
+From `.venv/lib/python3.13/site-packages/textual/widgets/_rich_log.py`:
+```python
+def write(
+    self,
+    content: RenderableType | object,
+    width: int | None = None,
+    expand: bool = False,  # <-- THIS IS THE VILLAIN
+    shrink: bool = True,
+    ...
+)
+```
+
+When `expand=False` (default), RichLog measures the content's minimum width and renders at that width, **completely ignoring** the Panel's own `expand=True` property!
+
+The Panel's expand tells Rich "expand to console width", but RichLog overrides the console width to be just the measured content width. Two different expand flags, two different systems!
+
+### The Real Fix:
+Pass `expand=True` to `rich_log.write()`:
+
+```python
+# Before
+self.rich_log.write(panel)
+
+# After
+self.rich_log.write(panel, expand=True)
+```
+
+### Files Modified:
+| File | Change |
+|------|--------|
+| `src/tunacode/ui/app.py` | 3 panel writes → `expand=True` (lines 325, 377, 558) |
+| `src/tunacode/ui/plan_approval.py` | 1 panel write → `expand=True` (line 132) |
+| `src/tunacode/ui/renderers/panels.py` | Removed `width=TOOL_PANEL_WIDTH` (harmless cleanup) |
+| `src/tunacode/ui/renderers/search.py` | Removed unused import |
+| `src/tunacode/ui/renderers/tools/update_file.py` | Removed unused import |
+
+### The Lesson:
+When Rich Panel has `expand=True` but isn't expanding in Textual:
+1. The Panel's expand is **not** the issue
+2. Check how the panel is being **written** to the widget
+3. RichLog.write() has its own expand parameter!
+
+### Status:
+- Changes made, ruff passes
+- NOT COMMITTED YET - user needs to test
+- Previous width removal changes are technically unnecessary but harmless
+
+### Commands:
+```bash
+git diff --stat  # See all changes
+uv run ruff check src/tunacode/ui/  # Verify
+# Restart tunacode and make NEW request to test
+```
+
+### Philosophical Note:
+This bug was a perfect example of "the abstraction leaked". Panel.expand and RichLog.write(expand=) look like they should be the same thing, but they operate at different levels. Panel tells Rich what to do. RichLog tells Rich what size canvas to give it. The canvas size wins.

tunacode_cli-0.1.28/.claude/debug_history/list-dir-tool-execution-error.md

@@ -0,0 +1,55 @@
+---
+title: list_dir halts agent on bad paths
+link: list-dir-tool-execution-error
+type: delta
+path: src/tunacode/tools/list_dir.py
+depth: 0
+seams: [M] module
+ontological_relations:
+  - relates_to: [[tools]]
+  - affects: [[tool-executor]]
+  - fixes: [[agent-halt-on-tool-error]]
+tags:
+  - tools
+  - error-handling
+  - list_dir
+  - ModelRetry
+created_at: 2026-01-07T22:54:00-08:00
+updated_at: 2026-01-07T23:15:00-08:00
+uuid: a1b2c3d4-e5f6-7890-abcd-ef1234567890
+---
+
+## Summary
+
+`list_dir` raised `FileNotFoundError` on non-existent directories, which `@base_tool` wrapped as `ToolExecutionError`. Since `ToolExecutionError` is in `NON_RETRYABLE_ERRORS`, the agent halted instead of letting the LLM self-correct with a valid path.
+
+## Context
+
+Surfaced when agent called `list_dir("/home/tuna/tunacode/apps")` - a directory that doesn't exist. Agent crashed with `ToolExecutionError` instead of retrying.
+
+## Root Cause
+
+Error propagation chain:
+1. `list_dir` raises `FileNotFoundError`
+2. `@base_tool` decorator wraps it as `ToolExecutionError`
+3. `tool_executor.py` has `ToolExecutionError` in `NON_RETRYABLE_ERRORS`
+4. Non-retryable errors propagate immediately, halting the agent
+
+First attempted fix: switch to `@file_tool` decorator. Failed because `@file_tool` expects required `filepath` positional arg, but `list_dir` has optional `directory="."`.
+
+## Changes
+
+- Import `ModelRetry` from `pydantic_ai.exceptions`
+- Replace `raise FileNotFoundError(...)` with `raise ModelRetry(...)`
+- Replace `raise NotADirectoryError(...)` with `raise ModelRetry(...)`
+- Keep `@base_tool` decorator (not `@file_tool`)
+
+## Behavioral Impact
+
+- Agent no longer halts on bad directory paths
+- LLM receives retry signal with error message, can self-correct
+- No change to valid path behavior
+
+## Related Cards
+
+- [[glob-grep-error-strings]] - similar smell: return error strings instead of raising

tunacode_cli-0.1.28/.claude/qa/no-cargo-cult-fixes.md

@@ -0,0 +1,52 @@
+---
+title: No Cargo Cult Fixes - Question Every Change
+link: no-cargo-cult-fixes
+type: qa
+path: qa/
+depth: 1
+seams: [M]
+ontological_relations:
+  - relates_to: [[code-review]]
+  - affects: [[all-modules]]
+  - fixes: [[scope-creep]]
+tags:
+  - discipline
+  - shims
+  - code-review
+created_at: 2026-01-09T22:15:00Z
+updated_at: 2026-01-09T22:15:00Z
+uuid: 4fa0c1e7-d7d0-415a-91e4-d69b28210ff0
+---
+
+## Problem
+
+When extracting changes from a messy PR, I blindly copied a fix to `retry.py` without questioning whether it was needed.
+
+The signature preservation fix was for pydantic-ai tool schema generation. `retry_on_json_error` is a JSON parsing utility - it never gets passed to pydantic-ai's `Tool()`. The fix there was a shim.
+
+## Root Cause
+
+Cargo culting. "The original PR had it, so I included it."
+
+## Lesson
+
+Before applying any fix, ask: **"Does this code path actually hit the problem?"**
+
+For the signature preservation bug specifically:
+- pydantic-ai uses `inspect.signature()` to generate JSON schemas for tools
+- Only wrappers that produce functions passed to `Tool()` need the fix
+- `retry_on_json_error` wraps JSON parsers, not pydantic-ai tools
+
+## Rule
+
+If you encounter a shim, fix it. Don't care who made it. Don't propagate it.
+
+## Files That Actually Needed The Fix
+
+1. `research_agent.py` - `ProgressTracker.wrap_tool()` wraps tools for pydantic-ai
+2. `decorators.py` - `base_tool()` and `file_tool()` wrap tools for pydantic-ai
+3. `present_plan.py` - `create_present_plan_tool()` creates a pydantic-ai tool
+
+## Files That Did NOT Need The Fix
+
+- `retry.py` - wraps JSON parsers, not pydantic-ai tools

{tunacode_cli-0.1.24 → tunacode_cli-0.1.28}/.gitignore

@@ -81,3 +81,5 @@ vendor/
 .beads/
 .osgrep
 .osgrep*
+.pre-commit-cache/
+TODO.md

{tunacode_cli-0.1.24 → tunacode_cli-0.1.28}/.pre-commit-config.yaml

@@ -13,6 +13,9 @@ repos:
     hooks:
       - id: trailing-whitespace
       - id: end-of-file-fixer
+        # models_registry.json is auto-generated config; lsp/__init__.py is empty stub
+        # trailing newline changes create diff noise
+        exclude: (models_registry\.json|lsp/__init__\.py)$
       - id: check-yaml
         args: ['--allow-multiple-documents']
       - id: check-added-large-files
@@ -44,6 +47,7 @@ repos:
       - id: ruff
         args: ['--fix', '--show-fixes']
       - id: ruff-format  # Re-enabled - ruff handles linting, ruff-format handles formatting
+        exclude: (models_registry\.json|lsp/__init__\.py)$
 
   # Type checking with mypy
   - repo: https://github.com/pre-commit/mirrors-mypy

{tunacode_cli-0.1.24 → tunacode_cli-0.1.28}/CHANGELOG.md

@@ -1,5 +1,49 @@
 ## [Unreleased]
 
+## [0.1.26] - 2026-01-09
+
+### Added
+- NeXTSTEP agent response panels with streaming support (#218)
+
+## [0.1.25] - 2026-01-08
+
+### Added
+- Local mode for small context window models with configurable tool limits (#215, #216)
+- BaseToolRenderer pattern for compact NeXTSTEP panels (#214)
+- Local mode documentation and README link
+
+### Changed
+- Tool improvements and unified BaseToolRenderer pattern
+
+## [0.1.24] - 2026-01-07
+
+### Added
+- Plan mode feature with gitignore-aware grep (#213)
+- Dynamic provider config from registry, OpenAI-only for non-Anthropic
+
+### Fixed
+- Restore plan mode feature (accidentally deleted in d816ff2)
+
+## [0.1.23] - 2026-01-06
+
+### Fixed
+- Include models_registry.json in wheel distribution
+
+## [0.1.22] - 2026-01-06
+
+### Fixed
+- Use load_models_registry instead of cached version for provider config
+- Resolve async/sync mismatch in _normalize_tool_args
+
+## [0.1.21] - 2026-01-03
+
+### Added
+- Comprehensive codebase map with SEAMS analysis
+
+### Changed
+- Refactor exception formatting
+- Cleanup obsolete memory-bank and audit files
+
 ## [0.1.20] - 2026-01-02
 
 ### Added

{tunacode_cli-0.1.24 → tunacode_cli-0.1.28}/CLAUDE.md

@@ -1,3 +1,24 @@
+---
+title: Tunacode Project Guidelines
+link: claude-md
+type: doc
+path: CLAUDE.md
+depth: 0
+seams: [A, M]
+ontological_relations:
+  - relates_to: [[tunacode]]
+  - affects: [[code-style, workflow, quality-gates]]
+tags:
+  - guidelines
+  - cheatsheet
+  - code-style
+  - quality-gates
+  - workflow
+created_at: 2025-01-01T00:00:00Z
+updated_at: 2026-01-08T00:00:00Z
+uuid: claude-md-tunacode-001
+---
+
 ## Tunacode
 
 This project is tunacode, much like you! It's a TUI code agent that can be used to code and debug code or general agentic tasks.
@@ -279,7 +300,7 @@ PR #263: "chore: remove unused grep tool"
 
 ## KB Directory
 
-Maintain a `.claude/markdown` directory with:
+Maintain a `.claude/` directory with:
 
 - **metadata/** — dependency graphs, file classifications, error pattern database
 - **code_index/** — function call graphs, type relationships, interface mappings
@@ -289,6 +310,8 @@ Maintain a `.claude/markdown` directory with:
 - **qa/** — solved problems database with reasoning
 - **delta/** — semantic changelogs explaining changes
 
+Select the most semantically correct directory and create a card in it.
+
 ### Continuous Learning
 
 Dump bugs, smells, issues here as you encounter them. Raw is fine. A skill will organize this into proper kb entries later.
@@ -297,6 +320,14 @@ Format: `[date] [type] description`
 
 Types: bug, smell, pattern, lesson, antipattern
 
+[2026-01-07] [lesson] When there's a type mismatch between A and B, fix where A or B is defined, not every place that uses them. Don't scatter changes across 5+ files when one line at the source fixes everything.
+
+[2026-01-08] [pattern] Local mode config: `docs/configuration/tunacode.local.json.example` - use when running local models. Key settings: `local_mode: true`, `local_max_tokens: 1000`, `context_window_size: 10000`, `OPENAI_BASE_URL` for local server.
+
+[2026-01-08] [pattern] Syntax highlighting in tool renderers: Use `syntax_utils.py` for `get_lexer(filepath)` and `syntax_or_text(content, filepath)`. Consistent monokai theme. 9 renderers now registered: bash, glob, grep, list_dir, read_file, research_codebase, update_file, web_fetch, write_file. Commit `9db8e92`.
+
+[2026-01-08] [lesson] **RichLog.write() has its own expand parameter!** When Panel(expand=True) doesn't expand in Textual, the fix is `rich_log.write(panel, expand=True)`. Panel.expand tells Rich what to do; RichLog.write(expand=) tells Rich what canvas size to use. Two different systems - canvas wins. See JOURNAL.md "The Great Panel Width Debugging Adventure".
+
 ---
 
 We are currently in the middle of a large rewrite few test exist and documentation and that is okay. We will build the test and documentation as we go

tunacode_cli-0.1.28/CLAUDE_LOCAL.md

@@ -0,0 +1,72 @@
+# Tunacode (Local System Prompt)
+
+TUI code agent. Structure: `ui/` (TUI), `core/` (agent), `tools/` (system access).
+
+## Architecture
+
+Dependencies flow one direction: `ui → core → tools → utils/types`. Never backward.
+
+## Code Rules
+
+1. **Guard clauses** - Return early, flatten nesting
+2. **Explicit typing** - Use `cast()`, `assert`, avoid `# type: ignore`
+3. **No magic values** - Use named constants
+4. **Pass inputs openly** - No hidden state
+5. **Delete dead code** - VCS remembers
+
+## Error Handling
+
+**Fail fast, fail loud.** No silent fallbacks. Raise exceptions with clear messages.
+
+```python
+# Wrong
+if not path.exists():
+    return None
+
+# Right
+if not path.exists():
+    raise FileNotFoundError(f"Not found: {path}")
+```
+
+## Quality Gates
+
+1. **No shims** - Fix interfaces at root, never patch around them
+2. **High cohesion** - One module = one responsibility
+3. **Low coupling** - Modules don't know each other's internals
+4. **Design by contract** - Preconditions, postconditions, invariants
+
+## Workflow
+
+- `uv` for packages, `.venv` for environment
+- `uv run ruff check --fix .` before commits
+- `uv run pytest` for tests
+- Small, focused diffs. Commit frequently.
+
+## Don'ts
+
+- Don't add features beyond what's asked
+- Don't create abstractions for one-time operations
+- Don't add comments to unchanged code
+- Don't use `--no-verify` on commits
+- Don't import ui from core or tools
+
+## Example: Fix a bug
+
+User: "Fix the typo in greet function"
+
+1. **Read first** - Always read before editing
+```json
+{"name": "read_file", "arguments": {"filepath": "src/utils.py"}}
+```
+
+2. **Make targeted edit**
+```json
+{"name": "update_file", "arguments": {"filepath": "src/utils.py", "old_text": "def greet(naem):", "new_text": "def greet(name):"}}
+```
+
+3. **Verify** - Run tests
+```json
+{"name": "bash", "arguments": {"command": "uv run pytest tests/test_utils.py -x"}}
+```
+
+Done. One fix, one commit.

{tunacode_cli-0.1.24 → tunacode_cli-0.1.28}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tunacode-cli
-Version: 0.1.24
+Version: 0.1.28
 Summary: Your agentic CLI developer.
 Project-URL: Homepage, https://tunacode.xyz/
 Project-URL: Repository, https://github.com/alchemiststudiosDOTai/tunacode
@@ -32,7 +32,6 @@ Requires-Dist: rich<15.0.0,>=14.2.0
 Requires-Dist: ruff>=0.14.0
 Requires-Dist: textual-autocomplete>=4.0.6
 Requires-Dist: textual<5.0.0,>=4.0.0
-Requires-Dist: tiktoken<1.0.0,>=0.12.0
 Requires-Dist: typer>=0.15.0
 Provides-Extra: dev
 Requires-Dist: autoflake>=2.0.0; extra == 'dev'
@@ -67,24 +66,27 @@ A TUI code agent.
 
 ## Interface
 
-![TUI Interface](docs/images/tui.png)
-
 The Textual-based terminal user interface provides a clean, interactive environment for AI-assisted coding, with a design heavily inspired by the classic NeXTSTEP user interface.
 
+![Agent Response Panel](docs/media/agent-response.png)
+*Agent response panel with formatted output*
+
+![Read File Tool](docs/media/read-file-tool.png)
+*Tool rendering with syntax highlighting*
+
+![Plan Approval](docs/media/plan-approval.png)
+*Structured plan approval workflow*
+
 ## Theme Support
 
 The interface supports multiple themes for different preferences and environments.
 
-![Theme](docs/images/theme.png)
-
 Customize the appearance with built-in themes or create your own color schemes.
 
 ## Model Setup
 
 Configure your AI models and settings through the provided setup interface.
 
-![TUI Model Setup](docs/images/tui-model-setup.png)
-
 **Note:** TunaCode has full bash shell access. This tool assumes you know what you're doing. If you're concerned, run it in a sandboxed environment.
 
 ## v0.1.1 - Major Rewrite
@@ -129,6 +131,8 @@ export ANTHROPIC_API_KEY="your-key"
 
 Config file location: `~/.config/tunacode.json`
 
+For advanced settings including **local mode** for small context models, see the [Configuration Guide](docs/configuration/README.md).
+
 ## Commands
 
 | Command  | Description                  |

{tunacode_cli-0.1.24 → tunacode_cli-0.1.28}/README.md

@@ -14,24 +14,27 @@ A TUI code agent.
 
 ## Interface
 
-![TUI Interface](docs/images/tui.png)
-
 The Textual-based terminal user interface provides a clean, interactive environment for AI-assisted coding, with a design heavily inspired by the classic NeXTSTEP user interface.
 
+![Agent Response Panel](docs/media/agent-response.png)
+*Agent response panel with formatted output*
+
+![Read File Tool](docs/media/read-file-tool.png)
+*Tool rendering with syntax highlighting*
+
+![Plan Approval](docs/media/plan-approval.png)
+*Structured plan approval workflow*
+
 ## Theme Support
 
 The interface supports multiple themes for different preferences and environments.
 
-![Theme](docs/images/theme.png)
-
 Customize the appearance with built-in themes or create your own color schemes.
 
 ## Model Setup
 
 Configure your AI models and settings through the provided setup interface.
 
-![TUI Model Setup](docs/images/tui-model-setup.png)
-
 **Note:** TunaCode has full bash shell access. This tool assumes you know what you're doing. If you're concerned, run it in a sandboxed environment.
 
 ## v0.1.1 - Major Rewrite
@@ -76,6 +79,8 @@ export ANTHROPIC_API_KEY="your-key"
 
 Config file location: `~/.config/tunacode.json`
 
+For advanced settings including **local mode** for small context models, see the [Configuration Guide](docs/configuration/README.md).
+
 ## Commands
 
 | Command  | Description                  |