agent

Accepted internal output modes for CLI subcommands.

Default LangGraph runnable config.

Sets recursion_limit to 1000 to accommodate deeply nested agent graphs without hitting the default LangGraph ceiling.

The default agent name used when no -a flag is provided.

When True, compact_conversation requires HITL approval like other gated tools.

Matches the ### Model Identity section in the system prompt, up to the next heading or end of string.

Get the default coding agent instructions.

These are the immutable base instructions that cannot be modified by the agent. Long-term memory (AGENTS.md) is handled separately by the middleware.

Get the glyph set for the current charset mode.

Get the default working directory for a given sandbox provider.

Read the server project context from environment transport data.

List subagents from user and/or project directories.

Scans for subagent definitions in the provided directories. Project subagents override user subagents with the same name.

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.

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.

List all available agents.

Reset an agent to default or copy from another agent.

Build the ### Model Identity section for the system prompt.

Get the base system prompt for the agent.

Loads the base system prompt template from system_prompt.md and interpolates dynamic sections (model identity, working directory, skills path, execution mode).

Create a CLI-configured agent with flexible options.

This is the main entry point for creating a deepagents CLI agent, usable both internally and from external code (e.g., benchmarking frameworks).

Metadata for a connected MCP server and its tools.

Swap the model or per-call settings from runtime.context.

Inject local context (git state, project structure, etc.) into the system prompt.

Runs a bash detection script via backend.execute() on first interaction and again after each summarization event, stores the result in state, and appends it to the system prompt on every model call.

Because the script runs inside the backend, it works for both local shells and remote sandboxes.

Explicit user/project path context for project-sensitive behavior.

Validate shell commands against an allow-list without HITL interrupts.

When the agent invokes a shell tool (any tool in SHELL_TOOL_NAMES), this middleware checks the command against the configured allow-list before execution. Rejected commands are returned as error ToolMessage objects — the graph never pauses, so LangSmith traces stay as a single continuous run.

Use this middleware in non-interactive mode to avoid the interrupt/resume cycle that fragments traces.

Load async subagent definitions from config.toml.

Reads the [async_subagents] section where each sub-table defines a remote LangGraph deployment:

[async_subagents.researcher]
description = "Research agent"
url = "https://my-deployment.langsmith.dev"
graph_id = "agent"

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.