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

Feature Request: Support ~/.config for theme directory on macOS

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

No implementation file, test, or entry point is identified in the issue; first determine whether path resolution belongs in this themes repository or in Warp itself. Done means Warp supports ~/.config/warp-terminal/themes/ or an agreed environment-variable alternative, rather than requiring only ~/.warp/themes/.

Written by the indexing model from the issue text.

Description

Problem

Users expect Warp themes to be stored in ~/.config on macOS because other applications use this folder. Currently, Warp uses ~/.warp instead, which confuses new users.

Current Behavior

  • Themes must go in: ~/.warp/themes/
    • Users look in: ~/.config/warp-terminal/themes/
      • Result: Users cannot find where to put themes

Expected Behavior

  • Allow users to store themes in ~/.config/warp-terminal/themes/
    • OR make it configurable with an environment variable
      • OR show a helpful error message when themes are in wrong location

Why This Matters

  • Users manage dotfiles and expect everything in ~/.config
    • Makes Warp easier to use for new users
      • Consistent with other modern terminal applications

Workaround (for now)

Users can create a symlink:

ln -s ~/.config/warp-terminal ~/.warp
Dominant language
Python
Stars
1k
Forks
255
PR merge metrics
No merged PRs in 30d

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 warpdotdev/themes

All issues in warpdotdev/themes

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.