Logs, Terminal and Files
Day-2 runtime tools for services and containers.
The runtime surfaces you need once something is deployed:
- Runtime logs — tail and filter the live output of any service's containers from the service's Logs tab. Runtime logs are ephemeral (the container's stdout), while build logs are permanent artifacts of the deployment pipeline.
- Interactive terminal — open a full TTY into a running container to run diagnostics, migrations or one-off commands; the session streams over the same socket as the logs.
- Container file browser — list, read and stat the files inside a container without copying data out; the same surface powers the container workbench rows.
Keep log volume bounded#
With streaming logs visible live, remember that runtime logs are not archived by the platform by default — long-running services accumulate only what Docker keeps. Deployments, on the other hand, keep their build logs for the deployment's lifetime, so a failed build can always be audited from the deployment details modal.
Debugging with "Ask the AI"#
When a deployment fails or a health check trips, the Ask the AI action fetches the relevant logs server-side (treated as untrusted data) and asks the configured AI provider for a diagnosis. Logs, question and result remain transient — nothing is stored. Connect a provider first under Settings → Providers.