tsugite-cli 0.12.2__tar.gz → 0.14.0__tar.gz

{tsugite_cli-0.12.2 → tsugite_cli-0.14.0}/.github/copilot-instructions.md

@@ -4,16 +4,16 @@ Tsugite is a micro-agent CLI: agents are Markdown + YAML frontmatter, rendered v
 
 ### Architecture
 
-**Flow:** `Agent.md` (YAML + Jinja2) → `renderer.py` → `TsugiteAgent` → LiteLLM → Tools
+**Flow:** `Agent.md` (YAML + Jinja2) → `renderer.py` → `TsugiteAgent` → Provider → Tools
 
 **Key Modules:**
-- `cli/__init__.py` - Typer CLI (run, chat, render, config, mcp, tools, agents, attachments, cache)
+- `cli/__init__.py` - Typer CLI (run, chat, render, config, tools, agents, attachments, cache)
 - `md_agents.py` - Parse frontmatter + agent resolution + directives
 - `builtin_agents/` - File-based built-in agent definitions (default.md, chat-assistant.md)
 - `agent_inheritance.py` - Agent resolution pipeline + inheritance chain
 - `chat.py` - Chat session management with history
 - `agent_runner.py` - Execution orchestration, prefetch, tool wiring, multi-step
-- `core/agent.py` - LiteLLM agent loop + streaming
+- `core/agent.py` - agent loop + streaming
 - `renderer.py` - Jinja2 rendering + helpers (now, today, slugify, env, file_exists, read_text, is_file, is_dir)
 - `tools/` - Tool registry + implementations
 - `shell_tool_config.py` + `tools/shell_tools.py` - Custom shell command wrappers
@@ -62,7 +62,6 @@ File-based agents distributed with the package in `tsugite/builtin_agents/` dire
 **Merge rules:**
 - Scalars (model, max_steps): Child overwrites
 - Lists (tools): Merge + deduplicate
-- Dicts (mcp_servers): Merge, child keys override
 - Strings (instructions): Concatenate with `\n\n`
 
 **Opt-out:** `extends: none` skips all inheritance.
@@ -236,7 +235,6 @@ assert tool is not None
 
 **Safety:**
 - Shell tool guard: Never relax dangerous patterns blocklist
-- MCP: Requires `--trust-mcp-code` flag
 - File ops: Use `Path.resolve()` to prevent traversal
 
 **Testing:** Test-first workflow. Add minimal failing test, run target, widen to full suite before merge.

{tsugite_cli-0.12.2 → tsugite_cli-0.14.0}/.github/workflows/ci.yml

@@ -28,7 +28,7 @@ jobs:
           enable-cache: true
 
       - name: Install dependencies
-        run: uv sync --dev
+        run: uv sync --dev --all-extras
 
       - name: Run ruff check
         run: uv run ruff check --show-fixes .
@@ -58,7 +58,7 @@ jobs:
           enable-cache: true
 
       - name: Install dependencies
-        run: uv sync --dev
+        run: uv sync --dev --all-extras
 
       - name: Run tests
         run: uv run pytest -v

{tsugite_cli-0.12.2 → tsugite_cli-0.14.0}/.github/workflows/docker-publish.yml

@@ -52,7 +52,6 @@ jobs:
         uses: docker/build-push-action@v5
         with:
           context: .
-          file: ./Dockerfile.runtime
           platforms: linux/amd64,linux/arm64
           push: true
           tags: ${{ steps.meta.outputs.tags }}

tsugite_cli-0.14.0/.github/workflows/pypi-publish.yml

@@ -0,0 +1,49 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - 'v*'
+  workflow_dispatch:
+
+jobs:
+  build-and-publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write    # Required for creating GitHub releases
+      id-token: write    # Required for PyPI trusted publishing
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0   # Full history so auto-generated release notes can diff
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Build all workspace packages
+        run: uv build --all-packages
+
+      - name: Publish to PyPI
+        # Trusted publishing: each package (tsugite-cli, tsugite-tmux, ...) must be
+        # registered separately on PyPI as a trusted publisher pointing at this workflow.
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+      - name: Generate release notes from conventional commits
+        id: changelog
+        uses: orhun/git-cliff-action@v4
+        with:
+          config: cliff.toml
+          args: --latest --strip header
+
+      - name: Create GitHub release
+        uses: softprops/action-gh-release@v2
+        with:
+          body: ${{ steps.changelog.outputs.content }}
+          files: dist/*

{tsugite_cli-0.12.2 → tsugite_cli-0.14.0}/.gitignore

@@ -173,7 +173,8 @@ secrets/*
 
 # TODO: temp - I need to clean up the docs
 docs-old/
-examples/
+examples/*
+!examples/tsugite-example-plugin/
 agents/
 .claude/
 .tsugite/

{tsugite_cli-0.12.2 → tsugite_cli-0.14.0}/AGENTS.md

@@ -2,12 +2,14 @@
 
 This file provides guidance to AI agents (tsugite, Claude Code, etc.) when working with code in this repository.
 
+See [CONTRIBUTING.md](CONTRIBUTING.md) for commit message conventions and PR guidelines.
+
 ## Commands
 
 ### Development Setup
 ```bash
-# Install dependencies
-uv sync --dev
+# Install dependencies (core + daemon extras + core plugins)
+uv sync --all-extras
 
 # Run all tests
 uv run pytest
@@ -54,7 +56,7 @@ Tsugite is an agentic CLI that executes AI agents defined as markdown files with
 1. **CLI Entry** (`tsugite/cli/__init__.py`)
    - Typer-based CLI with subcommands
    - Main commands: `run` (single-shot), `chat` (interactive), `render` (preview)
-   - Additional: `daemon`, `workspace`, `init`, `validate`, `mcp`, `serve`, `agents`, `config`, `attachments`, `cache`, `tools`, `history`
+   - Additional: `daemon`, `workspace`, `init`, `validate`, `agents`, `config`, `attachments`, `cache`, `tools`, `history`
 
 2. **Agent Resolution & Inheritance** (`tsugite/agent_inheritance.py`)
    - Resolves agent names to file paths using search order:
@@ -73,6 +75,7 @@ Tsugite is an agentic CLI that executes AI agents defined as markdown files with
      - `<!-- tsu:step -->` - Multi-step workflow stages
      - `<!-- tsu:ignore -->` - Documentation blocks (stripped before LLM)
      - `<!-- tsu:tool -->` - Execute tools during rendering
+     - `<!-- tsu:exec --> ... <!-- /tsu:exec -->` - Run arbitrary Python at render time, capture result into Jinja context
 
 4. **Agent Preparation** (`tsugite/agent_preparation.py`)
    - **Unified preparation pipeline** (used by both `run` and `render` commands)
@@ -102,22 +105,20 @@ Tsugite is an agentic CLI that executes AI agents defined as markdown files with
    - Integrates with history system for conversation continuity
 
 7. **LLM Agent Loop** (`tsugite/core/agent.py`)
-   - `TsugiteAgent` - Custom agent using LiteLLM directly
+   - `TsugiteAgent` - Custom agent using tsugite's provider abstraction
    - Think-Code-Observation loop (max_turns iterations)
    - Supports reasoning models (o1, o3, Claude extended thinking)
    - Direct control over model parameters (temperature, reasoning_effort)
    - Code execution via `LocalExecutor`
 
 8. **Tool System** (`tsugite/tools/`)
-   - Tool registry with built-in tools (fs, http, shell, tasks, agents, memory, skills, history, interactive)
-   - Category system: `@fs`, `@http`, `@shell`, `@tasks`, `@agents`, `@memory`, `@skills`, `@history`, `@interactive`
-   - Custom shell tools (config-based command wrappers)
-   - MCP integration (`tsugite/mcp_client.py`)
-   - Tool expansion supports globs (`*_search`) and exclusions (`-delete_file`)
+   - Tool registry with built-in tools (fs, http, shell, agents, skills, history, interactive) plus optional categories (notify, schedule, scratchpad, sessions, secrets, tmux — gated by `_OPTIONAL_CATEGORIES` in `tools/__init__.py`)
+   - Custom shell tools (config-based command wrappers in `tools/shell_tools.py`)
+   - Tool expansion supports globs (`*_search`), categories (`@fs`), and exclusions (`-delete_file`)
 
 9. **Event System** (`tsugite/events/`)
    - Event-driven architecture for UI decoupling
-   - 20 event types: execution, LLM, meta, progress, skills
+   - 28 event types: execution, LLM, meta, progress, skills
    - `EventBus` dispatches to multiple handlers
    - Handlers: Rich console, plain text, JSONL, chat, REPL
 
@@ -131,17 +132,16 @@ Tsugite is an agentic CLI that executes AI agents defined as markdown files with
     - XDG-compliant paths: `~/.config/tsugite/` or `$XDG_CONFIG_HOME/tsugite/`
     - JSON config with model aliases, default settings
     - Attachment storage (reusable context)
-    - MCP server registration
     - Auto-context discovery (CLAUDE.md, AGENTS.md, CONTEXT.md)
 
 ### Key Data Structures
 
-**AgentConfig** (`md_agents.py:43`)
+**AgentConfig** (`md_agents.py:36`)
 - Pydantic model for agent frontmatter
 - Validates all fields (name, model, tools, max_turns, etc.)
 - Schema exported to `tsugite/schemas/agent.schema.json`
 
-**PreparedAgent** (`agent_preparation.py:17`)
+**PreparedAgent** (`agent_preparation.py:69`)
 - Dataclass containing everything for execution/display
 - Ensures `render` shows exactly what `run` executes
 - Contains: agent, config, system_message, user_message, tools, context
@@ -180,6 +180,37 @@ Summarize findings
 - Safety: `max_iterations` (default 10) prevents infinite loops
 - Loop context: `{{ iteration }}`, `{{ max_iterations }}`, `{{ is_looping_step }}`
 
+### Exec Directives
+
+`<!-- tsu:exec name="..." assign="..." -->...<!-- /tsu:exec -->` runs an arbitrary Python block at agent-prep time and binds the return value (or last expression) to a Jinja variable. Use it for deterministic dispatchers, preprocessing, and branching that don't justify an LLM round-trip.
+
+```markdown
+<!-- tsu:exec name="dispatch" assign="targets" -->
+import os, json
+out = []
+for p in sorted(os.listdir("inbox")):
+    if p.endswith(".json"):
+        out.append({"path": p, "source": json.loads(open(f"inbox/{p}").read())["source"]})
+out
+<!-- /tsu:exec -->
+
+Inventory: {{ targets }}
+```
+
+**Semantics:**
+- Block body is opaque to Jinja; prior-directive vars (prefetch, tool, earlier exec) arrive as **Python locals**, not via `{{ }}` substitution. So `{{ }}` literals inside Python strings work.
+- Return value: explicit `return_value(x)` or the last expression in the block (Jupyter-style). Explicit `return_value` wins.
+- Plain Python is allowed (`open`, `os`, etc.) - the directive is for trusted preprocessing, distinct from LLM-emitted code in `tsugite/core/subprocess_executor.py`.
+- Top-level only in v1: between/before/after `tsu:step` directives, never inside step content.
+
+**Optional attributes:** `assign="var"`, `stdout_assign="var"`, `timeout=30`, `continue_on_error=true`.
+
+**Render mode:** `tsu render` executes exec blocks by default. Pass `--no-exec` to substitute placeholders instead (e.g. when the block has side effects you want to inspect without running).
+
+**Return-type policy:** values must JSON-serialize. `Path -> str`, `datetime -> isoformat()`, `set -> sorted list` are coerced automatically. Other non-serializable types raise (convert explicitly).
+
+See `examples/exec_dispatcher.md` for a runnable inbox-watcher pattern.
+
 ### Event-Driven UI
 
 All UI output goes through the event system:
@@ -241,7 +272,7 @@ Tsugite supports vision (images), audio, and document understanding through the
 **How It Works:**
 
 1. **URL Attachments** (Images/Documents):
-   - LiteLLM fetches the URL directly (no download overhead)
+   - The provider fetches the URL directly (no download overhead — support varies by provider and content type; see `tsugite/attachments/url.py`)
    - Example: `tsu run -f https://example.com/chart.png "Describe this chart"`
    - Automatically detected via HTTP HEAD request
 
@@ -286,6 +317,63 @@ tsu run -f image1.jpg -f image2.jpg "Compare these images"
 - YouTube handler: `tsugite/attachments/youtube.py` (fetches transcripts)
 - LLM formatting: `tsugite/core/agent.py:_format_attachment()`
 
+#### Frontmatter Attachment Specs
+
+The `attachments:` field accepts either plain string paths (legacy) or dict-form `AttachmentSpec` entries. Both forms can be mixed in the same list.
+
+**String form** (existing): rendered through Jinja, then loaded as a single file. Prefix with `-` to remove a workspace default (e.g., `-MEMORY.md`).
+
+```yaml
+attachments:
+  - MEMORY.md
+  - "{{ today() }}.md"
+  - -SKIP.md  # remove a workspace default named SKIP.md
+```
+
+**Dict form** (`AttachmentSpec`): adds `assign:`, `mode: index`, glob expansion, and other knobs.
+
+```yaml
+attachments:
+  - path: MEMORY.md
+    assign: memory_content        # bind file content as Jinja variable
+
+  - path: USER.md
+    assign: user_prefs
+    attach: false                 # bind variable but don't inject into prompt
+
+  - path: "memory/topics/*.md"    # glob - one Attachment per matched file
+    assign: topic_files           # bound as list[dict] of {path, content}
+
+  - path: "memory/topics/*.md"
+    mode: index                   # render path+heading list, not full content
+    name: topic_index             # explicit attachment name (default derives from glob)
+    assign: topics                # bound as list[dict] of {path, heading, size_bytes, mtime}
+    index_format: first_heading   # path_only | first_line | first_heading | frontmatter
+    max_entries: 50               # cap, warns if exceeded
+```
+
+**Variable shapes** (when `assign:` is set):
+
+| Spec | Shape |
+|---|---|
+| `mode: full`, single concrete file | `str` (file content) |
+| `mode: full`, glob | `list[dict]` of `{path, content}` (binaries skipped) |
+| `mode: index` | `list[dict]` of `{path, heading, size_bytes, mtime}` |
+| Single file, missing | `None` |
+| Empty glob | `[]` |
+
+**Constraints (validated at parse time):**
+- `assign:` must be a valid Python identifier.
+- Two specs can't share the same `assign` value.
+- `attach: false` requires `assign:` (otherwise the attachment loads for nothing).
+- `path:` cannot start with `-` (use string form for removal).
+
+**Index mode rendering** wraps the formatted index in an existing `<attachment>` tag with a `mode="index"` attribute, e.g. `<attachment name="topic_index" mode="index">...</attachment>`. Agents are expected to call `read_file(path=...)` to fetch individual entries on demand.
+
+**Collisions:** if an `assign:` name shadows a built-in or prefetch variable, the assignment wins and a warning is logged.
+
+See `examples/attachment_assign_demo.md` and `examples/attachment_index_demo.md` for runnable references.
+
 ## Development Patterns
 
 ### Adding a New Built-in Agent
@@ -315,14 +403,31 @@ tsu run -f image1.jpg -f image2.jpg "Compare these images"
 
 1. Update `AgentConfig` Pydantic model (`md_agents.py`)
 2. Regenerate schema: `uv run python scripts/regenerate_schema.py`
-3. Update documentation in CLAUDE.md (user guide section)
+3. Update relevant documentation in `AGENTS.md` and any user-facing doc under `docs/`
 4. Add validation tests in `tests/test_agent_parser.py`
 
 ## Testing Strategy
 
-- **TDD preferred**: Write tests first when building new features. Tests don't need to be elaborate — simple tests that verify the expected behavior are enough. This creates a fast feedback loop and catches integration issues early (e.g., contextvar propagation, tool registration) before manual testing.
+### TDD is the default
+
+For any non-trivial bug fix or feature, write a failing test **first**. Exceptions: typo fixes, docs, pure refactors, and changes the user has explicitly scoped as exploratory.
+
+The workflow:
+
+1. **Reproduce before fixing.** Write the smallest test that demonstrates the symptom as reported. Run it. If it passes on master, the hypothesis is wrong — do not write a fix. Investigate further, ask the user for more detail, or add logging.
+2. **Implement the fix.** Keep the change minimal. Do not refactor or add adjacent cleanup in the same diff.
+3. **Verify the test is load-bearing.** Temp-revert the production change and re-run. The test must go red again. If it still passes, the test isn't actually exercising the fix — rework it.
+4. **Cover adjacent cases before declaring done.** When touching a parser, protocol boundary, or state machine, enumerate at least two adjacent input shapes and add tests for them. Narrow tests let bugs sneak in through the cases you didn't think about.
+5. **Run the local regression suite.** At minimum, the test files next to the modules you changed. Faster than running everything, catches silent breakage of existing tests.
+6. **Honest uncertainty.** If a hypothesis doesn't reproduce, say so. Don't ship a "probably-this" fix with no failing test to anchor it — that's how placebo fixes get merged.
+
+Reproducing tests don't need to be elaborate. A 10-line test that flips red→green is worth more than a 100-line one that nobody understands.
+
+### Test layers
+
 - **Unit tests**: Individual functions and classes
-- **Pipeline tests**: Mock only `TsugiteAgent`/`litellm.acompletion` but exercise the full pipeline (parsing → rendering → preparation → tool expansion → execution). Most tests in the suite are this style.
+- **Pipeline tests**: Mock only `TsugiteAgent` / the provider's `acompletion` but exercise the full pipeline (parsing → rendering → preparation → tool expansion → execution). Most tests in the suite are this style.
+- **Integration tests**: Live under `tests/integration/` (not collected by default — see `pyproject.toml` `norecursedirs`). Run explicitly with `uv run pytest tests/integration/`. Good for concurrency, cwd, and daemon-wiring tests that need real threading or a real workspace.
 - **Smoke tests**: `tests/smoke_test.sh` hits a real LLM API (requires `OPENAI_API_KEY`, not run in CI)
 - **Fixtures**: `conftest.py` provides shared test data
 - **Mocking**: Use `@pytest.fixture` for LLM responses
@@ -348,6 +453,28 @@ tsu run -f image1.jpg -f image2.jpg "Compare these images"
 6. **Test both sync and async paths**: Many tools support both execution modes
 7. **Don't embed prompts in adapters/code**: Use context variables + conditional blocks in `default.md` instead. Add new context vars in `_build_agent_context()` (base adapter) and default them in `agent_preparation.py`, then use `{% if var %}` in the agent template. This keeps all prompt content in one place and leverages the existing rendering pipeline.
 
+## Web UI
+
+The daemon's web UI lives at `tsugite/daemon/web/`.
+
+### Stack
+
+- **Alpine.js 3** loaded from CDN. No build step. No React. Don't port this to a framework - the design handoff explicitly said match visuals, not internal structure.
+- **Starlette** serves `index.html` plus `/static/{css,js,icons}` and the `/api/*` routes (`tsugite/daemon/adapters/http.py`).
+- CSS lives in three files. Read all three before adding rules: `theme.css` (Catppuccin tokens), `console.css` (Console redesign - the real stylesheet), `styles.css` (legacy modals/auth/forms; ~120 lines, pruned aggressively after the redesign).
+- View modules under `js/views/`: `conversations.js` (orchestrator) + `conversation/{sessions,history,streaming,input,attachments,event_types}.js` mixins, plus `workspace.js`, `schedules.js`, `webhooks.js`, `usage.js`, `file-editor.js`. Shared helpers: `js/api.js` (REST + SSE), `js/utils.js` (markdown, formatters, toast).
+
+### Theme tokens
+
+- Use **bare token names** - `var(--base)`, `var(--mantle)`, `var(--crust)`, `var(--surface0/1/2)`, `var(--text)`, `var(--lavender)`, `var(--blue)`, `var(--peach)`, etc. The legacy `--ctp-*` aliases were removed.
+- **Visual depth is `crust < mantle < base`** (darker → lighter on Frappé/Mocha/Macchiato). For dark-on-dark panels, panels go `var(--mantle)` and inner cards `var(--surface0)` or `var(--crust)`. Don't put a brighter (`--bg`/`--base`) header over a `--mantle` panel - it inverts the depth on dark themes.
+- Never hardcode hex colors. They won't theme-switch. Even in JS palette objects (e.g. `PI_COLORS` in `conversations.js`), use `var(--pink)` strings - they get embedded into `:style="background: ..."` and resolve through the CSS cascade.
+- `<meta name="theme-color">` is synced to the active theme's `--crust` via an `Alpine.effect` in `app.js` so the PWA status bar / mobile chrome track the theme.
+
+### Verification
+
+Browser verification on UI changes is mandatory. The smoketest recipe - daemon spinup, Playwright wiring, and the post-redesign DOM selectors - is captured in the agent's project memory file `project_daemon_ui_smoketest.md`. There's also a `project_webui_console_hotzones.md` memory listing the load-bearing assumptions in the new UI (pulse signal, mid-turn reload guards, theme depth, PWA resume, mobile back-buttons) that bit during the redesign and should be re-read before touching session lifecycle, theme tokens, or PWA behaviour.
+
 ## Code Review Policy
 
 - **Automatically run the `code-simplifier:code-simplifier` agent** (via the Task tool) after implementing any changes, without waiting for the user to ask. This catches duplication, unnecessary complexity, and keeps the codebase DRY.

tsugite_cli-0.14.0/CONTRIBUTING.md

@@ -0,0 +1,54 @@
+# Contributing
+
+Quick guide for contributors. See [AGENTS.md](AGENTS.md) for architecture and dev commands.
+
+## Commit messages
+
+Use [Conventional Commits](https://www.conventionalcommits.org/). Format:
+
+```
+<type>(<scope>): <subject>
+```
+
+Keep the subject on one line, lowercase, no trailing period. Body is optional and rarely needed.
+
+### Allowed types
+
+These match the groups in `cliff.toml` so release notes generate cleanly:
+
+| Type       | Use for                                                      |
+|------------|--------------------------------------------------------------|
+| `feat`     | User-visible new capability                                  |
+| `fix`      | Bug fix                                                      |
+| `refactor` | Code restructure with no behavior change                     |
+| `docs`     | Documentation only                                           |
+| `test`     | Tests only                                                   |
+| `chore`    | Deps, version bumps, formatting, tooling, lockfile           |
+| `ci`       | CI/release pipeline only                                     |
+| `revert`   | Reverts a prior commit                                       |
+
+Don't use other prefixes (`wip:`, `bump:`, `lint:`, `style:`, etc.). Squash WIP commits before merging. Roll lint/format/version bumps into `chore:`.
+
+### Breaking changes
+
+Append `!` to the type or add a `BREAKING CHANGE:` footer:
+
+```
+feat!: drop Python 3.10 support
+```
+
+### Scopes
+
+Scopes are optional, but should be limited to one of these:
+
+`webui`, `daemon`, `agent`, `cli`, `skills`, `history`, `sandbox`
+
+### Examples
+
+```
+feat(webui): show session topic inline in sidebar
+fix(agent): use ast.parse to locate code block close fence
+refactor(history): per-event JSONL log replaces Turn aggregate
+chore: bump lxml to 6.1.0 (CVE-2026-41066)
+docs: add plugin docs
+```

tsugite_cli-0.14.0/Dockerfile

@@ -0,0 +1,19 @@
+FROM python:3.12-slim
+
+RUN apt-get update && apt-get upgrade -y && apt-get install -y --no-install-recommends \
+    git \
+    ripgrep \
+    curl \
+    ca-certificates \
+    && rm -rf /var/lib/apt/lists/*
+
+COPY . /app
+WORKDIR /app
+RUN pip install --no-cache-dir ".[daemon]"
+
+RUN useradd -m tsu && mkdir -p /workspace && chown tsu:tsu /workspace
+USER tsu
+WORKDIR /workspace
+
+ENTRYPOINT ["tsu"]
+CMD ["--help"]

{tsugite_cli-0.12.2 → tsugite_cli-0.14.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tsugite-cli
-Version: 0.12.2
+Version: 0.14.0
 Summary: Micro-agent runner for task automation using markdown definitions
 Author: Justyn Shull
 License: GNU AFFERO GENERAL PUBLIC LICENSE
@@ -246,7 +246,6 @@ Requires-Dist: ddgs>=9.6.0
 Requires-Dist: html2text>=2020.1.16
 Requires-Dist: httpx>=0.25
 Requires-Dist: jinja2>=3.1
-Requires-Dist: mcp>=1.0
 Requires-Dist: nest-asyncio>=1.5.0
 Requires-Dist: pathspec>=0.11.0
 Requires-Dist: portalocker>=2.8.0
@@ -334,8 +333,8 @@ tsu run +default "summarize the files in this directory"
 # Run an agent file directly
 tsu run my-agent.md "do the thing"
 
-# Start the web UI
-tsu serve
+# Start the daemon (web UI, Discord/Telegram bots)
+tsu daemon
 ```
 
 ## Features
@@ -347,7 +346,6 @@ tsu serve
 - **Skills** directory-based knowledge modules (mostly) following the [agentskills.io](https://agentskills.io/) SKILL.md format
 - **Hooks** that fire shell commands on lifecycle events (post-tool, pre-message, pre/post-compact)
 - **Sandbox** (linux only) via bubblewrap with filesystem and network isolation
-- **MCP** integration for connecting to MCP servers
 
 ## Agents in more detail
 
@@ -395,7 +393,7 @@ All paths follow [XDG Base Directory](https://specifications.freedesktop.org/bas
 
 | Path                                   | Default                              | Contents                                     |
 |----------------------------------------|--------------------------------------|----------------------------------------------|
-| `$XDG_CONFIG_HOME/tsugite/`            | `~/.config/tsugite/`                 | `config.json`, `mcp.json`, `daemon.yaml`     |
+| `$XDG_CONFIG_HOME/tsugite/`            | `~/.config/tsugite/`                 | `config.json`, `daemon.yaml`                 |
 | `$XDG_DATA_HOME/tsugite/history/`      | `~/.local/share/tsugite/history/`    | Session history (JSONL per session)          |
 | `$XDG_DATA_HOME/tsugite/daemon/`       | `~/.local/share/tsugite/daemon/`     | Daemon state                                 |
 | `$XDG_DATA_HOME/tsugite/secrets/`      | `~/.local/share/tsugite/secrets/`    | Encrypted secrets (`secrets.db`)             |
@@ -409,7 +407,7 @@ All paths follow [XDG Base Directory](https://specifications.freedesktop.org/bas
 ```bash
 git clone https://github.com/justyns/tsugite.git
 cd tsugite
-uv sync --dev
+uv sync --all-extras
 ```
 
 ## Status

{tsugite_cli-0.12.2 → tsugite_cli-0.14.0}/README.md

@@ -63,8 +63,8 @@ tsu run +default "summarize the files in this directory"
 # Run an agent file directly
 tsu run my-agent.md "do the thing"
 
-# Start the web UI
-tsu serve
+# Start the daemon (web UI, Discord/Telegram bots)
+tsu daemon
 ```
 
 ## Features
@@ -76,7 +76,6 @@ tsu serve
 - **Skills** directory-based knowledge modules (mostly) following the [agentskills.io](https://agentskills.io/) SKILL.md format
 - **Hooks** that fire shell commands on lifecycle events (post-tool, pre-message, pre/post-compact)
 - **Sandbox** (linux only) via bubblewrap with filesystem and network isolation
-- **MCP** integration for connecting to MCP servers
 
 ## Agents in more detail
 
@@ -124,7 +123,7 @@ All paths follow [XDG Base Directory](https://specifications.freedesktop.org/bas
 
 | Path                                   | Default                              | Contents                                     |
 |----------------------------------------|--------------------------------------|----------------------------------------------|
-| `$XDG_CONFIG_HOME/tsugite/`            | `~/.config/tsugite/`                 | `config.json`, `mcp.json`, `daemon.yaml`     |
+| `$XDG_CONFIG_HOME/tsugite/`            | `~/.config/tsugite/`                 | `config.json`, `daemon.yaml`                 |
 | `$XDG_DATA_HOME/tsugite/history/`      | `~/.local/share/tsugite/history/`    | Session history (JSONL per session)          |
 | `$XDG_DATA_HOME/tsugite/daemon/`       | `~/.local/share/tsugite/daemon/`     | Daemon state                                 |
 | `$XDG_DATA_HOME/tsugite/secrets/`      | `~/.local/share/tsugite/secrets/`    | Encrypted secrets (`secrets.db`)             |
@@ -138,7 +137,7 @@ All paths follow [XDG Base Directory](https://specifications.freedesktop.org/bas
 ```bash
 git clone https://github.com/justyns/tsugite.git
 cd tsugite
-uv sync --dev
+uv sync --all-extras
 ```
 
 ## Status

tsugite_cli-0.14.0/cliff.toml

@@ -0,0 +1,44 @@
+# git-cliff config for tsugite
+# Generates release notes from conventional commit messages.
+# https://git-cliff.org/docs/configuration
+
+[changelog]
+header = ""
+body = """
+{% if version %}\
+## {{ version | trim_start_matches(pat="v") }} ({{ timestamp | date(format="%Y-%m-%d") }})
+{% else %}\
+## Unreleased
+{% endif %}\
+{% for group, commits in commits | group_by(attribute="group") %}
+### {{ group | upper_first }}
+{% for commit in commits %}
+- {{ commit.message | split(pat="\n") | first | trim }}{% if commit.id %} ({{ commit.id | truncate(length=7, end="") }}){% endif %}\
+{% endfor %}
+{% endfor %}\n
+"""
+trim = true
+footer = ""
+
+[git]
+conventional_commits = true
+filter_unconventional = false
+split_commits = false
+commit_parsers = [
+    { message = "^feat", group = "Features" },
+    { message = "^fix", group = "Bug Fixes" },
+    { message = "^perf", group = "Performance" },
+    { message = "^refactor", group = "Refactor" },
+    { message = "^docs", group = "Documentation" },
+    { message = "^test", group = "Tests" },
+    { message = "^ci", group = "CI" },
+    { message = "^chore\\(release\\)", skip = true },
+    { message = "^chore", group = "Maintenance" },
+    { message = "^revert", group = "Reverts" },
+    { message = ".*", group = "Other" },
+]
+filter_commits = false
+tag_pattern = "v[0-9]*"
+ignore_tags = ""
+topo_order = false
+sort_commits = "oldest"