skills.rest
ryan-haver
ryan-haverCOMMUNITY
Explore all skills by this author →
GitHub

remote-logs

Fetch build and runtime logs from deployed FuseBase app backends using the fusebase remote-logs command.

5|2|Updated Feb 9, 2026
Search Tags:#debugging#deployment#troubleshooting#logging#backend#cli#fusebase
One-click install
npx skills add https://github.com/ryan-haver/fusebase-mcp --skill remote-logs-ryan-haver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: remote-logs
Source: https://github.com/ryan-haver/fusebase-mcp/tree/main/apps/client-portal-dashboard/.claude/skills/remote-logs
Command: npx skills add https://github.com/ryan-haver/fusebase-mcp --skill remote-logs-ryan-haver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a deployed app backend fails or misbehaves, you cannot inspect it like a local process. This Skill explains how to retrieve build logs and runtime logs from the cloud so you can diagnose failed deployments, startup crashes, and container issues without guesswork. ## Core Features & Use Cases - Build Log Retrieval: Fetch logs from the most recent deployment to diagnose Dockerfile errors, npm install failures, and build-time issues. - Runtime Log Inspection: Stream console (stdout/stderr) or system logs from the running backend, with tail counts up to 300 entries. - Sidecar Container Filtering: Isolate logs from a specific container (e.g., api or a named sidecar) when multiple containers run together. - Use Case: Your app deploys successfully but crashes on startup. Run fusebase remote-logs runtime <appId> --tail 50 to see the unhandled exception, fix the code, and redeploy. ## Quick Start Ask the AI to fetch the runtime logs for your deployed app using fusebase remote-logs so you can diagnose why the backend is failing.

Frequently Asked Questions about remote-logs

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

FAQPage Schema
How do I check logs for a deployed FuseBase app backend?▼

Use the fusebase remote-logs command. Run `fusebase remote-logs build <appId>` for build and deployment logs, or `fusebase remote-logs runtime <appId>` for live stdout/stderr from the running backend.

How to debug a failed FuseBase deployment?▼

Fetch the build logs with `fusebase remote-logs build <appId>`. The output shows the build status, full Dockerfile execution, npm install output, and the deploy job ID, which reveals build-time errors causing the failure.

Can I filter runtime logs to a specific sidecar container?▼

Yes. Use the --container flag, for example `fusebase remote-logs runtime <appId> --container chromium`. Use `api` for the main backend or the sidecar name for sidecar containers.

Does remote-logs work for frontend-only apps?▼

No. Remote logs are only produced by apps with a backend/ folder that have been deployed via fusebase deploy. Frontend-only apps do not generate build or runtime logs in the cloud.

Why does remote-logs say no successful deploy found?▼

This error means the latest deployment failed, so there is no running backend to read runtime logs from. Check the build logs first, fix the underlying issue, and redeploy the app.

What is the difference between console and system runtime logs?▼

Console logs contain your application's stdout/stderr output such as console.log statements and unhandled exceptions. System logs, fetched with --type system, cover infrastructure events like health check failures, container restarts, and resource limits.

Related Skills

Explore More Software Engineering Skills→
fusebase-devfusebase-dev
6

fusebase-cli

Initialize Fusebase Apps projects, configure permissions, and deploy production builds via CLI.

Official
Advanced
fusebase-devfusebase-dev
6

remote-logs

Fetch build and runtime logs from fusebase-deployed backends.

Official
Intermediate
fusebase-devfusebase-dev
6

dev-debug-logs

Locate and interpret runtime logs for local FuseBase app debugging.

Official
Intermediate
stevenmunozstevenmunoz

debug-cloud-function

Debug Firebase Cloud Functions using log-first analysis to identify failures and timeouts.

Community
Intermediate