import { TeamshareApi } from '../api'; import type { LlmOptions, LlmResult } from './llm-core'; export { DEFAULT_LLM_BASE_URL, DEFAULT_LLM_MODEL } from './llm-core'; export type { LlmResult, LlmOptions } from './llm-core'; export { QUESTION_MARKER, buildTools } from './llm-tools'; export type { ToolSessionContext } from './llm-tools'; export { complete, completeStream, gatewayHeaders, isOpenRouterUrl, } from './llm-chat'; export declare function runLlmSession(api: TeamshareApi, taskId: string, brief: string, opts: LlmOptions, projectId?: string): Promise; /** * Project-level tool loop (chat mentions): same as runLlmSession but * conversational — no task brief, no continuation persistence, no status * checks. Used when the agent is @mentioned in project chat and the * --self/harness=none loop fires with full MCP tools. * * Returns the final reply text. */ export declare function runProjectSession(api: TeamshareApi, projectId: string, prompt: string, opts: LlmOptions, projectName?: string, /** * Chat channel this reply belongs in (2026-10). Pins `post_chat_message` * so a `--self` reply in a non-General channel does not land in General * (and get duplicated by the scoped runner check). */ channelId?: string): Promise; /** * Document-assistant self-mode session (IMP-9xx): identical tool loop to * {@link runProjectSession} but framed around ONE document. Lets a doc * comment mention trigger real actions (create_task, add_comment, search…) * even without an installed harness - parity with what the harness path * gets through the per-session MCP config. */ export declare function runDocumentSession(api: TeamshareApi, ctx: { projectId: string; documentId: string; }, prompt: string, opts: LlmOptions): Promise;