remote-logs

Fetch build and runtime logs from fusebase-deployed backends.

6|Updated May 29, 2026
One-click install
npx skills add https://github.com/fusebase-dev/fusebase-flow --skill remote-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remote-logs
Source: https://github.com/fusebase-dev/fusebase-flow/tree/main/.agents/skills/remote-logs
Command: npx skills add https://github.com/fusebase-dev/fusebase-flow --skill remote-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a deployed app backend encounters issues, manually navigating cloud provider interfaces to find relevant logs is slow and inefficient, especially when you need to distinguish between build-time deployment failures and live runtime errors, or isolate logs for specific sidecar containers.

Core Features & Use Cases

  • Build Log Access: Retrieve full logs from the most recent deployment to diagnose failed builds, Dockerfile errors, or npm install failures.
  • Runtime Log Filtering: Pull live console (stdout/stderr) or system (infrastructure) logs from running backends, with options to limit log entries, filter by container name (including sidecars), and adjust log tail length.
  • Use Case: If your deployed backend is crashing on startup, use this skill to fetch the last 50 runtime console logs to quickly identify unhandled exceptions without leaving your development environment.

Quick Start

Use the remote-logs skill to fetch the last 200 runtime console logs for your deployed app with ID your-app-id to diagnose a startup crash.

Frequently Asked Questions about remote-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve runtime logs for a deployed backend crashing on startup?

To retrieve runtime logs for a deployed backend crash, fetch live console output using remote logs filtering. You can tail the last 50 runtime console logs to quickly identify unhandled exceptions without navigating cloud provider interfaces.

How do I access cloud build logs to diagnose failed deployments?

Access cloud build logs by retrieving full output from your most recent deployment. This allows you to diagnose failed builds, Dockerfile errors, or npm install failures directly from your development environment.

Can I filter container logs to isolate output from specific sidecars?

Yes, you can filter container logs by specific container names, including sidecars. This allows you to isolate sidecar container logs and pull targeted runtime console or system infrastructure logs from running backends.

Does remote log retrieval work with apps deployed outside fusebase deploy?

No, remote log retrieval applies exclusively to apps with a backend/ folder that have been deployed via fusebase deploy. It cannot fetch logs for backends deployed through other cloud provider interfaces.

How do I adjust log tail length when fetching deployment logs?

Adjust log tail length by specifying a limit on log entries when pulling runtime console or system logs. You can configure the fetch to return the last 200 entries to diagnose issues like startup crashes.