Plugin on Producthunt daily

claude-hud

Sat, 21 Mar 2026 15:38:03 +0800

jarrodwatts/claude-hud

Claude HUD

A Claude Code plugin that shows what’s happening — context usage, active tools, running agents, and todo progress. Always visible below your input.

Install

Inside a Claude Code instance, run the following commands:

Step 1: Add the marketplace

`1`	`/plugin marketplace add jarrodwatts/claude-hud`

Step 2: Install the plugin

⚠️ Linux users: Click here first

On Linux, /tmp is often a separate filesystem (tmpfs), which causes plugin installation to fail with:

`1`	`EXDEV: cross-device link not permitted`

Fix: Set TMPDIR before installing:

`1`	`mkdir -p ~/.cache/tmp && TMPDIR=~/.cache/tmp claude`

Then run the install command below in that session. This is a Claude Code platform limitation.

`1`	`/plugin install claude-hud`

Step 3: Configure the statusline

`1`	`/claude-hud:setup`

Done! Restart Claude Code to load the new statusLine config, then the HUD will appear.

What is Claude HUD?

Claude HUD gives you better insights into what’s happening in your Claude Code session.

What You See	Why It Matters
Project path	Know which project you’re in (configurable 1-3 directory levels)
Context health	Know exactly how full your context window is before it’s too late
Tool activity	Watch Claude read, edit, and search files as it happens
Agent tracking	See which subagents are running and what they’re doing
Todo progress	Track task completion in real-time

What You See

Default (2 lines)

1
2

[Opus | Max] │ my-project git:(main*)
Context █████░░░░░ 45% │ Usage ██░░░░░░░░ 25% (1h 30m / 5h)

Line 1 — Model, plan name (or Bedrock), project path, git branch
Line 2 — Context bar (green → yellow → red) and usage rate limits

Optional lines (enable via `/claude-hud:configure`)

1
2
3

◐ Edit: auth.ts | ✓ Read ×3 | ✓ Grep ×2        ← Tools activity
◐ explore [haiku]: Finding auth code (2m 15s)    ← Agent status
▸ Fix authentication bug (2/5)                   ← Todo progress

How It Works

Claude HUD uses Claude Code’s native statusline API — no separate window, no tmux required, works in any terminal.

1
2

Claude Code → stdin JSON → claude-hud → stdout → displayed in your terminal
           ↘ transcript JSONL (tools, agents, todos)

Key features:

Native token data from Claude Code (not estimated)
Scales with Claude Code’s reported context window size, including newer 1M-context sessions
Parses the transcript for tool/agent activity
Updates every ~300ms

Configuration

Customize your HUD anytime:

`1`	`/claude-hud:configure`

The guided flow handles layout and display toggles. Advanced overrides such as custom colors and thresholds are preserved there, but you set them by editing the config file directly:

First time setup: Choose a preset (Full/Essential/Minimal), then fine-tune individual elements
Customize anytime: Toggle items on/off, adjust git display style, switch layouts
Preview before saving: See exactly how your HUD will look before committing changes

Presets

Preset	What’s Shown
Full	Everything enabled — tools, agents, todos, git, usage, duration
Essential	Activity lines + git status, minimal info clutter
Minimal	Core only — just model name and context bar

After choosing a preset, you can turn individual elements on or off.

Manual Configuration

Edit ~/.claude/plugins/claude-hud/config.json directly for advanced settings such as colors.*, pathLevels, and threshold overrides. Running /claude-hud:configure preserves those manual settings.

Options

Option	Type	Default	Description
`lineLayout`	string	`expanded`	Layout: `expanded` (multi-line) or `compact` (single line)
`pathLevels`	1-3	1	Directory levels to show in project path
`elementOrder`	string[]	`["project","context","usage","environment","tools","agents","todos"]`	Expanded-mode element order. Omit entries to hide them in expanded mode.
`gitStatus.enabled`	boolean	true	Show git branch in HUD
`gitStatus.showDirty`	boolean	true	Show `*` for uncommitted changes
`gitStatus.showAheadBehind`	boolean	false	Show `↑N ↓N` for ahead/behind remote
`gitStatus.showFileStats`	boolean	false	Show file change counts `!M +A ✘D ?U`
`display.showModel`	boolean	true	Show model name `[Opus]`
`display.showContextBar`	boolean	true	Show visual context bar `████░░░░░░`
`display.contextValue`	`percent` \| `tokens` \| `remaining`	`percent`	Context display format (`45%`, `45k/200k`, or `55%` remaining)
`display.showConfigCounts`	boolean	false	Show CLAUDE.md, rules, MCPs, hooks counts
`display.showDuration`	boolean	false	Show session duration `⏱️ 5m`
`display.showSpeed`	boolean	false	Show output token speed `out: 42.1 tok/s`
`display.showUsage`	boolean	true	Show usage limits (Pro/Max/Team only)
`display.usageBarEnabled`	boolean	true	Display usage as visual bar instead of text
`display.sevenDayThreshold`	0-100	80	Show 7-day usage when >= threshold (0 = always)
`display.showTokenBreakdown`	boolean	true	Show token details at high context (85%+)
`display.showTools`	boolean	false	Show tools activity line
`display.showAgents`	boolean	false	Show agents activity line
`display.showTodos`	boolean	false	Show todos progress line
`display.showSessionName`	boolean	false	Show session slug or custom title from `/rename`
`usage.cacheTtlSeconds`	number	60	How long (seconds) to cache a successful usage API response
`usage.failureCacheTtlSeconds`	number	15	How long (seconds) to cache a failed usage API response before retrying
`colors.context`	color name	`green`	Base color for the context bar and context percentage
`colors.usage`	color name	`brightBlue`	Base color for usage bars and percentages below warning thresholds
`colors.warning`	color name	`yellow`	Warning color for context thresholds and usage warning text
`colors.usageWarning`	color name	`brightMagenta`	Warning color for usage bars and percentages near their threshold
`colors.critical`	color name	`red`	Critical color for limit-reached states and critical thresholds

Supported color names: red, green, yellow, magenta, cyan, brightBlue, brightMagenta.

Usage Limits (Pro/Max/Team)

Usage display is enabled by default for Claude Pro, Max, and Team subscribers. It shows your rate limit consumption on line 2 alongside the context bar.

The 7-day percentage appears when above the display.sevenDayThreshold (default 80%):

`1`	`Context █████░░░░░ 45% │ Usage ██░░░░░░░░ 25% (1h 30m / 5h) \| ██████████ 85% (2d / 7d)`

To disable, set display.showUsage to false.

Requirements:

Claude Pro, Max, or Team subscription (not available for API users)
OAuth credentials from Claude Code (created automatically when you log in)

Troubleshooting: If usage doesn’t appear:

Ensure you’re logged in with a Pro/Max/Team account (not API key)
Check display.showUsage is not set to false in config
API users see no usage display (they have pay-per-token, not rate limits)
AWS Bedrock models display Bedrock and hide usage limits (usage is managed in AWS)
Non-default ANTHROPIC_BASE_URL / ANTHROPIC_API_BASE_URL settings skip usage display, because the Anthropic OAuth usage API may not apply
If you are behind a proxy, set HTTPS_PROXY (or HTTP_PROXY/ALL_PROXY) and optional NO_PROXY
For high-latency environments, increase usage API timeout with CLAUDE_HUD_USAGE_TIMEOUT_MS (milliseconds)

Example Configuration

{
  "lineLayout": "expanded",
  "pathLevels": 2,
  "elementOrder": ["project", "tools", "context", "usage", "environment", "agents", "todos"],
  "gitStatus": {
    "enabled": true,
    "showDirty": true,
    "showAheadBehind": true,
    "showFileStats": true
  },
  "display": {
    "showTools": true,
    "showAgents": true,
    "showTodos": true,
    "showConfigCounts": true,
    "showDuration": true
  },
  "colors": {
    "context": "cyan",
    "usage": "cyan",
    "warning": "yellow",
    "usageWarning": "magenta",
    "critical": "red"
  },
  "usage": {
    "cacheTtlSeconds": 120,
    "failureCacheTtlSeconds": 30
  }
}

Display Examples

1 level (default): [Opus] │ my-project git:(main)

2 levels: [Opus] │ apps/my-project git:(main)

3 levels: [Opus] │ dev/apps/my-project git:(main)

With dirty indicator: [Opus] │ my-project git:(main*)

With ahead/behind: [Opus] │ my-project git:(main ↑2 ↓1)

With file stats: [Opus] │ my-project git:(main* !3 +1 ?2)

! = modified files, + = added/staged, ✘ = deleted, ? = untracked
Counts of 0 are omitted for cleaner display

Troubleshooting

Config not applying?

Check for JSON syntax errors: invalid JSON silently falls back to defaults
Ensure valid values: pathLevels must be 1, 2, or 3; lineLayout must be expanded or compact
Delete config and run /claude-hud:configure to regenerate

Git status missing?

Verify you’re in a git repository
Check gitStatus.enabled is not false in config

Tool/agent/todo lines missing?

These are hidden by default — enable with showTools, showAgents, showTodos in config
They also only appear when there’s activity to show

HUD not appearing after setup?

Restart Claude Code so it picks up the new statusLine config
On macOS, fully quit Claude Code and run claude again in your terminal

Requirements

Claude Code v1.0.80+
Node.js 18+ or Bun

Development

git clone https://github.com/jarrodwatts/claude-hud
cd claude-hud
npm ci && npm run build
npm test

See CONTRIBUTING.md for guidelines.

License

MIT — see LICENSE

Star History

eslint

Wed, 24 Sep 2025 15:28:00 +0800

eslint/eslint

ESLint

ESLint is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. In many ways, it is similar to JSLint and JSHint with a few exceptions:

ESLint uses Espree for JavaScript parsing.
ESLint uses an AST to evaluate patterns in code.
ESLint is completely pluggable, every single rule is a plugin and you can add more at runtime.

Installation and Usage

Prerequisites: Node.js (^18.18.0, ^20.9.0, or >=21.1.0) built with SSL support. (If you are using an official Node.js distribution, SSL is always built in.)

You can install and configure ESLint using this command:

`1`	`npm init @eslint/config@latest`

After that, you can run ESLint on any file or directory like this:

`1`	`npx eslint yourfile.js`

pnpm Installation

To use ESLint with pnpm, we recommend setting up a .npmrc file with at least the following settings:

1
2

auto-install-peers=true
node-linker=hoisted

This ensures that pnpm installs dependencies in a way that is more compatible with npm and is less likely to produce errors.

Configuration

You can configure rules in your eslint.config.js files as in this example:

import { defineConfig } from "eslint/config";

export default defineConfig([
	{
		files: ["**/*.js", "**/*.cjs", "**/*.mjs"],
		rules: {
			"prefer-const": "warn",
			"no-constant-binary-expression": "error",
		},
	},
]);

The names "prefer-const" and "no-constant-binary-expression" are the names of rules in ESLint. The first value is the error level of the rule and can be one of these values:

"off" or 0 - turn the rule off
"warn" or 1 - turn the rule on as a warning (doesn’t affect exit code)
"error" or 2 - turn the rule on as an error (exit code will be 1)

The three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the configuration docs).

Version Support

The ESLint team provides ongoing support for the current version and six months of limited support for the previous version. Limited support includes critical bug fixes, security issues, and compatibility issues only.

ESLint offers commercial support for both current and previous versions through our partners, Tidelift and HeroDevs.

See Version Support for more details.

Code of Conduct

ESLint adheres to the OpenJS Foundation Code of Conduct.

Filing Issues

Before filing an issue, please be sure to read the guidelines for what you’re reporting:

Frequently Asked Questions

Does ESLint support JSX?

Yes, ESLint natively supports parsing JSX syntax (this must be enabled in configuration). Please note that supporting JSX syntax is not the same as supporting React. React applies specific semantics to JSX syntax that ESLint doesn’t recognize. We recommend using eslint-plugin-react if you are using React and want React semantics.

Does Prettier replace ESLint?

No, ESLint and Prettier have different jobs: ESLint is a linter (looking for problematic patterns) and Prettier is a code formatter. Using both tools is common, refer to Prettier’s documentation to learn how to configure them to work well with each other.

What ECMAScript versions does ESLint support?

ESLint has full support for ECMAScript 3, 5, and every year from 2015 up until the most recent stage 4 specification (the default). You can set your desired ECMAScript syntax and other settings (like global variables) through configuration.

What about experimental features?

ESLint’s parser only officially supports the latest final ECMAScript standard. We will make changes to core rules in order to avoid crashes on stage 3 ECMAScript syntax proposals (as long as they are implemented using the correct experimental ESTree syntax). We may make changes to core rules to better work with language extensions (such as JSX, Flow, and TypeScript) on a case-by-case basis.

In other cases (including if rules need to warn on more or fewer cases due to new syntax, rather than just not crashing), we recommend you use other parsers and/or rule plugins. If you are using Babel, you can use @babel/eslint-parser and @babel/eslint-plugin to use any option available in Babel.

Once a language feature has been adopted into the ECMAScript standard (stage 4 according to the TC39 process), we will accept issues and pull requests related to the new feature, subject to our contributing guidelines. Until then, please use the appropriate parser and plugin(s) for your experimental feature.

Which Node.js versions does ESLint support?

ESLint updates the supported Node.js versions with each major release of ESLint. At that time, ESLint’s supported Node.js versions are updated to be:

The most recent maintenance release of Node.js
The lowest minor version of the Node.js LTS release that includes the features the ESLint team wants to use.
The Node.js Current release

ESLint is also expected to work with Node.js versions released after the Node.js Current release.

Refer to the Quick Start Guide for the officially supported Node.js versions for a given ESLint release.

Where to ask for help?

Open a discussion or stop by our Discord server.

Why doesn’t ESLint lock dependency versions?

Lock files like package-lock.json are helpful for deployed applications. They ensure that dependencies are consistent between environments and across deployments.

Packages like eslint that get published to the npm registry do not include lock files. npm install eslint as a user will respect version constraints in ESLint’s package.json. ESLint and its dependencies will be included in the user’s lock file if one exists, but ESLint’s own lock file would not be used.

We intentionally don’t lock dependency versions so that we have the latest compatible dependency versions in development and CI that our users get when installing ESLint in a project.

The Twilio blog has a deeper dive to learn more.

Releases

We have scheduled releases every two weeks on Friday or Saturday. You can follow a release issue for updates about the scheduling of any particular release.

Security Policy

ESLint takes security seriously. We work hard to ensure that ESLint is safe for everyone and that security issues are addressed quickly and responsibly. Read the full security policy.

Semantic Versioning Policy

ESLint follows semantic versioning. However, due to the nature of ESLint as a code quality tool, it’s not always clear when a minor or major version bump occurs. To help clarify this for everyone, we’ve defined the following semantic versioning policy for ESLint:

Patch release (intended to not break your lint build)
- A bug fix in a rule that results in ESLint reporting fewer linting errors.
- A bug fix to the CLI or core (including formatters).
- Improvements to documentation.
- Non-user-facing changes such as refactoring code, adding, deleting, or modifying tests, and increasing test coverage.
- Re-releasing after a failed release (i.e., publishing a release that doesn’t work for anyone).
Minor release (might break your lint build)
- A bug fix in a rule that results in ESLint reporting more linting errors.
- A new rule is created.
- A new option to an existing rule that does not result in ESLint reporting more linting errors by default.
- A new addition to an existing rule to support a newly-added language feature (within the last 12 months) that will result in ESLint reporting more linting errors by default.
- An existing rule is deprecated.
- A new CLI capability is created.
- New capabilities to the public API are added (new classes, new methods, new arguments to existing methods, etc.).
- A new formatter is created.
- eslint:recommended is updated and will result in strictly fewer linting errors (e.g., rule removals).
Major release (likely to break your lint build)
- eslint:recommended is updated and may result in new linting errors (e.g., rule additions, most rule option updates).
- A new option to an existing rule that results in ESLint reporting more linting errors by default.
- An existing formatter is removed.
- Part of the public API is removed or changed in an incompatible way. The public API includes:
  - Rule schemas
  - Configuration schema
  - Command-line options
  - Node.js API
  - Rule, formatter, parser, plugin APIs

According to our policy, any minor update may report more linting errors than the previous release (ex: from a bug fix). As such, we recommend using the tilde (~) in package.json e.g. "eslint": "~3.1.0" to guarantee the results of your builds.

License

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Team

These folks keep the project moving and are resources for help.

Technical Steering Committee (TSC)

The people who manage releases, review feature requests, and meet regularly to ensure ESLint is properly maintained.

Nicholas C. Zakas

Francesco Trotta

Milos Djermanovic

Reviewers

The people who review and implement new features.

唯然	Nitin Kumar

Committers

The people who review and fix bugs and help triage issues.

fnx

Josh Goldberg ✨

Tanuj Kanti

루밀LuMir

Website Team

Team members who focus specifically on eslint.org

Amaresh S M

Harish

Percy Ma

LazyVim

Mon, 22 Sep 2025 15:30:38 +0800

LazyVim/LazyVim

Install · Configure · Docs

LazyVim is a Neovim setup powered by 💤 lazy.nvim to make it easy to customize and extend your config. Rather than having to choose between starting from scratch or using a pre-made distro, LazyVim offers the best of both worlds - the flexibility to tweak your config as needed, along with the convenience of a pre-configured setup.

✨ Features

🔥 Transform your Neovim into a full-fledged IDE
💤 Easily customize and extend your config with lazy.nvim
🚀 Blazingly fast
🧹 Sane default settings for options, autocmds, and keymaps
📦 Comes with a wealth of plugins pre-configured and ready to use

⚡️ Requirements

Neovim >= 0.11.2 (needs to be built with LuaJIT)
Git >= 2.19.0 (for partial clones support)
a Nerd Font (optional)
a C compiler for nvim-treesitter. See here

🚀 Getting Started

You can find a starter template for LazyVim here

Try it with Docker

docker run -w /root -it --rm alpine:edge sh -uelic '
  apk add git lazygit fzf curl neovim ripgrep alpine-sdk --update
  git clone https://github.com/LazyVim/starter ~/.config/nvim
  cd ~/.config/nvim
  nvim
'

Install the LazyVim Starter

Make a backup of your current Neovim files:

1
2

mv ~/.config/nvim ~/.config/nvim.bak
mv ~/.local/share/nvim ~/.local/share/nvim.bak

Clone the starter

`1`	`git clone https://github.com/LazyVim/starter ~/.config/nvim`

Remove the .git folder, so you can add it to your own repo later
1

rm -rf ~/.config/nvim/.git
Start Neovim!
1

nvim
Refer to the comments in the files on how to customize LazyVim.

There’s a great video created by @elijahmanor with a walkthrough to get started.

@dusty-phillips wrote a comprehensive book called LazyVim for Ambitious Developers available for free online.

📂 File Structure

The files under config will be automatically loaded at the appropriate time, so you don’t need to require those files manually. LazyVim comes with a set of default config files that will be loaded before your own. See here

You can add your custom plugin specs under lua/plugins/. All files there will be automatically loaded by lazy.nvim

~/.config/nvim
├── lua
│   ├── config
│   │   ├── autocmds.lua
│   │   ├── keymaps.lua
│   │   ├── lazy.lua
│   │   └── options.lua
│   └── plugins
│       ├── spec1.lua
│       ├── **
│       └── spec2.lua
└── init.lua

⚙️ Configuration

Refer to the docs

better-auth

Wed, 23 Jul 2025 15:34:42 +0800

better-auth/better-auth

Better Auth

The most comprehensive authentication library for TypeScript
Learn more »

Discord · Website · Issues

About the Project

Better Auth is framework-agnostic authentication (and authorization) library for TypeScript. It provides a comprehensive set of features out of the box and includes a plugin ecosystem that simplifies adding advanced functionalities with minimal code in short amount of time. Whether you need 2FA, multi-tenant support, or other complex features. It lets you focus on building your actual application instead of reinventing the wheel.

Why Better Auth

Authentication in the TypeScript ecosystem is a half-solved problem. Other open-source libraries often requires a lot of additional code for anything beyond basic authentication. Rather than just pushing third-party services as the solution, I believe we can do better as a community—hence, Better Auth.

Contribution

Better Auth is free and open source project licensed under the MIT License. You are free to do whatever you want with it.

You could help continuing its development by:

Security

If you discover a security vulnerability within Better Auth, please send an e-mail to security@better-auth.com.

All reports will be promptly addressed, and you’ll be credited accordingly.

youtube-music

Wed, 09 Jul 2025 15:30:58 +0800

th-ch/youtube-music

YouTube Music

Read this in other languages: 한국어, Française, Íslenska, Español, Pусский, Українська, Magyar, Português, 日本語

Electron wrapper around YouTube Music featuring:

Native look & feel, aims at keeping the original interface
Framework for custom plugins: change YouTube Music to your needs (style, content, features), enable/disable plugins in one click

Demo Image

Player Screen (album color theme & ambient light)

Content

Features:

Auto confirm when paused (Always Enabled): disable the “Continue Watching?” popup that pause music after a certain time
And more …

Available plugins:

Ad Blocker: Block all ads and tracking out of the box
Album Actions: Adds Undislike, Dislike, Like, and Unlike buttons to apply this to all songs in a playlist or album
Album Color Theme: Applies a dynamic theme and visual effects based on the album color palette
Ambient Mode: Applies a lighting effect by casting gentle colors from the video, into your screen’s background
Audio Compressor: Apply compression to audio (lowers the volume of the loudest parts of the signal and raises the volume of the softest parts)
Blur Navigation Bar: makes navigation bar transparent and blurry
Bypass Age Restrictions: bypass YouTube’s age verification
Captions Selector: Enable captions
Compact Sidebar: Always set the sidebar in compact mode
Crossfade: Crossfade between songs
Disable Autoplay: Makes every song start in “paused” mode
Discord Rich Presence: Show your friends what you listen to with Rich Presence
Downloader: downloads MP3 directly from the interface (youtube-dl)
Equalizer: add filters to boost or cut specific range of frequencies (e.g. bass booster)
Exponential Volume: Makes the volume slider exponential so it’s easier to select lower volumes
In-App Menu: gives bars a fancy, dark look

(see this post if you have problem accessing the menu after enabling this plugin and hide-menu option)
Scrobbler: Adds scrobbling support for Last.fm and ListenBrainz
Lumia Stream: Adds Lumia Stream support
Lyrics Genius: Adds lyrics support for most songs
Music Together: Share a playlist with others. When the host plays a song, everyone else will hear the same song
Navigation: Next/Back navigation arrows directly integrated in the interface, like in your favorite browser
No Google Login: Remove Google login buttons and links from the interface
Notifications: Display a notification when a song starts playing (interactive notifications are available on windows)
Picture-in-picture: allows to switch the app to picture-in-picture mode
Playback Speed: Listen fast, listen slow! Adds a slider that controls song speed
Precise Volume: Control the volume precisely using mousewheel/hotkeys, with a custom hud and customizable volume steps
Shortcuts (& MPRIS): Allows setting global hotkeys for playback (play/pause/next/previous) + disable media osd by overriding media keys + enable Ctrl/CMD + F to search + enable linux mpris support for mediakeys + custom hotkeys for advanced users
Skip Disliked Song: Skips disliked songs
Skip Silences: Automatically skip silenced sections
SponsorBlock: Automatically Skips non-music parts like intro/outro or parts of music videos where the song isn’t playing
Synced Lyrics: Provides synced lyrics to songs, using providers like LRClib.
Taskbar Media Control: Control playback from your Windows taskbar
TouchBar: Custom TouchBar layout for macOS
Tuna OBS: Integration with OBS’s plugin Tuna
Unobtrusive Player: Prevents the player from popping up when playing a song
Video Quality Changer: Allows changing the video quality with a button on the video overlay
Video Toggle: Adds a button to switch between Video/Song mode. can also optionally remove the whole video tab
Visualizer: Different music visualizers

Translation

You can help with translation on Hosted Weblate.

Download

You can check out the latest release to quickly find the latest version.

Arch Linux

Install the youtube-music-bin package from the AUR. For AUR installation instructions, take a look at this wiki page.

macOS

You can install the app using Homebrew (see the cask definition):

`1`	`brew install th-ch/youtube-music/youtube-music`

If you install the app manually and get an error “is damaged and can’t be opened.” when launching the app, run the following in the Terminal:

`1`	`/usr/bin/xattr -cr /Applications/YouTube\ Music.app`

Windows

You can use the Scoop package manager to install the youtube-music package from the extras bucket.

1
2

scoop bucket add extras
scoop install extras/youtube-music

Alternately you can use Winget, Windows 11s official CLI package manager to install the th-ch.YouTubeMusic package.

Note: Microsoft Defender SmartScreen might block the installation since it is from an “unknown publisher”. This is also true for the manual installation when trying to run the executable(.exe) after a manual download here on github (same file).

`1`	`winget install th-ch.YouTubeMusic`

How to install without a network connection? (in Windows)

Download the *.nsis.7z file for your device architecture in release page.
- x64 for 64-bit Windows
- ia32 for 32-bit Windows
- arm64 for ARM64 Windows
Download installer in release page. (*-Setup.exe)
Place them in the same directory.
Run the installer.

Themes

You can load CSS files to change the look of the application (Options > Visual Tweaks > Themes).

Some predefined themes are available in https://github.com/kerichdev/themes-for-ytmdesktop-player.

Dev

git clone https://github.com/th-ch/youtube-music
cd youtube-music
pnpm install --frozen-lockfile
pnpm dev

Build your own plugins

Using plugins, you can:

manipulate the app - the BrowserWindow from electron is passed to the plugin handler
change the front by manipulating the HTML/CSS

Creating a plugin

Create a folder in src/plugins/YOUR-PLUGIN-NAME:

index.ts: the main file of the plugin

import style from './style.css?inline'; // import style as inline

import { createPlugin } from '@/utils';

export default createPlugin({
  name: 'Plugin Label',
  restartNeeded: true, // if value is true, ytmusic show restart dialog
  config: {
    enabled: false,
  }, // your custom config
  stylesheets: [style], // your custom style,
  menu: async ({ getConfig, setConfig }) => {
    // All *Config methods are wrapped Promise<T>
    const config = await getConfig();
    return [
      {
        label: 'menu',
        submenu: [1, 2, 3].map((value) => ({
          label: `value ${value}`,
          type: 'radio',
          checked: config.value === value,
          click() {
            setConfig({ value });
          },
        })),
      },
    ];
  },
  backend: {
    start({ window, ipc }) {
      window.maximize();

      // you can communicate with renderer plugin
      ipc.handle('some-event', () => {
        return 'hello';
      });
    },
    // it fired when config changed
    onConfigChange(newConfig) { /* ... */ },
    // it fired when plugin disabled
    stop(context) { /* ... */ },
  },
  renderer: {
    async start(context) {
      console.log(await context.ipc.invoke('some-event'));
    },
    // Only renderer available hook
    onPlayerApiReady(api: YoutubePlayer, context: RendererContext) {
      // set plugin config easily
      context.setConfig({ myConfig: api.getVolume() });
    },
    onConfigChange(newConfig) { /* ... */ },
    stop(_context) { /* ... */ },
  },
  preload: {
    async start({ getConfig }) {
      const config = await getConfig();
    },
    onConfigChange(newConfig) {},
    stop(_context) {},
  },
});

Common use cases

injecting custom CSS: create a style.css file in the same folder then:

// index.ts
import style from './style.css?inline'; // import style as inline

import { createPlugin } from '@/utils';

export default createPlugin({
  name: 'Plugin Label',
  restartNeeded: true, // if value is true, ytmusic will show a restart dialog
  config: {
    enabled: false,
  }, // your custom config
  stylesheets: [style], // your custom style
  renderer() {} // define renderer hook
});

If you want to change the HTML:

import { createPlugin } from '@/utils';

export default createPlugin({
  name: 'Plugin Label',
  restartNeeded: true, // if value is true, ytmusic will show the restart dialog
  config: {
    enabled: false,
  }, // your custom config
  renderer() {
    // Remove the login button
    document.querySelector(".sign-in-link.ytmusic-nav-bar").remove();
  } // define renderer hook
});

communicating between the front and back: can be done using the ipcMain module from electron. See index.ts file and example in sponsorblock plugin.

Build

Clone the repo
Follow this guide to install pnpm
Run pnpm install --frozen-lockfile to install dependencies
Run pnpm build:OS

pnpm dist:win - Windows
pnpm dist:linux - Linux (amd64)
pnpm dist:linux:deb-arm64 - Linux (arm64 for Debian)
pnpm dist:linux:rpm-arm64 - Linux (arm64 for Fedora)
pnpm dist:mac - macOS (amd64)
pnpm dist:mac:arm64 - macOS (arm64)

Builds the app for macOS, Linux, and Windows, using electron-builder.

Production Preview

`1`	`pnpm start`

Tests

`1`	`pnpm test`

Uses Playwright to test the app.

License

MIT © th-ch

FAQ

If Hide Menu option is on - you can show the menu with the alt key (or ` [backtick] if using the in-app-menu plugin)

Ghost-Downloader-3

Tue, 27 May 2025 15:30:04 +0800

XiaoYouChR/Ghost-Downloader-3

简体中文 | English

[!IMPORTANT] Due to the developer’s preparation for the college entrance exam (Gaokao), project updates are temporarily suspended 😭 Join QQ group 531928387 for latest updates

[!NOTE] The project is still in its early stages, and there is still a lot of shortcomings.

[!TIP] If you want to use Ghost-Downloader-3 on Windows 7, please download the version v3.5.8-Portable.

AI-powered next-generation cross-platform multithreaded downloader

Report Bug · Request Feature

About The Project

A downloader developed out of personal interest, and my first Python project 😣
Originally intended to help a Bilibili Uploader with resource integration 😵‍💫
Features include IDM-like intelligent chunking without file merging, and AI-powered smart boost 🚀
Thanks to Python’s🐍 accessibility, the project will support plugins🧩 in the future to maximize Python’s🐍 advantages

Platform	Required Version	Architectures	Compatible
🐧 Linux	`glibc 2.35+`	`x86_64`/`arm64`	✅
🪟 Windows	`7 SP1+`	`x86_64`/`arm64`	✅
🍎 macOS	`11.0+`	`x86_64`/`arm64`	✅

[!TIP] Arch Linux AUR support: Community-maintained packages ghost-downloader-bin and ghost-downloader-git are now available (Maintainer: @zxp19821005)

Roadmap

✅ Global settings
✅ More detailed download information
✅ Scheduled tasks
✅ Browser extension optimization
✅ Global speed limit
✅ Memory optimization
- ✅ Upgrade Qt version
- ✅ Implement HttpClient reuse
- ✅ Replace some multithreading with coroutines
❌ MVC → MVVM upgrade and a new architecture based on events (In progress…see branch: feature/Plugins)
❌ Enhanced task editing (powerful features like binding multiple Clients to one task)
❌ Magnet/BT download (Considering libtorrent implementation)
❌ Powerful plugin system
❌ Powerful browser extension features

Visit Open issues to see all requested features (and known issues).

	Free code signing on Windows provided by SignPath.io, certficate by SignPath Foundation

Contributing

Contributions make the open source community an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion, fork the repo and create a pull request. You can also simply open an issue with the “Enhancement” tag. Don’t forget to give the project a star⭐! Thanks again!

Fork the Project
Create your Feature Branch (git checkout -b feature/AmazingFeature)
Commit your Changes (git commit -m ‘Add some AmazingFeature’)
Push to the Branch (git push origin feature/AmazingFeature)
Open a Pull Request

Thanks to all contributors who have participated in this project!

Screenshots

License

Distributed under the GPL v3.0 License. See LICENSE for more information.

Contact

E-mail - XiaoYouChR@qq.com
QQ Group - 531928387

References

PyQt-Fluent-Widgets Powerful, extensible and beautiful Fluent Design widgets
Httpx A fast and multi-purpose HTTP toolkit
Aiofiles File support for asyncio
Loguru A library which aims to bring enjoyable logging in Python
Nuitka The Python compiler
PySide6 The official Python module
Darkdetect Allow to detect if the user is using Dark Mode on
pyqt5-concurrent A QThreadPool based task concurrency library

Acknowledgments

@zhiyiYo Provided great help for this project!
@一只透明人- Tested almost every version since Ghost-Downloader-1！
@Sky·SuGar Created the project banner！

kickstart.nvim

Wed, 14 May 2025 15:30:02 +0800

nvim-lua/kickstart.nvim

kickstart.nvim

Introduction

A starting point for Neovim that is:

Small
Single-file
Completely Documented

NOT a Neovim distribution, but instead a starting point for your configuration.

Installation

Install Neovim

Kickstart.nvim targets only the latest ‘stable’ and latest ’nightly’ of Neovim. If you are experiencing issues, please make sure you have the latest versions.

Install External Dependencies

External Requirements:

Basic utils: git, make, unzip, C Compiler (gcc)
ripgrep, fd-find
Clipboard tool (xclip/xsel/win32yank or other depending on the platform)
A Nerd Font: optional, provides various icons
- if you have it set vim.g.have_nerd_font in init.lua to true
Emoji fonts (Ubuntu only, and only if you want emoji!) sudo apt install fonts-noto-color-emoji
Language Setup:
- If you want to write Typescript, you need npm
- If you want to write Golang, you will need go
- etc.

[!NOTE] See Install Recipes for additional Windows and Linux specific notes and quick install snippets

Install Kickstart

[!NOTE] Backup your previous configuration (if any exists)

Neovim’s configurations are located under the following paths, depending on your OS:

OS	PATH
Linux, MacOS	`$XDG_CONFIG_HOME/nvim`, `~/.config/nvim`
Windows (cmd)	`%localappdata%\nvim\`
Windows (powershell)	`$env:LOCALAPPDATA\nvim\`

Recommended Step

Fork this repo so that you have your own copy that you can modify, then install by cloning the fork to your machine using one of the commands below, depending on your OS.

[!NOTE] Your fork’s URL will be something like this: https://github.com/<your_github_username>/kickstart.nvim.git

You likely want to remove lazy-lock.json from your fork’s .gitignore file too - it’s ignored in the kickstart repo to make maintenance easier, but it’s recommended to track it in version control.

Clone kickstart.nvim

[!NOTE] If following the recommended step above (i.e., forking the repo), replace nvim-lua with <your_github_username> in the commands below

Linux and Mac

`1`	`git clone https://github.com/nvim-lua/kickstart.nvim.git "${XDG_CONFIG_HOME:-$HOME/.config}"/nvim`

Windows

If you’re using cmd.exe:

`1`	`git clone https://github.com/nvim-lua/kickstart.nvim.git "%localappdata%\nvim"`

If you’re using powershell.exe

`1`	`git clone https://github.com/nvim-lua/kickstart.nvim.git "${env:LOCALAPPDATA}\nvim"`

Post Installation

Start Neovim

nvim

That’s it! Lazy will install all the plugins you have. Use :Lazy to view the current plugin status. Hit q to close the window.

Read The Friendly Documentation

Read through the init.lua file in your configuration folder for more information about extending and exploring Neovim. That also includes examples of adding popularly requested plugins.

[!NOTE] For more information about a particular plugin check its repository’s documentation.

Getting Started

The Only Video You Need to Get Started with Neovim

FAQ

What should I do if I already have a pre-existing Neovim configuration?
- You should back it up and then delete all associated files.
- This includes your existing init.lua and the Neovim files in ~/.local which can be deleted with rm -rf ~/.local/share/nvim/
Can I keep my existing configuration in parallel to kickstart?
- Yes! You can use NVIM_APPNAME=nvim-NAME to maintain multiple configurations. For example, you can install the kickstart configuration in ~/.config/nvim-kickstart and create an alias:
  1
  
  alias nvim-kickstart='NVIM_APPNAME="nvim-kickstart" nvim'
  When you run Neovim using nvim-kickstart alias it will use the alternative config directory and the matching local directory ~/.local/share/nvim-kickstart. You can apply this approach to any Neovim distribution that you would like to try out.
What if I want to “uninstall” this configuration:
- See lazy.nvim uninstall information
Why is the kickstart init.lua a single file? Wouldn’t it make sense to split it into multiple files?
- The main purpose of kickstart is to serve as a teaching tool and a reference configuration that someone can easily use to git clone as a basis for their own. As you progress in learning Neovim and Lua, you might consider splitting init.lua into smaller parts. A fork of kickstart that does this while maintaining the same functionality is available here:
  - kickstart-modular.nvim
- Discussions on this topic can be found here:
  - Restructure the configuration
  - Reorganize init.lua into a multi-file setup

Install Recipes

Below you can find OS specific install instructions for Neovim and dependencies.

After installing all the dependencies continue with the Install Kickstart step.

Windows Installation

Windows with Microsoft C++ Build Tools and CMake

Installation may require installing build tools and updating the run command for `telescope-fzf-native`

See telescope-fzf-native documentation for more details

This requires:

Install CMake and the Microsoft C++ Build Tools on Windows

`1`	`{'nvim-telescope/telescope-fzf-native.nvim', build = 'cmake -S. -Bbuild -DCMAKE_BUILD_TYPE=Release && cmake --build build --config Release && cmake --install build --prefix build' }`

Windows with gcc/make using chocolatey

Alternatively, one can install gcc and make which don't require changing the config, the easiest way is to use choco:

install chocolatey either follow the instructions on the page or use winget, run in cmd as admin:

`1`	`winget install --accept-source-agreements chocolatey.chocolatey`

install all requirements using choco, exit the previous cmd and open a new one so that choco path is set, and run in cmd as admin:

`1`	`choco install -y neovim git ripgrep wget fd unzip gzip mingw make`

WSL (Windows Subsystem for Linux)

wsl --install
wsl
sudo add-apt-repository ppa:neovim-ppa/unstable -y
sudo apt update
sudo apt install make gcc ripgrep unzip git xclip neovim

Linux Install

Ubuntu Install Steps

1
2
3

sudo add-apt-repository ppa:neovim-ppa/unstable -y
sudo apt update
sudo apt install make gcc ripgrep unzip git xclip neovim

Debian Install Steps

sudo apt update
sudo apt install make gcc ripgrep unzip git xclip curl

# Now we install nvim
curl -LO https://github.com/neovim/neovim/releases/latest/download/nvim-linux-x86_64.tar.gz
sudo rm -rf /opt/nvim-linux-x86_64
sudo mkdir -p /opt/nvim-linux-x86_64
sudo chmod a+rX /opt/nvim-linux-x86_64
sudo tar -C /opt -xzf nvim-linux-x86_64.tar.gz

# make it available in /usr/local/bin, distro installs to /usr/bin
sudo ln -sf /opt/nvim-linux-x86_64/bin/nvim /usr/local/bin/

Fedora Install Steps

`1`	`sudo dnf install -y gcc make git ripgrep fd-find unzip neovim`

Arch Install Steps

`1`	`sudo pacman -S --noconfirm --needed gcc make git ripgrep fd unzip neovim`

mason.nvim

Sat, 10 May 2025 15:26:31 +0800

mason-org/mason.nvim

Portable package manager for Neovim that runs everywhere Neovim runs.
Easily install and manage LSP servers, DAP servers, linters, and formatters.

:help mason.nvim

^{Latest version: v2.0.0}

Introduction

:h mason-introduction

mason.nvim is a Neovim plugin that allows you to easily manage external editor tooling such as LSP servers, DAP servers, linters, and formatters through a single interface. It runs everywhere Neovim runs (across Linux, macOS, Windows, etc.), with only a small set of external requirements needed.

Packages are installed in Neovim’s data directory (:h standard-path) by default. Executables are linked to a single bin/ directory, which mason.nvim will add to Neovim’s PATH during setup, allowing seamless access from Neovim builtins (shell, terminal, etc.) as well as other 3rd party plugins.

For a list of all available packages, see https://mason-registry.dev/registry/list.

Screenshots

Requirements

:h mason-requirements

mason.nvim relaxes the minimum requirements by attempting multiple different utilities (for example, wget, curl, and Invoke-WebRequest are all perfect substitutes). The minimum recommended requirements are:

neovim >= 0.10.0
For Unix systems:
- git(1)
- curl(1) or GNU wget(1)
- unzip(1)
- GNU tar (tar(1) or gtar(1) depending on platform)
- gzip(1)
For Windows systems:
- pwsh or powershell
- git
- GNU tar
- One of the following:
  - 7zip
  - peazip
  - archiver
  - winzip
  - WinRAR

Note that mason.nvim will regularly shell out to external package managers, such as cargo and npm. Depending on your personal usage, some of these will also need to be installed. Refer to :checkhealth mason for a full list.

Installation

Packer

1
2
3

use {
    "mason-org/mason.nvim"
}

lazy.nvim

1
2
3

{
    "mason-org/mason.nvim"
}

vim-plug

`1`	`Plug 'mason-org/mason.nvim'`

Setup

:h mason-quickstart

`1`	`require("mason").setup()`

mason.nvim is optimized to load as little as possible during setup. Lazy-loading the plugin, or somehow deferring the setup, is not recommended.

Refer to the Configuration section for information about which settings are available.

Extensions

Refer to the Wiki for a list of 3rd party extensions.

mason-lspconfig.nvim - recommended for usage with lspconfig

Commands

:h mason-commands

:Mason - opens a graphical status window
:MasonUpdate - updates all managed registries
:MasonInstall <package> ... - installs/re-installs the provided packages
:MasonUninstall <package> ... - uninstalls the provided packages
:MasonUninstallAll - uninstalls all packages
:MasonLog - opens the mason.nvim log file in a new tab window

Registries

Mason’s core package registry is located at mason-org/mason-registry. Before any packages can be used, the registry needs to be downloaded. This is done automatically for you when using the different Mason commands (e.g. :MasonInstall), but can also be done manually by using the :MasonUpdate command.

If you’re utilizing Mason’s Lua APIs to access packages, it’s recommended to use the :h mason-registry.refresh() and/or :h mason-registry.update() functions to ensure you have the latest package information before retrieving packages.

Configuration

:h mason-settings

You may optionally configure certain behavior of mason.nvim when calling the .setup() function. Refer to the default configuration for a list of all available settings.

Example:

require("mason").setup({
    ui = {
        icons = {
            package_installed = "✓",
            package_pending = "➜",
            package_uninstalled = "✗"
        }
    }
})

Default configuration

---@class MasonSettings
local DEFAULT_SETTINGS = {
    ---@since 1.0.0
    -- The directory in which to install packages.
    install_root_dir = path.concat { vim.fn.stdpath "data", "mason" },

    ---@since 1.0.0
    -- Where Mason should put its bin location in your PATH. Can be one of:
    -- - "prepend" (default, Mason's bin location is put first in PATH)
    -- - "append" (Mason's bin location is put at the end of PATH)
    -- - "skip" (doesn't modify PATH)
    ---@type '"prepend"' | '"append"' | '"skip"'
    PATH = "prepend",

    ---@since 1.0.0
    -- Controls to which degree logs are written to the log file. It's useful to set this to vim.log.levels.DEBUG when
    -- debugging issues with package installations.
    log_level = vim.log.levels.INFO,

    ---@since 1.0.0
    -- Limit for the maximum amount of packages to be installed at the same time. Once this limit is reached, any further
    -- packages that are requested to be installed will be put in a queue.
    max_concurrent_installers = 4,

    ---@since 1.0.0
    -- [Advanced setting]
    -- The registries to source packages from. Accepts multiple entries. Should a package with the same name exist in
    -- multiple registries, the registry listed first will be used.
    registries = {
        "github:mason-org/mason-registry",
    },

    ---@since 1.0.0
    -- The provider implementations to use for resolving supplementary package metadata (e.g., all available versions).
    -- Accepts multiple entries, where later entries will be used as fallback should prior providers fail.
    -- Builtin providers are:
    --   - mason.providers.registry-api  - uses the https://api.mason-registry.dev API
    --   - mason.providers.client        - uses only client-side tooling to resolve metadata
    providers = {
        "mason.providers.registry-api",
        "mason.providers.client",
    },

    github = {
        ---@since 1.0.0
        -- The template URL to use when downloading assets from GitHub.
        -- The placeholders are the following (in order):
        -- 1. The repository (e.g. "rust-lang/rust-analyzer")
        -- 2. The release version (e.g. "v0.3.0")
        -- 3. The asset name (e.g. "rust-analyzer-v0.3.0-x86_64-unknown-linux-gnu.tar.gz")
        download_url_template = "https://github.com/%s/releases/download/%s/%s",
    },

    pip = {
        ---@since 1.0.0
        -- Whether to upgrade pip to the latest version in the virtual environment before installing packages.
        upgrade_pip = false,

        ---@since 1.0.0
        -- These args will be added to `pip install` calls. Note that setting extra args might impact intended behavior
        -- and is not recommended.
        --
        -- Example: { "--proxy", "https://proxyserver" }
        install_args = {},
    },

    ui = {
        ---@since 1.0.0
        -- Whether to automatically check for new versions when opening the :Mason window.
        check_outdated_packages_on_open = true,

        ---@since 1.0.0
        -- The border to use for the UI window. Accepts same border values as |nvim_open_win()|.
        -- Defaults to `:h 'winborder'` if nil.
        border = nil,

        ---@since 1.11.0
        -- The backdrop opacity. 0 is fully opaque, 100 is fully transparent.
        backdrop = 60,

        ---@since 1.0.0
        -- Width of the window. Accepts:
        -- - Integer greater than 1 for fixed width.
        -- - Float in the range of 0-1 for a percentage of screen width.
        width = 0.8,

        ---@since 1.0.0
        -- Height of the window. Accepts:
        -- - Integer greater than 1 for fixed height.
        -- - Float in the range of 0-1 for a percentage of screen height.
        height = 0.9,

        icons = {
            ---@since 1.0.0
            -- The list icon to use for installed packages.
            package_installed = "◍",
            ---@since 1.0.0
            -- The list icon to use for packages that are installing, or queued for installation.
            package_pending = "◍",
            ---@since 1.0.0
            -- The list icon to use for packages that are not installed.
            package_uninstalled = "◍",
        },

        keymaps = {
            ---@since 1.0.0
            -- Keymap to expand a package
            toggle_package_expand = "<CR>",
            ---@since 1.0.0
            -- Keymap to install the package under the current cursor position
            install_package = "i",
            ---@since 1.0.0
            -- Keymap to reinstall/update the package under the current cursor position
            update_package = "u",
            ---@since 1.0.0
            -- Keymap to check for new version for the package under the current cursor position
            check_package_version = "c",
            ---@since 1.0.0
            -- Keymap to update all installed packages
            update_all_packages = "U",
            ---@since 1.0.0
            -- Keymap to check which installed packages are outdated
            check_outdated_packages = "C",
            ---@since 1.0.0
            -- Keymap to uninstall a package
            uninstall_package = "X",
            ---@since 1.0.0
            -- Keymap to cancel a package installation
            cancel_installation = "<C-c>",
            ---@since 1.0.0
            -- Keymap to apply language filter
            apply_language_filter = "<C-f>",
            ---@since 1.1.0
            -- Keymap to toggle viewing package installation log
            toggle_package_install_log = "<CR>",
            ---@since 1.8.0
            -- Keymap to toggle the help view
            toggle_help = "g?",
        },
    },
}

^{👋 didn't find what you were looking for? Try looking in the help docs :help mason.nvim!}

ImHex

Wed, 23 Apr 2025 15:33:14 +0800

WerWolv/ImHex

A Hex Editor for Reverse Engineers, Programmers and people who value their retinas when working at 3 AM.
/ˈɪmhɛks/

Supporting

If you like my work, please consider supporting me on GitHub Sponsors, Patreon or PayPal. Thanks a lot!

Screenshots

More Screenshots

Features

Featureful hex view

Byte patching
Patch management
Infinite Undo/Redo
“Copy bytes as…”
- Bytes
- Hex string
- C, C++, C#, Rust, Python, Java & JavaScript array
- ASCII-Art hex view
- HTML self-contained div
Simple string and hex search
Goto from start, end and current cursor position
Colorful highlighting
- Configurable foreground highlighting rules
- Background highlighting using patterns, find results and bookmarks
Displaying data as a list of many different types
- Hexadecimal integers (8, 16, 32, 64 bit)
- Signed and unsigned decimal integers (8, 16, 32, 64 bit)
- Floats (16, 32, 64 bit)
- RGBA8 Colors
- HexII
- Binary
Decoding data as ASCII and custom encodings
- Built-in support for UTF-8, UTF-16, ShiftJIS, most Windows encodings and many more
Paged data view

Custom C++-like pattern language for parsing highlighting a file's content

Automatic loading based on MIME types and magic values
Arrays, pointers, structs, unions, enums, bitfields, namespaces, little and big endian support, conditionals and much more!
Useful error messages, syntax highlighting and error marking
Support for visualizing many different types of data
- Images
- Audio
- 3D Models
- Coordinates
- Time stamps

Theming support

Doesn’t burn out your retinas when used in late-night sessions
- Dark mode by default, but a light mode is available as well
Customizable colors and styles for all UI elements through shareable theme files
Support for custom fonts

Importing and Exporting data

Base64 files
IPS and IPS32 patches
Markdown reports

Data Inspector

Interpreting data as many different types with endianness, decimal, hexadecimal and octal support and bit inversion
- Unsigned and signed integers (8, 16, 24, 32, 48, 64 bit)
- Floats (16, 32, 64 bit)
- Signed and Unsigned LEB128
- ASCII, Wide and UTF-8 characters and strings
- time32_t, time64_t, DOS date and time
- GUIDs
- RGBA8 and RGB65 Colors
Copying and modifying bytes through the inspector
Adding new data types through the pattern language
Support for hiding rows that aren’t used

Node-based data pre-processor

Modify, decrypt and decode data before it’s being displayed in the hex editor
Modify data without touching the underlying source
Support for adding custom nodes

Loading data from many different data sources

Local Files
- Support for huge files with fast and efficient loading
Raw Disks
- Loading data from raw disks and partitions
GDB Server
- Access the RAM of a running process or embedded devices through GDB
Intel Hex and Motorola SREC data
Process Memory
- Inspect the entire address space of a running process

Data searching

Support for searching the entire file or only a selection
String extraction
- Option to specify minimum length and character set (lower case, upper case, digits, symbols)
- Option to specify encoding (ASCII, UTF-8, UTF-16 big and little endian)
Sequence search
- Search for a sequence of bytes or characters
- Option to ignore character case
Regex search
- Search for strings using regular expressions
Binary Pattern
- Search for sequences of bytes with optional wildcards
Numeric Value search
- Search for signed/unsigned integers and floats
- Search for ranges of values
- Option to specify size and endianness
- Option to ignore unaligned values

Data hashing support

Many different algorithms available
- CRC8, CRC16 and CRC32 with custom initial values and polynomials
  - Many default polynomials available
- MD5
- SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
- Adler32
- AP
- BKDR
- Bernstein, Bernstein1
- DEK, DJB, ELF, FNV1, FNV1a, JS, PJW, RS, SDBM
- OneAtTime, Rotating, ShiftAndXor, SuperFast
- Murmur2_32, MurmurHash3_x86_32, MurmurHash3_x86_128, MurmurHash3_x64_128
- SipHash64, SipHash128
- XXHash32, XXHash64
- Tiger, Tiger2
- Blake2B, Blake2S
Hashing of specific regions of the loaded data
Hashing of arbitrary strings

Diffing support

Compare data of different data sources
Difference highlighting
Table view of differences

Integrated disassembler

Support for all architectures supported by Capstone
- ARM32 (ARM, Thumb, Cortex-M, AArch32)
- ARM64
- MIPS (MIPS32, MIPS64, MIPS32R6, Micro)
- x86 (16-bit, 32-bit, 64-bit)
- PowerPC (32-bit, 64-bit)
- SPARC
- IBM SystemZ
- xCORE
- M68K
- TMS320C64X
- M680X
- Ethereum
- RISC-V
- WebAssembly
- MOS65XX
- Berkeley Packet Filter

Bookmarks

Support for bookmarks with custom names and colors
Highlighting of bookmarked region in the hex editor
Jump to bookmarks
Open content of bookmark in a new tab
Add comments to bookmarks

Featureful data analyzer and visualizer

File magic-based file parser and MIME type database
Byte type distribution graph
Entropy graph
Highest and average entropy
Encrypted / Compressed file detection
Digram and Layered distribution graphs

YARA Rule support

Scan a file for vulnerabilities with official yara rules
Highlight matches in the hex editor
Jump to matches
Apply multiple rules at once

Helpful tools

Itanium, MSVC, Rust and D-Lang demangler based on LLVM
ASCII table
Regex replacer
Mathematical expression evaluator (Calculator)
Graphing calculator
Hexadecimal Color picker with support for many different formats
Base converter
Byte swapper
UNIX Permissions calculator
Wikipedia term definition finder
File utilities
- File splitter
- File combiner
- File shredder
IEEE754 Float visualizer
Division by invariant multiplication calculator
TCP Client/Server
Euclidean algorithm calculator

Built-in Content updater

Download all files found in the database directly from within ImHex
- Pattern files for decoding various file formats
- Libraries for the pattern language
- Magic files for file type detection
- Custom data processor nodes
- Custom encodings
- Custom themes
- Yara rules

Modern Interface

Support for multiple workspaces
Support for custom layouts
Detachable windows

Easy to get started

Support for many different languages
Simplified mode for beginners
Extensive documentation
Many example files available on the Database
Achievements guiding you through the features of ImHex
Interactive tutorials

Pattern Language

The Pattern Language is the completely custom programming language developed for ImHex. It allows you to define structures and data types in a C-like syntax and then use them to parse and highlight a file’s content.

Source Code: Link
Documentation: Link

Database

For format patterns, libraries, magic and constant files, check out the ImHex-Patterns repository.

Feel free to PR your own files there as well!

Requirements

To use ImHex, the following minimal system requirements need to be met.

[!IMPORTANT] ImHex requires a GPU with OpenGL 3.0 support in general. There are releases available (with the -NoGPU suffix) that are software rendered and don’t require a GPU, however these can be a lot slower than the GPU accelerated versions.

If possible at all, make ImHex use the dedicated GPU on your system instead of the integrated one. ImHex will usually run fine with integrated GPUs as well but certain Intel HD GPU drivers on Windows are known to cause graphical artifacts.

OS:
- Windows: Windows 7 or higher (Windows 10/11 recommended)
- macOS: macOS 13 (Ventura) or higher,
  - Lower versions should still work too, but you’ll need to compile ImHex yourself. The release binaries will NOT work.
  - The macOS build is not signed and will require you to manually allow them in the Security & Privacy settings.
- Linux: “Modern” Linux. The following distributions have official releases available. Other distros are supported through the AppImage and Flatpak releases.
  - Ubuntu and Debian
  - Fedora
  - RHEL/AlmaLinux
  - Arch Linux
  - Basically any other distro will work as well when compiling ImHex from sources.
CPU: Officially supported are x86_64 and ARM64, though any Little Endian 64 bit CPU should work.
GPU: OpenGL 3.0 or higher
- Integrated Intel HD iGPUs are supported, however certain drivers are known to cause various graphical artifacts, especially on Windows. Use at your own risk.
- In case you don’t have a GPU available, there are software rendered releases available for Windows and macOS
RAM: ~150MiB, more is required for more complex analysis
Storage: 150MiB

Installing

Information on how to install ImHex can be found in the Install guide

Compiling

To compile ImHex on any platform, GCC (or Clang) is required with a version that supports C++23 or higher. Windows and Linux releases are being built using latest available GCC. MacOS releases are being built using latest available LLVM Clang.

Important to note is, the MSVC and AppleClang compilers are both NOT supported since they’re both generally severely outdated and lack features GCC and LLVM Clang have.

[!NOTE] Many dependencies are bundled into the repository using submodules so make sure to clone it using the --recurse-submodules option. All dependencies that aren’t bundled, can be installed using the dependency installer scripts found in the /dist folder.

For more information, check out the Compiling guide.

Contributing

See Contributing

Plugin development

To develop plugins for ImHex, use the following template project to get started. You then have access to the entirety of libimhex as well as the ImHex API and the Content Registry to interact with ImHex or to add new content.

ImHex Plugin Template

Credits

Contributors

iTrooz for getting ImHex onto the Web as well as hundreds of contributions in every part of the project
jumanji144 for huge contributions to the Pattern Language and ImHex’s infrastructure
Mary for her immense help porting ImHex to MacOS and help during development
Roblabla for adding MSI Installer support to ImHex
Mailaender for getting ImHex onto Flathub
Everybody else who has reported issues on Discord or GitHub that I had great conversations with :)

Dependencies

Thanks a lot to ocornut for their amazing Dear ImGui which is used for building the entire interface
- Thanks to epezent for ImPlot used to plot data in various places
- Thanks to Nelarius for ImNodes used as base for the data processor
- Thanks to BalazsJako for ImGuiColorTextEdit used for the pattern language syntax highlighting
Thanks to nlohmann for their json library used for configuration files
Thanks to vitaut for their libfmt library which makes formatting and logging so much better
Thanks to btzy for nativefiledialog-extended and their great support, used for handling file dialogs on all platforms
Thanks to danyspin97 for xdgpp used to handle folder paths on Linux
Thanks to aquynh for capstone which is the base of the disassembly window
Thanks to rxi for microtar used for extracting downloaded store assets
Thanks to VirusTotal for Yara used by the Yara plugin
Thanks to Martinsos for edlib used for sequence searching in the diffing view
Thanks to ron4fun for HashLibPlus which implements every hashing algorithm under the sun
Thanks to mackron for miniaudio used to play audio files
Thanks to all other groups and organizations whose libraries are used in ImHex

License

The biggest part of ImHex is under the GPLv2-only license. Notable exceptions to this are the following parts which are under the LGPLv2.1 license:

/lib/libimhex: The library that allows Plugins to interact with ImHex.
/plugins/ui: The UI plugin library that contains some common UI elements that can be used by other plugins

The reason for this is to allow for proprietary plugins to be developed for ImHex.

Awesome-Dify-Workflow

Fri, 18 Apr 2025 15:28:32 +0800

svcvit/Awesome-Dify-Workflow

Awesome-Dify-Workflow 🚀

Share & Discover Useful Dify Workflows! For personal use & learning.

English | 中文

分享一些好用的 Dify 工作流程，自用、学习两相宜，请使用 Dify 0.13.0 及以上版本导入。已支持多 任务并行、会话变量、表单、echart渲染 相关特性。Agent节点为1.0版本之后功能，请尽可能使用最新版DIFY导入。

所有的 Workflow 基本都可以免费使用，更多 Workflow 收集整理中……

分享群

开了一个分享群，有兴趣可以加入，如果你有关于 workflow 的问题也可以一起讨论。（2025/04/17 更新）

主群都超200了，加群主好友，备注 dify，拉你到人多一些的群。不过微信风控，有时候加不上，可以稍后再试。
当然，也可以加新群，目前人少一点，基本1-2天左右一个群就能满200.

视频教程

最近计划更新一个DIFY使用系列教程，基本上有手就会，里面包含很多我个人使用过程中的一些理解，相信不管你是新手小白，还是企业用户，都会有所收货。

名称	视频	文字摘要版
01课 - DIFY的本地化部署与启动	https://www.youtube.com/watch?v=6LnHVay289w	https://blog.vcvit.me/2025/04/09/01-dify-local-deployment-and-startup/
02课 - DIFY模型配置	https://www.youtube.com/watch?v=4I2DgPR3qDA	https://blog.vcvit.me/2025/04/10/02-dify-model-configuration/
03课 - chatflow和workfow的区别	https://www.youtube.com/watch?v=quEA_7LVWA8	https://blog.vcvit.me/2025/04/11/03-dify-workflow-vs-chatflow/

常见问题

这里总结了一些群里常见的问题，不定期更新，内容不会很多，希望对你有帮助。

AI 流程平台对比——Dify、Fastgpt、Ragflow

dify 有没有国内的镜像源配置呀?

A：我一般把所有image，前面的链接加上 dockerpull.org

sandbox 如何安装pandas这些第三方库？

A：打开 /docker/volumes/sandbox/dependencies/python-requirements.txt 填入需要安装的依赖，重启sandbox即可。

定时任务可以如何处理？我希望定时执行某个流程。

A：可以参考项目 https://github.com/leochen-g/dify-schedule

节点间传递string数据，提示超限制，如何处理

A：修改 .env 中的一段： CODE_MAX_STRING_LENGTH: 1000000 TEMPLATE_TRANSFORM_MAX_LENGTH: 1000000 重启容器

拿到图片URL后能在聊天窗口显示吗，试了下markdown但什么都没显示出来。

A：你的做法是对的，只是你的图片不支持跨域，所以没渲染出来

请教一个问题，知识库上传大文件提出报错，修改配置文件后，还是无法上传大文件，如下是配置文件中修改上传文件地方；

A:nginx 也要改；在.env里面；搜 nginx，应该能找到

知识库永久排队问题

A：修改 .env 中的一段：LOG_FILE=/app/logs/server.log；重启容器

在哪里可以自学Dify?

A：可以参考 https://dify101.com

Dify生成图表有什么好方案？

A：Dify自带了一些绘图功能，包括柱状图、曲线图等。也可以自己写一个Echarts插件，从数据库读取数据并画图。

Dify知识库上传PDF乱码怎么办？

A：可以使用工具将PDF转换成Markdown格式再上传。

DuckDuckGo 翻译现在是不可用了吗

A：应该是服务器挂了代理，但是dify是启在docker里面的，没挂。

探索 Dify 的官方示例应用全部是英文，怎么切换成中文？

A：点击右上角，头像，设置，语言，先切换成其它语言，再切换成中文，即可。

管理员密码忘记了怎么搞？

A：执行下面的指令：docker exec -it docker-api-1 flask reset-password

SANDBOX

sandbox 运行pandas，numpy>2.0，matplotlib，scikit-learn 代码老报错，可以使用我开发的另外一个简单版dify-sandbox-py，这些依赖已经测试可以使用。

DIFY 1.0 插件

dify_plugin_collection 仓库存放着 DIFY 的官方市场插件安装包，方便离线用户自由选择，不定期更新。

如果你希望开发插件，我有2个插件的源码 google翻译、对话Agent 希望可以给你参考。

模型

你可以使用最近火热的deepseek-R1，硅基流动提供免费2000万Tokens，如果使用邀请注册，你和我都会获赠免费2000万token的额度：https://cloud.siliconflow.cn/i/MwADckCi
如果你希望体验 OpenAI 或 Anthropic 的模型，可以使用我搭建的服务 CoffBox 的服务配置方式参考如何在Dify中使用CoffBox的服务这个方式仅供个人使用，如果你需要大规模使用，openrouter会是个更好的选择。

参考截图

所有 DSL 都为工作流模式，可以方便的发布为工具后，嵌入 ChatBot 流程。工作流会包含基础的输入、条件判断、变量聚合器、输出等内容。

DSL 目录

你可以参考下面每个 yml 的描述，找到你需要的 Workflow，然后在 DSL 文件夹中找到对应的文件，复制文件的 URL，导入自己的 Dify 账号即可。

2025-04-17更新

文件	描述	来源
`sanic-web`	这是一个使用DIFY作为服务层的数据库问答项目，项目有独立的web交互界面，请访问 https://github.com/apconw/sanic-web 查看详情。项目完成度很高，按照文档一步步操作即可启动。使用ollama的qwen和deepseek模型，即可获得不错的效果。	sanic-web

2025-04-16更新

文件	描述	来源
`MCP-amap.yml`	使用MCP Agent 策略进行MCP工具的调用示例，MCP使用高德地图提供的在线服务，你可以先注册一个开发者账号，申请一个免费的Key。替换下图中马赛克部分这里还有一个官方示例Dify MCP 插件指南：一键连接 Zapier，轻松调用 7000+ App 工具	@svcvit

2025-04-07更新

文件	描述	来源
`图文知识库`	如果你希望检索知识库后，是图配文的效果，你需要在知识库里加上图片的远程连接即可。可参考本示例，包含一个markdown文件。	@svcvit

2025-03-21更新

文件	描述	来源
`Demo-tod_agent.yml`	使用dify 1.0 的Agent节点，针对对话场景优化的Agent策略，例如：多轮对话、上下文理解、信息收集等。https://marketplace.dify.ai/plugins/svcvit/agent	@svcvit

2025-02-24更新

文件	描述	来源
`Deep Researcher On Dify .yml`	Deep Researcher 工作流复现方案	@AdamPlatin123

2025-02-17更新

文件	描述	来源
`Agent工具调用.yml`	使用dify 1.0 的Agent节点，使用FC调用不同的工具，进行回复。	@svcvit

2025-01-23更新

文件	描述	来源
`旅行Demo.yml`	使用dify 1.0 的Agent节点，演示旅行信息收集，Tool调用，对话历史上下文存储。将对话消息存入对话变量，纳入Agent的思考上下文。	@svcvit

2025-01-21更新

文件	描述	来源
`春联生成器.yml`	春联生成工具，注意字体需要电脑有，可以按需修改字体。	微信群@Junjie.M
`春联生成器 (“福”到了版本).yml`		微信群@Junjie.M
`完蛋！我被LLM包围了！ .yml`	【完蛋！我被LLM包围了！】借鉴了：https://github.com/modelscope/modelscope/tree/master/examples/apps/llm_riddles	微信群@Junjie.M

2024-12-05更新

文件	描述	来源
`File_read.yml`	使用sandbox读取文件并解析，需要使用dify-sandbox-py，挂在上传目录，这是一个pandas读取csv的示例，具体方法参考右侧来源链接	@svcvit
`runLLMCode.yml`	使用LLM生成的Code，再通过sandbox去执行。因为code节点无法直接引用LLM的代码，所以通过HTTP请求的方式执行，这里有一个分析csv的示例。	@svcvit
`数据分析.7z`	数据分析的示例，可以根据需求查询数据库，生成对应的解读和图表。示例中包括流程文件和flask的服务。	微信群：简单&平凡@

2024-11-29更新

文件	描述	来源
`LanguageConsistencyChecker.yml`	三语言检查器，主要处理翻译的内容优化，它还有一个web端配套	langfixer

2024-11-22更新

文件	描述	来源
`matplotlib.yml`	使用matplotlib画图，将图片输出为base64，再通过回复渲染图片。注意，官方sandbox权限比较复杂，安装完matplotlib也无法使用，请使用dify-sandbox-py	@svcvit
`jieba.yml`	jieba 分词示例，请使用dify-sandbox-py	@svcvit

2024-11-20更新

文件	描述	来源
`json-repair.yml`	大模型输出的JSON格式不标准，少个引号，多个括号，通过这个流程修复为可解析的的JSON	@svcvit

2024-11-15更新

文件	描述	来源
`json_translate.yml`	解析JSON中的需要翻译的内容，使用迭代器进行翻译，再组合成新的JSON，保持原有JSON的结构	@svcvit

2024-11-14更新

文件	描述	来源
`腾讯云SubtitleInfo.yml`	这是一个代码相关的示例，通过腾讯云的授权信息加密，获取需要的内容信息参考。如果你需要使用代码节点，可以参考用法。	微信分享群
`chart_demo.yml`	通过回复内容渲染charts的图表内容。当然你可以可以根据sql查询数据，拼接成需要的内容	@svcvit

2024-11-12更新

文件	描述	来源
`Form表单聊天Demo.yml`	在对话框登录之后有权限访问模型	@svcvit

翻译

文件	描述	来源
`中译英.yml`	通过宝玉的 Prompt，直译->反思->意译，将中文翻译成高质量的英文。	暂无
`DuckDuckGo 翻译+LLM 二次翻译.yml`	与三步翻译类似，但是把第一步的直译变成传统翻译引擎翻译，节省 Token，提高翻译效率，同时提高翻译质量。	暂无
`translation_workflow.yml`	使用吴恩达提出 Agentic Workflow 制作的翻译工具，录入`输入语言`、`目标语言`、`国家`、`原始文本` 4 个参数，提供更细致的翻译结果	translation-agent
`宝玉的英译中优化版.yml`	宝玉的科技文章翻译优化版本，主要优化了提示词和 xml 标签	翻译 GPT 的提示词更新和优化
`全书翻译.yml`	DIFY 官方示例，切分长文本，再迭代器内翻译	DIFY 官方探索内容

工具

文件	描述	来源
`SEO Slug Generator.yml`	给自己的博文生成 url slug，参考来源于宝玉的 X	twitter
`Document_chat_template.yml`	一个通过知识库聊天的模版	Winson-030
`搜索大师.yml`	通过 SearXNG 进行搜索，再通过 jina 获取搜索内容	Winson-030
`标题党创作.yml`	一位爆款网文作家	ghostviper
`文章仿写-单图_多图自动搭配.yml`	文章仿写	ghostviper
`Text to Card Iteration.yml`	自动生成小红书这种卡片。	🔥Dify Workflow-Agent 设计交流 @Arthur
`Dify 运营一条龙.yml`	小红书、抖音、微博、B 站一条龙运营。（2024/11/21更新，主流程已经不能用了，因为图片生成那个服务问题很多，而且限制了分辨率，导致生成图完全不对了，全当看个思路。）	Dify 一键生成多尺寸 Cover 与全平台文案
`Jina Reader Jinja.yml`	一个基于 TavilySearch 和 Jina 的问答流程	🔥Dify Workflow-Agent 设计交流群分享
`llm2o1.cn.yml`	任务拆解→提取步骤→迭代步骤执行→归纳总结→输出结果	@okooo5km
`dify_course_demo.yml`	自动化生成全套教程。	dify_course
`simple-kimi.yml`	简易自制 Kimi	aws-samples
`Claude3 Code Translation.yml`	不同代码种类之间的翻译工作流	aws-samples

聊天机器人

文件	描述	来源
`根据用户的意图进行回复.yml`	根据用户的聊天内容，进行意图判定，根据意图选择不同的工作流路径进行回复，再风格化聊天机器人话术	无
`mem0ai`	一个有记忆的聊天流程，完整代码见来源链接	dify-plugin-mem0ai
`记忆测试.yml`	添加短期记忆，CoT 思维链的示例，自动问答机器人也可以主动触达，根据上下文选择最佳回复	来自微信 svcvit

代码

文件	描述	来源
`Python Coding Prompt.yml`	通过聊天对话方式生成 Python 代码	Sonnet 3.5 for Coding 😍 - System Prompt

使用方法

下载本项目至本地，导入 DLS 文件即可，当然，你可以进行必要的调整，例如模版的调整，或提示词的调整。

nvim-lspconfig

Thu, 17 Apr 2025 15:30:46 +0800

neovim/nvim-lspconfig

nvim-lspconfig

nvim-lspconfig is a “data only” repo, providing basic, default Nvim LSP client configurations for various LSP servers.

View all configs or :help lspconfig-all from Nvim.

Important ⚠️

These configs are best-effort and supported by the community (you). See contributions.
If you found a bug in Nvim LSP (:help lsp), report it to Neovim core.
- Do not report it here. Only configuration data lives here.
This repo only provides configurations. Its programmatic API is deprecated and must not be used externally.
- The “framework” parts (not the configs) of nvim-lspconfig will be upstreamed to Nvim core.

Install

Requires Nvim 0.10 above. Update Nvim and nvim-lspconfig before reporting an issue.

Install nvim-lspconfig using Vim’s “packages” feature:

`1`	`git clone https://github.com/neovim/nvim-lspconfig ~/.config/nvim/pack/nvim/start/nvim-lspconfig`

Or use a 3rd-party plugin manager (consult the documentation for your plugin manager).

Quickstart

Install a language server, e.g. pyright
1

npm i -g pyright
Add the language server setup to your init.lua.
- Nvim 0.11+ (see vim.lsp.config)
  1
  
  vim.lsp.enable('pyright')
- Nvim 0.10 (legacy, not supported)
  1
  
  require'lspconfig'.pyright.setup{}
Ensure your project/workspace contains a root marker as specified in :help lspconfig-all.
Open a code file in Nvim. LSP will attach and provide diagnostics.
1

nvim main.py
Run :checkhealth lsp to see the status or to troubleshoot.

Read :help lspconfig for details. Read :help lspconfig-all for the full list of server-specific details. For servers not on your $PATH (e.g., jdtls, elixirls), you must manually set the cmd parameter, see vim.lsp.config.

Configuration

Nvim sets some default options and mappings when a buffer attaches to LSP (see :help lsp-config). In particular:

'tagfunc'
- Enables “go to definition” capabilities using <C-]> and other tag commands.
'omnifunc'
- Enables (manual) omni mode completion with <C-X><C-O> in Insert mode. For autocompletion, an autocompletion plugin is required.
'formatexpr'
- Enables LSP formatting with gq.
K maps to vim.lsp.buf.hover() in Normal mode.
[d and ]d map to vim.diagnostic.goto_prev() and vim.diagnostic.goto_next(), respectively.
<C-W>d maps to vim.diagnostic.open_float().

Further customization can be achieved using the LspAttach autocommand event. The LspDetach autocommand event can be used to “cleanup” mappings if a buffer becomes detached from an LSP server. See :h LspAttach and :h LspDetach for details and examples. See :h lsp-buf for details on other LSP functions.

Extra settings can be specified for each LSP server:

Nvim 0.11+ (see vim.lsp.config)

vim.lsp.config('rust_analyzer', {
  -- Server-specific settings. See `:help lsp-quickstart`
  settings = {
    ['rust-analyzer'] = {},
  },
})

Nvim 0.10 (legacy, not supported)

local lspconfig = require('lspconfig')
lspconfig.rust_analyzer.setup {
  -- Server-specific settings. See `:help lspconfig-setup`
  settings = {
    ['rust-analyzer'] = {},
  },
}

vim.lsp.config

nvim-lspconfig includes configurations compatible with vim.lsp under lsp/, so servers can be enabled (auto-activated when a filetype is opened) with:

`1`	`vim.lsp.enable('pyright')`

and configured with:

1
2
3

vim.lsp.config('pyright', {
  cmd = { … },
})

which extends the configuration under lsp/. For further information see :help lsp-config.

[!WARNING]
Some servers are currently missing.

Troubleshooting

The most common reasons a language server does not start or attach are:

Language server is not installed. nvim-lspconfig does not install language servers for you. You should be able to run the cmd defined in each server’s Lua module from the command line and see that the language server starts. If the cmd is an executable name instead of an absolute path to the executable, ensure it is on your path.
Missing filetype plugins. Certain languages are not detecting by Vim/Nvim because they have not yet been added to the filetype detection system. Ensure :set ft? shows the filetype and not an empty value.
Not triggering root detection. Some language servers will only start if it is opened in a directory, or child directory, containing a file which signals the root of the project. Most of the time, this is a .git folder, but each server defines the root config in the lua file. See doc/configs.md or the source for the list of root directories.
You must pass capabilities for each setup {} if you want these to take effect.
Do not call setup {} twice for the same server. The second call to setup {} will overwrite the first.

Bug reports

If you found a bug with LSP functionality, report it to Neovim core.

Before reporting a bug, check your logs and the output of :LspInfo. Add the following to your init.vim to enable logging:

`1`	`vim.lsp.set_log_level("debug")`

Attempt to run the language server, and open the log with:

:LspLog

Most of the time, the reason for failure is present in the logs.

Commands

:LspInfo (alias to :checkhealth vim.lsp) shows the status of active and configured language servers.
:LspStart <config_name> Start the requested server name. Will only successfully start if the command detects a root directory matching the current config. Pass autostart = false to your .setup{} call for a language server if you would like to launch clients solely with this command. Defaults to all servers matching current buffer filetype.
:LspStop [<client_id_or_name> ...] Stops the given server(s). Defaults to stopping all servers active on the current buffer. To force stop add ++force
:LspRestart [<client_id_or_name> ...] Restarts the given client(s), and attempts to reattach to all previously attached buffers.

Contributions

If a language server is missing from configs.md, contributing a new configuration for it helps others, especially if the server requires special setup. Follow these steps:

Read CONTRIBUTING.md.
Create a new file at lsp/SERVER_NAME.lua.
- Copy an existing config to get started. Most configs are simple. For an extensive example see texlab.lua.
Ask questions on GitHub Discussions or in the Neovim Matrix room.

Release process

To publish a release:

Create and push a new tag.
After pushing the tag, a GitHub action will automatically package the plugin and publish the release to LuaRocks.

License

nvim-lspconfig is licensed under the terms of the Apache 2.0 license.

See LICENSE.md

Plugin on Producthunt daily

claude-hud

Claude HUD

Install

What is Claude HUD?

What You See

Default (2 lines)

Optional lines (enable via /claude-hud:configure)

How It Works

Configuration

Presets

Manual Configuration

Options

Usage Limits (Pro/Max/Team)

Example Configuration

Display Examples

Troubleshooting

Requirements

Development

License

Star History

eslint

ESLint

Table of Contents

Installation and Usage

pnpm Installation

Configuration

Version Support

Code of Conduct

Filing Issues

Frequently Asked Questions

Does ESLint support JSX?

Does Prettier replace ESLint?

What ECMAScript versions does ESLint support?

What about experimental features?

Which Node.js versions does ESLint support?

Where to ask for help?

Why doesn’t ESLint lock dependency versions?

Releases

Security Policy

Semantic Versioning Policy

License

Team

Technical Steering Committee (TSC)

Reviewers

Committers

Website Team

Sponsors

Platinum Sponsors

Gold Sponsors

Silver Sponsors

Bronze Sponsors

Technology Sponsors

LazyVim

Install · Configure · Docs

✨ Features

⚡️ Requirements

🚀 Getting Started

📂 File Structure

⚙️ Configuration

better-auth

Better Auth

About the Project

Why Better Auth

Contribution

Security

youtube-music

YouTube Music

Demo Image

Content

Features:

Available plugins:

Translation

Download

Arch Linux

macOS

Windows

How to install without a network connection? (in Windows)

Themes

Dev

Optional lines (enable via `/claude-hud:configure`)