/**
 * Shared help text for the two flags that name *where* a message goes:
 * `--instance` (the instance) and `--agent` (the CLI tool behind it).
 *
 * Issue #1638: the flags were not interchangeable and the docs did not say so.
 * `--instance` is accepted by `send` / `wait` / `respond` / `capture` /
 * `auto-yes`; `--agent` is accepted by every one of those except `wait`, which
 * rejects it with `unknown option` (exit 1). A worktree cut for Codex therefore
 * ran Claude in silence when a workflow copied from the quick start omitted the
 * target flag on the one command that could not take it.
 *
 * ## Why `--agent` is kept rather than removed
 *
 * Removing it would break every shipped script, the embedded `commandmate docs`
 * guide and the published user guide, in exchange for making the flag set look
 * symmetric. It also cannot be removed outright: `send --register` needs an
 * explicit CLI tool whenever the instance id is not itself a tool id
 * (`--instance codex-3 --register` has no other way to say "this is codex"),
 * and an ad-hoc instance the roster has never seen carries no tool either.
 *
 * So `--agent` stays as-is — same parsing, same precedence (Issue #1629: the
 * roster wins, a contradiction is an error) — and only its *position* changes:
 * it is the supplement for ad-hoc, roster-less instances, not the way to pick
 * an agent. The recommended form is `--instance <id>` on its own, which works
 * on all five commands: a rostered instance carries its CLI tool, and an
 * instance id that is itself a tool id (`--instance codex`) resolves to that
 * tool's primary instance without a roster row.
 *
 * Adding `wait --agent` was rejected in #1629: without an instance, `--agent
 * codex` does not say *which* codex session to wait on.
 */
/**
 * `--agent` description for send / respond / capture / auto-yes.
 * `instances add --agent` is deliberately NOT this text: there the flag
 * declares the tool of a new roster entry and is required, not a supplement.
 */
export declare const AGENT_OPTION_DESCRIPTION: string;
/** `--instance` description, shared by send / respond / capture / auto-yes. */
export declare const INSTANCE_OPTION_DESCRIPTION: string;
/**
 * `--instance` description for `wait`, which has no `--agent` to fall back on.
 * Spelling that out here is the point of the Issue: a workflow that names the
 * agent on `send` and nothing on `wait` waits on the wrong session in silence.
 */
export declare const WAIT_INSTANCE_OPTION_DESCRIPTION: string;
/**
 * `--instance` description for `interrupt` (Issue #2101).
 *
 * `interrupt` takes no `--agent`, on the `wait` precedent and for the same
 * reason #1629 gave: the flag would have to say *which* session, and a bare
 * `--agent codex` does not. The default here is not "the primary instance"
 * either — `POST /api/worktrees/:id/interrupt` with no `instanceId` stops EVERY
 * running session of the worktree, so the flag is what narrows a multi-instance
 * worktree to one, and its absence is a deliberate broadcast rather than a
 * fallback.
 */
export declare const INTERRUPT_INSTANCE_OPTION_DESCRIPTION: string;
//# sourceMappingURL=agent-target-options.d.ts.map