tqdm CLI
The tqdm command adds a progress indicator to line or byte streams so users can follow a long script prepared by an agent.
- 31,379 ★ on the repository
- Last commit
Extended access
Why this level
- The CLI reads its input stream; writes and network actions depend on neighboring commands and their permissions.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/tqdm-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI reads its input stream; writes and network actions depend on neighboring commands and their permissions.
This is third-party code. Review the repository files before installing.
What it does
tqdm can sit between shell commands to track a flowing workload. Data continues through standard output, while progress appears on a separate stream. An agent can add it to copying, archiving or export processing to make long operations visible. The CLI counts lines or bytes and reports throughput. A known total enables completion estimates and percentages. Separate modes accept numeric progress already emitted by another program.
Who it is for. Authors of long processing scripts who need to show people the progress of agent-prepared commands.
Good fit when
- A large export is streamed and the user needs progress visibility.
- An archive operation has a known total size.
- A script already emits a numeric counter that could drive a progress bar.
- An agent prepares a terminal pipeline with separate data and status output.
Not a fit when
- You need job scheduling, retries and recovery.
- The process exposes neither observable data nor a progress counter.
- You expect an exact completion time with an unknown workload.
Example request
Add a byte-progress indicator to the archive command, preserve the data stream and explain how the total size is obtained.Limitations
Percentages and remaining-time estimates need a meaningful total; otherwise only completed throughput is known. The terminal must handle carriage returns correctly or logs may fill with separate progress lines. Numeric-update mode expects numbers, so arbitrary text logs need preparation before use. tqdm observes transmitted data but does not validate the output or reverse side effects performed by other commands in the pipeline.
How to disable. Remove tqdm from the pipeline or stop the whole script. Inspect partial files written by neighboring commands separately.
FAQ
Does the bar enter the processed data?
Not by default. Data goes to standard output and progress to standard error.
Can I count bytes instead of lines?
Yes. Use `--bytes`.
How do I specify total work?
Pass `--total` in the appropriate units.
Can I use it without importing Python code?
Yes. The package provides the tqdm command and module execution.
Why does the bar appear on new lines?
The terminal or log viewer may not support the required cursor behavior. Check how output is rendered.
Discussion
No questions or reviews yet.
Related
CLI toolsThe CLI runs several commands in one terminal and labels their output so users can distinguish processes in agent workflows.
A CLI turns Git changes into a guided code walkthrough with questions and explanations written by your existing agent
A Java thread dump analyzer with an MCP server: an agent finds deadlocks and stuck threads without reading huge stack logs
A CLI that records coding-agent steps and links file lines to the tool call, conversation and original request behind them.
Two Rust commands for the terminal: qq answers a quick command-line question, and qa performs a single step with files and commands
An open-source Rust and Tauri agentic terminal: bring your own model keys, a unified timeline, and transparent tool calls.
README in short
The package also includes a Python library, but shell pipelines can use the CLI directly. Units and progress appearance are configurable.