hx-cli 0.2.11__tar.gz → 0.2.13__tar.gz

{hx_cli-0.2.11 → hx_cli-0.2.13}/CHANGELOG.md

@@ -28,6 +28,63 @@ the project follows [semantic versioning](https://semver.org/).
 
 ---
 
+## [0.2.13] - 2026-10-04
+
+### Added
+
+- Claude Pro/Max route: `hx auth login claude-code`, then
+  `hx --model claude-code/claude-sonnet-5`. Runs Claude models on your Claude
+  subscription through the official Claude Code CLI, with HX's own tools,
+  approvals and transcript. `/model` lists the account's models and `/effort`
+  their levels.
+- Behind a TLS-inspecting proxy the `claude-code` route takes the same
+  settings as every other route: `HX_CA_BUNDLE` reaches Claude Code as
+  `NODE_EXTRA_CA_CERTS` and `HX_SSL_NO_VERIFY` as
+  `NODE_TLS_REJECT_UNAUTHORIZED=0`, Claude Code's own `CLAUDE_CODE_CERT_STORE`
+  and `CLAUDE_CODE_CLIENT_CERT` / `_KEY` / `_KEY_PASSPHRASE` (for a network
+  that requires a client certificate) pass through, and a certificate failure
+  it reports names the fix.
+- On the `claude-code` route, a turn Anthropic bills as Extra Usage while
+  your plan still has room says so, and names HX's part of the system prompt,
+  instead of claiming the plan's usage limit is reached. A turn whose prompt
+  carries HX's own system prompt text (a copied `system-prompt.md`, an
+  AGENTS.md, an agent definition) is refused before it is sent, naming where
+  the text is; `hx prompt` shows the sources.
+
+### Fixed
+
+- A subagent that fails - a provider error, a refused prompt, the turn limit -
+  reports why to the parent model, instead of "(the subagent returned no
+  text)".
+- `Glob` with a pattern of `.` or `./` returns an error saying to use `*` or
+  `**/*`, and an absolute pattern one naming the `path` and relative pattern
+  to send instead, on every Python version, instead of a Python exception.
+- With `tui.enterWhileBusy` set to `"steer"`, `alt+enter` queues a message
+  behind the running turn, as the prompt says. It used to steer like `enter`,
+  leaving no way to queue in that mode.
+- The status bar's `⧗N queued` count stays visible in a project with a long
+  path or branch name; the path is shortened instead of the count being cut off.
+
+---
+
+## [0.2.12] - 2026-10-01
+
+### Fixed
+
+- `/exit` and `ctrl+d` return the shell at once. They used to wait up to 10
+  seconds on a model call renaming the session; sessions are no longer renamed
+  on the way out, in the TUI or with `hx -p`.
+- A name set with `/title` is no longer replaced by a generated one, including
+  one that was still being generated when you set it.
+- The session name is generated from the opening and the latest stretch of the
+  conversation, not only its first 2000 characters.
+- A session left before its first name came back is named from your first
+  message, instead of being listed by `/resume` with no name.
+- A session left with `/resume` into another directory is renamed for what it
+  became, by the HX that starts there, in the background.
+
+---
+
 ## [0.2.11] - 2026-10-01
 
 ### Fixed
@@ -776,7 +833,9 @@ First release, published to PyPI as [`hx-cli`](https://pypi.org/project/hx-cli/)
 - `/configure` and `hx auth` for the OpenRouter key, `hx upgrade` for
   self-update, and `install.sh` bootstrapping uv with a pinned Python.
 
-[Unreleased]: https://github.com/aletisunil/hx/compare/v0.2.11...HEAD
+[Unreleased]: https://github.com/aletisunil/hx/compare/v0.2.13...HEAD
+[0.2.13]: https://github.com/aletisunil/hx/compare/v0.2.12...v0.2.13
+[0.2.12]: https://github.com/aletisunil/hx/compare/v0.2.11...v0.2.12
 [0.2.11]: https://github.com/aletisunil/hx/compare/v0.2.10...v0.2.11
 [0.2.10]: https://github.com/aletisunil/hx/compare/v0.2.9...v0.2.10
 [0.2.9]: https://github.com/aletisunil/hx/compare/v0.2.8...v0.2.9

{hx_cli-0.2.11 → hx_cli-0.2.13}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: hx-cli
-Version: 0.2.11
+Version: 0.2.13
 Summary: HX - an agent harness for the terminal
 Project-URL: Homepage, https://hx.sunilaleti.dev
 Project-URL: Documentation, https://hx.sunilaleti.dev
@@ -31,6 +31,7 @@ Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
 Requires-Dist: pytest-cov>=5.0; extra == 'dev'
 Requires-Dist: pytest>=8.2; extra == 'dev'
 Requires-Dist: ruff>=0.6; extra == 'dev'
+Requires-Dist: trustme>=1.2; extra == 'dev'
 Requires-Dist: types-pygments; extra == 'dev'
 Requires-Dist: types-pyyaml; extra == 'dev'
 Provides-Extra: symbols
@@ -90,7 +91,7 @@ Requires Python 3.11+. macOS and Linux. Update with `hx upgrade`.
 
 ### Credentials
 
-HX reaches models over three routes. Which one serves a turn is decided by the
+HX reaches models over four routes. Which one serves a turn is decided by the
 model id alone, so "what paid for that" is always answerable by reading it:
 
 | Model id | Route | Billing |
@@ -98,8 +99,10 @@ model id alone, so "what paid for that" is always answerable by reading it:
 | `anthropic/claude-sonnet-4.5`, `openai/gpt-5`, … | OpenRouter | per token, API key |
 | `openai-codex/gpt-5.6-terra` | ChatGPT Plus/Pro | your subscription |
 | `devin/swe-1-6`, `devin/claude-opus-5`, … | Devin | your subscription |
+| `claude-code/claude-sonnet-5`, `claude-code/claude-opus-4-8`, … | Claude Pro/Max, via Claude Code | your subscription |
 
-Credentials live in `~/.hx/auth.json`, mode 0600, one entry per route.
+Credentials live in `~/.hx/auth.json`, mode 0600, one entry per route - except
+Claude Code's, which stays with Claude Code.
 
 **OpenRouter.** On first run HX asks for a key. Get one at
 <https://openrouter.ai/keys>. Change it later with `/configure` in the TUI, or:
@@ -223,6 +226,47 @@ changes what a turn costs or how much fits. Router models such as
 `devin/adaptive` are resolved to a concrete model on every turn by Devin itself.
 If the list cannot be fetched, `devin/swe-1-6` and `devin/swe-1-6-fast` stand in.
 
+**Claude Pro/Max.** HX runs Claude models on your Claude subscription through
+the official [Claude Code](https://claude.com/claude-code) CLI, the way the
+Claude Agent SDK does. Install Claude Code, then:
+
+```sh
+hx auth login claude-code       # Claude Code's own sign-in; or /login inside HX
+hx --model claude-code/claude-sonnet-5
+```
+
+HX holds no Claude token. The login is Claude Code's, kept and refreshed where
+Claude Code keeps it, so `hx auth logout claude-code` only tells you to run
+`claude auth logout` - which signs out every Claude Code on the machine. A
+headless machine can use a token from `claude setup-token` in
+`CLAUDE_CODE_OAUTH_TOKEN`. A Console login (`claude auth login --console`) bills
+per token and is refused: this route is the subscription.
+
+How a turn works: HX starts `claude -p` with every one of Claude Code's own
+tools switched off and serves HX's tools to it as an MCP server. The model's
+tool calls are run, permission-checked and drawn by HX exactly as on every
+other route; Claude Code holds each call open until HX answers it, however long
+an approval takes. The system prompt is Claude Code's, with your AGENTS.md
+files, skills index and `--append-system-prompt` text added. One Claude Code
+process serves a conversation for as long as it can, so the prompt cache
+carries from turn to turn; after an interrupt, a steer while a tool runs, a
+compaction, `/model`, `/effort` or a resumed session, HX starts a new one on a
+session rebuilt from its own transcript. That costs a second or so and a
+partly cold cache, not the conversation.
+
+Claude Code is started isolated from your Claude Code setup: no CLAUDE.md, no
+hooks, no plugins or MCP servers from `~/.claude`, no auto-memory, no
+auto-compaction (HX compacts its own transcript), and nothing saved to Claude
+Code's session list. Variables that would move it off the subscription -
+`ANTHROPIC_API_KEY`, `ANTHROPIC_BASE_URL`, `CLAUDE_CODE_USE_BEDROCK` and the
+rest - are removed from its environment; its TLS settings are kept (see
+*Behind a TLS-inspecting proxy* below). `HX_CLAUDE_CODE_PATH` points HX at a
+`claude` other than the one on `PATH`.
+
+`/model` offers the models Claude Code lists for the account, each with the
+efforts it accepts for `/effort`; `/models refresh` asks again. When a usage
+limit is reached, HX says which one and when it resets.
+
 **Web search.** Optional, and the one credential that is not a model route.
 It powers two tools:
 
@@ -232,7 +276,7 @@ It powers two tools:
 | `WebFetch` | read up to 5 URLs, returned as markdown |
 
 [Tavily](https://app.tavily.com) bills per search rather than per token, so it
-works identically on both routes — including the ChatGPT subscription one,
+works identically on every route - including the subscription ones,
 where a provider-native search tool is not on offer.
 
 Get a key at <https://app.tavily.com> — the free tier is 1000 searches a month
@@ -286,9 +330,18 @@ startup every session, because it is not a fix. A TLS failure is reported in
 one line - `/model` and the startup notice both name the certificate problem
 rather than reporting an empty catalogue with no cause.
 
-There is no Claude Pro/Max route. Anthropic rejects OAuth tokens unless the
-request impersonates Claude Code, which HX will not do. Claude models stay
-available through OpenRouter.
+The same settings cover the `claude-code` route, whose requests Claude Code
+makes with its own TLS stack: HX passes `HX_CA_BUNDLE` on to it as
+`NODE_EXTRA_CA_CERTS` (unless you already set that yourself), and
+`HX_SSL_NO_VERIFY` as `NODE_TLS_REJECT_UNAUTHORIZED=0`. Claude Code reads the
+OS trust store on its own, and its own TLS settings reach it untouched:
+`CLAUDE_CODE_CERT_STORE`, and `CLAUDE_CODE_CLIENT_CERT`,
+`CLAUDE_CODE_CLIENT_KEY` and `CLAUDE_CODE_CLIENT_KEY_PASSPHRASE` for a network
+that requires a client certificate.
+
+HX never sends a Claude subscription token to the API itself - Anthropic
+accepts those only from Claude Code, and HX will not impersonate it. The
+`claude-code` route runs the real Claude Code instead.
 
 ---
 
@@ -314,7 +367,7 @@ hx mcp list|add|remove      # manage MCP servers
 hx mcp login <server>       # sign in to a remote MCP server in the browser
 hx mcp logout <server>      # forget a remote MCP server's sign-in
 hx auth [set|clear]         # manage the OpenRouter key
-hx auth login [provider]    # sign in (openrouter, openai-codex, devin)
+hx auth login [provider]    # sign in (openrouter, openai-codex, devin, claude-code)
 hx auth logout <provider>   # forget a stored credential
 hx docs [section]           # the manual; no argument lists its sections
 hx changelog [version]      # what shipped in each version
@@ -709,8 +762,14 @@ After the first exchange, HX asks the model for a short name for the session and
 writes it to `~/.hx/sessions/<id>/meta.json`, so `/resume` lists work rather
 than timestamps. It is one small call — cap 32 output tokens, `models.title_model`
 if you want a cheaper model for it — and it is counted in `/cost` like any other.
-If the call fails the session is still named, from your first message. `/title
-<text>` renames it.
+If the call fails, or you leave before it is back, the session is still named,
+from your first message.
+
+The live session is never renamed while it runs, and nothing is renamed on
+`/exit`, which returns your shell at once. A session you leave with `/clear` or
+`/resume` - including a `/resume` into another directory - is renamed in the
+background for what it became. `/title <text>` renames it yourself, and a name
+you chose is never replaced.
 
 `/resume` lists every session except the one you are in: this directory's
 first, then other directories', each row naming where it lives. A session from

{hx_cli-0.2.11 → hx_cli-0.2.13}/README.md

@@ -50,7 +50,7 @@ Requires Python 3.11+. macOS and Linux. Update with `hx upgrade`.
 
 ### Credentials
 
-HX reaches models over three routes. Which one serves a turn is decided by the
+HX reaches models over four routes. Which one serves a turn is decided by the
 model id alone, so "what paid for that" is always answerable by reading it:
 
 | Model id | Route | Billing |
@@ -58,8 +58,10 @@ model id alone, so "what paid for that" is always answerable by reading it:
 | `anthropic/claude-sonnet-4.5`, `openai/gpt-5`, … | OpenRouter | per token, API key |
 | `openai-codex/gpt-5.6-terra` | ChatGPT Plus/Pro | your subscription |
 | `devin/swe-1-6`, `devin/claude-opus-5`, … | Devin | your subscription |
+| `claude-code/claude-sonnet-5`, `claude-code/claude-opus-4-8`, … | Claude Pro/Max, via Claude Code | your subscription |
 
-Credentials live in `~/.hx/auth.json`, mode 0600, one entry per route.
+Credentials live in `~/.hx/auth.json`, mode 0600, one entry per route - except
+Claude Code's, which stays with Claude Code.
 
 **OpenRouter.** On first run HX asks for a key. Get one at
 <https://openrouter.ai/keys>. Change it later with `/configure` in the TUI, or:
@@ -183,6 +185,47 @@ changes what a turn costs or how much fits. Router models such as
 `devin/adaptive` are resolved to a concrete model on every turn by Devin itself.
 If the list cannot be fetched, `devin/swe-1-6` and `devin/swe-1-6-fast` stand in.
 
+**Claude Pro/Max.** HX runs Claude models on your Claude subscription through
+the official [Claude Code](https://claude.com/claude-code) CLI, the way the
+Claude Agent SDK does. Install Claude Code, then:
+
+```sh
+hx auth login claude-code       # Claude Code's own sign-in; or /login inside HX
+hx --model claude-code/claude-sonnet-5
+```
+
+HX holds no Claude token. The login is Claude Code's, kept and refreshed where
+Claude Code keeps it, so `hx auth logout claude-code` only tells you to run
+`claude auth logout` - which signs out every Claude Code on the machine. A
+headless machine can use a token from `claude setup-token` in
+`CLAUDE_CODE_OAUTH_TOKEN`. A Console login (`claude auth login --console`) bills
+per token and is refused: this route is the subscription.
+
+How a turn works: HX starts `claude -p` with every one of Claude Code's own
+tools switched off and serves HX's tools to it as an MCP server. The model's
+tool calls are run, permission-checked and drawn by HX exactly as on every
+other route; Claude Code holds each call open until HX answers it, however long
+an approval takes. The system prompt is Claude Code's, with your AGENTS.md
+files, skills index and `--append-system-prompt` text added. One Claude Code
+process serves a conversation for as long as it can, so the prompt cache
+carries from turn to turn; after an interrupt, a steer while a tool runs, a
+compaction, `/model`, `/effort` or a resumed session, HX starts a new one on a
+session rebuilt from its own transcript. That costs a second or so and a
+partly cold cache, not the conversation.
+
+Claude Code is started isolated from your Claude Code setup: no CLAUDE.md, no
+hooks, no plugins or MCP servers from `~/.claude`, no auto-memory, no
+auto-compaction (HX compacts its own transcript), and nothing saved to Claude
+Code's session list. Variables that would move it off the subscription -
+`ANTHROPIC_API_KEY`, `ANTHROPIC_BASE_URL`, `CLAUDE_CODE_USE_BEDROCK` and the
+rest - are removed from its environment; its TLS settings are kept (see
+*Behind a TLS-inspecting proxy* below). `HX_CLAUDE_CODE_PATH` points HX at a
+`claude` other than the one on `PATH`.
+
+`/model` offers the models Claude Code lists for the account, each with the
+efforts it accepts for `/effort`; `/models refresh` asks again. When a usage
+limit is reached, HX says which one and when it resets.
+
 **Web search.** Optional, and the one credential that is not a model route.
 It powers two tools:
 
@@ -192,7 +235,7 @@ It powers two tools:
 | `WebFetch` | read up to 5 URLs, returned as markdown |
 
 [Tavily](https://app.tavily.com) bills per search rather than per token, so it
-works identically on both routes — including the ChatGPT subscription one,
+works identically on every route - including the subscription ones,
 where a provider-native search tool is not on offer.
 
 Get a key at <https://app.tavily.com> — the free tier is 1000 searches a month
@@ -246,9 +289,18 @@ startup every session, because it is not a fix. A TLS failure is reported in
 one line - `/model` and the startup notice both name the certificate problem
 rather than reporting an empty catalogue with no cause.
 
-There is no Claude Pro/Max route. Anthropic rejects OAuth tokens unless the
-request impersonates Claude Code, which HX will not do. Claude models stay
-available through OpenRouter.
+The same settings cover the `claude-code` route, whose requests Claude Code
+makes with its own TLS stack: HX passes `HX_CA_BUNDLE` on to it as
+`NODE_EXTRA_CA_CERTS` (unless you already set that yourself), and
+`HX_SSL_NO_VERIFY` as `NODE_TLS_REJECT_UNAUTHORIZED=0`. Claude Code reads the
+OS trust store on its own, and its own TLS settings reach it untouched:
+`CLAUDE_CODE_CERT_STORE`, and `CLAUDE_CODE_CLIENT_CERT`,
+`CLAUDE_CODE_CLIENT_KEY` and `CLAUDE_CODE_CLIENT_KEY_PASSPHRASE` for a network
+that requires a client certificate.
+
+HX never sends a Claude subscription token to the API itself - Anthropic
+accepts those only from Claude Code, and HX will not impersonate it. The
+`claude-code` route runs the real Claude Code instead.
 
 ---
 
@@ -274,7 +326,7 @@ hx mcp list|add|remove      # manage MCP servers
 hx mcp login <server>       # sign in to a remote MCP server in the browser
 hx mcp logout <server>      # forget a remote MCP server's sign-in
 hx auth [set|clear]         # manage the OpenRouter key
-hx auth login [provider]    # sign in (openrouter, openai-codex, devin)
+hx auth login [provider]    # sign in (openrouter, openai-codex, devin, claude-code)
 hx auth logout <provider>   # forget a stored credential
 hx docs [section]           # the manual; no argument lists its sections
 hx changelog [version]      # what shipped in each version
@@ -669,8 +721,14 @@ After the first exchange, HX asks the model for a short name for the session and
 writes it to `~/.hx/sessions/<id>/meta.json`, so `/resume` lists work rather
 than timestamps. It is one small call — cap 32 output tokens, `models.title_model`
 if you want a cheaper model for it — and it is counted in `/cost` like any other.
-If the call fails the session is still named, from your first message. `/title
-<text>` renames it.
+If the call fails, or you leave before it is back, the session is still named,
+from your first message.
+
+The live session is never renamed while it runs, and nothing is renamed on
+`/exit`, which returns your shell at once. A session you leave with `/clear` or
+`/resume` - including a `/resume` into another directory - is renamed in the
+background for what it became. `/title <text>` renames it yourself, and a name
+you chose is never replaced.
 
 `/resume` lists every session except the one you are in: this directory's
 first, then other directories', each row naming where it lives. A session from

{hx_cli-0.2.11 → hx_cli-0.2.13}/pyproject.toml

@@ -55,6 +55,9 @@ dev = [
   # A VT emulator, so tests can assert what the differ actually paints rather
   # than what it claims to have written.
   "pyte>=0.8",
+  # A throwaway CA, so the TLS tests can stand up the intercepting proxy a
+  # corporate network puts between HX and the API.
+  "trustme>=1.2",
 ]
 
 [project.scripts]

{hx_cli-0.2.11 → hx_cli-0.2.13}/src/hx/__init__.py

@@ -1,5 +1,5 @@
 """HX - an agent harness for the terminal."""
 
-__version__ = "0.2.11"
+__version__ = "0.2.13"
 
 __all__ = ["__version__"]

{hx_cli-0.2.11 → hx_cli-0.2.13}/src/hx/agents/subagent.py

@@ -107,7 +107,13 @@ class SubagentRunner:
         try:
             loop = self._build_loop(definition, subagent_id)
             result = await loop.run(prompt)
-            report = _final_text(result) or "(the subagent returned no text)"
+            report = _final_text(result)
+            if result.error is not None:
+                # The parent model only sees the report: without the reason it
+                # cannot tell a refused or broken run from one with nothing to say.
+                failure = f"The subagent failed: {result.error}"
+                report = f"{report}\n\n{failure}" if report else failure
+            report = report or "(the subagent returned no text)"
             cost = loop.session.usage.total_cost_usd
             self._roll_up_cost(loop)
             return SubagentResult(