<table border="0">
<tr>
<td width="200" align="center" valign="top">
<img src="docs/assets/logo.svg" width="180" alt="MangoFetch logo">
</td>
<td valign="top">
<h1>🥭 mangofetch</h1>
<p><strong>Brutally fast. Extensible. Pure Rust.</strong><br/>
<em>TUI/CLI app for fetch everything you want from internet</em></p>
<p>
<a href="https://crates.io/crates/mangofetch-cli"><img src="https://img.shields.io/crates/v/mangofetch-cli?style=plastic&color=orange" alt="Crates.io"></a>
<a href="LICENSE"><img src="https://img.shields.io/badge/license-GPL--3.0-blue?style=plastic" alt="License GPL-3.0"></a>
<img src="https://img.shields.io/badge/Built%20With-Rust-red?style=plastic&logo=rust" alt="Built with Rust">
<img src="https://img.shields.io/badge/Architecture-Asynchronous-brightgreen?style=plastic" alt="Async">
<img src="https://img.shields.io/badge/Concurrency-Tokio-purple?style=plastic" alt="Tokio">
</p>
</td>
</tr>
</table>
---
<p align="center">
<img src="docs/assets/shot.png" alt="MangoFetch in action" width="900" />
</p>
___
- [🥭 mangofetch](#🥭-mangofetch)
- [Overview](#overview)
- [🛠️ Installation](#🛠️-installation)
- [Via Cargo (Recommended)](#via-cargo-recommended)
- [From Source](#from-source)
- [✨ Key Features (v0.5.1)](#key-features-v050)
- [🏗️ Technical Architecture](#🏗️-technical-architecture)
- [Core Components](#core-components)
- [⚙️ The Core Engine Lifecycle](#️-the-core-engine-lifecycle)
- [Key Engineering Milestones](#key-engineering-milestones)
- [🕹️ Command Reference](#🕹️-command-reference)
- [🗺️ Roadmap & Milestones](#🗺️-roadmap-milestones)
- [🤝 Acknowledgments](#🤝-acknowledgments)
- [Contributing](#contributing)
- [License](#license)
## Overview
**MangoFetch** represents a paradigm shift in terminal-based media acquisition. Engineered with uncompromising standards for memory safety and concurrency, it eschews bloated graphical interfaces in favor of a raw, low-latency execution environment. Built upon the robust foundations of **Tokio** and **Reqwest**, the engine is explicitly designed to saturate network throughput and orchestrate massive archival batches seamlessly, completely decoupling asynchronous I/O operations from the main thread.
With the release of **v0.5.1**, MangoFetch transcends traditional CLI tools by introducing a professional-grade **TUI (Terminal User Interface)**. This interface blends hardcore operational efficiency with striking visual ergonomics, featuring dynamic settings management, fluid mouse event propagation, and a suite of 11 bespoke Tropical Fruit color palettes.
As of **v0.5.1**, MangoFetch features a professional-grade **TUI (Terminal User Interface)** with tropical fruit themes, mouse support, and an advanced dynamic settings engine.
<p align="center">
<img src="docs/assets/shot2_down_view.png" alt="MangoFetch in action" width="900" />
</p>
---
## 🛠️ Installation
### Via Cargo (Recommended)
The fastest way to install the CLI directly to your system path:
```zsh
cargo install mangofetch-cli
```
### From Source
For developers who want the absolute bleeding edge or wish to modify the core:
```zsh
git clone https://github.com/julesklord/mangofetch-cli.git
cd mangofetch-cli
cargo build --release
# The compiled binary will be available at: target/release/mangofetch
```
---
## ✨ Key Features (v0.5.1)
* **1000+ Platforms**: Deep, zero-overhead integration with `yt-dlp` to support virtually any media portal on the internet.
* **Interactive TUI**: A highly responsive, full-screen dashboard powered by `ratatui`, featuring **11 Tropical Fruit Themes** (Mango, Pitaya, Guayaba, Passionfruit, and more).
* **Fluid Mouse Support**: Full support for pointer events—scroll through sprawling download queues and actuate tabs directly via mouse telemetry.
* **Vim-Style Commands**: For the ultimate power user, actuate ultra-fast, non-blocking operations via the `:` command buffer.
* **P2P & Torrents**: Native protocol implementations for magnet links and peer-to-peer decentralized file sharing.
* **Intelligent Extraction Engine**: Features multi-segment HTTP downloads, staggered connection starts to bypass rate limits, and zero-copy metadata embedding.
---
## 🏗️ Technical Architecture
MangoFetch is rigorously organized as a modular workspace, enforcing strict separation of concerns. This architectural decision ensures the core engine remains portable, highly testable, and isolated from the rendering layer.
```mermaid
graph TD
User([Terminal User]) -->|CLI Commands| CLI(mangofetch-cli)
subgraph MangoFetch Workspace
CLI -->|Dispatch & Render| Core(mangofetch-core)
subgraph Core Engine
Core --> Queue[Async Download Queue]
Core --> Registry[Platform Registry]
Queue --> IO[Tokio Async I/O]
Registry --> Ext_Native[Native Extractors]
Registry --> Ext_Generic[Generic Extractor]
end
CLI -.->|Dynamic Linking| SDK(mangofetch-plugin-sdk)
end
Ext_Generic -->|Wraps| YTDLP[yt-dlp Binary]
Ext_Native -->|Muxes Audio/Video| FFmpeg[FFmpeg Binary]
YTDLP -.-> Network((Internet))
IO -.-> Network
IO --> Disk[(Local Storage)]
```
### Core Components
- **`mangofetch-core`**: The UI-agnostic heartbeat of the system. It governs the asynchronous download queue, orchestrates connection pooling, and houses the platform-specific native extractors (YouTube, Instagram, TikTok, etc.). It intelligently encapsulates `yt-dlp` and `ffmpeg` for complex stream muxing, automatically provisioning these binaries if omitted from the host `$PATH`.
- **`mangofetch-cli`**: A hyper-lightweight frontend built with `clap`. It acts as a highly optimized dispatcher consuming the core library, rendering real-time telemetry via a brutalist, information-dense ANSI interface or the interactive TUI.
- **`mangofetch-plugin-sdk`**: A robust FFI-compatible SDK engineered to extend MangoFetch's capabilities dynamically at runtime via shared libraries (`.so` / `.dll`).
---
## ⚙️ The Core Engine Lifecycle
The `mangofetch-core` queue is intrinsically fault-tolerant. Operating on a resilient asynchronous loop, if a single task in a 10,000-item batch encounters a network anomaly, the queue isolates the failure, initiates exponential backoff retries, and continues processing the matrix without stalling.
```mermaid
stateDiagram-v2
[*] --> Queued : User Submits URL
Queued --> FetchingMetadata : Worker Thread Picks Item
FetchingMetadata --> Active : Media Info Resolved
FetchingMetadata --> Error : Network/Parse Failure
state Active {
[*] --> Allocating
Allocating --> Downloading : Progress Stream via MPSC
Downloading --> Muxing : Audio+Video Merge (FFmpeg)
Muxing --> [*]
}
Active --> Complete : Success
Active --> Error : Interruption / Connection Drop
Error --> Queued : Retry Logic Triggered
Complete --> [*]
```
### Key Engineering Milestones
- **Asynchronous I/O Pipeline:** Built upon `tokio::sync::mpsc` channels for non-blocking progress reporting. The UI rendering thread is completely decoupled from the heavy I/O threads, guaranteeing fluid terminal refreshes.
- **Self-Healing Dependencies:** Automatic checksum validation, resolution, downloading, and path-linking of external binaries (`ffmpeg`, `yt-dlp`).
- **Intelligent Parser Heuristics:** The Platform Registry attempts to natively parse media using zero-cost abstractions, falling back to generic extractors only when mathematically necessary.
---
## 🕹️ Command Reference
For a comprehensive breakdown of all execution flags, API arguments, and TUI keybindings, please consult our **[Official Engineering Wiki](docs/wiki/Home.md)**.
* 🚀 **[Installation Guide](docs/wiki/Installation.md)**
* 🛠️ **[CLI Command Reference](docs/wiki/CLI-Guide.md)**
* 🖥️ **[TUI Interactive Guide](docs/wiki/TUI-Experience.md)**
* 🏗️ **[Technical Architecture](docs/wiki/Architecture.md)**
| `mangofetch download <url>` | `mango d <url>` | Single file payload extraction and download. |
| `mangofetch download-multiple <file>` | `mango dm <file>` | High-throughput batch archival from a manifest file. |
| `mangofetch info <url>` | `mango i <url>` | Perform media metadata telemetry without touching disk. |
| `mangofetch list` | `mango ls` | Inspect current active queue and historical matrix. |
| `mangofetch clean` | `mango c` | Clear persistent download history and purge cache. |
| `mangofetch config` | `mango cfg` | Manage engine parameters, connection limits, and paths. |
| `mangofetch check` | `mango ch` | Verify cryptographic integrity of system dependencies. |
| `mangofetch update` | `mango up` | Upgrade internal dependency binaries to latest hashes. |
| `mangofetch logs` | `mango log` | Tail raw asynchronous application logs for debugging. |
| `mangofetch about` | `mango a` | Display engine version, license, and telemetry data. |
---
## 🗺️ Roadmap & Milestones
| **v0.1.0** | ✅ | Initial release and asynchronous architecture setup |
| **v0.2.0** | ✅ | Standalone rewrite — GUI stripped, core engine highly optimized |
| **v0.3.1** | ✅ | Rebranding cleanup, test matrix fixes, and documentation |
| **v0.4.0** | ✅ | **The TUI Release:** Full-screen interactive terminal interface |
| **v0.5.1** | ✅ | **UX & Polish:** Tropical themes, pointer support, dynamic UI |
| **v0.6.0** | ⏳ | Plugin management and community extractors via FFI SDK |
| **v0.7.0** | ⏳ | Decentralized P2P swarm integration |
---
## 🤝 Acknowledgments
- **[OmniGet](https://github.com/tonhowtf/omniget)** — The absolute backbone of this project. A huge shoutout to _tonhowft_ for architecting the original extraction logic and queue engine that MangoFetch builds upon.
- **[yt-dlp](https://github.com/yt-dlp/yt-dlp)** — The incredible extraction engine handling the heavy lifting for over a thousand unsupported platforms.
## Contributing
Pull requests are fiercely welcomed. We adhere to rigorous engineering standards. For major architectural permutations, please open an RFC issue first to discuss your algorithm and approach. See `CONTRIBUTING.md` for guidelines.
## License
<p align="center">
Engineered with 🦀 and 🥭 by <a href="https://github.com/julesklord">Jules Martins</a>.<br>
Released under the terms of the GPL-3.0 License.
</p>