@phnx-labs/agents-cli 1.22.119 → 1.22.121

package/dist/lib/session/prompt.d.ts

@@ -1,213 +0,0 @@
-/**
- * Prompt cleaning and topic extraction for session messages.
- *
- * Strips noise injected by the agent framework (system context lines, XML
- * wrapper tags, team-spawn boilerplate) so that only the real user intent
- * remains. Used by the session picker to show a human-readable topic line.
- */
-import type { SessionAttachment, SessionEvent } from './types.js';
-/**
- * True when a `role=user` message is harness-injected scaffolding, not a genuine
- * user turn. Text-based so it is cross-harness by construction (the markers are
- * the same wrappers across Claude/Codex/etc.); harnesses that already drop their
- * own scaffolding at parse time simply never reach here.
- */
-export declare function isSyntheticUserMessage(raw: string | undefined): boolean;
-/**
- * Inner text of a `<user_query>` wrapper, or the original string if none.
- * Same extraction Cursor already applies in `parseCursorUserText`.
- */
-export declare function unwrapUserQuery(text: string): string;
-/**
- * Return one genuine user turn in full.
- * Synthetic scaffolding is rejected as a whole so an injected Apps/AGENTS
- * preamble can never become the session's displayed request. Unlike the topic
- * cleaner, this intentionally preserves internal whitespace and every line of
- * the user's actual request. A Grok/Cursor `<user_query>` wrapper is unwrapped
- * so the stored turn is the originating request, not the harness tags.
- */
-export declare function cleanFirstUserMessage(raw: string | undefined): string | undefined;
-/**
- * LATEST genuine user message from an already-normalized event stream.
- *
- * The operative request of a `/continue`d, redirected, or interrupted-and-
- * restated session is the last thing the user said, not the first (PHNX-3939).
- * Same rejection rules as {@link firstUserMessageFromEvents} — walking from the
- * end so a long transcript stops at the first genuine turn it meets.
- */
-export declare function lastUserMessageFromEvents(events: SessionEvent[]): string | undefined;
-/** First genuine user message from an already-normalized event stream. */
-export declare function firstUserMessageFromEvents(events: SessionEvent[]): string | undefined;
-/**
- * Extract the invoked slash-command name from a raw `role=user` message, or
- * undefined when the message carries no `<command-name>` wrapper. Used by
- * `parseClaudeContent` to populate `SessionEvent.slashCommand`.
- *
- * Normalizes a leading `/` onto the result: current Claude Code wraps the
- * name WITH the slash already (`/recap`), but the wrapper predates that and
- * older transcripts carry the bare name (`recap`) — normalizing here means
- * every consumer sees one consistent `/name` shape regardless of vintage.
- */
-export declare function extractSlashCommandName(raw: string | undefined): string | undefined;
-/**
- * Extract the invoked slash-command name from the `SlashCommand` tool's input
- * — the MODEL invoking a command programmatically, not the user typing it.
- * The tool's `command` field carries the full invocation text (name plus any
- * args, e.g. `/code:commit fix the bug`); only the leading command token is
- * the name, matching {@link extractSlashCommandName}'s shape.
- */
-export declare function extractSlashCommandFromToolInput(toolInput: Record<string, any> | undefined): string | undefined;
-export declare const HEADLESS_PLAN_MODE_PREFIX = "You are running in HEADLESS PLAN MODE.";
-/** Strip framework noise from a raw session prompt, returning only meaningful user text. */
-export declare function cleanSessionPrompt(raw: string): string;
-/**
- * How a session's first user turn reads once its framework noise is stripped —
- * so a UI row can show `[image]` / `$ cmd` / `/skill` instead of a screenshot
- * path, a pasted shell line, or a skill's install directory.
- */
-export type UserPromptKind = 'text' | 'image' | 'command' | 'skill';
-interface ClassifiedPrompt {
-    /**
-     * The one-line, display-ready form of the prompt — never a bare path. NOT
-     * length-capped: the recap card shows it in full; row consumers cap it
-     * themselves (`deriveSessionRecap`).
-     */
-    clean: string;
-    kind: UserPromptKind;
-}
-/**
- * Classify a raw first user turn into a display-ready `{ clean, kind }`, so a
- * Fleet/session row shows the user's actual intent rather than path noise:
- *
- *   - `skill`   — a `/skill` invocation's injected "Base directory for this
- *                 skill: …" line collapses to `/<name>`.
- *   - `command` — a `$ `-prefixed shell paste keeps only the first command.
- *   - `image`   — a screenshot/image path standing alone, or an image
- *                 attachment with no real accompanying text, becomes `[image]`.
- *   - `text`    — everything else: wrapper tags stripped (via
- *                 {@link cleanSessionPrompt}) and any inline image path replaced
- *                 with `[image]` so a mixed prompt still drops the path.
- *
- * Pure and cross-harness (text markers, no per-agent branch). `hasImageAttachment`
- * lets a caller that only has an already-extracted topic line still detect an
- * image-only turn from the row's attachment list.
- */
-export declare function classifyUserPrompt(raw: string | undefined, opts?: {
-    hasImageAttachment?: boolean;
-}): ClassifiedPrompt;
-/**
- * Reduce a harness-generated session title to something worth showing as a
- * headline, or `undefined` when it is not (PHNX-3999 F26/F27).
- *
- * Claude's `ai-title` and Cursor's `chatMeta.title` are both derived from the
- * FIRST turn of the transcript, so whatever the harness injected there becomes
- * the session's name: a skill's install-directory preamble, a `!`-prefixed shell
- * echo wrapped in `<bash-input>`, a `/clear`. The owner's recording shows both
- * failures — one row titled with shell-command XML wrappers, others reading
- * `/clear`. Three rungs, in order:
- *
- *  1. A skill invocation collapses to `/<skill>` ({@link classifyUserPrompt}
- *     reports `kind: 'skill'` only for that injected line).
- *  2. Harness scaffolding is REJECTED, not cleaned: `<bash-input>`,
- *     `<command-name>`, `<local-command-stdout>`, `<system-reminder>` and the
- *     rest of {@link isSyntheticUserMessage}'s cross-harness list, plus a title
- *     that is only tags. Stripping the tags would leave the shell command
- *     itself as the headline, which is the same wrong answer with tidier
- *     punctuation.
- *  3. A bare control command is rejected ({@link BARE_CONTROL_COMMAND_RE}).
- *
- * A rejected label returns `undefined`, so the row falls to the next rung of the
- * canonical ladder — the daemon-generated title, then the user's own first
- * prompt (`sessionHeadline`, `session/title.ts`). Nothing is deleted: the
- * original turn stays on the row as `firstUserMessage` / `request`, so the
- * details view still shows exactly what the agent was told.
- *
- * A user-authored title (Claude `/rename` / `custom-title`) is never passed
- * here — the caller keeps it verbatim.
- */
-export declare function cleanGeneratedSessionLabel(title: string | undefined): string | undefined;
-/**
- * Extract a one-line topic from a raw user message, or undefined if the message
- * is pure noise.
- *
- * Rejection is {@link isSyntheticUserMessage} — the SAME list the turn cleaner
- * uses. This function used to consult a shorter, looser copy of it
- * (permissions / collaboration / AGENTS.md / local-command-caveat /
- * `<command-*>` only), which is how a `/model` echo (`<local-command-stdout>`)
- * or a skill body ("Base directory for this skill:") became a session's topic —
- * and then its displayed title — while `cleanFirstUserMessage` rejected the same
- * text (PHNX-3939). Whatever is not a genuine user turn is not a topic either.
- *
- * The check runs twice on purpose: once on the raw message, and again after
- * {@link cleanSessionPrompt} strips wrapper tags, since stripping can expose a
- * marker (a skill body) that the tags were hiding.
- */
-export declare function extractSessionTopic(raw: string): string | undefined;
-/**
- * One classified piece of a request that is not prose: an image or file the user
- * dropped in, or an `@path` directory reference. `name` is the basename (or the
- * `@ref` verbatim) — the sidebar renders these as chips beside the request text.
- */
-interface RequestAttachmentRef {
-    kind: 'image' | 'file' | 'dir';
-    name: string;
-}
-/**
- * A user request split into its parts, never rewritten (PHNX-3939).
- *
- * The rule this type exists to enforce: the request card shows what the agent
- * was actually told. Prose is joined and whitespace-collapsed, never
- * paraphrased or summarized — a model rewrite is what the optional summarizer's
- * `goal` is for, and it is labeled as such. Everything that is NOT the user's
- * sentence (screenshot paths, `host:/path` clip references, `@dir` mentions,
- * pasted terminal echo) is pulled out into `attachments` / `pastedLines` so the
- * sentence survives intact instead of being buried.
- */
-export interface TidyRequest {
-    /** The user's prose, joined and whitespace-collapsed. Empty for an image-only turn. */
-    text: string;
-    /** First sentence of {@link text}, capped — the one line a row shows. */
-    headline: string;
-    kind: UserPromptKind;
-    /** The invocation this turn came in as, e.g. `/continue 8231082e`. */
-    command?: string;
-    attachments: RequestAttachmentRef[];
-    /** Lines classified as pasted terminal echo rather than prose. */
-    pastedLines: number;
-}
-/**
- * First sentence of a block of text, flattened and capped.
- *
- * Leading markdown headings are skipped so the headline is the ask, not the
- * section label. A block that then opens with markdown structure (a table row, a
- * bullet, a numbered item) is reduced to its first LINE — a sentence-terminator
- * scan across a table would otherwise splice two cells together. Markdown
- * emphasis characters are dropped so a headline never renders as raw syntax. A
- * "sentence" shorter than 12 characters is not one (an abbreviation, a version
- * number), so the whole flattened text is kept instead.
- */
-export declare function firstSentence(text: string, cap?: number): string;
-/**
- * Split one raw user turn into prose, attachments and pasted terminal echo
- * WITHOUT rewriting a word of it (PHNX-3939). Returns `undefined` when the turn
- * is harness-injected scaffolding or carries nothing to show.
- *
- * Order matters and mirrors how a turn is actually assembled:
- *   1. a `<user_query>` wrapper is unwrapped (Grok/Cursor);
- *   2. a `/name <id>` or `<command-name>` invocation becomes `command`, and any
- *      prose inside `<command-args>` becomes the request itself — this is what
- *      makes a `/plan -- Wait hold on…` turn read as the user's sentence rather
- *      than as a bare command name;
- *   3. whole-message scaffolding is rejected;
- *   4. a multi-line paste that opens with a command and asks nothing is pasted
- *      output, not a request;
- *   5. every remaining segment (split on ` -- ` and per line) is classified as
- *      an attachment, terminal echo, or prose.
- *
- * `opts.attachments` are the row's own recorded attachments, folded in so an
- * image the harness captured but the text never named still shows as a chip.
- */
-export declare function tidyRequest(raw: string | undefined, opts?: {
-    attachments?: SessionAttachment[];
-}, depth?: number): TidyRequest | undefined;
-export {};