A guide for retrieving build and runtime logs from a deployed app backend. Build logs show deployment steps, while runtime logs show the running server's output and errors.

Use it to inspect failed or ongoing deployments and to view recent logs from a deployed backend. Local-only apps should use a different debugging guide.

It separates cloud deployment problems from local development logs, making it easier to investigate the right system. It applies only to apps that have a backend folder.

How fusebase-dev/fusebase-flow configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to fusebase-dev/fusebase-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/fusebase-dev/fusebase-flow/main/.agents/skills/remote-logs/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/fusebase-dev/fusebase-flow

Made for: Claude Code.

Or install fusebase-flow, the plugin that ships this one along with the rest of its 56 skills, 8 commands, 4 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/fusebase-dev/fusebase-flow/remote-logs/github.svg)](https://agentmods.dev/skills/fusebase-dev/fusebase-flow/remote-logs)

Your own site

<a href="https://agentmods.dev/skills/fusebase-dev/fusebase-flow/remote-logs"><img src="https://agentmods.dev/badge/skills/fusebase-dev/fusebase-flow/remote-logs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/fusebase-dev/fusebase-flow/remote-logs"><img src="https://agentmods.dev/badge/skills/fusebase-dev/fusebase-flow/remote-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,121 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00056	$0.01121
Opus 5.5	$0.00022	$0.00448
Sonnet 5.5	$0.00011	$0.00224
Haiku 4.5	$0.00006	$0.00112

Measured 2mo ago against content hash 551abc90796d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

remote-logs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

remote-logs — 100% identical, 0 lines differ

.agents/skills/remote-logs/SKILL.md · 155 lines

How it starts

The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Remote Logs

This skill applies only to apps with a backend/ folder. Frontend-only apps do not produce remote logs.

When an app backend has been deployed using fusebase deploy, you can fetch logs from the cloud:

Build logs - Output from the container image build process
Runtime logs - Live stdout/stderr and system logs from the running backend

Important Distinction

Context	Command	What It Reads
Local development	`fusebase dev start`	Log files in `<app>/logs/dev-*/`
Deployed backend	`fusebase remote-logs`	Cloud build and runtime logs

If the app is running locally via fusebase dev start, use the dev-debug-logs skill instead.

Commands

Build Logs

Fetch build/deployment logs from the most recent deploy:

fusebase remote-logs build <appId>

Output includes:

Build status (in_progress, failed, finished)
Full build log (Dockerfile execution, npm install, etc.)
Deploy job ID for reference

Runtime Logs

Fetch live logs from the running backend:

# Default: last 100 console (stdout/stderr) entries
fusebase remote-logs runtime <appId>

# Specify tail count (0-300)
fusebase remote-logs runtime <appId> --tail 200

# Get system logs instead of console logs
fusebase remote-logs runtime <appId> --type system

# Filter to a specific container (backend or sidecar)
fusebase remote-logs runtime <appId> --container api
fusebase remote-logs runtime <appId> --container my-sidecar

Options:

--tail <n> - Number of log entries (0-300, default: 100)
--type <type> - Log type: console (stdout/stderr) or system (service/infrastructure logs)
--container <name> - Filter logs to a specific container. Use api for the main backend, or the sidecar name for sidecar containers

Log Format with Sidecars

When an app backend has sidecar containers, runtime logs include output from all containers. Each log line is prefixed with the container name:

Read the full file on GitHub · 155 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 155 lines · 56 tokens per session scan A 551abc90796d

Subscribe to this mod's changes

remote-logs is a skill published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 13d ago), licensed MIT. It adds 56 tokens to every session and 1,121 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Cloud Debugging DevOps and cloud ai-coding-assistant codex cursor fusebase github-copilot

remote-logs next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
remote-logsfusebase-dev/fusebase-flow	Skill	9	13d ago	MIT	A	56	Claude Code
gcloud-usagefcakyon/claude-codex-settings	Skill	1.2k	today	Apache-2.0	A	49	Claude Code
troubleshoot-websitehostinger/api-mcp-server	Skill	171	yesterday	MIT	A	139	Claude Code, Codex
lov-clash-tun-doctorlovstudio/skills	Skill	72	yesterday	MIT	A	93	Claude Code
lov-app-optimizerlovstudio/skills	Skill	72	yesterday	MIT	A	105	Claude Code
lov-runtime-auditlovstudio/skills	Skill	72	yesterday	MIT	A	66	Claude Code
lov-app-professional-designlovstudio/skills	Skill	72	yesterday	MIT	A	79	Claude Code

fusebase-flow: Skill for Claude Code