python-agent-harness 1.5.5.8__tar.gz → 1.5.6.0__tar.gz

{python_agent_harness-1.5.5.8/python_agent_harness.egg-info → python_agent_harness-1.5.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-agent-harness
-Version: 1.5.5.8
+Version: 1.5.6.0
 Summary: A lightweight, hackable mini-OpenCode written in Python.
 Author-email: Huming Chen <chenhuming@gmail.com>
 License-Expression: MIT
@@ -9,7 +9,6 @@ Classifier: Development Status :: 5 - Production/Stable
 Classifier: Environment :: Console
 Classifier: Intended Audience :: Developers
 Classifier: Operating System :: MacOS
-Classifier: Operating System :: Microsoft :: Windows
 Classifier: Operating System :: POSIX :: Linux
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
@@ -20,6 +19,7 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: rich>=13.0
 Requires-Dist: httpx>=0.27
+Requires-Dist: certifi>=2024.0
 Requires-Dist: prompt_toolkit>=3.0
 Provides-Extra: mcp
 Requires-Dist: mcp<3,>=2.0; extra == "mcp"
@@ -105,6 +105,7 @@ Edit `~/.config/python-agent-harness/config.json` and set your `base_url`, `api_
 
 - **FSM-driven execution** — explicit `WAIT` / `TOOL` / `TRET` / `SUPERVISE` / `DONE` / `ERRS` / `ABRT` states. Completion supervision nudges the model when it stops early, while failed tool calls are sanitized so they never strand the agent. Transient API failures (`429` / `5xx`) retry with exponential backoff and jitter. Auth-expired status codes (configurable via `AUTH_REFRESH_STATUS_CODES` in `config.py`; defaults to `[401, 502]`) trigger automatic API key re-read from config/env — some API gateways return `502` instead of `401` when the backend auth token has expired. Note: codes in this list are treated as auth-expired exclusively and will not be retried with backoff, so only include codes that are unambiguously auth-related in your environment.
 - **Context management** — CJK-aware token estimation, per-model context windows, and automatic compaction at 70% usage.
+- **Image & text attachments** — attach an image or a text file with `@path` in your message (e.g. `@screenshot.png`, `@README.md`): images (PNG/JPEG/GIF/WebP, up to 20 MB, magic-byte validated) become multimodal `image_url` parts, text files are inlined as text. Only images and text files are supported as input. Path supports web-url for image as well.
 - **Coding tools** — `Agent`, `TodoWrite`, `Glob`, `Grep`, `Read`, `Insert`, `Edit` (including unified diffs), `Write`, `Mkdir`, `Bash`, `Skill`, `Question`, `LSP`, and `PlanExit`. Synchronous tools execute sequentially, but a round made up entirely of read-only tools (`Read`, `Glob`, `Grep`, `Skill`, `LSP`) is dispatched concurrently via a bounded thread pool; asynchronous tools such as `Bash` and `Agent` can run concurrently as well. Results are always delivered in the model's emitted order.
 - **Plan / Build modes** — plan mode is read-only except for the per-session plan file.
 - **Persistent sessions** — sessions are automatically saved after every response to `~/.local/share/python-agent-harness/sessions/`, with LLM-generated titles and support for `/restore --latest` and `/sessions`.
@@ -112,6 +113,7 @@ Edit `~/.config/python-agent-harness/config.json` and set your `base_url`, `api_
 - **MCP support** — optional MCP integration through the `[mcp]` extra. MCP tools become ordinary agent tools such as `mcp__<server>__<tool>`. Supports `stdio`, `streamable-http`, and `sse` transports.
 - **Slash commands** — built-in `/init`, `/review`, `/explain`, and other commands, plus custom commands loaded from `prompts/commands/*.md`.
 - **Custom agents** — switch the main agent's system prompt at runtime with `/agent`. Agent prompt files live in `prompts/agents/*.md`. Use `default_agent` in the config file to start sessions with a specific agent.
+- **Embeddable runtime boundaries** — drive the agent from programs: `headless --json` for one-shot CI/scripting (write-only JSONL stream), `serve` for hosting apps (resident process, bidirectional protocol: multi-turn memory, mid-run Q&A, protocol-level cancel).
 
 ## Inspired by opencode
 
@@ -145,7 +147,8 @@ All LLM settings live in a single JSON configuration file. Environment variables
     "api_key": "sk-...",
     "model": "gpt-5-mini",
     "reasoning_effort": null,
-    "stream": true
+    "stream": true,
+    "supports_image_input": false
   },
   "models": {
     "_comment": "Named LLM profiles for /model switching. Partial settings; unset keys inherit the main llm.",
@@ -171,7 +174,8 @@ All LLM settings live in a single JSON configuration file. Environment variables
     "max_tokens": null,
     "timeout": null,
     "reasoning_effort": null,
-    "stream": null
+    "stream": null,
+    "supports_image_input": null
   },
   "default_agent": null,
   "paths": {
@@ -210,7 +214,7 @@ All LLM settings live in a single JSON configuration file. Environment variables
 
 ### Configuration options
 
-- **`llm`** — main LLM configuration. Optional keys include `temperature`, `max_tokens`, `timeout`, `reasoning_effort`, and `stream`. Values such as `reasoning_effort` are passed to the API as-is when set. `run --no-stream` overrides `stream`.
+- **`llm`** — main LLM configuration. Optional keys include `temperature`, `max_tokens`, `timeout`, `reasoning_effort`, `stream`, and `supports_image_input`. Values such as `reasoning_effort` are passed to the API as-is when set. `run --no-stream` overrides `stream`. `supports_image_input` (default `false`) controls whether `@path` image attachments are sent to the model or stripped with a warning.
 - **`models`** — named LLM profiles for runtime switching with `/model`. A profile is a partial settings dictionary; unset keys inherit from the main `llm`. `default` restores the main LLM configuration.
 - **`context_windows`** — optional per-model context-window overrides (tokens). Keys are model names or substrings (e.g., `deepseek-v4`); matched in file order, first match wins. Overrides the built-in `CONTEXT_WINDOWS` table in `config.py`.
 - **`subagent_llm`** — LLM configuration for `Agent` tool requests. Unset values inherit from the main `llm`. Set `profile` to reuse a profile from `models`. Precedence is: profile settings > explicit `subagent_llm` settings > main `llm` > environment variables.
@@ -225,10 +229,100 @@ All LLM settings live in a single JSON configuration file. Environment variables
 ## Usage
 
 ```sh
-python-agent-harness run [project-dir]
+python-agent-harness run [--project DIR]
 ```
 
-Launches the interactive TUI agent. If `project-dir` is omitted, the current directory is used.
+Launches the interactive TUI agent. If `--project` is omitted, the current directory is used.
+
+### Headless mode
+
+```sh
+python-agent-harness headless [prompt] [--project DIR] [--restore [SPEC]] [--model NAME]
+```
+
+Runs a single prompt without the TUI — for CI, scripting, and piping.
+The assistant's answer is written to stdout once the run completes;
+tool/status events go to stderr, so the answer stream stays clean.
+Interactive prompts are auto-answered (`confirm` → yes, `ask` →
+"Unanswered"), so a run never blocks.
+
+- The prompt is a positional argument; when omitted it is read from stdin:
+
+  ```sh
+  python-agent-harness headless "fix the failing test"
+  echo "fix the failing test" | python-agent-harness headless
+  ```
+
+- `--restore` continues a saved session (the conversation auto-saves after
+  each response). Bare `--restore` uses the most recent session; a SPEC may
+  be a file path or a title substring:
+
+  ```sh
+  python-agent-harness headless "now add tests" --restore
+  python-agent-harness headless "next step" --restore parser-refactor
+  ```
+
+- `--model NAME` selects the model: a profile from the `models` config
+  section (same as the TUI's `/model`), or a raw model name on the
+  configured endpoint when no such profile exists. An explicit `--model`
+  wins over the model restored by `--restore`.
+
+- `--json` emits the run as JSON lines on stdout instead of plain text —
+  one `{"type": ...}` object per line: `start` (echoes the prompt and
+  submit warnings), `delta` (streamed text chunks), `notify` (tool and
+  status events, with `kind`/`data`), `log`, and a final `result` (the
+  filtered answer plus any `errors`). Diagnostics (restore/model notes,
+  a plain-text echo of error events) still go to stderr, so one pipe
+  carries the structured stream. Exit codes are unchanged.
+
+  ```sh
+  python-agent-harness headless "fix it" --json | jq -c 'select(.type=="result")'
+  ```
+
+- Exit code is 0 on success, 1 when the prompt was empty (only failed
+  `@file` references), the run raised an agent error, or the restore failed.
+
+### Serve mode (resident JSONL server)
+
+```sh
+python-agent-harness serve [--project DIR] [--answer-timeout SECONDS]
+```
+
+A persistent, bidirectional runtime boundary for hosting applications
+(a web backend, an IDE, a CI driver).  Unlike `headless --json` (one
+prompt per process, write-only stream), `serve` keeps the
+`Controller`/`Session` resident and speaks a request/response protocol
+over stdin/stdout — the same process boundary (containerizable), but
+the host can:
+
+- submit multiple prompts over the process's lifetime — no per-turn
+  interpreter spawn, and conversation history is retained between them
+  (multi-turn memory);
+- answer the agent's mid-run questions (the `Question` tool and
+  plan-exit confirmation) via an `answer` op;
+- cancel a run as a protocol message (no signal semantics).
+
+Protocol (one JSON object per line):
+
+```
+host → agent: {"op": "submit", "prompt": ..., "run_id": ...}
+              {"op": "answer", "run_id": ..., "answers": [...]}
+              {"op": "cancel", "run_id": ...}
+              {"op": "ping"} | {"op": "shutdown"}
+agent → host: {"type": "ready"}                       first line
+              {"seq": N, "type": "start"|"delta"|"notify"|"log", "run_id": ...}
+              {"seq": N, "type": "result", "run_id": ..., "answer": ...,
+               "errors": [...], "usage": {...}, "cancelled": bool}
+              {"type": "error", "error": ...}         protocol failures
+```
+
+A mid-run question arrives as a `notify` with `kind: "ask"` (data has
+`kind: "ask"|"confirm"`); reply with `answer`.  One run at a time; a
+`submit` while one is active is rejected with an `error` line.
+`--answer-timeout SECONDS` bounds how long a pending question waits
+for the host's answer (default: forever).  The result line's shape is
+identical to `headless --json`'s, so a driver can speak both
+protocols with one parser.
 
 ### Slash commands
 
@@ -282,33 +376,9 @@ You are a personal assistant. You do NOT modify files or run shell commands.
 | **Tools** | Can restrict (`allow_planexit=False`) | All tools, minus the agent's `exclude_tools` |
 | **Ctrl-C** | Restores to default prompt | Stays on the custom agent |
 
-## Project layout
-
-```text
-python_agent_harness/
-├── agent.py           # Agent FSM core: states, transitions, supervision
-├── tool_runner.py     # Tool-call execution/delivery + history salvage
-├── context_manager.py # Context-ratio tracking + compaction
-├── client.py          # OpenAI-compatible streaming client (httpx)
-├── models.py          # Message / ToolCall / ToolSpec data classes
-├── token_estimator.py # CJK-aware token estimation + calibration
-├── planmode.py        # Plan/build modes + plan-file lifecycle
-├── prompts.py         # Prompt loading + system-prompt assembly
-├── persistence.py     # Session persistence + titles
-├── session.py         # Session wiring hub + MCP lifecycle
-├── subagent.py        # Sub-agent runner + error containment
-├── commands.py        # Init/review/custom command definitions
-├── cli.py             # CLI entry points
-├── tui/               # Rich + prompt_toolkit TUI (package)
-├── diffrender.py      # Unified diff generation + Rich rendering
-├── lsp/               # Built-in LSP client
-├── mcp/               # Optional MCP client
-└── tools/             # Tool implementations + registry
-```
-
 ## Development
 
-Requires Python ≥ 3.11. CI runs against Python 3.11, 3.12, and 3.13 on Linux, MacOS and Windows.
+Requires Python ≥ 3.11. CI runs against Python 3.11, 3.12, and 3.13 on Linux and MacOS.
 
 ```sh
 make test                           # unit tests

{python_agent_harness-1.5.5.8 → python_agent_harness-1.5.6.0}/README.md

@@ -71,6 +71,7 @@ Edit `~/.config/python-agent-harness/config.json` and set your `base_url`, `api_
 
 - **FSM-driven execution** — explicit `WAIT` / `TOOL` / `TRET` / `SUPERVISE` / `DONE` / `ERRS` / `ABRT` states. Completion supervision nudges the model when it stops early, while failed tool calls are sanitized so they never strand the agent. Transient API failures (`429` / `5xx`) retry with exponential backoff and jitter. Auth-expired status codes (configurable via `AUTH_REFRESH_STATUS_CODES` in `config.py`; defaults to `[401, 502]`) trigger automatic API key re-read from config/env — some API gateways return `502` instead of `401` when the backend auth token has expired. Note: codes in this list are treated as auth-expired exclusively and will not be retried with backoff, so only include codes that are unambiguously auth-related in your environment.
 - **Context management** — CJK-aware token estimation, per-model context windows, and automatic compaction at 70% usage.
+- **Image & text attachments** — attach an image or a text file with `@path` in your message (e.g. `@screenshot.png`, `@README.md`): images (PNG/JPEG/GIF/WebP, up to 20 MB, magic-byte validated) become multimodal `image_url` parts, text files are inlined as text. Only images and text files are supported as input. Path supports web-url for image as well.
 - **Coding tools** — `Agent`, `TodoWrite`, `Glob`, `Grep`, `Read`, `Insert`, `Edit` (including unified diffs), `Write`, `Mkdir`, `Bash`, `Skill`, `Question`, `LSP`, and `PlanExit`. Synchronous tools execute sequentially, but a round made up entirely of read-only tools (`Read`, `Glob`, `Grep`, `Skill`, `LSP`) is dispatched concurrently via a bounded thread pool; asynchronous tools such as `Bash` and `Agent` can run concurrently as well. Results are always delivered in the model's emitted order.
 - **Plan / Build modes** — plan mode is read-only except for the per-session plan file.
 - **Persistent sessions** — sessions are automatically saved after every response to `~/.local/share/python-agent-harness/sessions/`, with LLM-generated titles and support for `/restore --latest` and `/sessions`.
@@ -78,6 +79,7 @@ Edit `~/.config/python-agent-harness/config.json` and set your `base_url`, `api_
 - **MCP support** — optional MCP integration through the `[mcp]` extra. MCP tools become ordinary agent tools such as `mcp__<server>__<tool>`. Supports `stdio`, `streamable-http`, and `sse` transports.
 - **Slash commands** — built-in `/init`, `/review`, `/explain`, and other commands, plus custom commands loaded from `prompts/commands/*.md`.
 - **Custom agents** — switch the main agent's system prompt at runtime with `/agent`. Agent prompt files live in `prompts/agents/*.md`. Use `default_agent` in the config file to start sessions with a specific agent.
+- **Embeddable runtime boundaries** — drive the agent from programs: `headless --json` for one-shot CI/scripting (write-only JSONL stream), `serve` for hosting apps (resident process, bidirectional protocol: multi-turn memory, mid-run Q&A, protocol-level cancel).
 
 ## Inspired by opencode
 
@@ -111,7 +113,8 @@ All LLM settings live in a single JSON configuration file. Environment variables
     "api_key": "sk-...",
     "model": "gpt-5-mini",
     "reasoning_effort": null,
-    "stream": true
+    "stream": true,
+    "supports_image_input": false
   },
   "models": {
     "_comment": "Named LLM profiles for /model switching. Partial settings; unset keys inherit the main llm.",
@@ -137,7 +140,8 @@ All LLM settings live in a single JSON configuration file. Environment variables
     "max_tokens": null,
     "timeout": null,
     "reasoning_effort": null,
-    "stream": null
+    "stream": null,
+    "supports_image_input": null
   },
   "default_agent": null,
   "paths": {
@@ -176,7 +180,7 @@ All LLM settings live in a single JSON configuration file. Environment variables
 
 ### Configuration options
 
-- **`llm`** — main LLM configuration. Optional keys include `temperature`, `max_tokens`, `timeout`, `reasoning_effort`, and `stream`. Values such as `reasoning_effort` are passed to the API as-is when set. `run --no-stream` overrides `stream`.
+- **`llm`** — main LLM configuration. Optional keys include `temperature`, `max_tokens`, `timeout`, `reasoning_effort`, `stream`, and `supports_image_input`. Values such as `reasoning_effort` are passed to the API as-is when set. `run --no-stream` overrides `stream`. `supports_image_input` (default `false`) controls whether `@path` image attachments are sent to the model or stripped with a warning.
 - **`models`** — named LLM profiles for runtime switching with `/model`. A profile is a partial settings dictionary; unset keys inherit from the main `llm`. `default` restores the main LLM configuration.
 - **`context_windows`** — optional per-model context-window overrides (tokens). Keys are model names or substrings (e.g., `deepseek-v4`); matched in file order, first match wins. Overrides the built-in `CONTEXT_WINDOWS` table in `config.py`.
 - **`subagent_llm`** — LLM configuration for `Agent` tool requests. Unset values inherit from the main `llm`. Set `profile` to reuse a profile from `models`. Precedence is: profile settings > explicit `subagent_llm` settings > main `llm` > environment variables.
@@ -191,10 +195,100 @@ All LLM settings live in a single JSON configuration file. Environment variables
 ## Usage
 
 ```sh
-python-agent-harness run [project-dir]
+python-agent-harness run [--project DIR]
 ```
 
-Launches the interactive TUI agent. If `project-dir` is omitted, the current directory is used.
+Launches the interactive TUI agent. If `--project` is omitted, the current directory is used.
+
+### Headless mode
+
+```sh
+python-agent-harness headless [prompt] [--project DIR] [--restore [SPEC]] [--model NAME]
+```
+
+Runs a single prompt without the TUI — for CI, scripting, and piping.
+The assistant's answer is written to stdout once the run completes;
+tool/status events go to stderr, so the answer stream stays clean.
+Interactive prompts are auto-answered (`confirm` → yes, `ask` →
+"Unanswered"), so a run never blocks.
+
+- The prompt is a positional argument; when omitted it is read from stdin:
+
+  ```sh
+  python-agent-harness headless "fix the failing test"
+  echo "fix the failing test" | python-agent-harness headless
+  ```
+
+- `--restore` continues a saved session (the conversation auto-saves after
+  each response). Bare `--restore` uses the most recent session; a SPEC may
+  be a file path or a title substring:
+
+  ```sh
+  python-agent-harness headless "now add tests" --restore
+  python-agent-harness headless "next step" --restore parser-refactor
+  ```
+
+- `--model NAME` selects the model: a profile from the `models` config
+  section (same as the TUI's `/model`), or a raw model name on the
+  configured endpoint when no such profile exists. An explicit `--model`
+  wins over the model restored by `--restore`.
+
+- `--json` emits the run as JSON lines on stdout instead of plain text —
+  one `{"type": ...}` object per line: `start` (echoes the prompt and
+  submit warnings), `delta` (streamed text chunks), `notify` (tool and
+  status events, with `kind`/`data`), `log`, and a final `result` (the
+  filtered answer plus any `errors`). Diagnostics (restore/model notes,
+  a plain-text echo of error events) still go to stderr, so one pipe
+  carries the structured stream. Exit codes are unchanged.
+
+  ```sh
+  python-agent-harness headless "fix it" --json | jq -c 'select(.type=="result")'
+  ```
+
+- Exit code is 0 on success, 1 when the prompt was empty (only failed
+  `@file` references), the run raised an agent error, or the restore failed.
+
+### Serve mode (resident JSONL server)
+
+```sh
+python-agent-harness serve [--project DIR] [--answer-timeout SECONDS]
+```
+
+A persistent, bidirectional runtime boundary for hosting applications
+(a web backend, an IDE, a CI driver).  Unlike `headless --json` (one
+prompt per process, write-only stream), `serve` keeps the
+`Controller`/`Session` resident and speaks a request/response protocol
+over stdin/stdout — the same process boundary (containerizable), but
+the host can:
+
+- submit multiple prompts over the process's lifetime — no per-turn
+  interpreter spawn, and conversation history is retained between them
+  (multi-turn memory);
+- answer the agent's mid-run questions (the `Question` tool and
+  plan-exit confirmation) via an `answer` op;
+- cancel a run as a protocol message (no signal semantics).
+
+Protocol (one JSON object per line):
+
+```
+host → agent: {"op": "submit", "prompt": ..., "run_id": ...}
+              {"op": "answer", "run_id": ..., "answers": [...]}
+              {"op": "cancel", "run_id": ...}
+              {"op": "ping"} | {"op": "shutdown"}
+agent → host: {"type": "ready"}                       first line
+              {"seq": N, "type": "start"|"delta"|"notify"|"log", "run_id": ...}
+              {"seq": N, "type": "result", "run_id": ..., "answer": ...,
+               "errors": [...], "usage": {...}, "cancelled": bool}
+              {"type": "error", "error": ...}         protocol failures
+```
+
+A mid-run question arrives as a `notify` with `kind: "ask"` (data has
+`kind: "ask"|"confirm"`); reply with `answer`.  One run at a time; a
+`submit` while one is active is rejected with an `error` line.
+`--answer-timeout SECONDS` bounds how long a pending question waits
+for the host's answer (default: forever).  The result line's shape is
+identical to `headless --json`'s, so a driver can speak both
+protocols with one parser.
 
 ### Slash commands
 
@@ -248,33 +342,9 @@ You are a personal assistant. You do NOT modify files or run shell commands.
 | **Tools** | Can restrict (`allow_planexit=False`) | All tools, minus the agent's `exclude_tools` |
 | **Ctrl-C** | Restores to default prompt | Stays on the custom agent |
 
-## Project layout
-
-```text
-python_agent_harness/
-├── agent.py           # Agent FSM core: states, transitions, supervision
-├── tool_runner.py     # Tool-call execution/delivery + history salvage
-├── context_manager.py # Context-ratio tracking + compaction
-├── client.py          # OpenAI-compatible streaming client (httpx)
-├── models.py          # Message / ToolCall / ToolSpec data classes
-├── token_estimator.py # CJK-aware token estimation + calibration
-├── planmode.py        # Plan/build modes + plan-file lifecycle
-├── prompts.py         # Prompt loading + system-prompt assembly
-├── persistence.py     # Session persistence + titles
-├── session.py         # Session wiring hub + MCP lifecycle
-├── subagent.py        # Sub-agent runner + error containment
-├── commands.py        # Init/review/custom command definitions
-├── cli.py             # CLI entry points
-├── tui/               # Rich + prompt_toolkit TUI (package)
-├── diffrender.py      # Unified diff generation + Rich rendering
-├── lsp/               # Built-in LSP client
-├── mcp/               # Optional MCP client
-└── tools/             # Tool implementations + registry
-```
-
 ## Development
 
-Requires Python ≥ 3.11. CI runs against Python 3.11, 3.12, and 3.13 on Linux, MacOS and Windows.
+Requires Python ≥ 3.11. CI runs against Python 3.11, 3.12, and 3.13 on Linux and MacOS.
 
 ```sh
 make test                           # unit tests

{python_agent_harness-1.5.5.8 → python_agent_harness-1.5.6.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "python-agent-harness"
-version = "1.5.5.8"
+version = "1.5.6.0"
 description = "A lightweight, hackable mini-OpenCode written in Python."
 authors = [
     {name = "Huming Chen", email = "chenhuming@gmail.com"}
@@ -17,7 +17,6 @@ classifiers = [
     "Environment :: Console",
     "Intended Audience :: Developers",
     "Operating System :: MacOS",
-    "Operating System :: Microsoft :: Windows",
     "Operating System :: POSIX :: Linux",
     "Programming Language :: Python :: 3.11",
     "Programming Language :: Python :: 3.12",
@@ -27,6 +26,7 @@ classifiers = [
 dependencies = [
     "rich>=13.0",
     "httpx>=0.27",
+    "certifi>=2024.0",
     "prompt_toolkit>=3.0",
 ]
 
@@ -57,7 +57,7 @@ dev = [
 ]
 
 [project.scripts]
-python-agent-harness = "python_agent_harness.cli:main"
+python-agent-harness = "python_agent_harness.entry.cli:main"
 
 [tool.setuptools.packages.find]
 include = ["python_agent_harness*"]
@@ -90,10 +90,10 @@ source = ["python_agent_harness"]
 branch = true
 # The console/TUI entry points aren't exercised by unittest; omit the ones
 # that would otherwise drag the number down without adding signal.
-omit = ["python_agent_harness/__main__.py"]
+omit = [
+    "python_agent_harness/__main__.py",
+]
 
 [tool.coverage.report]
 show_missing = true
-# Current line + branch coverage is ~98%. Gate at 90 to leave headroom for
-# small changes while still catching real regressions. Raise as coverage grows.
-fail_under = 90
+fail_under = 95

{python_agent_harness-1.5.5.8 → python_agent_harness-1.5.6.0}/python_agent_harness/__init__.py

@@ -1,13 +1,14 @@
 """python-agent-harness: a Python port of the gptel-agent-harness."""
 
-from .client import Client, LLMClient
+from .core.models import AgentMode, ImagePart, Message, TextPart, ToolCall, ToolSpec
+from .entry.cli import main  # noqa: F401  (public lib surface: main entry point)
+from .llm.client import Client, LLMClient
 from .lsp.config import LSPConfig, LSPServerConfig
 from .mcp.config import MCPConfig, MCPServerConfig
 from .mcp.manager import MCPManager
-from .models import AgentMode, Message, ToolCall, ToolSpec
-from .session import Session
+from .session.session import Session
 
-__version__ = "1.5.5.8"
+__version__ = "1.5.6.0"
 
 __all__ = [
     "Client",
@@ -20,6 +21,8 @@ __all__ = [
     "MCPManager",
     "MCPServerConfig",
     "Message",
+    "TextPart",
+    "ImagePart",
     "ToolCall",
     "ToolSpec",
     "__version__",

{python_agent_harness-1.5.5.8 → python_agent_harness-1.5.6.0}/python_agent_harness/__main__.py

@@ -1,5 +1,5 @@
 import sys
 
-from .cli import main
+from .entry.cli import main
 
 sys.exit(main())

python_agent_harness-1.5.6.0/python_agent_harness/core/__init__.py

@@ -0,0 +1 @@
+"""Core engine: agent loop, tool dispatch, models, and context utilities."""