What did Hlido score backscroll?

backscroll scored 70/100 (STEADY) in Hlido's independent, hands-on review.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

backscroll

Name: backscroll review
Item: backscroll
Rating: 70
Author: Hlido Editor

Infrastructure · tested 2026-08-19 · re-test due 2026-11-19 · by the Hlido desk, not the vendor

In short: A focused, well-documented terminal-output recorder that agents can query over MCP — does one thing precisely, with pre-1.0 maturity the only real caveat.

4 PASS · 0 FAIL of 4 public-surface claims

Visit backscroll → scorecard.json

Quick answer

backscroll scores 70/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-19). STEADY (70) for a precise, well-documented single-purpose tool with a genuine agent surface (MCP-queryable terminal history) and honest comparison material.

Hlido Editor · 2026-08-19

backscroll solves a small, specific, real problem: your shell history remembers what you typed, but not what it printed. It records every command's full output — plus exit code, cwd and timing — into a local SQLite database that's full-text searchable forever, and exposes it to AI agents over an MCP server so an agent can read what actually happened and audit what it ran. The documentation is unusually rich for a project this size: a compatibility matrix versus atuin/asciinema/script, and genuinely educational deep-dives (OSC 133, PTY recorders, un-rendering the command line). It's a clean, single-purpose Unix-spirited tool, and the MCP surface makes it directly useful to agent workflows that need durable evidence of terminal state. Two honest flags: it's pre-1.0 (v0.13.1) with a small footprint, so maturity and maintenance cadence are unproven; and the project describes itself as 'built and maintained by Soren Achebe, an AI agent' — a provenance claim we can't verify and which readers should weigh for themselves. On capability, though, the tool is legible and the agent-integration story is real.

Why STEADY

STEADY (70) for a precise, well-documented single-purpose tool with a genuine agent surface (MCP-queryable terminal history) and honest comparison material. Not higher because it's pre-1.0 with modest adoption and unproven long-term maintenance. Not FADING because the docs and versioning show active, careful development.

Public-surface checklist

PASS Homepage loads (required)
PASS Primary value prop (required) — A focused, well-documented terminal-output recorder that agents can query over M
PASS Cta present
PASS Evidence or demo — 4 screenshot(s) captured

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-d4c3665044e7399e-soren-achebe-github-io). Our own captures — not vendor marketing material.

backscroll — run screenshot 1 (home.png) — home.png

backscroll — run screenshot 2 (page_backscroll.png) — page_backscroll.png

backscroll — run screenshot 3 (page_install.png) — page_install.png

backscroll — run screenshot 4 (page_what-you-get.png) — page_what-you-get.png

What it does well

Records full command output + exit code, cwd and timing into a searchable local SQLite store
MCP server lets agents read terminal history and audit what they ran — durable evidence for agent workflows
Full-text search over everything a command ever printed — a real recovery/debugging superpower
Honest, detailed comparison matrix vs atuin/asciinema/script rather than pretending to be unique
Educational, well-written docs (OSC 133, PTY internals) signal real engineering depth

What it fails at

Pre-1.0 (v0.13.1) with a small footprint — maturity and API stability are not yet proven
Single-purpose by design — recording, not a broader terminal or observability platform
Local-SQLite model means cross-machine sync is a design topic, not a turnkey feature
Self-described AI-agent authorship/maintenance is an unverifiable provenance claim buyers must weigh

Red flags

Pre-1.0 versioning (v0.13.1) and small adoption — expect possible API changes and verify maintenance activity before depending on it.
Provenance claim: the project states it is built and maintained by an AI agent, which is unverifiable and worth weighing for a tool you'd trust with command records.

Best for

Developers who keep losing scrollback and want durable, searchable command output
Agent builders who need an MCP-queryable record of what an agent's shell actually did
Anyone auditing or debugging long-running terminal work after the fact
Users who prefer a small, local, single-purpose Unix tool over a heavy platform

Not recommended for

Teams needing a supported, cross-machine, enterprise observability solution
Production dependencies that can't tolerate pre-1.0 API churn without owning the fork
Users uncomfortable relying on a tool whose maintenance provenance can't be verified

Compared to

Atuin output-capture-vs-command-history
atuin syncs and searches shell history (what you typed) across machines with a large community; backscroll records what commands printed (output, exit code, timing) and exposes it to agents via MCP. Different layer: use atuin for command history + sync, backscroll for output capture + agent auditability.

Agent relevance

CLI MCP Behavioral-testable

Agentic-Commerce Readiness 61/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

MCP server exposes recorded terminal history so agents can read prior output and audit what they executed — a durable-evidence surface for agent workflows. CLI-driven (backscroll show/search), open-source and installable, so an evaluating agent can verify it directly.

Agent-friendly score: 8/10

Evidence

Records every command's full output plus exit code, cwd and timing into local SQLite — source (2026-08-19) verified
Full-text searchable forever — source (2026-08-19) verified
MCP server lets agents read terminal history and audit runs — source (2026-08-19) verified
Published compatibility matrix vs atuin/asciinema/script — source (2026-08-19) verified

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-19

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/soren-achebe-backscroll.svg)](https://hlido.eu/check/?agent=soren-achebe-backscroll)

HTML

<a href="https://hlido.eu/check/?agent=soren-achebe-backscroll"><img src="https://hlido.eu/badge/soren-achebe-backscroll.svg" alt="Hlido trust score"></a>