@xano/cli 1.0.6-beta.6 → 1.0.6-beta.8

package/README.md

@@ -56,20 +56,20 @@ Notes:
 - **`--per_page` is only offered where the endpoint accepts it.** Static-host endpoints hardcode 100 items per page server-side, so those commands take `--page` alone. `xano static_host list --per_page 10` previously parsed but did nothing; it is now rejected rather than silently ignored.
 - **All paged commands default `--per_page` to 50.** The test-list commands previously requested 10000 internally so nothing was ever cut off; now that the footer and the JSON envelope both report position, a page that stops at 50 is visible rather than silent. Raise it (up to 10000) when you want everything in one call.
 - **The last group has no CLI paging.** Those endpoints page server-side but return a plain array with no page or total metadata, so the CLI cannot tell you where you are. Rather than show a page number with no context — or infer "more available" from a full page, which is wrong exactly when the result count is a multiple of the page size — these commands are left as-is. **They return at most 25–50 items** (50 for tenants and ephemerals, 25 for releases, platforms, and tenant backups). If you have more than that, query the Metadata API directly until those endpoints return paging metadata.
-- **`--output json` returns an envelope, not a bare array.** Every list command emits `{count, items, ...}`, with `page`, `per_page`, `next_page`, `prev_page`, and `total` included only when the endpoint actually reports them. This is a **breaking change** for scripts that parsed the previous bare array — read `.items` instead.
+- **`--output json` returns an envelope, not a bare array.** Every list command emits `{items, ...}` using the Metadata API's own field names — `curPage`, `nextPage`, `prevPage`, `itemsTotal` — each included only when the endpoint actually reports it. `perPage` is the one field the CLI adds, since the API never echoes it back and it is otherwise invisible at its default. This is a **breaking change** for scripts that parsed the previous bare array — read `.items` instead.
 
   ```jsonc
   // xano function list -o json
   {
-    "count": 50,
-    "page": 2,
-    "per_page": 50,
-    "next_page": 3,     // absent on the last page — never inferred
+    "curPage": 2,
+    "perPage": 50,      // injected by the CLI; everything else mirrors the API
+    "nextPage": 3,      // absent on the last page — never inferred
+    "prevPage": 1,
     "items": [ /* ... */ ]
   }
   ```
 
-  The point of the envelope is that a script gets the same honest stop condition a human gets from the footer. Without it the only signal available is `items.length < per_page`, which is wrong exactly when the result count is a multiple of the page size. Absence of `next_page` means the server said there is no next page; it is never omitted as a guess.
+  The point of the envelope is that a script gets the same honest stop condition a human gets from the footer, in the same shape the raw Metadata API returns. Without it the only signal available is `items.length < perPage`, which is wrong exactly when the result count is a multiple of the page size. Absence of `nextPage` means the server said there is no next page; it is never omitted as a guess.
 
 ### Authentication
 

package/dist/commands/hatch/index.d.ts

@@ -0,0 +1,130 @@
+/**
+ * `xano hatch "<prompt>"` — start a Hatch build and watch it to its ending.
+ *
+ * Extends oclif's `Command` rather than `BaseCommand` (see the plan's KTD5):
+ * `BaseCommand` exists to resolve a Xano profile, and Hatch's API takes no
+ * credentials, so inheriting it would put a `-p/--profile` flag on the command
+ * that changes nothing — and would break the "works on a fresh install with no
+ * credentials file" property outright. What that gives up is `verboseFetch`
+ * (whose User-Agent is reproduced by {@link HatchClient}) and the update-check
+ * notice.
+ *
+ * Everything below the oclif class is a plain function over injected
+ * dependencies, so the whole run — the ordering, the exit codes, the interrupt,
+ * the snapshot backstop — is testable without a socket, a TTY, or oclif.
+ */
+import { Command } from '@oclif/core';
+import type { Activity, CreateSessionResponse, SessionSnapshot, TerminalOutcome } from '../../utils/hatch-contract.js';
+import type { SseEvent } from '../../utils/sse.js';
+/** Hatch's own wall-clock budget for a single build. */
+export declare const HATCH_BUILD_BUDGET_MS: number;
+/**
+ * How far past that budget the client keeps watching.
+ *
+ * The server's expiry sweep is what produces the `expired` terminal activity,
+ * and it runs on its own schedule; giving it a minute of slack means the
+ * server's own answer normally wins the race and the cap stays what it is
+ * meant to be — a backstop against a connection that died in a way that looked
+ * like it was still alive, not the usual way a build ends.
+ */
+export declare const WATCH_CAP_MARGIN_MS = 60000;
+/** The hard ceiling on a watch. Hitting it resolves the outcome from the snapshot. */
+export declare const WATCH_CAP_MS: number;
+/**
+ * What the run ended as. A superset of the contract's terminal outcomes:
+ * `started` is `--no-wait`, and `interrupted` is Ctrl-C — neither is a build
+ * ending, but a scripted caller still has to get one object with a verdict in
+ * it rather than an empty stream.
+ */
+export type HatchRunOutcome = 'interrupted' | 'started' | TerminalOutcome;
+/** The single object `-o json` puts on stdout. */
+export interface HatchRunSummary {
+    message?: string;
+    outcome: HatchRunOutcome;
+    sessionId: string;
+    siteUrl?: string;
+    watchUrl?: string;
+}
+export interface HatchRunResult {
+    exitCode: number;
+    summary: HatchRunSummary;
+}
+/** The slice of {@link HatchClient} the run needs, so tests can stub it. */
+export interface HatchSessionApi {
+    createSession(): Promise<CreateSessionResponse>;
+    getSnapshot(sessionId: string): Promise<SessionSnapshot>;
+    openStream(sessionId: string, lastEventId?: number | string): Promise<Response>;
+    submitPrompt(sessionId: string, prompt: string): Promise<void>;
+}
+/**
+ * Two sinks, not one: stdout carries the result and stderr carries the
+ * progress. The run decides which is which — under `-o json` every human line
+ * goes to `err` so stdout holds exactly one object and the run pipes into `jq`.
+ */
+export interface HatchIo {
+    err(line: string): void;
+    out(line: string): void;
+}
+/** The spinner, abstracted so the run never touches `ux` (or a TTY) in tests. */
+export interface HatchSpinner {
+    start(action: string, status?: string): void;
+    stop(message?: string): void;
+    update(status: string): void;
+}
+export interface RunHatchOptions {
+    /** Spinner on. Gated by the caller exactly as `BaseCommand.waitForBuild()` does. */
+    animate: boolean;
+    /** Overrides {@link WATCH_CAP_MS}; exists for tests. */
+    capMs?: number;
+    client: HatchSessionApi;
+    /** Aborted by the `SIGINT` handler. */
+    interrupt?: AbortSignal;
+    io: HatchIo;
+    /** `-o json`: one object on stdout, everything else on stderr. */
+    json: boolean;
+    prompt: string;
+    /** Passed through to {@link readSseWithReconnect}; exists for tests. */
+    reconnect?: {
+        backoffMs?: (attempt: number) => number;
+        maxAttempts?: number;
+        sleep?: (ms: number) => Promise<void>;
+    };
+    spinner?: HatchSpinner;
+    verbose: boolean;
+    /** False under `--no-wait`: print the link, do not open the stream. */
+    wait: boolean;
+}
+/**
+ * Rejects a prompt that is empty or only whitespace, before anything is sent.
+ *
+ * Note what is deliberately *not* here: an upper bound. Hatch truncates at 5000
+ * characters, and a second limit in the client is a second number to keep in
+ * step with the first. The prompt goes out as given.
+ */
+export declare function validatePrompt(prompt: string): string;
+/** An activity off an SSE frame, or undefined if the frame carried no usable JSON. */
+export declare function parseActivity(event: SseEvent): Activity | undefined;
+/** Printed on Ctrl-C. The build is server-side; the user only needs telling. */
+export declare function interruptBlock(watchUrl?: string): string[];
+/**
+ * Run a build end to end.
+ *
+ * The ordering is load-bearing: the watch link is printed after session-create
+ * and *before* the stream is opened, so a stream that never opens still leaves
+ * the user with a link to a build that is running regardless.
+ */
+export declare function runHatch(options: RunHatchOptions): Promise<HatchRunResult>;
+export default class Hatch extends Command {
+    static args: {
+        prompt: import("@oclif/core/interfaces").Arg<string, Record<string, unknown>>;
+    };
+    static description: string;
+    static examples: string[];
+    static flags: {
+        api: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        'no-wait': import("@oclif/core/interfaces").BooleanFlag<boolean>;
+        output: import("@oclif/core/interfaces").OptionFlag<string, import("@oclif/core/interfaces").CustomOptions>;
+        verbose: import("@oclif/core/interfaces").BooleanFlag<boolean>;
+    };
+    run(): Promise<void>;
+}

package/dist/commands/hatch/index.js

@@ -0,0 +1,386 @@
+/* eslint-disable n/no-unsupported-features/node-builtins -- Response/ReadableStream/AbortSignal are stable on the Node 20.12 floor this package targets; the rule's support data is stale, and src/utils/sse.ts and src/utils/hatch-client.ts hit the same false positives */
+/**
+ * `xano hatch "<prompt>"` — start a Hatch build and watch it to its ending.
+ *
+ * Extends oclif's `Command` rather than `BaseCommand` (see the plan's KTD5):
+ * `BaseCommand` exists to resolve a Xano profile, and Hatch's API takes no
+ * credentials, so inheriting it would put a `-p/--profile` flag on the command
+ * that changes nothing — and would break the "works on a fresh install with no
+ * credentials file" property outright. What that gives up is `verboseFetch`
+ * (whose User-Agent is reproduced by {@link HatchClient}) and the update-check
+ * notice.
+ *
+ * Everything below the oclif class is a plain function over injected
+ * dependencies, so the whole run — the ordering, the exit codes, the interrupt,
+ * the snapshot backstop — is testable without a socket, a TTY, or oclif.
+ */
+import { Args, Command, Flags, ux } from '@oclif/core';
+import { DEFAULT_HATCH_URL, HATCH_URL_ENV_VAR, HatchClient, outcomeFromSnapshot, resolveHatchUrl } from '../../utils/hatch-client.js';
+import { exitCodeFor, initialRenderState, openingBlock, QUEUED_STATUS, reduceActivity, reduceReconnecting, renderLines, terminalBlock, } from '../../utils/hatch-render.js';
+import { readSseWithReconnect } from '../../utils/sse.js';
+/** Hatch's own wall-clock budget for a single build. */
+export const HATCH_BUILD_BUDGET_MS = 15 * 60 * 1000;
+/**
+ * How far past that budget the client keeps watching.
+ *
+ * The server's expiry sweep is what produces the `expired` terminal activity,
+ * and it runs on its own schedule; giving it a minute of slack means the
+ * server's own answer normally wins the race and the cap stays what it is
+ * meant to be — a backstop against a connection that died in a way that looked
+ * like it was still alive, not the usual way a build ends.
+ */
+export const WATCH_CAP_MARGIN_MS = 60_000;
+/** The hard ceiling on a watch. Hitting it resolves the outcome from the snapshot. */
+export const WATCH_CAP_MS = HATCH_BUILD_BUDGET_MS + WATCH_CAP_MARGIN_MS;
+/**
+ * Rejects a prompt that is empty or only whitespace, before anything is sent.
+ *
+ * Note what is deliberately *not* here: an upper bound. Hatch truncates at 5000
+ * characters, and a second limit in the client is a second number to keep in
+ * step with the first. The prompt goes out as given.
+ */
+export function validatePrompt(prompt) {
+    if (prompt.trim() === '') {
+        throw new Error('a prompt is required: describe what you want built, e.g. xano hatch "a landing page for a bakery"');
+    }
+    return prompt;
+}
+/** An activity off an SSE frame, or undefined if the frame carried no usable JSON. */
+export function parseActivity(event) {
+    if (!event.data)
+        return undefined;
+    try {
+        const parsed = JSON.parse(event.data);
+        if (!parsed || typeof parsed !== 'object')
+            return undefined;
+        return parsed;
+    }
+    catch {
+        // A frame this client cannot read is not a reason to fail a build that is
+        // still running — the same forward-compatibility posture as an unknown kind.
+        return undefined;
+    }
+}
+/** Printed on Ctrl-C. The build is server-side; the user only needs telling. */
+export function interruptBlock(watchUrl) {
+    if (!watchUrl)
+        return ['Stopped watching. The build keeps running.'];
+    return ['Stopped watching — the build keeps running. Follow it at:', `  ${watchUrl}`];
+}
+/** Never resolves; stands in for an absent interrupt so the race is uniform. */
+function idleGate() {
+    return {
+        dispose() { },
+        promise: new Promise(() => { }),
+    };
+}
+function deadlineGate(ms) {
+    let timer;
+    const promise = new Promise((resolve) => {
+        timer = setTimeout(() => resolve({ kind: 'capped' }), ms);
+        // The cap must never be the reason a finished command lingers.
+        timer.unref?.();
+    });
+    return {
+        dispose() {
+            if (timer)
+                clearTimeout(timer);
+        },
+        promise,
+    };
+}
+function interruptGate(signal) {
+    if (!signal)
+        return idleGate();
+    let onAbort;
+    const promise = new Promise((resolve) => {
+        onAbort = () => resolve({ kind: 'interrupted' });
+        if (signal.aborted)
+            onAbort();
+        else
+            signal.addEventListener('abort', onAbort, { once: true });
+    });
+    return {
+        dispose() {
+            if (onAbort)
+                signal.removeEventListener('abort', onAbort);
+        },
+        promise,
+    };
+}
+/**
+ * The event stream, plus the two things that can end the watch before it does.
+ *
+ * A custom iterable rather than a `while` loop so the consumer is a plain
+ * `for await` — and so the three endings are one `Promise.race` in one place.
+ * When the cap or the interrupt wins, the pending `next()` is abandoned; the
+ * consumer closes the generator on its way out.
+ */
+function racingSteps(iterator, gates) {
+    return {
+        [Symbol.asyncIterator]() {
+            return {
+                async next() {
+                    const step = await Promise.race([
+                        iterator.next().then((result) => (result.done ? { kind: 'closed' } : { event: result.value, kind: 'event' })),
+                        ...gates.map((gate) => gate.promise),
+                    ]);
+                    return { done: false, value: step };
+                },
+            };
+        },
+    };
+}
+/**
+ * Run a build end to end.
+ *
+ * The ordering is load-bearing: the watch link is printed after session-create
+ * and *before* the stream is opened, so a stream that never opens still leaves
+ * the user with a link to a build that is running regardless.
+ */
+export async function runHatch(options) {
+    const { animate, client, interrupt, io, json, prompt, spinner, verbose, wait } = options;
+    validatePrompt(prompt);
+    // Progress is not result. Under `-o json` it moves to stderr rather than
+    // being buffered: a run killed by a proxy drop must not leave the session id
+    // and the link nowhere at all, and `-o json` is the mode most likely to be
+    // running unattended.
+    const progress = (line) => {
+        if (json)
+            io.err(line);
+        else
+            io.out(line);
+    };
+    const session = await client.createSession();
+    const { sessionId, watchUrl } = session;
+    for (const line of openingBlock(watchUrl))
+        progress(line);
+    await client.submitPrompt(sessionId, prompt);
+    const conclude = (outcome, exitCode, build) => {
+        const summary = {
+            ...(build?.message === undefined ? {} : { message: build.message }),
+            outcome,
+            sessionId,
+            ...(build?.siteUrl === undefined ? {} : { siteUrl: build.siteUrl }),
+            ...(watchUrl === undefined ? {} : { watchUrl }),
+        };
+        if (json)
+            io.out(JSON.stringify(summary, null, 2));
+        return { exitCode, summary };
+    };
+    if (!wait)
+        return conclude('started', 0);
+    let state = initialRenderState();
+    const emit = (result) => {
+        for (const line of renderLines(result, { animate }))
+            progress(line);
+        if (animate)
+            spinner?.update(result.status);
+        state = result.state;
+    };
+    if (animate)
+        spinner?.start('Building', QUEUED_STATUS);
+    else
+        progress(QUEUED_STATUS);
+    const iterator = readSseWithReconnect({
+        ...options.reconnect,
+        isTerminal: (event) => parseActivity(event)?.kind === 'terminal',
+        onReconnecting(attempt) {
+            emit(reduceReconnecting(state, attempt));
+        },
+        async open(lastEventId) {
+            const response = await client.openStream(sessionId, lastEventId);
+            if (!response.body)
+                throw new Error('the Hatch build stream returned an empty response body');
+            return response.body;
+        },
+    })[Symbol.asyncIterator]();
+    const gates = [deadlineGate(options.capMs ?? WATCH_CAP_MS), interruptGate(interrupt)];
+    const { done, ending, streamError } = await watchToEnding(iterator, gates, (event) => {
+        // A frame that carried no usable activity is not an ending — skip it.
+        const activity = parseActivity(event);
+        if (!activity)
+            return;
+        const result = reduceActivity(state, activity, { verbose, watchUrl });
+        if (result.done && animate)
+            spinner?.stop('');
+        emit(result);
+        return result.done;
+    });
+    if (animate && !done)
+        spinner?.stop('');
+    if (ending === 'interrupted') {
+        for (const line of interruptBlock(watchUrl))
+            progress(line);
+        return conclude('interrupted', 0);
+    }
+    // The stream closing is the fast path, not the guarantee. Anything that got
+    // here — the cap, a close with no terminal activity, a stream that could not
+    // be opened at all — asks the server what actually happened rather than
+    // assuming. One call on an exceptional path, not a poll loop.
+    let ended = done;
+    if (!ended) {
+        ended = await resolveFromSnapshot(client, sessionId, ending, streamError);
+        for (const line of terminalBlock(ended.outcome, watchUrl))
+            progress(line);
+    }
+    return conclude(ended.outcome.outcome, ended.exitCode, ended.outcome);
+}
+/**
+ * Consume the stream until something ends it: a terminal activity, the
+ * wall-clock cap, an interrupt, a close, or a throw.
+ *
+ * `handle` folds each event and returns the build's ending if that event was
+ * the one that carried it — keeping the render side of the loop out of here.
+ */
+async function watchToEnding(iterator, gates, handle) {
+    const result = { ending: 'closed' };
+    try {
+        for await (const step of racingSteps(iterator, gates)) {
+            if (step.kind !== 'event') {
+                result.ending = step.kind;
+                break;
+            }
+            const done = handle(step.event);
+            if (done) {
+                result.done = done;
+                result.ending = 'closed';
+                break;
+            }
+        }
+    }
+    catch (error) {
+        result.streamError = error;
+    }
+    finally {
+        for (const gate of gates)
+            gate.dispose();
+        // Deliberately not awaited. On the cap and interrupt paths the generator is
+        // parked on a read of a stream that is still open, and an async generator
+        // queues `return()` behind that pending `next()` — awaiting it would hang
+        // on exactly the two paths that exist to stop a hang.
+        const closing = iterator.return?.();
+        if (closing)
+            closing.catch(() => { });
+    }
+    return result;
+}
+/** Why the watch ended without a terminal activity, in the user's words. */
+function unresolvedMessage(ending, streamError) {
+    const cause = streamError instanceof Error ? ` (${streamError.message})` : '';
+    if (ending === 'capped') {
+        return `Stopped watching after ${Math.round(WATCH_CAP_MS / 60_000)} minutes and the build had not reported an ending. It may still be running.`;
+    }
+    return `The build stream ended before the build did, and the server has not reported an ending yet${cause}.`;
+}
+async function resolveFromSnapshot(client, sessionId, ending, streamError) {
+    let snapshot;
+    let snapshotError;
+    try {
+        snapshot = await client.getSnapshot(sessionId);
+    }
+    catch (error) {
+        snapshotError = error;
+    }
+    const outcome = snapshot && outcomeFromSnapshot(snapshot);
+    if (outcome)
+        return { exitCode: exitCodeFor(outcome.outcome), outcome };
+    // Still in flight, or the snapshot itself failed. Either way this is not a
+    // success and silence is not an option: fail with what is known.
+    return {
+        exitCode: 1,
+        outcome: { message: unresolvedMessage(ending, snapshotError ?? streamError), outcome: 'failed' },
+    };
+}
+export default class Hatch extends Command {
+    static args = {
+        prompt: Args.string({
+            description: 'What you want built, in plain language',
+            required: true,
+        }),
+    };
+    static description = 'Build and deploy a full-stack app from a prompt, with Hatch';
+    static examples = [
+        `$ xano hatch "a landing page for a bakery, with an order form"
+Your idea is being created, follow along for more details:
+  https://hatch.mesh0.ai/s/K7QM2XPA9RTV`,
+        `$ xano hatch "an inventory tracker" --no-wait
+(prints the follow-along link and returns immediately)`,
+        `$ xano hatch "a recipe box" -o json | jq -r .siteUrl
+(one JSON object on stdout; progress goes to stderr)`,
+        `$ xano hatch "a bakery site" --api http://localhost:8080
+(point at a local Hatch API; XANO_HATCH_URL does the same)`,
+    ];
+    static flags = {
+        // No `env:` here even though the variable is honoured. This repo's custom
+        // help class renders `[env: X]` for any flag that declares one, and oclif
+        // renders it too, so declaring it prints the hint twice. Precedence lives
+        // in `resolveHatchUrl`, which is where it was put to begin with.
+        api: Flags.string({
+            description: `Hatch base URL. Defaults to $${HATCH_URL_ENV_VAR}, then ${DEFAULT_HATCH_URL}`,
+            required: false,
+        }),
+        'no-wait': Flags.boolean({
+            default: false,
+            description: 'Print the follow-along link and exit without watching the build',
+        }),
+        output: Flags.string({
+            char: 'o',
+            default: 'summary',
+            description: 'Output format',
+            options: ['json', 'summary'],
+        }),
+        verbose: Flags.boolean({
+            default: false,
+            description: 'Print the build log lines as they arrive (disables the spinner)',
+        }),
+    };
+    async run() {
+        const { args, flags } = await this.parse(Hatch);
+        const json = flags.output === 'json';
+        const { verbose } = flags;
+        // Same gating as BaseCommand.waitForBuild(): a spinner belongs only on an
+        // interactive TTY that is not emitting JSON and not interleaving log lines.
+        const animate = Boolean(process.stdout.isTTY) && !json && !verbose;
+        const client = new HatchClient({
+            baseUrl: resolveHatchUrl({ env: process.env[HATCH_URL_ENV_VAR], flag: flags.api }),
+            version: this.config.version,
+        });
+        // The build is server-side and unaffected by this process leaving; the
+        // handler exists only so the user is told so rather than left guessing.
+        const controller = new AbortController();
+        const onInterrupt = () => controller.abort();
+        process.on('SIGINT', onInterrupt);
+        let result;
+        try {
+            result = await runHatch({
+                animate,
+                client,
+                interrupt: controller.signal,
+                io: {
+                    err: (line) => this.logToStderr(line),
+                    out: (line) => this.log(line),
+                },
+                json,
+                prompt: args.prompt,
+                spinner: {
+                    start: (action, status) => ux.action.start(action, status),
+                    stop: (message) => ux.action.stop(message ?? ''),
+                    update(status) {
+                        ux.action.status = status;
+                    },
+                },
+                verbose,
+                wait: !flags['no-wait'],
+            });
+        }
+        catch (error) {
+            this.error(error.message);
+        }
+        finally {
+            process.off('SIGINT', onInterrupt);
+        }
+        if (result.exitCode !== 0)
+            this.exit(result.exitCode);
+    }
+}

package/dist/utils/hatch-client.d.ts

@@ -0,0 +1,74 @@
+/**
+ * A minimal HTTP client for the Hatch API.
+ *
+ * Deliberately free of oclif: it takes its `fetch` and its version string as
+ * options so it is unit-testable without a network or a command instance.
+ * Hatch authenticates an anonymous session purely by the signed cookie handed
+ * back from session-create, so this client's only state is that cookie.
+ */
+import type { BuildOutcome, CreateSessionResponse, SessionSnapshot } from './hatch-contract.js';
+/** Where `xano hatch` talks to when nothing else says otherwise. */
+export declare const DEFAULT_HATCH_URL = "https://hatch.mesh0.ai";
+/** The env var that points the command at a local API or a staging droplet. */
+export declare const HATCH_URL_ENV_VAR = "XANO_HATCH_URL";
+/**
+ * Resolve the Hatch origin: `--api` flag > `XANO_HATCH_URL` > the default.
+ *
+ * Trailing slashes are stripped here rather than at each call site, so no
+ * request ever ends up asking for `//api/sessions`.
+ */
+export declare function resolveHatchUrl(source: {
+    env?: string;
+    flag?: string;
+}): string;
+/**
+ * Session-create answered without a `Set-Cookie`. Named because every later
+ * call would otherwise 404 or 403 with no hint of the real cause.
+ */
+export declare class HatchSessionCookieError extends Error {
+    constructor(message: string);
+}
+export interface HatchClientOptions {
+    /** Origin only, no trailing slash — see `resolveHatchUrl`. */
+    baseUrl: string;
+    fetchImpl?: typeof fetch;
+    /** Reported as `xano-cli/<version>`; passed in so oclif stays out of here. */
+    version: string;
+}
+/**
+ * Derive how a build ended from its snapshot, in the same shape a `terminal`
+ * activity carries — so the command's stream path and its snapshot backstop
+ * agree on what "done" looks like. Undefined while the build is in flight.
+ */
+export declare function outcomeFromSnapshot(snapshot: SessionSnapshot): BuildOutcome | undefined;
+export declare class HatchClient {
+    private readonly baseUrl;
+    private readonly fetchImpl;
+    /** The `name=value` pair captured from session-create. */
+    private sessionCookie;
+    private readonly userAgent;
+    constructor(options: HatchClientOptions);
+    /**
+     * Mint an anonymous session, asking for a watch link.
+     *
+     * `watchUrl` is optional on purpose: a Hatch deployed before the `?watch=1`
+     * affordance answers without one, and the command degrades to watching
+     * without a link rather than failing.
+     */
+    createSession(): Promise<CreateSessionResponse>;
+    /** `GET /api/sessions/:id` — the backstop when the stream says nothing. */
+    getSnapshot(sessionId: string): Promise<SessionSnapshot>;
+    /**
+     * Open the session's SSE stream, returning the raw `Response` for a reader
+     * to frame.
+     *
+     * `lastEventId` goes in the `Last-Event-ID` **header**. Hatch's frontend also
+     * appends `?from=<n>`, but the server reads only the header — sending the
+     * query parameter alone silently replays the whole build on every reconnect.
+     */
+    openStream(sessionId: string, lastEventId?: number | string): Promise<Response>;
+    /** `POST /api/sessions/:id/prompt` — the server answers 202. */
+    submitPrompt(sessionId: string, prompt: string): Promise<void>;
+    /** Every request carries the User-Agent, and the cookie once we hold one. */
+    private request;
+}