import type { CliAdapter } from './types.js';
/** Relay CLI (binary `relay`) is the current
 *  release name of what used to ship as Seed — a fork of Claude Code.
 *  It is identical to Claude Code in flags, slash commands and on-disk session
 *  layout (per-project JSONL transcripts, `sessions/<pid>.json`, `tasks/` fd
 *  locks, keybindings.json, settings.json hooks); it differs only in the binary
 *  name, its auth (ByteCloud / bytedcli / SuperRelay), and its data root.
 *
 *  IMPORTANT — Relay 3.x moved its default config dir.  Older Seed/Relay kept a
 *  `.claude-runtime` directory *inside the install package*; Relay 3.x now
 *  defaults to `~/.relay` (honoring `RELAY_CONFIG_DIR`) for the standard
 *  node_modules install and AUTO-MIGRATES the legacy `.claude-runtime` away —
 *  but only when `CLAUDE_CONFIG_DIR` is unset.  Botmux pins `CLAUDE_CONFIG_DIR`,
 *  so the migration never fires; we must therefore point at Relay's *real*
 *  default ourselves.  This is hard-coded to track the installed Relay; if a
 *  future Relay changes the location again, update `deriveRelayDataDir` to match
 *  (see the still-different Seed adapter, which keeps `.claude-runtime`). */
/** Relay's config/data root: `RELAY_CONFIG_DIR` override, else `~/.relay`.
 *  This is exactly what a bare `relay` resolves on a node_modules install, so a
 *  hand-run `relay login` (token written to `~/.relay/byted-cloud-auth.json`)
 *  and a botmux-spawned Relay share one login — fixing the 401 caused by the old
 *  `<pkg>/.claude-runtime` derivation, where Relay 3.x never writes. */
export declare function deriveRelayDataDir(): string;
export declare function createRelayAdapter(pathOverride?: string): CliAdapter;
export declare const create: typeof createRelayAdapter;
//# sourceMappingURL=relay.d.ts.map