myte 0.0.13 → 0.0.15

package/README.md

@@ -8,6 +8,8 @@ Use one of these flows:
 
 - Local dependency in your project:
   - `npm install myte`
+  - then run `npx myte ai "Explain this repository"`
+  - then run `npx myte ai "Return a JSON object with risks and next_steps" --json-response`
   - then run `npx myte config --json`
   - then run `npx myte bootstrap`
   - then run `npx myte run-qaqc --mission-ids M001 --wait --sync`
@@ -24,6 +26,7 @@ Use one of these flows:
   - or `npm exec myte -- query "What changed in logging?" --with-diff`
 - Global install:
   - `npm i -g myte`
+  - then run `myte ai "Explain this repository"`
   - then run `myte bootstrap`
   - then run `myte run-qaqc --mission-ids M001 --wait --sync`
   - then run `myte sync-qaqc`
@@ -37,6 +40,7 @@ Use one of these flows:
   - then run `myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
   - then run `myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
 - No install:
+  - `npx myte@latest ai "Explain this repository"`
   - `npx myte@latest bootstrap`
   - `npx myte@latest run-qaqc --mission-ids M001 --wait --sync`
   - `npx myte@latest sync-qaqc`
@@ -56,12 +60,14 @@ Important:
 - `npm install myte` gives the user everything needed locally.
 - The normal local command is `npx myte ...` or `npm exec myte -- ...`.
 - Bare `myte ...` only works after `npm i -g myte`.
+- `myte ai` uses `MYTEAI_API_KEY` and the `api.myte.ai` gateway.
 
 ## Requirements
 
 - Node `18+`
 - macOS, Linux, and Windows are supported
 - `git` available in `PATH` for `--with-diff`
+- `MYTEAI_API_KEY=<inference_api_key>` available in your shell or in a `.env` for `myte ai`
 - `MYTE_API_KEY=<project_api_key>` available in your shell or in a `.env`
 - the CLI searches for `.env` in the current folder and then up parent directories
 - For deterministic diff capture, run from:
@@ -78,6 +84,17 @@ Run this first when onboarding on a new machine:
 - or `npm exec myte -- config --json`
 - or `npx myte@latest config --json`
 
+## Myte AI gateway
+
+Use `myte ai` as the thin inference gateway client. The npm package does not ship models or backend internals; it sends your request to `api.myte.ai` with `MYTEAI_API_KEY`.
+
+Examples:
+
+- `npx myte ai "Explain what this repository does"`
+- `npx myte ai "Return a JSON object with risks and next_steps" --json-response`
+- `npm exec myte -- ai "Summarize this file"`
+- `myte ai "Return clean JSON only" --json-response`
+
 It confirms:
 - the API key resolves to the expected project
 - which repo names the project is configured with
@@ -116,22 +133,23 @@ Useful forms:
 
 Run this from any workspace with a valid project key:
 
-- `npx myte run-qaqc --mission-ids M001,M002 --wait --sync`
-- or `npm exec myte -- run-qaqc --mission-ids M001,M002 --wait --sync`
-- or `myte run-qaqc --mission-ids M001,M002 --wait --sync`
+- `npx myte run-qaqc --mission-ids "M001,M002" --wait --sync`
+- or `npm exec myte -- run-qaqc --mission-ids "M001,M002" --wait --sync`
+- or `myte run-qaqc --mission-ids "M001,M002" --wait --sync`
 
 What it does:
 - queues QAQC for up to 10 explicit mission ids through the project-key API surface
 - returns a `batch_id` immediately
 - uses `--wait` to poll the batch until it reaches a terminal state
 - uses `--sync` to refresh `MyteCommandCenter/data/qaqc.yml` after a completed batch
+- on PowerShell, quote comma-separated multi-id values: `--mission-ids "M001,M002"`
 - runs through the dedicated `project_api_qaqc` queue inside the existing Celery service, with a global budget of `20` dispatch starts/minute and `20` live jobs
 - a saturated `run-qaqc --wait` batch can take roughly `5-10` minutes before sync has final data to pull
 
 Useful forms:
 - `npx myte run-qaqc --mission-ids M001`
-- `npx myte run-qaqc --mission-ids M001,M002 --wait`
-- `npx myte run-qaqc --mission-ids M001,M002 --wait --sync --json`
+- `npx myte run-qaqc --mission-ids "M001,M002" --wait`
+- `npx myte run-qaqc --mission-ids "M001,M002" --wait --sync --json`
 
 ## Sync active mission QAQC context
 
@@ -365,6 +383,7 @@ Notes:
 - `--subject` is required.
 - The body can come from `--body-markdown`, `--body-file`, a positional file path, positional inline text, or `--stdin`.
 - `target_contact_ids` are optional. If omitted, the backend selects the linked primary client contact when available.
+- If no linked client contacts exist, the backend falls back to the project owner so internal projects can still draft/send updates through the same flow.
 - Use `--target-contact-id <id>` multiple times or `--target-contact-ids <id1,id2>`.
 - The CLI prints the returned draft summary, including the draft id, status, recipients, and snippet.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "myte",
-  "version": "0.0.13",
-  "description": "Myte developer CLI (Project Assistant + deterministic diffs).",
+  "version": "0.0.15",
+  "description": "Myte developer CLI (Project Assistant + Myte AI gateway).",
   "type": "commonjs",
   "license": "MIT",
   "files": [
@@ -16,6 +16,6 @@
     "node": ">=18"
   },
   "dependencies": {
-    "@mytegroupinc/myte-core": "0.0.13"
+    "@mytegroupinc/myte-core": "0.0.15"
   }
 }