/**
 * CoreRemoteCommand — Telegram `/core <verb> [args...]` router.
 *
 * v1.11.0 — Core ↔ Agent Bridge (Phase 4).
 *
 * Routing decision per verb:
 *   - status, memory, agents → answered DIRECTLY by the daemon (zero
 *     latency — they read shared state, no need to round-trip through the
 *     CLI inbox).
 *   - run, flow              → enqueued in ~/.openlife/cli-inbox/ for the
 *     core CLI to consume via `openlife bridge pull`. These verbs are
 *     cwd-sensitive and only the core CLI has the right working directory.
 *
 * The AUTHORIZATION layer (single-user allowlist via
 * OPENLIFE_TELEGRAM_ALLOWED_USER_ID) is enforced by Gateway BEFORE this
 * router runs. CoreRemoteCommand never decides who can call it.
 */
export interface RouteResult {
    reply: string;
    messageId: string;
    synchronous: boolean;
    routed: 'direct' | 'inbox' | 'rejected';
}
export declare class CoreRemoteCommand {
    /** Parse the trailing portion of a `/core ` command into verb + args. */
    static parse(input: string): {
        verb: string;
        args: string[];
    } | null;
    /** Route a parsed `/core ...` command. Returns the Telegram reply text. */
    static handle(input: string): Promise<RouteResult>;
    private static handleDirect;
    private static directStatus;
    private static directMemory;
    private static directAgents;
    private static directStory;
    private static directStoryList;
    private static directEpics;
    /** Exposed for tests. */
    static _supportedVerbs(): string[];
    static _directVerbs(): string[];
}
