Skip to content

Tell-Tail

Understand a live log stream in your terminal or browser. Tell-Tail follows one file or reads stdin, measures throughput and severity, and keeps a small sample of recent errors in memory.

These guides cover Tell-Tail 0.5.0, the published release. The installed binary includes AI Activity, local call inspection, managed application log sources and MCP diagnostics.

Install

With Homebrew:

brew install ding-labs/tap/tell-tail

Or with Cargo (Rust 1.88 or later):

cargo install tell-tail --version 0.5.0 --locked

Download native binaries for Apple Silicon on macOS 14+ or Linux x86_64/ARM64. The browser dashboard is embedded in the binary; it needs no Node, Python, account, or hosted service.

Explore AI Activity

Run tell-tail desktop --demo --open for a synthetic example. On an Apple Silicon Mac, the desktop plugin guide covers installation and persistent tracing. Default tracing keeps diagnostic metadata. Enable local call inspection separately to view a selected command, the matching request and excerpts of failure output.

See desktop activity, the workspace guide and application log sources.

Inspect desktop MCP logs

On macOS, discover existing Codex Desktop and Claude Desktop MCP logs:

tell-tail mcp --open

The local dashboard shows reported failures, scoped recovery, a searchable timeline, and source freshness. No client configuration change or restart is needed. It reads logs; it does not call MCP servers or capture complete traffic. For synthetic examples on Mac or Linux, run tell-tail mcp --demo --open. See MCP diagnostics for explicit Linux log directories and source limits.

Existing Homebrew users can upgrade with brew update && brew upgrade ding-labs/tap/tell-tail. Check tell-tail --version for 0.4.0 or later before using MCP mode.

Your first log stream

Follow new lines in a log file:

tell-tail app.log

Open the browser dashboard and include existing lines:

tell-tail app.log --from start --output web --open

No log file handy? Run the built-in synthetic demo:

tell-tail --demo --window 5 --output web --open

The browser dashboard stays available until Ctrl+C. In the terminal, press q to quit, space to freeze the display, and ? for controls. Following normally starts at the end of a file; an empty display is expected until new lines arrive.

Go further

Statistics and recent error previews live in memory and reset on restart. Log severity ratios describe received records; they do not establish application health. Webhook delivery is best effort.