Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Save YouTube playlists via URL

Open
#412 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
backend, cli

Research direction

Start by reading the configuration parsing and playlist-loading entry points, then trace how the TUI currently saves and refreshes playlist contents. The issue names no files or tests, so locate the existing URL and playlist handling before estimating the change. Done means a YouTube or YouTube Music playlist URL can be configured and refreshed from the TUI without browser cookies or OAuth.

Written by the indexing model from the issue text.

Description

enhancement

Problem

I have some unlisted YouTube and YouTube Music Playlists that I update regularly. I like the mechanism of loading one with u, then pressing p and w to save its contents directly to a TOML file. But this won't keep them updated. Unless there is something I haven't found in the docs.

Proposal

Being able to save a playlist directly to the config, and being able to refresh it from the TUI.
I know you can do this by using the cookies from a browser or OAuth, but being able to do it without those would make them a lot more portable and independent.

Mockups / references

Perhaps something like:

[[playlist]]
path = "https://music.youtube.com/playlist?list=..."
title = "Favorite Songs" # Optional, would use the actual playlist title by default
Dominant language
Go
Stars
4.4k
Forks
307
Avg merge
3d 6h
Merged PRs (30d)
26

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bjarneo/cliamp

All issues in bjarneo/cliamp

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.