thread_selector

Build a full LangSmith thread URL if tracing is configured.

Combines get_langsmith_project_name and fetch_langsmith_project_url into a single convenience helper.

Get the glyph set for the current charset mode.

Check whether the terminal is in ASCII charset mode.

Convenience wrapper so widgets can branch on charset without importing both _detect_charset_mode and CharsetMode.

Open the URL from a Rich link style on click, if present.

Rich Style(link=...) embeds OSC 8 terminal hyperlinks, but Textual's mouse capture intercepts normal clicks before the terminal can act on them. By handling the Textual click event directly we open the URL with a single click, matching the behavior of links in the Markdown widget.

URLs that fail the safety check (e.g. containing hidden Unicode or homograph domains) are blocked and not opened; the event bubbles and a warning is logged and displayed as a Textual notification.

On success the event is stopped so it does not bubble further. On failure (e.g. no browser available in a headless environment) the error is logged at debug level and the event bubbles normally.

Thread metadata returned by list_threads.

A clickable thread option in the selector.

Confirmation modal shown before deleting a thread.

Modal dialog for browsing and resuming threads.

Displays recent threads with keyboard navigation, fuzzy search, configurable columns, and delete support.

Returns a thread_id string on selection, or None on cancel.

LangChain brand colors and semantic constants for the CLI.

Single source of truth for color values used in Python code (Rich markup, Content.styled, Content.from_markup). CSS-side styling should reference Textual CSS variables: built-in variables ($primary, $background, $text-muted, $error-muted, etc.) are set via register_theme() in DeepAgentsApp.__init__, while the few app-specific variables ($mode-bash, $mode-command, $skill, $skill-hover, $tool, $tool-hover) are backed by these constants via App.get_theme_variable_defaults().

Code that needs custom CSS variable values should call get_css_variable_defaults(dark=...). For the full semantic color palette, look up the ThemeColors instance via ThemeEntry.REGISTRY.

Users can define custom themes in ~/.deepagents/config.toml under [themes.<name>] sections. Each new theme section must include label (str); dark (bool) defaults to False if omitted (set to True for dark themes). Color fields are optional and fall back to the built-in dark/light palette based on the dark flag. Sections whose name matches a built-in theme override its colors without replacing it. See _load_user_themes() for details.