Base44: `logs` Command for Terminal Backend Debugging
Base44Base44 released a logs CLI command that streams backend function log output directly to a developer's terminal, displaying up to 50 entries by default across all project functions. The command supports filtering by function name, time range, and result count, and maps console methods (log, error, warn, debug) to structured severity levels. This gives developers a native terminal-based debugging workflow for Base44 backend functions without needing to open the web editor.
Sources & Mentions
1 external resource covering this update
base44 logs: Terminal Debugging for Backend Functions
Base44 extended its CLI with a logs command, enabling developers to query and view log output from their backend functions directly in the terminal. Previously, inspecting function logs required navigating through the Base44 web interface; the new command brings that visibility into any terminal-based workflow.
Basic Usage
Running base44 logs from a project directory reads the local .app.jsonc file to identify the target app and returns the 50 most recent log entries across all backend functions in that project. No additional configuration is needed.
base44 logs
Filtering Options
The command exposes several flags for narrowing results:
| Flag | Purpose |
|---|---|
--function <names> |
Filter to specific function names (comma-separated) |
--since <datetime> |
Show logs from this time onward (ISO 8601 format) |
--until <datetime> |
Show logs up to this time (ISO 8601 format) |
-n, --limit <n> |
Set result count between 1 and 1,000 (default: 50) |
--order <order> |
Sort order: asc or desc (default: desc) |
Log Output Format
Each log entry includes a timestamp, severity level, function name in brackets, and the message body:
2026-02-24 08:23:37 ERROR [send-email] Failed to deliver to user@example.com: connection timed out
Severity Level Mapping
The severity level in each log entry maps directly to the console method used in the function code:
console.log/console.info→INFOconsole.error→ERRORconsole.warn→WARNINGconsole.debug→DEBUG
Output may also include system-level entries from Deno Deploy (the underlying runtime for Base44 backend functions), such as isolate startup times.