approval

Tool names recognized as shell/command-execution tools.

Only 'execute' is registered by the SDK and CLI backends in practice. 'bash' and 'shell' are legacy names carried over and kept as backwards-compatible aliases.

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.

Check a URL for suspicious Unicode and domain spoofing patterns.

Detect deceptive or hidden Unicode code points in text.

Join safety warnings into a display string with overflow indicator.

Flatten nested dict/list structures into key-path/string pairs.

Return whether a key path suggests URL-like content.

Render hidden Unicode characters as explicit markers.

Example output: abc<U+202E RIGHT-TO-LEFT OVERRIDE>def.

Remove known dangerous/invisible Unicode characters from text.

Summarize Unicode issues for warning messages.

Deduplicates by code point. When more than max_items unique entries exist, the summary is truncated with a +N more entries suffix.

Get the renderer for a tool by name.

Approval menu using standard Textual patterns.

Key design decisions (following mistral-vibe reference):

• Container base class with compose()
• BINDINGS for key handling (not on_key)
• can_focus_children = False to prevent focus theft
• Simple Static widgets for options
• Standard message posting
• Tool-specific widgets via renderer pattern

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.