import type { CommandContext, CommandResult } from '../types.js';
/** `org logs <name> [--run id] [--role r] [--filter-tool t] [--filter-role r] [--tools-only] [--audit-filter allow|deny] [--follow]` — formatted bus.jsonl tail. */
export declare const logsAction: (ctx: CommandContext, name: string) => Promise<CommandResult>;
/**
 * `org watch <name> <role> [--verbose] [--stats]` — live-tail one role's
 * assistant chat text.
 *
 * Every runner (Claude included — this isn't specific to the subprocess CLI
 * runners) funnels through session.ts's shared message loop, which emits
 * each assistant-text chunk onto the bus as a `chat` event. This command is
 * just `logsAction` pre-filtered to that event type + role and formatted as
 * a plain transcript instead of the full annotated event line — a friendlier
 * front door onto infrastructure that already exists and already covers
 * every runtime uniformly. For the fuller event stream (tool calls, audit
 * decisions) use `org logs <name> --role <role> --follow` directly.
 *
 * --verbose additionally interleaves that role's `status` events (session
 * start/end, restart/crash/backoff, state changes) into the transcript, so
 * a human watching sees WHY a role went quiet instead of just silence.
 * --stats prints a running token/cost line off that role's `usage` events
 * (emitted per turn by session.ts, same as --verbose: already-existing bus
 * data, no new instrumentation).
 */
export declare const watchAction: (ctx: CommandContext, name: string) => Promise<CommandResult>;
/** `org events <name> [--run id] [--follow] [--since <eventId|iso>] [--ndjson]`
 *  — live tail of a run's bus.jsonl as NDJSON, one BusEvent per line
 *  (protocol §7.3). This is the machine streaming surface; `org logs` stays
 *  the human one. NDJSON is the only output mode (--ndjson accepted for
 *  spec symmetry). */
export declare const eventsAction: (ctx: CommandContext, name: string) => Promise<CommandResult>;
//# sourceMappingURL=org-observe-logs.d.ts.map