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

Remap m to the Music folder in the file explorer and add the "button" tip to the bottom of the first cliamp page.

Open
#585 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
cli

Research direction

Start by reading the file explorer hotkey handling and the code that renders Cliamp’s first page; the issue does not name specific files or tests. Check how the existing mute binding and Music folder path are handled, then verify that a key opens that folder and the first page shows the tip.

Written by the indexing model from the issue text.

Description

enhancement

Problem

UX wise, I find it a bit unintuitive and too difficult to just play local albums and music files via Cliamp.
When I first fired up Cliamp, I had no idea for how to find my local music and play it. First you have to figure out that "o" opens your file explorer, and then you have to navigate to the music folder. It should not be this difficult.

Proposal

I suggest to map m to the Music folder (instead of mute), and then add this tip to the bottom of "landing page" in Cliamp.
If it is not desirable to map m, then another key can be used - the main proposal here is to map a key to the music folder and add this tip to the Cliamp interface.

The hotkey should take you to this path:

Image

A tip should be added to the bottom:

Image
Dominant language
Go
Stars
4.4k
Forks
307
Avg merge
3d 8h
Merged PRs (30d)
34

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.