I’ve been messing around with Windows Terminal themes previously, and recently wanted to change my theme (again). Naturally, that turned into a project of its own. Because apparently picking a colour scheme and getting on with my day would be far too straightforward. Well, it actually would be if I used any other terminal emulator.

If you’ve ever used Gogh, you’ll know it’s a collection of terminal colour schemes originally intended for various terminal emulators on Linux and macOS. There’s a frankly unreasonable number of them, which is great when you’re trying to find something that looks right and… less great when you realise you want to use them somewhere else entirely.

Windows Terminal has its own JSON format for colour schemes, so you can’t just take a Gogh theme and drop it straight into your settings. Not without doing some conversion(s) first. So I decided to convert the lot, primarily for myself. Just so I can swap these out whenever I feel like it, and not have to run through this entire process again somewhere down the line.

All original 1,250 colour schemes

I’ve put together wt-gogh-themes on GitHub, containing 1,250 Gogh colour schemes converted into Windows Terminal’s native JSON format.

Each theme is provided as an individual JSON file, ready to be copied into the schemes array in your Windows Terminal settings.json. No shell scripts to run, and no need to manually translate colour values yourself.

Just pick a theme, copy the JSON, and you’re done. The conversion maps Gogh’s sixteen ANSI colours, background, foreground and cursor into the corresponding Windows Terminal properties. There’s also the selection background to account for, which Gogh doesn’t define consistently in the source files. For those themes, I’ve used existing selection colours where a matching palette could be established, and derived a fallback for the rest.

The idea is to preserve the original colours rather than introduce my own interpretation of what a theme should look like. If a theme looks terrible, that’s between you and whoever designed it. My goal here was to keep it faithful, not to judge your choice in terminal theme.

What’s the goal, why an entire repository?

Honestly, I wanted more options for Windows Terminal without having to hunt around for individual ports of themes I liked.

There are already plenty of excellent colour schemes by default (surprisingly, thanks Microsoft) that available for Windows Terminal, and this isn’t an attempt to replace any of them. It’s simply a way to make an existing collection of themes available in a format Windows Terminal understands.

Having every theme available individually also makes it relatively painless to browse through them, try something different, and switch back when you inevitably decide the previous one looked better.

One thing worth mentioning: I wouldn’t recommend importing all 1,250 schemes into your terminal settings unless you have a particular reason to do so. Windows Terminal has to load and parse its configuration, and carrying around a huge list of schemes isn’t particularly useful when you only use a handful of them. Best way to do add themes is to keep the ones you like, leave the rest untouched from the repository, and tweak it whenever the mood strikes.

A few things to be aware of…

These are conversions of existing themes, not a collection of palettes I’ve personally designed or painstakingly tweaked. Some themes have questionable contrast, and a few might not be particularly comfortable to use for extended periods. That’s part of the source collection, rather than something the conversion process attempts to fix.

Windows Terminal also has some built-in colour schemes, so a small number of Gogh themes share names with existing schemes. If you’re importing one of those, it’s worth checking the name and renaming it if necessary to avoid a collision.

I’ve kept the individual theme files separate so you can inspect them, make your own adjustments, or simply grab the ones you want without having to deal with the entire collection.

And also, these were converted en-masse with my Hermes agent. So while I’ve ran through and validated quite a large chunk of these themes personally, a few may have issues as of this initial deployment. Feel free to open an issue within the GitHub repository if you find any, and I’ll try to fix it once I can get around to it!

Where can I find them?

The repository is available here:

cherryfops/wt-gogh-themes

It’s a fairly straightforward project, but it solves a small annoyance I had and makes a pretty substantial collection of themes easier to use on Windows.

And that’s it, really. Just something I decided to work on because it seemed useful for me, and might help another soul out there also using Windows Terminal with a need for their chosen theme(s).

Well I eventually got around to it. I’ve been delaying this, and there’s still some hitches that you’ll encounter because I’ve been working on this locally for a while. But hey, I finally got a proper CI/CD pipeline setup and can get this out and live.

There’s not much you’ll find on here as of writing. Certain things are setup in a certain way, partially ambitious on my part in regards to my future creativity, such as…

• The “Categories” dropdown in the header having hard-configured values used, though not all of them are available just yet as no posts under them exist.
• Limited content overall - this being the first and only post initially. That will of course change over time.
• Possible compliance or otherwise related pages being available. Albeit, no cookies or tracking are deployed here (no JS actually, Hugo static site that’s heavily tweaked from the Bear Cub theme). Just haven’t done an effective audit of that yet.

What’s currently in place?

The structure overall is - as far as I am aware - functionally sound. There’s also some neat little things I find important or cool to include. You’ll notice them about, but primarily there’s two areas.

First area is the Resources page I’ve got setup. Contains a bunch compendium essentially, with technical documentation, files or other information such as SEO related details, that are optimally setup (in my opinion) for both human reading while retaining optimization as a machine-readable page too.

Technical, boring? Yeah. But I mean that’s kind of my thing so that checks out I would say.

Second is more broad and general, which is the overall design of the site itself as a feature. If you compare this visual aesthetic to the original Bear Cub theme, you’ll see exactly how it’s a significant change overall.

This isn’t to say there won’t be further changes down the line of course. I am absolutely someone who lives off of the mantra “If it ain’t broke, take it apart and fix it anyway” like most engineer-type individuals.

And what’s next?

Realistically, this is it for now. I’d be very surprised if you are reading this, since it is a much more “personal” kind of blog, but hey I’m not going to complain if you are.

I have a list of some goals, some more likely to be obvious than others. Some of those being…

• Future content that I myself publish for my own sake. Anything from rambling to technical stuff, project details, etc.
• Further SEO optimization. It’s definitely poor at the moment, and that’s because I can’t stand spending hours doing it. I should, but I don’t, and that’s on me.
• Possible work into better mobile view, as this is 100% a desktop first design and experience. I’ve barely tested on mobile in fairness.

There’s also a point where I do plan on delving further into being a furry degenerate, and possibly uploading and storing my photos I’ve taken during that time in some way also. A kind of gallery on here for people to view if they wanted to for any reason, but primarily for my own sake since I have the goal of keeping that stored off my own devices in some capacity also.

Regardless, thanks for checking this out since you’re here, and hi! I promise I’ll be good and post here occassionally, and the goal is always to stay personal - nothing monetized or commercialized.

I grew up as an FPS game nerd and spent a good chunk of my teenage years and early twenties around competitive gaming and esports. I was a writer covering Counter-Strike and Overwatch, and was also part of Team Dignitas for a while.

These days I’m less obsessed with competitive gaming than I used to be sadly. Partly because I’m getting old, partly because I have an actual job now, and partly because my ADHD-riddled brain has apparently decided that having enough time to play new games is an unreasonable request.

I still play some stuff every now and then, but usually gravitate back towards things I’ve already spent far too many hours with, rather than keeping up with new releases or anything competitive nowadays.

Hobbies and Interests

I work in technical support, mostly around Linux, WordPress, hosting, infrastructure and cloud services.

I like figuring out how things work, taking things apart, breaking them, fixing them, and occasionally deciding that whatever problem I’ve created would be easier to solve by building the entire thing myself.

That tendency extends to this website and its good ol’ cheap VPS hosting it. Remember, if it ain’t broke, it doesn’t have enough features yet.

Favourite Games

In no particular order since that’d be impossible to rank them, and I love some of these for completely different reasons…

• Half-Life Series
• Black Mesa
• Cyberpunk 2077
• Halo: The Master Chief Collection
• Satisfactory
• Sid Meier’s Civilization V & VI
• Fallout: New Vegas
• Furi

You can also find my collection of personally used Civ VI QoL and UI Improvement mods that I deem near-essential. If you enjoy Civilization VI, it’s worth getting most of these.

Elsewhere Online

If you haven’t already seen it somehow, there’s actually a “Links” dropdown to find my social media and other online accounts I tend to use.

Usually, if you want to reach out to me for any reason, the easiest and fastest way is through Telegram most the time. Followed by X (Twitter), and then lastly anywhere else.

This page provides information for security researchers, users, and anyone who discovers a potential vulnerability.

Reporting

If you believe you have found a security vulnerability, please report it privately using the contact method listed in security.txt.

When reporting an issue, please include as much of the following information as possible:

• A clear description of the vulnerability.
• The affected URL, endpoint, service, or component.
• Steps required to reproduce the issue.
• The potential security impact.
• Proof-of-concept material where appropriate.
• Any relevant request, response, log, or error information.
• Your preferred method of contact.

Please do not include passwords, authentication tokens, private keys, personal data, or other sensitive information unnecessarily.

Responsible Disclosure

Please allow reasonable time for an issue to be investigated and, where appropriate, remediated before publicly disclosing technical details.

Security researchers are asked to avoid actions that could negatively affect the availability, integrity, or confidentiality of the site or its users.

In particular, please do not:

• Access, modify, or delete data belonging to other users.
• Attempt to gain persistent access to systems.
• Perform denial-of-service or resource-exhaustion attacks.
• Use social engineering against people or third-party providers.
• Access credentials, private communications, or other sensitive information beyond what is necessary to demonstrate the issue.
• Destroy or alter data.
• Publicly disclose an exploitable vulnerability before it has been given reasonable opportunity to be addressed.

If sensitive information is encountered accidentally while investigating a vulnerability, stop accessing it and report the exposure.

Scope

The primary scope of this policy is:

• The cherryfox.dev domain.
• Subdomains operated as part of the cherryfox.dev domain.
• Public-facing services directly operated by me and exposed through the cherryfox.dev domain or its subdomains.

Third-party services and infrastructure are generally outside the direct scope of this policy. These may include hosting, DNS, CDN, analytics, external authentication, feed, badge, and other third-party services.

A vulnerability in a third-party service should normally be reported to the provider responsible for that service.

Out of Scope

The following generally do not constitute security vulnerabilities on their own:

• Missing security headers without a demonstrated security impact.
• Best-practice recommendations without an exploitable vulnerability.
• Automated scanner findings without evidence of impact.
• Self-XSS requiring the victim to execute attacker-controlled code themselves.
• Issues that only affect outdated or unsupported browsers.
• Denial-of-service testing.
• Spam, phishing, or content submitted through intentionally public functionality.

This list is not exhaustive. Reports are considered based on their actual security impact.

Disclosure Timeline

There is no fixed remediation deadline or guaranteed resolution time. I will aim to acknowledge reports and investigate them as reasonably as possible.

Please allow reasonable time for investigation and remediation before publicly disclosing a vulnerability.

Safe Harbour

Good-faith security research is welcome.

Researchers who follow this policy, avoid accessing or modifying data unnecessarily, and stop testing when a vulnerability has been sufficiently demonstrated will be treated as acting in good faith.

Nothing on this page grants permission to violate applicable law or the terms of third-party services.

security.txt

A machine-readable security contact and disclosure policy is also available at:

security.txt

Other Resources

• Site Resources
• AI Safety information

Discovery

• robots.txt
• Sitemap

AI and LLMs

• llms.txt
• llms-full.txt
• ai.txt

Security

• security.txt
• ai-safety.txt

Feeds

• Atom
• RSS

Metadata

• humans.txt