/**
 * Startup commands — per-bot slash commands the worker types into a freshly
 * spawned CLI right after it's ready, BEFORE the user's first prompt (e.g.
 * `/effort ultracode`, `/model opus`). Extracted into a leaf module so both
 * bots.json parsing ({@link ../bot-registry.js}) and the `/botconfig` config
 * store ({@link ../services/bot-config-store.js}) share one normalization
 * without a circular import.
 *
 * Unlike {@link ./passthrough-commands.js}'s customPassthroughCommands — which
 * are single-token slash commands routed through the daemon — a startup command
 * is a whole input LINE typed verbatim into the CLI's TUI, so it MAY carry
 * space-delimited arguments (`/effort ultracode`). That's why the free-text
 * parser splits on comma/newline only (never whitespace) and the per-entry
 * normalizer keeps internal spaces intact.
 */
/**
 * Normalize a single startup command: collapse embedded newlines (each command
 * must submit as one line), trim, and ensure a leading `/` (so users can type
 * `effort ultracode` or `/effort ultracode`). Returns null for empty / too-long
 * input. Internal spaces (arguments) are preserved.
 */
export declare function normalizeStartupCommand(cmd: unknown): string | null;
/**
 * Parse free-text dashboard / `/botconfig` input into a normalized, order-
 * preserving, deduped startup-command list. Commands are separated by comma OR
 * newline (NOT whitespace, since a command's arguments are space-delimited).
 * Mirrors the normalization {@link ../bot-registry.js}'s parseBotConfigsFromText
 * applies when loading bots.json, so a round-trip through the card is stable.
 */
export declare function parseStartupCommandsInput(raw: string): string[];
/** Normalize an array (bots.json form) of startup commands. */
export declare function normalizeStartupCommandList(arr: unknown): string[];
/**
 * Whether a spawn should (re-)run startupCommands. They run on a genuinely fresh
 * CLI process; a reattach to a LIVE persistent (tmux/zellij/herdr/zmx) pane — e.g. a
 * daemon restart recovering an existing session — is the SAME CLI with its
 * effort/model/context already established, so re-typing `/effort` (idempotent)
 * or `/clear`,`/compact` (NOT idempotent) would corrupt it. Skip on reattach.
 */
export declare function shouldRunStartupCommandsOnSpawn(opts: {
    willReattachPersistent: boolean;
}): boolean;
/**
 * Whether to defer the initial prompt from launch-args to the normal input queue
 * so startupCommands precede it. Only when commands exist AND the CLI bakes the
 * first prompt into launch args (passesInitialPromptViaArgs, e.g. Gemini `-i`):
 * an args-baked prompt would execute BEFORE flushPending's startup-command hook,
 * breaking the "before the first message" contract. Adopt never spawns fresh.
 * Default path (no startupCommands) is untouched, so args-CLIs keep their robust
 * `-i` delivery unless a bot opts in.
 */
export declare function shouldDeferInitialPromptForStartup(opts: {
    hasStartupCommands: boolean;
    adoptMode: boolean;
    passesInitialPromptViaArgs: boolean;
}): boolean;
//# sourceMappingURL=startup-commands.d.ts.map