Deep Agents Code now includes an in-app Debug Console. Press `Ctrl+\` to
inspect session details and filter, view, or copy recent application
logs without enabling file-based debug logging.
---
Debugging client-side TUI problems currently requires restarting with
file logging enabled and tailing a log in another terminal. This adds an
in-app Debug Console, modeled on Mistral Vibe's console, so users can
inspect session state and recent application logs without leaving the
TUI.
Open the console with `Ctrl+\` or the hidden `/debug` command. It shows
a point-in-time snapshot of the version, model, thread, working
directory, auto-approve state, sandbox, MCP servers, token usage, and
debug-log path. Below that, it tails recent `deepagents_code.*` records
from an always-on bounded in-memory buffer and supports filtering by
severity.
The buffer captures `INFO` and above by default, or the level selected
with `DEEPAGENTS_CODE_LOG_LEVEL`. `DEEPAGENTS_CODE_DEBUG` continues to
enable append-only file logging and defaults capture to `DEBUG`.
`Ctrl+L` clears the current console view without clearing the underlying
buffer; `c` copies the visible filtered records retained since the last
clear, and clicking a record copies only that record.
---------
Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
Long server startup failures can exceed the chat banner limit and hide
the actionable part of the exception. Truncated startup errors now keep
the UI readable while pointing users at the debug log path, or telling
them how to re-run with debug logging enabled.
Move `configure_debug_logging` from individual modules to the package
root in `__init__.py` so all child loggers inherit the same file handler
via propagation. This eliminates duplicate handler attachments when
multiple modules import the debug helper, and makes the logging
configuration idempotent across reloads.
Mason Daugherty