@sayknow-cli/coding-agent 0.3.11 → 0.3.13

package/dist/types/modes/utils/injected-user-submission.d.ts

@@ -1,52 +0,0 @@
-import type { ImageContent, TextContent } from "@sayknow-cli/ai";
-import type { InteractiveModeContext } from "../types";
-/**
- * Normalize the content passed to an extension `sendUserMessage` call into a
- * plain text string plus its image attachments. Mirrors the normalization in
- * `AgentSession.sendUserMessage` (text parts joined with "\n") so the resulting
- * text matches the eventual user `message_start` payload.
- */
-export declare function normalizeInjectedUserContent(content: string | (TextContent | ImageContent)[]): {
-    text: string;
-    images: ImageContent[];
-    imageCount: number;
-};
-/**
- * Record a remotely/programmatically injected user message (e.g. Telegram
- * inbound routed through the extension API) into the interactive TUI, so it is
- * captured in prompt history and shown immediately instead of only appearing
- * once the eventual `message_start` event lands.
- *
- * Local TUI submissions never reach this path (they go through
- * `session.prompt(...)` / `startPendingSubmission`), so this cannot double-add
- * local prompt history.
- *
- * - Always adds the injected text to editor prompt history.
- * - Idle injections optimistically render the user message and record a pending
- *   injected optimistic signature (a counting Map, so multiple idle injections
- *   before the first `message_start` do not clobber each other); the later user
- *   `message_start` consumes one count and skips both the duplicate chat add and
- *   the defensive editor clear (so a locally typed draft is preserved).
- * - Busy/queued injections refresh the pending-message display, which the
- *   caller has already populated by invoking `session.sendUserMessage(...)`
- *   before this helper.
- *
- * This helper never clears the editor text.
- */
-export declare function applyInjectedUserSubmission(ctx: InteractiveModeContext, input: {
-    content: string | (TextContent | ImageContent)[];
-    queued: boolean;
-}): void;
-/**
- * Record one pending optimistic render for an injected user message.
- *
- * Injected sends are fire-and-forget and multiple idle injections can be
- * rendered before the first `message_start` arrives, so a counting Map (not a
- * single slot) tracks how many optimistic renders are outstanding per signature.
- */
-export declare function incrementInjectedOptimisticSignature(ctx: InteractiveModeContext, signature: string): void;
-/**
- * Consume one pending injected optimistic render for `signature`. Decrements the
- * count (deleting the key at zero) and returns whether one was outstanding.
- */
-export declare function consumeInjectedOptimisticSignature(ctx: InteractiveModeContext, signature: string): boolean;

package/dist/types/modes/utils/keybinding-matchers.d.ts

@@ -1,10 +0,0 @@
-/**
- * Match the coding-agent interrupt key.
- *
- * Interactive mode installs a keybinding manager that exposes `app.interrupt`
- * globally, but some isolated component tests still run with only TUI
- * keybindings registered. In that case, fall back to raw Escape matching.
- */
-export declare function matchesAppInterrupt(data: string): boolean;
-export declare function matchesSelectCancel(data: string): boolean;
-export declare function matchesAppExternalEditor(data: string): boolean;

package/dist/types/modes/utils/terminal-bell.d.ts

@@ -1,3 +0,0 @@
-export type TerminalBellEvent = "complete" | "approval" | "ask";
-export declare function ringTerminalBell(event: TerminalBellEvent, output?: Pick<NodeJS.WriteStream, "write">): void;
-export declare function classifyHookSelectorBellEvent(title: string): TerminalBellEvent;

package/dist/types/modes/utils/tools-markdown.d.ts

@@ -1,5 +0,0 @@
-import type { Tool } from "../../tools";
-export interface ToolsMarkdownBindings {
-    tools: ReadonlyArray<Pick<Tool, "description" | "name">>;
-}
-export declare function buildToolsMarkdown(bindings: ToolsMarkdownBindings): string;

package/dist/types/modes/utils/ui-helpers.d.ts

@@ -1,54 +0,0 @@
-import type { AgentMessage } from "@sayknow-cli/agent-core";
-import type { AssistantMessage, Message } from "@sayknow-cli/ai";
-import { type Component } from "@sayknow-cli/tui";
-import type { InteractiveModeContext } from "../../modes/types";
-import type { SessionContext } from "../../session/session-manager";
-interface RenderInitialMessagesOptions {
-    preserveExistingChat?: boolean;
-}
-export declare function argsWithPartialJson(args: unknown, partialJson: unknown): unknown;
-export declare class UiHelpers {
-    #private;
-    private ctx;
-    constructor(ctx: InteractiveModeContext);
-    /** Extract text content from a user message */
-    getUserMessageText(message: Message): string;
-    /**
-     * Show a status message in the chat.
-     *
-     * If multiple status messages are emitted back-to-back (without anything else being added to the chat),
-     * we update the previous status line instead of appending new ones to avoid log spam.
-     */
-    showStatus(message: string, options?: {
-        dim?: boolean;
-    }): void;
-    addMessageToChat(message: AgentMessage, options?: {
-        populateHistory?: boolean;
-    }): Component[];
-    /**
-     * Render session context to chat. Used for initial load and rebuild after compaction.
-     * @param sessionContext Session context to render
-     * @param options.updateFooter Update footer state
-     * @param options.populateHistory Add user messages to editor history
-     */
-    renderSessionContext(sessionContext: SessionContext, options?: {
-        updateFooter?: boolean;
-        populateHistory?: boolean;
-    }): void;
-    renderInitialMessages(prebuiltContext?: SessionContext, options?: RenderInitialMessagesOptions): void;
-    clearEditor(): void;
-    showError(errorMessage: string): void;
-    showWarning(warningMessage: string): void;
-    showNewVersionNotification(newVersion: string): void;
-    updatePendingMessagesDisplay(): void;
-    queueCompactionMessage(text: string, mode: "steer" | "followUp"): void;
-    isKnownSlashCommand(text: string): boolean;
-    flushCompactionQueue(options?: {
-        willRetry?: boolean;
-    }): Promise<void>;
-    /** Move pending bash components from pending area to chat */
-    flushPendingBashComponents(): void;
-    findLastAssistantMessage(): AssistantMessage | undefined;
-    extractAssistantText(message: AssistantMessage): string;
-}
-export {};

package/dist/types/notifications/attachment-registry.d.ts

@@ -1,17 +0,0 @@
-/**
- * Process-wide registry mapping a session id to a sink that delivers a local
- * file to the session's connected Telegram chat as a document. Registered by
- * the notifications extension; consumed by the telegram_send tool.
- */
-/** Delivers a local file to the session's Telegram chat. */
-export type TelegramFileSink = (file: {
-    path: string;
-    caption?: string;
-}) => Promise<{
-    ok: boolean;
-    error?: string;
-}>;
-/** Register `sink` for `sessionId`. Returns a disposer that clears it. */
-export declare function registerTelegramFileSink(sessionId: string, sink: TelegramFileSink): () => void;
-/** The Telegram file sink for `sessionId`, if one is registered. */
-export declare function getTelegramFileSink(sessionId: string): TelegramFileSink | undefined;

package/dist/types/notifications/chat-adapters.d.ts

@@ -1,9 +0,0 @@
-import type { NotificationPresentationAdapter } from "./engine";
-type AdapterKind = "discord" | "slack";
-interface ChatAdapterOptions {
-    kind: AdapterKind;
-    channelId?: string;
-}
-export declare function createDiscordAdapter(opts?: Omit<ChatAdapterOptions, "kind">): NotificationPresentationAdapter;
-export declare function createSlackAdapter(opts?: Omit<ChatAdapterOptions, "kind">): NotificationPresentationAdapter;
-export {};

package/dist/types/notifications/config-commands.d.ts

@@ -1,64 +0,0 @@
-/**
- * In-thread configuration slash commands for the threaded session surface.
- *
- * Replies are thread-native now (the old `/answer <sessionId> …` command is
- * removed), but the user can still adjust per-surface behaviour from inside a
- * session thread with small slash commands:
- *
- * - `/verbose`            switch the mirror to verbose (full tool output + reasoning)
- * - `/lean`               switch back to lean (assistant text + tool names)
- * - `/verbosity lean|verbose`
- * - `/redact on|off`      toggle redaction of streamed content
- *
- * This parser is pure so the command grammar is unit-testable; the daemon maps
- * the returned change onto a `config_command` frame / settings update.
- */
-/** A parsed in-thread configuration change. */
-export interface ConfigCommandChange {
-    verbosity?: "lean" | "verbose";
-    redact?: boolean;
-}
-export type TelegramControlCommandName = "reasoning" | "usage" | "context" | "compact";
-export type TelegramControlCommand = {
-    name: "reasoning";
-    action: "cycle" | "status" | "set";
-    level?: string;
-} | {
-    name: "usage";
-} | {
-    name: "context";
-} | {
-    name: "compact";
-    instructions?: string;
-};
-export type TelegramControlCommandParseResult = {
-    kind: "none";
-} | {
-    kind: "ignored";
-    commandName: TelegramControlCommandName;
-} | {
-    kind: "command";
-    command: TelegramControlCommand;
-} | {
-    kind: "invalid";
-    commandName: TelegramControlCommandName;
-    usage: string;
-};
-export declare function telegramControlCommandUsage(commandName: TelegramControlCommandName): string;
-/** Parse deterministic Telegram session-control commands. Recognised roots fail closed. */
-export declare function parseTelegramControlCommand(text: string, botUsername?: string): TelegramControlCommandParseResult;
-/**
- * Parse an in-thread config command. Returns the requested change, or
- * `undefined` when the text is not a recognised config command (so the daemon
- * can fall through to treating it as a free-text injection).
- */
-export declare function parseInThreadConfigCommand(text: string): ConfigCommandChange | undefined;
-/**
- * Parse a `/rich on|off` toggle. Returns `true`/`false` for a recognised
- * on/off argument, or `undefined` otherwise (not a `/rich` command, or `/rich`
- * with a missing/invalid argument). This is intentionally SEPARATE from
- * `parseInThreadConfigCommand`: `/verbose`/`/redact` are producer/session config
- * forwarded over the WS, whereas rich is Telegram-daemon delivery policy handled
- * daemon-locally, so it never becomes a `config_command` frame or a user turn.
- */
-export declare function parseRichToggleCommand(text: string): boolean | undefined;

package/dist/types/notifications/config.d.ts

@@ -1,98 +0,0 @@
-import type { Settings } from "../config/settings";
-export interface NotificationConfig {
-    enabled: boolean;
-    botToken?: string;
-    chatId?: string;
-    discord: {
-        botToken?: string;
-        channelId?: string;
-    };
-    slack: {
-        botToken?: string;
-        channelId?: string;
-    };
-    redact: boolean;
-    verbosity: "lean" | "verbose";
-    idleTimeoutMs: number;
-    rich: {
-        enabled: boolean;
-    };
-    richDraft: {
-        enabled: boolean;
-    };
-}
-/** Read typed config from Settings. */
-export declare function getNotificationConfig(settings: Settings): NotificationConfig;
-export declare function hasNonBlankValue(value: string | undefined): boolean;
-/** Is Telegram configured with usable non-blank boundary credentials? */
-export declare function isTelegramConfigured(cfg: NotificationConfig): cfg is NotificationConfig & {
-    botToken: string;
-    chatId: string;
-};
-/** Is global config sufficient for auto-on (enabled + at least one configured adapter)? */
-export declare function isGloballyConfigured(cfg: NotificationConfig): boolean;
-/**
- * Per-run opt-out for completion notifications, honored before settings lookups.
- *
- * `SKC_NOTIFY=off` (also `0` / `false`, case-insensitive) suppresses the
- * completion notification surface for this process only. `config.yml` is
- * untouched and child processes inherit the env var, which lets non-interactive
- * fleet runs (`skc -p --no-session`) stay silent even when a user-level/global
- * completion notification configuration is enabled.
- */
-export declare function completionNotifyDisabledByEnv(env: NodeJS.ProcessEnv): boolean;
-/** Resolve whether the notifications extension should be registered at SDK startup. */
-export declare function shouldRegisterNotificationsExtension(input: {
-    env: NodeJS.ProcessEnv;
-    cfg?: NotificationConfig;
-    /** Task recursion depth; helper/subagent sessions must not spawn remote surfaces. */
-    taskDepth?: number;
-    /** Parent subagent id/prefix; present for helper/subagent sessions even when depth is omitted. */
-    parentTaskPrefix?: string;
-    /** Role-agent type/name; present for task sessions even if depth metadata is lost. */
-    currentAgentType?: string;
-}): boolean;
-/**
- * Resolve whether THIS session should run notifications.
- * Precedence (highest first):
- *  1) env.SKC_NOTIFICATIONS === "0"  -> false (hard opt-out)
- *  2) sessionDisabled === true       -> false (local /notify off)
- *  3) env.SKC_NOTIFICATIONS === "1" || env.SKC_NOTIFICATIONS_TOKEN present -> true (legacy explicit)
- *  4) isGloballyConfigured(cfg)      -> true (global auto-on)
- *  5) otherwise false
- */
-export declare function isSessionNotificationsEnabled(input: {
-    cfg: NotificationConfig;
-    env: NodeJS.ProcessEnv;
-    sessionDisabled: boolean;
-}): boolean;
-/** Mask a bot token for display: first 4 chars + "…" + "(len N)"; "(unset)" when undefined/empty. Never reveal full token. */
-export declare function maskToken(token: string | undefined): string;
-/** Stable non-reversible fingerprint of a token: sha256 hex, first 12 chars. */
-export declare function tokenFingerprint(token: string): string;
-/** Short session tag for display, e.g. last 6 chars of sessionId. */
-export declare function sessionTag(sessionId: string): string;
-export interface RedactableAction {
-    id: string;
-    kind: string;
-    sessionId: string;
-    question?: string;
-    options?: string[];
-    summary?: string;
-}
-/**
- * When redact is true, strip sensitive content for remote delivery:
- *  - ask: NOT redacted. An ask is an interactive prompt the human must read and
- *    answer on the remote surface; redacting its question/options would make it
- *    unanswerable, defeating remote answering. Asks are returned unchanged.
- *  - idle: summary removed, (no question/options).
- * When redact is false, return the action unchanged.
- *
- * Redaction still applies to streamed content frames (turn_stream, context_update,
- * image_attachment) which are suppressed at their emit sites, not here. Explicit
- * `telegram_send` file attachments are rejected before the file is read or forwarded.
- */
-export declare function buildRedactedAction(action: RedactableAction, opts: {
-    redact: boolean;
-    sessionTag: string;
-}): RedactableAction;

package/dist/types/notifications/daemon-paths.d.ts

@@ -1,10 +0,0 @@
-export interface DaemonPaths {
-    dir: string;
-    lock: string;
-    state: string;
-    roots: string;
-    steal: string;
-    aliases: string;
-    seenUpdates: string;
-}
-export declare function daemonPaths(agentDir: string): DaemonPaths;

package/dist/types/notifications/engine.d.ts

@@ -1,59 +0,0 @@
-import { type RedactableAction } from "./config";
-export type NotificationEvent = ({
-    type: "action_needed";
-} & RedactableAction) | {
-    type: "action_resolved";
-    id: string;
-    sessionId: string;
-    resolvedBy?: string;
-} | {
-    type: "frame";
-    sessionId: string;
-    frame: Record<string, unknown>;
-};
-export interface NotificationReplyRoute {
-    sessionId: string;
-    actionId: string;
-    answer: number | string | {
-        selected?: Array<number | string>;
-        custom?: string;
-    };
-}
-export interface NotificationAdapterPayload {
-    adapter: string;
-    channelKey?: string;
-    body: unknown;
-    route?: Omit<NotificationReplyRoute, "answer">;
-}
-export interface NotificationPresentationAdapter {
-    readonly kind: "telegram" | "discord" | "slack";
-    render(event: NotificationEvent): NotificationAdapterPayload[];
-    mapInbound(input: unknown): NotificationReplyRoute | undefined;
-}
-export interface EngineSessionSink {
-    sendReply(route: NotificationReplyRoute): void;
-}
-export interface NotificationEngineOptions {
-    redact: boolean;
-    sessionTag: (sessionId: string) => string;
-}
-/**
- * Shared presentation engine for managed notification clients.
- *
- * It owns fanout, redaction boundaries, pending-action routing, and reply
- * delivery into session sinks. Transport adapters stay pure: render an internal
- * event into a public-safe payload and map an inbound transport interaction
- * back into a session/action answer.
- */
-export declare class NotificationPresentationEngine {
-    private readonly opts;
-    readonly adapters: readonly NotificationPresentationAdapter[];
-    private readonly sessions;
-    private readonly pending;
-    constructor(adapters: readonly NotificationPresentationAdapter[], opts: NotificationEngineOptions);
-    connectSession(sessionId: string, sink: EngineSessionSink): void;
-    dropSession(sessionId: string): void;
-    fanout(event: NotificationEvent): NotificationAdapterPayload[];
-    routeInbound(adapterKind: NotificationPresentationAdapter["kind"], input: unknown): boolean;
-    private redactEvent;
-}

package/dist/types/notifications/helpers.d.ts

@@ -1,55 +0,0 @@
-/**
- * Pure helpers for the notifications extension.
- *
- * Kept side-effect-free so the mapping logic (ask extraction, idle summary,
- * dedupe keys) is unit-testable without a live session or the native server.
- */
-import { type RedactableAction } from "./config";
-/** A pending ask derived from an `ask` tool call. */
-export interface PendingAsk {
-    /** Action id: `${toolCallId}:${questionId}`. */
-    id: string;
-    /** Question text. */
-    question: string;
-    /** Option labels (may be empty for free-text questions). */
-    options: string[];
-}
-/** Truncate text to `max` chars, appending an ellipsis when cut. */
-export declare function truncate(text: string, max?: number): string;
-/** Stable per-turn idle dedupe key so exactly one idle action fires per turn. */
-export declare function idleDedupeKey(sessionId: string, turnIndex: number): string;
-/**
- * Extract pending asks from an `ask` tool call input.
- *
- * Defensive: tolerates partial/unknown shapes and always returns an array.
- */
-export declare function asksFromAskInput(toolCallId: string, input: unknown): PendingAsk[];
-/** Prepare an action JSON payload for remote notification delivery. */
-export declare function notificationActionPayload<T extends RedactableAction>(action: T, opts: {
-    redact: boolean;
-    sessionTag: string;
-}): RedactableAction;
-/** Extract a plain-text summary from an agent message's content, if any. */
-export declare function summaryFromMessage(message: unknown, max?: number): string | undefined;
-/**
- * Extract an idle summary from an `agent_end` event's settled message list: the
- * last message that yields text (i.e. the final assistant message; tool-result
- * messages have no text and are skipped).
- *
- * `agent_end` fires exactly once when the agent loop settles to await the user,
- * so emitting idle from this — instead of per-`turn_end` — produces exactly one
- * idle notification per genuine idle, eliminating the multi-turn flood.
- */
-export declare function summaryFromMessages(messages: unknown, max?: number): string | undefined;
-/** An agent-produced image extracted from a message's content. */
-export interface ExtractedImage {
-    source: string;
-    mime: string;
-    data: string;
-}
-/**
- * Extract agent-produced images (`{ type: "image", data, mimeType }` blocks)
- * from a message's content — e.g. computer-use/browser screenshots or tool
- * image outputs — for `image_attachment` delivery.
- */
-export declare function imageAttachmentsFromMessage(message: unknown, source?: string): ExtractedImage[];

package/dist/types/notifications/html-format.d.ts

@@ -1,75 +0,0 @@
-/**
- * Telegram HTML formatting helpers for the notifications SDK.
- *
- * All notifications-SDK Telegram output is sent with `parse_mode: "HTML"`. This
- * module is the single source of truth for: escaping dynamic text, converting a
- * bounded markdown subset into Telegram HTML, safely truncating a finished
- * message to Telegram's 4096-char limit without breaking tags/entities, and
- * laying out inline-keyboard buttons as a numbered grid.
- *
- * Discipline: escape first, tag second. Telegram only parses a small tag set
- * (b, i, u, s, code, pre, a, blockquote, tg-spoiler); a stray `<` or unbalanced
- * tag can make Telegram reject the whole message, so dynamic text is always
- * escaped before any tag is emitted.
- */
-export declare const TELEGRAM_PARSE_MODE: "HTML";
-export declare const TELEGRAM_MESSAGE_LIMIT = 4096;
-/** Escape text for Telegram HTML body content (`& < >`). */
-export declare function escapeHtml(value: string): string;
-/** Bold the given raw text (escaped internally). */
-export declare function bold(raw: string): string;
-/** Italicize the given raw text (escaped internally). */
-export declare function italic(raw: string): string;
-/** Render the given raw text as inline code (escaped internally). */
-export declare function code(raw: string): string;
-/** Render the given raw text as a preformatted block (escaped internally). */
-export declare function pre(raw: string): string;
-/**
- * Convert a bounded markdown subset into Telegram HTML. Supported: fenced code,
- * inline code, `**bold**`, `*italic*`, `[text](url)` (safe schemes only),
- * `#` headers, `>` blockquotes, and GFM tables (rendered as a monospace block).
- * Unsupported or malformed markdown is left as escaped literal text — never
- * emitted as unbalanced tags.
- */
-export declare function markdownToTelegramHtml(markdown: string): string;
-/**
- * Truncate a finished Telegram HTML message to at most `max` chars without
- * splitting a tag or entity, closing any still-open allowed tags and appending
- * `marker`. The final string is guaranteed to be <= `max`.
- */
-export declare function truncateTelegramHtml(message: string, max?: number, marker?: string): string;
-/** Split a finished Telegram HTML message into ordered chunks without splitting tags or entities. */
-export declare function splitTelegramHtml(message: string, max?: number): string[];
-/** Finalize an optional message: undefined passthrough, else safe-truncate. */
-export declare function finalizeTelegramHtml(message?: string): string | undefined;
-/**
- * One-based, plain-text button label (Telegram does not parse HTML in labels).
- *
- * Strips any leading `N.`/`N)` index already embedded in the label (e.g.
- * deep-interview options pre-numbered by the ask tool) and applies the canonical
- * one-based button index instead. This avoids duplicated numbering like
- * `1. 1. …` and keeps the displayed number aligned with the button's real index.
- */
-export declare function buttonLabel(label: string, index: number): string;
-/** Numbered, escaped option list for the Telegram message body. */
-export declare function numberedOptionList(labels: string[]): string;
-/** Compact numeric button label; full option text belongs in the message body. */
-export declare function choiceButtonLabel(index: number): string;
-export interface InlineButton {
-    text: string;
-    callback_data: string;
-}
-/**
- * Lay out option callbacks as compact numeric buttons. Telegram mobile clients
- * ellipsize long inline-keyboard labels and tall keyboards can be obscured by
- * the composer, so the full choice text is rendered in the message body while
- * the keyboard keeps only stable one-based tap targets.
- */
-export declare function buildCompactChoiceGrid(labels: string[], callbackForIndex: (index: number) => string): InlineButton[][];
-/**
- * Lay out option labels as a numbered button grid. Long buttons take a
- * full-width row; runs of short buttons are packed into rows of up to 3. The
- * callback value comes from `callbackForIndex(i)` using the original zero-based
- * option index — layout never changes callback semantics.
- */
-export declare function buildButtonGrid(labels: string[], callbackForIndex: (index: number) => string): InlineButton[][];