/**
 * Inject replies from Discord back into Claude Code sessions.
 *
 * Strategy: file-based relay. A Discord reply gets written to
 * `<bridge-dir>/pending-reply.txt`; a Claude Code hook (e.g.
 * `hooks/check-reply.sh`) reads and consumes it, piping the content to
 * the session's stdin. A history line is appended to `reply-history.jsonl`
 * (capped at 500 lines) for the `--history` CLI command.
 *
 * Tests and advanced setups can pass a custom `dir` to every function
 * (defaults to `~/.claude-bridge/`). The CLI calls the functions without
 * `dir` and uses the default — behavior for end users unchanged.
 */
export interface PendingReply {
    content: string;
    author: string;
    timestamp: number;
    sessionId?: string;
}
/** Write a pending reply for Claude Code to pick up. */
export declare function writePendingReply(reply: PendingReply, dir?: string): void;
/** Read and consume the pending reply (returns null if none). */
export declare function readPendingReply(dir?: string): PendingReply | null;
/** Check if there's a pending reply without consuming it. */
export declare function hasPendingReply(dir?: string): boolean;
/** Get reply history (last N entries). */
export declare function getReplyHistory(limit?: number, dir?: string): PendingReply[];