[Enhancement]: Improve model pull progress display with a progress bar instead of logs

[nimdrak]

Proposal

This issue is created to address the TODO comment found in the (c *Client) PullModel function, from @mdelapenya

// TODO: use a progressbar instead of multiple line output.

Why is it needed?

• Currently, pulling a model floods the terminal with raw log output. This makes it difficult for users to track the actual download progress and results in a poor user experience.

Proposed Solution

Replace the current line-by-line logging with a progress bar.
This can be achieved by:

• Parsing the JSON stream from the response body to get the download status.
• Using a terminal progress bar library (e.g., github.com/schollz/progressbar/v3) to visually display the progress based on the parsed data.

I'd appreciate any feedback on this proposal. If this sounds like a good idea, I'd be happy to open a Pull Request to implement it.

[asahasrabuddhe]

Thanks for opening this proposal 🙌 — replacing line-by-line logs with a proper progress indicator will definitely improve UX.

A couple of things to consider:

1. Fallback behaviour
   Detect non-TTY environments (CI, piping to a file) and fall back to plain line output.

2. Multiple layers / parallel downloads
   Depending on the registry’s stream, you might see multiple concurrent downloads. Either handle them as multi-row progress or aggregate to a single “overall” bar.

3. Error visibility
   Ensure non-progress/error messages remain clearly visible even with an in-place renderer.

4. Dependencies
   schollz/progressbar/v3 is lightweight, but Docker already solved this; we can reuse their approach and avoid adding a new UI dependency.

---

💡 Reference implementation (Docker’s approach):

• JSON messages: github.com/moby/moby/pkg/jsonmessage
jsonmessage.DisplayJSONMessagesStream() decodes the daemon’s JSON stream and renders per-layer progress, using terminal width to draw [====> ] bars and suppressing bars on narrow TTYs.

• Terminal support: github.com/moby/term

• Daemon side: streams JSONMessage entries, e.g.

    {
      "id": "sha256:...",
      "status": "Downloading",
      "progressDetail": { "current": 12345, "total": 67890 }
    }

• CLI side: read the stream and pass it to jsonmessage.DisplayJSONMessagesStream(); it handles decode + rendering and TTY quirks automatically.

If we want extra flexibility (auto TTY/plain, quiet mode, etc.), we could also look at BuildKit’s UI: github.com/moby/buildkit/util/progress/progressui.