Backblaze B2 Contents

Backblaze B2 Contents

v0.1.0

What's actually in your B2 bucket, and what changed last.

backblazeb2storagefilesshowcase
1 agents1 jobs1 cabinets2 pages

Backblaze B2 Contents

general

agents

🪣

B2 Reader

.agents/b2-reader/

Daily B2 Contents

0 9 * * *

1

Agents

1

Jobs

1

Depts

2

Pages

Backblaze B2 Contents
🪣 B2 Reader
Daily B2 Contents
🪣B2 Readerspecialist

Reads the synced bucket files off disk and writes what is in there.

Daily B2 Contentsactive

Backblaze B2 Contents

What's actually in your B2 bucket, and what changed last.

What you get

One page, waiting for you whenever you open it. What the bucket holds, in plain words — what it's mostly for, judging by what's actually in there — followed by the twenty files that changed most recently, newest first. Not an inventory of everything: a bucket with a hundred thousand files still gets twenty rows, because what matters is what moved.

Nothing is uploaded, deleted or renamed. It only reads.

How to look at it

Open the Contents app in this cabinet. It comes pre-filled with a made-up example so you can see the shape of it straight away — the page says clearly that those files are fake. Your first real summary takes its place.

Before it can read your real bucket

Connect B2 in Cabinet's integrations screen with an S3-compatible application key — the one from the S3 section, not a native B2 key — and choose a prefix. Cabinet syncs it down as ordinary files. Nothing here talks to Backblaze — it reads the files after they land.

Set aside a minute for it once. After that it stays connected. Until then the page keeps showing the example.

What's inside

  • B2 Reader — the one agent. Reads the synced files, writes the summary.
  • Daily B2 Contents — the one routine. Runs at 09:00 every day.
  • Contents — the one page. Opens on today, with a picker for earlier days.
Install
$ git clone --filter=blob:none --sparse https://github.com/cabinetai/cabinets.git && cd cabinets && git sparse-checkout set backblaze-b2-contents