Leyline 0.2.0

Leyline 0.2 adds AI on your own provider key: an assistant in the app that runs the radio from plain requests, and speech-to-text for each over on a recording or a live channel.

• The assistant. A column beside the inspector (the toolbar’s Assistant button, or View > Show Assistant, ⇧⌘A, once a key is added) takes plain requests and runs the radio with ley mcp’s tools: it tunes, sets the squelch, scans, records, keeps bookmarks, and moves the window to a band, the Library or a recording. Each step opens to its arguments and result. A call that takes the radio from another listener, deletes a recording, starts a kept job or paid transcription, imports or removes bookmarks, or follows text received over the air asks first, in words, with Decline, Allow in this chat and Allow. Stop ends a turn. Conversations are kept across a restart of the engine. The assistant never hears the audio.
• AI on your own key. Settings > AI and ley ai add, check and remove a key for Anthropic, OpenAI or an OpenAI-compatible server, choose the provider and model for each feature, and show the requests and tokens each one used by day or month, with no prices. The engine keeps the key in the login keychain and never returns it to a client. Adding a key gives every feature it serves that has no model yet the provider’s default (OpenAI: gpt-5 and whisper-1; Anthropic: claude-sonnet-5-5 for the assistant); ley ai use changes one. Settings says, for each feature, what it sends to which host.
• Speech. The speech decoder sends the audio of each over, and none of the silence between, to OpenAI’s transcription API or the server a key’s endpoint names, and keeps the words tied to the over: ley transcribe over a gated recording, after stating the minutes and the host; ley decode speech --freq on a live channel, with each over kept as a clip; and ley watch speech --freq 146.52 --where 'text~net control'. The Library transcribes a gated recording, shows each over’s words and the callsigns a pattern found in them, searches them, plays one over and exports them as text or SRT. ley play --over, --from and --to play part of a recording. There is no on-device speech engine yet.
• The window follows the radio. When another client (the assistant, a terminal’s ley tune, an agent on ley mcp) makes a channel on the window’s radio, the readout, the inspector, the transmissions log and the audio move to it, and the inspector says who tuned. While the window’s old channel is still recording, the inspector shows Still recording with a Stop.
• ley mcp. Eleven more tools: set, stop, list_bookmarks, add_bookmark, remove_bookmark, list_bands, list_presets, watch, attach_device, import_chirp and help. set refuses to change another client’s channel until take_over, as tune does, and each tool’s text starts with what it did.
• The sidebar. An open band’s Scan band and Channels are rows under its header, and the words are shorter (17 bands out of range ›, sq auto). A band the radio cannot tune reads disabled. A bookmark near a plan channel reads ≈ and the channel. A scan hit tunes and bookmarks the channel it names, or its measured frequency to 100 Hz.
• Tuning. The tuning field shows four decimals of MHz, cut and never rounded. A typed frequency tunes to the hertz, and Return with nothing typed keeps the exact frequency.
• Squelch. A measured squelch reads auto in the sidebar and (auto) after its level in ley state, ley set and the event lines.
• Bookmarks. Leaving a Tone or Note field saves it, as Return does; Escape throws the edit away. Bookmarks on one frequency (a repeater and its net from a CHIRP export) are one sidebar row named after the file’s first, Club repeater +1; the inspector lists each with its own tone and note, marks the one whose tone is on the air, and the transmissions log names each over by it. The file keeps every entry. A control beside the sidebar’s + sorts the bookmarks under every band by frequency or by name.
• The band rail. The rail’s one thumb is the view the spectrum and waterfall show, over a faint underlay for what the radio captures, so a 20 MHz HackRF capture fits the rail. Dragging the thumb pans the view inside the capture with no retune, and only a drag past its edge moves the radio. Picking a band fits the view to it with half a channel past each edge, so the channels on its edges show whole. − and + halve and double the span (4 MHz across), a click on the track tunes the nearest tick, and a marker at the spectrum’s edge (146.520 ▸) brings the view back to the tuned channel.
• Recordings that fall behind. When the engine cannot keep up with the radio, a recording lists each stretch it dropped and claims only the audio it wrote. ley recordings gains a DROPPED column, and the Library marks a part with gaps and ticks them on its level graph.
• Keys. A key the keychain will not give the engine is named with the keychain’s own words (cannot read the openai key from the keychain: …) in Settings’ Check and the assistant, rather than “no key is set”, and the engine logs every failed read. Settings calls a key for OpenAI’s own API OpenAI, and a key with an endpoint OpenAI-compatible. text~ in a watch or a search ignores punctuation at a word’s edges, so text~net control matches “net control.”.
• Fixes. A window that opens before the radio, or across a restart of the engine, takes the channel once the radio comes. A wide file radio keeps its tuned band in the sidebar. After Stop Listening, a band moves the radio another client left rather than asking for a second one. The Width pop-up no longer wraps 11.25 kHz, a tall inspector no longer pushes the transport bar out of the window, and the audio ladder shows a dash while the audio is silent. Go to… from the Library gives the filter its focus. The API key field no longer offers AutoFill.
• For test and check runs, leylined gains --no-audio, --file-scan-dwell and --secrets file, which keeps AI keys in a file under --data.