skydive-cli 0.3.0 → 0.4.0-beta.1033

package/CHANGELOG.md

@@ -7,6 +7,33 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.4.0] - 2026-08-07
+
+### Added
+
+- `skydive chat` works with API key auth: an API key alone now opens the chat TUI (and headless `chat -p`) without a browser login, using the key's pinned workspace.
+- `skydive config` command to view and set the safe, hand-editable CLI preferences (`shareMachineDefault`, `updateCheck`) without opening `config.json`. `config`/`config list` shows each key, its effective value, and whether it comes from the file or the built-in default; `config get`/`set`/`unset` read and change one key; `config path` prints the config file location. It only ever touches those preference keys, never credentials or flow-managed state.
+- Billing-blocked sends and runs now surface the server-authored recovery
+  guidance from the typed billing outcome. The chat TUI renders it as a
+  warning-toned system-notice row — live when a send is refused or a run is
+  stopped at the billing boundary, and again when reopening a conversation
+  that holds a persisted billing notice — instead of a generic error.
+  Headless `chat -p` and `messages get` print the guidance (state, recovery
+  step, and manage-billing URL) on stderr, keep any partial output already
+  streamed on stdout, and exit with code `5` (distinct from the generic `1`)
+  so scripted callers can tell a billing pause from a failure.
+- Syntax highlighting for 14 more languages in the chat transcript and file/review panes (python, bash, go, rust, c, cpp, java, ruby, css, html, json, yaml, and more) — previously only JavaScript/TypeScript rendered colored.
+
+### Changed
+
+- `skydive agent list` lists the full agent roster by default instead of a truncated page.
+
+### Fixed
+
+- Long multi-line bash tool-call commands (e.g. heredocs) are clamped with a `+N more · click to expand` tail instead of dumping their whole body into the scrollback.
+- Tool error output is clipped the same way as ok output, so a failing command no longer floods the transcript.
+- The TUI toast overlay has an opaque background instead of letting the transcript bleed through.
+
 ## [0.3.0] - 2026-08-04
 
 ### Added

package/README.md

@@ -132,6 +132,9 @@ skydive portal grant --agent <id|name>
 skydive portal revoke --agent <id|name>
 skydive portal status
 
+skydive config                  # list CLI preferences
+skydive config set updateCheck false
+
 skydive completion install      # set up TAB completion for your shell
 ```
 
@@ -313,6 +316,18 @@ messageId, text }` instead of streaming the raw text.
   the full reply whether it's still streaming or already finished. Message ids
   are the handle this API works in; run ids stay server-side.
 
+- **Exit codes.** `0` success, `1` any failure, `5` billing-blocked: the
+  workspace is paused by billing — either the send was refused before anything
+  ran, or the run was stopped at the billing boundary (anything already
+  streamed stays on stdout). The guidance and recovery URL print on stderr so
+  a scripted caller (an agent driving `-p`) can relay them to a human.
+  `messages get` uses the same codes. Treat these values as frozen.
+
+  With `--json`, a billing block still exits `5` but first emits a structured
+  result on stdout: `{ billingBlocked: { code, message }, text, messageId }` —
+  `text` is whatever streamed before the block and `messageId` is the handle
+  to re-fetch the full reply with `messages get` after billing recovers.
+
 It defaults to the production API (`https://api.skydive.com`). For local
 dev, point it at your stack:
 
@@ -433,9 +448,20 @@ Persistent state lives in a per-user JSON file managed by
 `SKYDIVE_CONFIG_NAME`). Most keys are written by flows — `auth login`, the
 device-login flow, the in-TUI theme picker — but the file is plain JSON and
 read fresh on every invocation, so preference keys can be set by editing it
-directly. There is deliberately no `skydive config` command.
+directly.
+
+The safe, hand-editable preference keys are also managed by `skydive config`,
+which only ever touches those keys — never credentials or flow-managed state:
+
+```sh
+skydive config                      # list preferences, values, and source
+skydive config get updateCheck      # print the effective value of one key
+skydive config set updateCheck false
+skydive config unset updateCheck    # revert to the built-in default
+skydive config path                 # print the config.json location
+```
 
-Hand-editable keys:
+Editable keys:
 
 | Key                   | Type    | Effect                                                                                                                                                                                                                          |
 | --------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

package/dist/js/billing-blocked-CwfG1BTR.mjs

@@ -0,0 +1,71 @@
+#!/usr/bin/env node
+import { z } from "zod";
+
+//#region src/chat/api/billing-blocked.ts
+const billingBlockedOutcomeSchema = z.object({
+	code: z.literal("billing_blocked"),
+	message: z.string().min(1)
+});
+const billingBlockedSendResponseSchema = z.object({
+	error: z.literal("billing_blocked"),
+	outcome: billingBlockedOutcomeSchema
+});
+/**
+* The typed billing outcome out of a failed send response, or null when the
+* failure isn't a billing block. HTTP 402 + the discriminated body above is
+* the whole check; anything else (a non-billing 402, an edge HTML page) is
+* someone else's error and keeps its existing handling.
+*/
+function billingBlockedOutcomeFromSendResponse({ status, body }) {
+	if (status !== 402) return null;
+	let parsed;
+	try {
+		parsed = JSON.parse(body);
+	} catch (_error) {
+		return null;
+	}
+	const response = billingBlockedSendResponseSchema.safeParse(parsed);
+	return response.success ? response.data.outcome : null;
+}
+/**
+* A billing block surfaced on the headless path (`chat -p`, `messages get`).
+* Distinct from a plain Error so the command layer can exit with
+* {@link BILLING_BLOCKED_EXIT_CODE}; `message` is the server-authored
+* guidance verbatim (state, recovery step, and manage-billing URL). The
+* context preserves what the run produced before the block so `--json`
+* callers get a structured result instead of losing the buffered output.
+*/
+var BillingBlockedError = class extends Error {
+	constructor(outcome, context) {
+		super(outcome.message);
+		this.outcome = outcome;
+		this.context = context;
+		this.name = "BillingBlockedError";
+	}
+};
+/**
+* The `--json` envelope for a billing-blocked headless invocation, emitted on
+* stdout before exiting with {@link BILLING_BLOCKED_EXIT_CODE}. Additive
+* contract: scripted callers get the server guidance, whatever text streamed
+* before the block, and the message id to re-fetch after recovery.
+*/
+function billingBlockedJsonResult(error, fallbackMessageId) {
+	return {
+		billingBlocked: {
+			code: error.outcome.code,
+			message: error.outcome.message
+		},
+		text: error.context.partialText ?? "",
+		messageId: error.context.messageId ?? fallbackMessageId
+	};
+}
+/**
+* Headless exit code for a billing-blocked send or run — distinct from the
+* generic `1` so scripted callers (Claude Code / Codex driving `chat -p`) can
+* tell "the workspace is paused by billing, relay the recovery URL" from an
+* ordinary failure. Documented in the CLI README; treat as frozen.
+*/
+const BILLING_BLOCKED_EXIT_CODE = 5;
+
+//#endregion
+export { billingBlockedOutcomeSchema as a, billingBlockedOutcomeFromSendResponse as i, BillingBlockedError as n, billingBlockedJsonResult as r, BILLING_BLOCKED_EXIT_CODE as t };

package/dist/js/billing-blocked-euid6MN9.mjs

@@ -0,0 +1,4 @@
+#!/usr/bin/env node
+import { a as billingBlockedOutcomeSchema, i as billingBlockedOutcomeFromSendResponse, n as BillingBlockedError, r as billingBlockedJsonResult, t as BILLING_BLOCKED_EXIT_CODE } from "./billing-blocked-CwfG1BTR.mjs";
+
+export { BILLING_BLOCKED_EXIT_CODE, BillingBlockedError, billingBlockedJsonResult };