hey-axi 0.3.2 → 0.3.3

package/README.md

@@ -4,7 +4,7 @@
 
 An agent-friendly wrapper for [HEY CLI](https://github.com/basecamp/hey-cli) (`hey`), Basecamp's command line for HEY email, calendars, todos, habits, time tracking and journals.
 
-hey-axi runs `hey`, asks for its JSON response envelope, and prints it as [TOON](https://github.com/toon-format/toon). It follows the [AXI](https://axi.md) principles: a live home view, minimal default fields, truncated long text, definitive empty states, and unknown flags rejected up front. On our synthetic benchmark that's **~89% fewer tokens than `hey --json`** ([docs/benchmarks.md](docs/benchmarks.md)). It also adds a few safety rails. It covers **every command in HEY CLI v1.7.0 plus the commands on HEY's unreleased `main` branch as of 2026-10-06** (commit [`9dfe00f`](https://github.com/basecamp/hey-cli/commit/9dfe00fb6594a4da5272b8ed0692f494229f14d2)): 155 runnable command paths, including the `login`/`logout` aliases, plus the `box <id>`-style shortcuts. It routes from a snapshot of HEY's own `hey commands --json` catalog. The main-only additions (`contact deliver`, `event delete --occurrence/--apply-to`) need a HEY built from main, or the next HEY release; with HEY v1.7.0 they fail with `kind: hey_outdated`. See [CHANGELOG.md](CHANGELOG.md) for what changed in each release.
+hey-axi runs `hey`, asks for its JSON response envelope, and prints it as [TOON](https://github.com/toon-format/toon). It follows the [AXI](https://axi.md) principles: a live home view, minimal default fields, truncated long text, definitive empty states, and unknown flags rejected up front. On our synthetic benchmark that's **~89% fewer tokens than `hey --json`** ([docs/benchmarks.md](docs/benchmarks.md)). It also adds a few safety rails. It covers **every command in HEY CLI v1.8.0** (released 2026-10-09; commit `732568e`): 156 runnable command paths, including the `login`/`logout` aliases, plus the `box <id>`-style shortcuts. It routes from a snapshot of HEY's own `hey commands --json` catalog. Commands added since v1.7.0 (`contact deliver`, `event delete --occurrence/--apply-to`, `screener clear`, `thread update`) need HEY v1.8.0 or newer; with an older HEY they fail with `kind: hey_outdated`. See [CHANGELOG.md](CHANGELOG.md) for what changed in each release.
 
 ## Install
 
@@ -34,6 +34,7 @@ hey-axi thread read 123                    # bodies cut at 1000 chars with "(tru
 hey-axi thread read 123 --full             # HEY's complete, untouched result
 hey-axi box view imbox --fields id,subject,creator.email_address   # choose columns (--fields all = every field)
 hey-axi thread read 123 --json             # the same shaped output as compact JSON
+hey-axi thread update 123 --name "Kitchen renovation quotes"   # rename a thread (nothing is emailed)
 hey-axi box view imbox --quiet             # drop HEY's summary/notice/breadcrumbs; keep data, count and hints
 hey-axi reply 123 --message - < note.txt   # message body from stdin (saved as a draft)
 hey-axi setup scope --label Acme           # per-directory home view (.hey-axi.json)
@@ -73,10 +74,10 @@ hey-axi move --help                        # usage, flags, examples, notes (no H
   - `forward`, `draft send` and `bulk-reply send` have no draft mode in HEY, so they're refused (exit 2) with the safe alternative (`reply … --to`, `draft show`, `bulk-reply preview`).
   - If you pass `--draft` or `--dry-run` yourself, hey-axi adds and marks nothing.
   - With `--allow-send`, a send HEY confirms is marked `sent: true` (and names the delivered message's `id`/`topic_id` when HEY reports them, as HEY main does). If HEY holds it for Undo Send (`delayed: true`), a `held` line says it hasn't gone out yet and the thread won't show it until it does.
-  - If HEY refuses to send and keeps the message as a draft (HEY main's `not_delivered`, usually the sending limit), the result is an error with `kind: not_delivered`, `sent: false` and the draft id, and says not to repeat the send. HEY v1.7.0 reports such a send as sent, so it can't be detected there.
-  - Recipients HEY would silently drop (no domain or top-level domain, like `bob` or `bob@example`) are refused (exit 2, `sent: false`) before HEY runs, for `compose`, `reply`, `forward` and `draft edit`. HEY main's own "not a valid email address" refusal is reported the same way.
+  - If HEY refuses to send and keeps the message as a draft (HEY v1.8.0's `not_delivered`, usually the sending limit), the result is an error with `kind: not_delivered`, `sent: false` and the draft id, and says not to repeat the send. HEY v1.7.0 reports such a send as sent, so it can't be detected there.
+  - Recipients HEY would silently drop (no domain or top-level domain, like `bob` or `bob@example`) are refused (exit 2, `sent: false`) before HEY runs, for `compose`, `reply`, `forward` and `draft edit`. HEY v1.8.0's own "not a valid email address" refusal is reported the same way.
 - **Credentials stay out of agent context.** `auth token` needs `--allow-secret` or `HEY_AXI_ALLOW_SECRETS=1`.
-- **Destructive commands need an opt-in.** `screener clear` (HEY main) moves everything waiting in the Screener to Trash, for every sender, and HEY asks for no confirmation. hey-axi refuses it (exit 2, HEY isn't run, nothing changes) unless you pass `--allow-destructive` or set `HEY_AXI_ALLOW_DESTRUCTIVE=1`. The refusal says what it would do and suggests `screener list` and per-sender `screener deny` first.
+- **Destructive commands need an opt-in.** `screener clear` (HEY v1.8.0) moves everything waiting in the Screener to Trash, for every sender, and HEY asks for no confirmation. hey-axi refuses it (exit 2, HEY isn't run, nothing changes) unless you pass `--allow-destructive` or set `HEY_AXI_ALLOW_DESTRUCTIVE=1`. The refusal says what it would do and suggests `screener list` and per-sender `screener deny` first.
 - **Content-first.** `compose`, `reply`, `draft edit`, `journal write`, `contact note set` and `bulk-reply send` must be given their content (`--message`, `--message -` for stdin, or a positional) and are refused (exit 2) otherwise, so HEY never opens an editor.
 - hey-axi's own flags (`--allow-send`, `--allow-secret`, `--allow-destructive`, `--interactive`, `--fields`, `--full`) are never forwarded to HEY. Switches take no value: `--draft=false` or `--allow-send=false` is refused (exit 2) rather than guessed at.
 
@@ -124,7 +125,7 @@ See [docs/listing.md](docs/listing.md) for how hey-axi gets listed on skills.sh
 
 ## Keeping up with HEY releases
 
-`src/manifest.json` is a snapshot of `hey commands --json` plus usage parsed from `hey <command> --help`. The current snapshot was built from HEY's unreleased `main` branch (commit `9dfe00f`, 2026-10-06), so its `hey_version` reads `1.7.0+main.9dfe00f`. To regenerate it:
+`src/manifest.json` is a snapshot of `hey commands --json` plus usage parsed from `hey <command> --help`. The current snapshot was built from basecamp/hey-cli `main` at the v1.8.0 release commit (`732568e`, 2026-10-09), so its `hey_version` reads `1.8.0`. To regenerate it:
 
 ```bash
 npm run refresh-manifest     # from whichever `hey` you have installed (runs only `hey version`, `hey commands`, `hey <command> --help`)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hey-axi",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "Agent-ergonomic AXI wrapper for Basecamp's HEY CLI: TOON output, send-to-draft safety, and a shareable agent skill",
   "keywords": [
     "axi",

package/skills/hey-axi/SKILL.md

@@ -2,7 +2,7 @@
 name: hey-axi
 description: Read, triage and draft HEY email (and HEY calendars, todos, habits, journal, time tracking) from the shell through hey-axi, a token-efficient TOON wrapper around Basecamp's HEY CLI that saves outgoing mail as drafts unless sending is explicitly allowed. Use when the user asks you to check, search, read, summarize, sort, label, screen, archive or reply to their HEY (hey.com) email, watch for new mail, or manage HEY todos, events, habits, journal entries or time tracks.
 license: MIT
-compatibility: Requires Node.js 20+ (commands run as `npx -y hey-axi`), the HEY CLI (`hey`, v1.7.0 or newer; `contact deliver` and `event delete --occurrence` need a HEY built from basecamp/hey-cli main until HEY's next release) signed in to a HEY account, and network access to app.hey.com.
+compatibility: Requires Node.js 20+ (commands run as `npx -y hey-axi`), the HEY CLI (`hey`, v1.7.0 or newer; `contact deliver`, `event delete --occurrence`, `screener clear` and `thread update` need v1.8.0 or newer) signed in to a HEY account, and network access to app.hey.com.
 metadata:
   author: TangentialSolutions
   repository: https://github.com/TangentialSolutions/hey-axi
@@ -66,7 +66,7 @@ npx -y hey-axi trash <id>...          npx -y hey-axi spam <id>...      npx -y he
 
 `screener clear` moves **everything** waiting in the Screener to Trash, for every sender, so hey-axi refuses it (exit 2, nothing changes) unless `--allow-destructive` is passed. Prefer `screener deny <clearance-id>` per sender. Only add `--allow-destructive` after the user has explicitly confirmed clearing the whole Screener.
 
-`npx -y hey-axi contact deliver <contact-id> --to imbox|feed|papertrail|screened-out` chooses where a contact's future mail arrives (a contact id from `contact list`). `npx -y hey-axi event delete <series-id> --occurrence <occurrence_id> --apply-to current|future` deletes one day (or that day onward) of a repeating event; the occurrence_id comes from `event day`/`event week`.
+`npx -y hey-axi contact deliver <contact-id> --to imbox|feed|papertrail|screened-out` chooses where a contact's future mail arrives (a contact id from `contact list`). `npx -y hey-axi event delete <series-id> --occurrence <occurrence_id> --apply-to current|future` deletes one day (or that day onward) of a repeating event; the occurrence_id comes from `event day`/`event week`. `npx -y hey-axi thread update <topic_id> --name "New subject"` renames a thread for everyone in the account; nothing is emailed (a collection's discussion thread takes its collection's name: use `collection update`).
 
 Mutations are idempotent: when the desired state already holds (already seen, already deleted), the answer is `noop: true` with exit 0, not an error.
 

package/skills/hey-axi/references/commands.md

@@ -1,8 +1,8 @@
 # hey-axi command reference
 
-<!-- Generated by scripts/gen-skill.js from src/manifest.json (hey 1.7.0+main.9dfe00f). Do not edit by hand. -->
+<!-- Generated by scripts/gen-skill.js from src/manifest.json (hey 1.8.0). Do not edit by hand. -->
 
-Every command from HEY CLI v1.7.0 plus the commands on HEY main as of 2026-10-06 (commit 9dfe00f, unreleased): 155 runnable paths, including the `login`/`logout` aliases and shortcut forms such as `box <name>`. Run each as `npx -y hey-axi <command> [args] [flags]` (just `hey-axi …` when it is installed globally).
+Every command from HEY CLI v1.8.0: 156 runnable paths, including the `login`/`logout` aliases and shortcut forms such as `box <name>`. Run each as `npx -y hey-axi <command> [args] [flags]` (just `hey-axi …` when it is installed globally).
 `npx -y hey-axi <command> --help` shows usage, arguments, every flag with its default, 2-3 examples and notes, offline.
 Flags every command accepts: `--account <id|all>`, `--json`, `--quiet`, `--fields <a,b|all>`, `--full`, `--ids-only`, `--count`, `--markdown`, `--html`, `--styled`, `--jq <expr>`. Unknown commands, flags and arguments, flags without a value and values of the wrong type are rejected before HEY runs (exit 2).
 
@@ -128,6 +128,7 @@ Flags every command accepts: `--account <id|all>`, `--json`, `--quiet`, `--field
 | `spam` | Mark email threads as spam |  |  |
 | `stop-ignoring` | Stop ignoring email threads |  |  |
 | `thread read` | Read a thread | `--allow-partial` | fields: id, at, from, email, to, cc, body |
+| `thread update` | Rename a thread | `--name <v>` |  |
 | `timetrack categories` | List time track categories |  | fields: id, title |
 | `timetrack category create` | Create a time track category |  |  |
 | `timetrack category delete` | Delete a time track category |  |  |

package/src/errors.js

@@ -173,7 +173,7 @@ export function translateFailure(result, context = {}) {
     if (usage) failure.kind = "usage";
     // hey-axi checked the command and flags against its catalog before HEY ran, so HEY
     // not knowing one means the installed HEY is older than that catalog (for example
-    // v1.7.0 and `contact deliver`, which is only on HEY's main branch so far).
+    // v1.7.0 and `contact deliver` or `thread update`, which arrived in v1.8.0).
     const unknown = usage && path && failure.error.match(/^unknown (flag|shorthand flag|command)[:\s]+["']?([^"'\s]+)["']?/i);
     if (unknown) {
       const what = /command/i.test(unknown[1]) ? `the command \`${path}\`` : `${unknown[2]} for \`${path}\``;

package/src/manifest.json

@@ -1,8 +1,8 @@
 {
- "source": "hey commands --json + hey <command> --help (basecamp/hey-cli main at 9dfe00f, 2026-10-06; unreleased, built from source)",
- "hey_version": "1.7.0+main.9dfe00f",
- "hey_commit": "9dfe00fb6594a4da5272b8ed0692f494229f14d2",
- "hey_commit_date": "2026-10-06",
+ "source": "hey commands --json + hey <command> --help (basecamp/hey-cli v1.8.0)",
+ "hey_version": "1.8.0",
+ "hey_commit": "732568eb9b09b44471e9fb889ba22308f87b4f95",
+ "hey_commit_date": "2026-10-09",
  "commands": [
   {
    "name": "account",
@@ -3279,8 +3279,8 @@
   {
    "name": "thread",
    "path": "thread",
-   "short": "Read email threads",
-   "notes": "Subcommands: read. Thread IDs come from hey box view. Use the same ID with hey reply or hey forward.",
+   "short": "Read and rename email threads",
+   "notes": "Subcommands: read, update. Thread IDs come from hey box view. Use the same ID with hey reply or hey forward.",
    "subcommands": [
     {
      "name": "read",
@@ -3302,6 +3302,28 @@
       "hey thread read 12345 --json",
       "hey thread read 12345 --markdown"
      ]
+    },
+    {
+     "name": "update",
+     "path": "thread update",
+     "short": "Rename a thread",
+     "notes": "Renames a thread (topic) by its topic_id, as HEY's web app does; nothing is emailed. --name is required, trimmed, and at most 1024 bytes. A thread merged into another is not renamed and the command fails; rename the thread it was merged into instead. A collection's discussion thread shows its collection's name whatever this sets: use hey collection update for it.",
+     "flags": [
+      {
+       "name": "name",
+       "value": true,
+       "type": "string",
+       "desc": "New thread name (required)",
+       "default": ""
+      }
+     ],
+     "synopsis": [
+      "hey thread update <thread-id> [flags]"
+     ],
+     "examples": [
+      "hey thread update 12345 --name \"Kitchen renovation quotes\"",
+      "hey thread rename 12345 --name \"Flights to Lisbon, May 14\""
+     ]
     }
    ],
    "synopsis": [

package/src/send.js

@@ -1,7 +1,7 @@
 // Reading what HEY says about outgoing mail.
 //
-// HEY CLI v1.7.0 answers a send with a summary only. HEY's main branch (unreleased as of
-// 2026-10-06, commit 9dfe00f) also:
+// HEY CLI v1.7.0 answers a send with a summary only. HEY v1.8.0 (first on HEY main after
+// v1.7.0) also:
 //   - names what went out: data.id (the message), data.topic_id (its thread), subject,
 //     and delayed (true while Undo Send holds it back; the thread doesn't show it yet)
 //   - fails a send HEY refused (usually the sending limit) with code not_delivered (exit 7),

package/src/version.js

@@ -1,3 +1,3 @@
 // Leaf module: no imports, so `hey-axi --version` answers before the CLI graph loads.
 // test/version.test.js keeps this in sync with package.json.
-export const VERSION = "0.3.2";
+export const VERSION = "0.3.3";