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

The `prompuff` command and MCP setups from each Linux package

Open
  • Is something wrong?
#52 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp, linux
Domain
backend-api-design, cli, desktop, testing

Research direction

Read src/Prompuff.App/Platform/CommandLineInstaller.cs and McpClientSetup.cs, then inspect CommandLineInstallerTests.cs and IntegrationsTests.cs. Trace how install type affects CLI detection and the generated MCP setup, including the Flatpak command and setups from #51. Done means copied .deb setup works with claude mcp add and tests cover every install type.

Written by the indexing model from the issue text.

Description

enhancement

The command-line tool and the MCP setups assume an install that Prompuff manages. A package puts things in other places.

What to do

  • A .deb or AUR copy already puts prompuff on the PATH, so Settings › Integrations shows it as installed rather than offering Install command-line tool.
  • A Flatpak runs the CLI as flatpak run --command=prompuff <app id>, so its MCP setups use that command.
  • The ready-to-paste MCP setups use the right command for each install type, from #51.

Where to look

  • src/Prompuff.App/Platform/CommandLineInstaller.cs: IsInstalled, CommandPath, NeedsPathSetup
  • src/Prompuff.App/Platform/McpClientSetup.cs
  • tests/Prompuff.App.Tests/CommandLineInstallerTests.cs and IntegrationsTests.cs

Done when

  • From a .deb install, claude mcp add with the copied setup searches the library through MCP.
  • Tests cover the setups for each install type.
Dominant language
C#
Stars
0
Forks
1
Avg merge
1h 21m
Merged PRs (30d)
22

Getting set up

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 hazeliscoding/prompuff

All issues in hazeliscoding/prompuff

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.