@microboxlabs/miot-chat 0.1.0

package/dist/index.d.ts

@@ -0,0 +1,107 @@
+import { RunMode, MiotHarnessClient } from '@microboxlabs/miot-harness-client';
+
+interface MiotChatProfile {
+    baseUrl: string;
+    token: string | null;
+    tenantId: string;
+    userId: string;
+    mode?: RunMode;
+    /**
+     * Organization slug; when set, runs route through the quarkus-srv harness
+     * proxy at {baseUrl}/api/v1/orgs/{orgSlug}/harness.
+     */
+    orgSlug?: string;
+}
+type ThemeConfig = string | {
+    name?: string;
+    tokens?: Record<string, string>;
+};
+interface MiotChatConfig {
+    defaultProfile: string;
+    profiles: Record<string, MiotChatProfile>;
+    theme?: ThemeConfig;
+}
+interface ResolvedConfig {
+    baseUrl: string;
+    token: string | null;
+    tenantId: string;
+    userId: string;
+    mode: RunMode;
+    profileName: string;
+    theme: ThemeConfig | null;
+    /**
+     * When true, outgoing runs request debug=true so the SSE stream
+     * carries full tool inputs and truncated tool outputs. Requires
+     * the server-side allow-list to permit the tenant.
+     */
+    debug: boolean;
+    /** Org slug resolved from flag > env > profile, or null when not set. */
+    orgSlug: string | null;
+    /**
+     * Effective base URL for the harness client — the quarkus proxy prefix
+     * ({baseUrl}/api/v1/orgs/{orgSlug}/harness) when orgSlug is set,
+     * otherwise baseUrl unchanged.
+     */
+    harnessBaseUrl: string;
+}
+interface CliFlags {
+    baseUrl?: string;
+    token?: string;
+    tenant?: string;
+    user?: string;
+    mode?: string;
+    profile?: string;
+    debug?: boolean;
+    org?: string;
+}
+interface ResolveOptions {
+    flags?: CliFlags;
+    env?: NodeJS.ProcessEnv;
+    configDir?: string;
+}
+declare const DEFAULT_CONFIG: MiotChatConfig;
+declare function getConfigDir(env?: NodeJS.ProcessEnv): string;
+declare function getConfigPath(env?: NodeJS.ProcessEnv): string;
+declare function readConfig(opts?: {
+    configDir?: string;
+}): MiotChatConfig;
+declare function writeConfig(cfg: MiotChatConfig, opts?: {
+    configDir?: string;
+}): void;
+declare function resolveConfig(opts?: ResolveOptions): ResolvedConfig;
+
+interface RunMiotChatOptions {
+    config: ResolvedConfig;
+    client: MiotHarnessClient;
+    env?: NodeJS.ProcessEnv;
+    stdin?: {
+        isTTY?: boolean;
+    };
+    stdout?: {
+        isTTY?: boolean;
+    };
+    /**
+     * Optional conversation id to forward to the headless REPL. Ignored
+     * in TUI mode (the user picks via /resume). Mirrors the legacy
+     * `miot-chat resume` flow.
+     */
+    conversationId?: string;
+}
+declare function shouldUseTui(env: NodeJS.ProcessEnv, stdin: {
+    isTTY?: boolean;
+}, stdout: {
+    isTTY?: boolean;
+}): boolean;
+declare function runMiotChat(opts: RunMiotChatOptions): Promise<number>;
+
+interface AskOptions {
+    message: string;
+    config: ResolvedConfig;
+    conversationId?: string;
+    stdout?: NodeJS.WritableStream;
+    stderr?: NodeJS.WritableStream;
+    noColor?: boolean;
+}
+declare function runAsk(opts: AskOptions): Promise<number>;
+
+export { type AskOptions, type CliFlags, DEFAULT_CONFIG, type MiotChatConfig, type MiotChatProfile, type ResolveOptions, type ResolvedConfig, type RunMiotChatOptions, type ThemeConfig, getConfigDir, getConfigPath, readConfig, resolveConfig, runAsk, runMiotChat, shouldUseTui, writeConfig };