melpa/melpa

[pr-open]: Add recipe for Pi package

localredhead — Tue, 16 Jun 2026 13:35:35 +0000

Run Pi (https://pi.dev) coding agent in Emacs via vterm. Supports project awareness, session management, and toggle/hide/restore. License: Apache 2.0 (GPL-compatible).

### Brief summary of what the package does
Run the [Pi coding agent](https://pi.dev) inside Emacs using `vterm` (emacs-libvterm) — the full TUI, including ANSI cursor positioning, interactive menus, and mouse support, rendered correctly.

Features:
- vterm-based launcher that shows Pi's native terminal interface unchanged
- Auto-detects project root via `project.el` (Emacs 27+) or Projectile and `cd`s before launching
- Session management: reuse existing sessions, toggle visibility (hide/restore), restart, or force a fresh session
- Configurable shell, auto-launch delay, and display behavior
- `pi-mode` minor mode with mode-line indicator
- Works on Emacs 28.1+ with no tree-sitter or C compiler required

### Direct link to the package repository
https://github.com/localredhead/pi.el

### Your association with the package
Maintainer / Creator

### Relevant communications with the upstream package maintainer
None needed.

### Checklist
- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)

[pr-open]: Add recipe for musicbrainz-interactive

zzkt — Tue, 16 Jun 2026 09:41:41 +0000

### Brief summary of what the package does

Interactive commands for searching and filtering MusicBrainz entities.

### Direct link to the package repository

https://github.com/zzkt/metabrainz

### Your association with the package

Maintainer

### Relevant communications with the upstream package maintainer

**None needed**

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [ ] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [ ] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for pg-propre

madtibo — Mon, 15 Jun 2026 10:51:38 +0000

## Add recipe for pg-propre

### Brief summary of what the package does

pg-propre integrates pg_propre (https://gitlab.com/madtibo/pg_propre), a fast Rust PostgreSQL SQL formatter and linter built on PostgreSQL's own parser, into Emacs. It uses the reformatter library to provide pg-propre-format-buffer/pg-propre-format-region commands and a pg-propre-format-on-save-mode minor mode, plus a Flymake backend (pg-propre-flymake) that surfaces pg_propre --lint diagnostics live.

### Direct link to the package repository

https://github.com/madtibo/emacs-pg-propre

### Your association with the package

I am the package author of pg_propre and emacs-pg-propre.

### Relevant communications with the upstream package maintainer

None needed — I am the upstream maintainer.

### Checklist

- [x] The package is released under a GPL-Compatible Free Software License
(https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read CONTRIBUTING.org
(https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an
Assisted-by: line as described in CONTRIBUTING.org (https://github.com/melpa/m
elpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [ ] The package has been maintained in a public repository for 1 month or
more
- [x] I've used the latest version of package-lint
(https://github.com/purcell/package-lint) to check for packaging issues, and
addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used M-x checkdoc to check the package's documentation strings
- [x] I've built and installed the package using the instructions in
CONTRIBUTING.org
(https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for gruber-darker-ayu-theme

Hadi493 — Sun, 14 Jun 2026 15:34:00 +0000

### Brief summary of what the package does

A blend of Gruber Darker's deep #181818 background with Ayu Dark's warm, high-contrast syntax palette.

### Direct link to the package repository

https://github.com/Hadi493/gruber-darker-ayu-theme

### Your association with the package

I am the maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a GPL-Compatible Free Software License
- [x] I've read CONTRIBUTING.org
- [ ] LLMs were used to generate some of the code
- [x] The package has been maintained in a public repository for 1 month or more
- [ ] I've used package-lint to check for packaging issues
- [ ] My elisp byte-compiles cleanly
- [ ] I've used checkdoc to check the package's documentation strings
- [ ] I've built and installed the package using the instructions in CONTRIBUTING.org

[pr-open]: Add recipe for shexc-ts-mode

ericprud — Sat, 13 Jun 2026 20:06:37 +0000

### Brief summary of what the package does

`shexc-ts-mode` is a tree-sitter major mode for ShExC (Shape Expressions
Compact Syntax), the Turtle-like syntax used by ShEx to describe and
validate the structure of RDF graphs. It is built on the
[tree-sitter-shexc](https://github.com/ericprud/tree-sitter-shexc) grammar
and provides syntax highlighting, structure-aware indentation, imenu,
xref (jump to shape definition/references), flymake diagnostics
(undefined shapes/prefixes, syntax errors, duplicate predicates),
shape-folding, and a "wrap/unwrap in shape" structural-editing pair.

### Direct link to the package repository

https://github.com/ericprud/shexc-mode-for-emacs

### Your association with the package

I'm the author and maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses) (MIT)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for org-history

Anoncheg1 — Sat, 13 Jun 2026 19:26:38 +0000

### Brief summary of what the package does
Show Dates column in Org for headers from git VCS + auto-commit with --amend per day

This package allows to:
1) Attach the dates of the last modification to Org headers as non-editable overlays.
2) Auto-commit with --amend once per day.
3) Request your confirmation only once.
4) Accurately save your answer to the .dir-locals.el file in the current directory.

### Direct link to the package repository

https://github.com/Anoncheg1/emacs-org-history

### Your association with the package

Author, maintainer

### Relevant communications with the upstream package maintainer

**None needed**

### Checklist

- [X] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [X] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [ ] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [X] The package has been maintained in a public repository for 1 month or more
- [X] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [X] My elisp byte-compiles cleanly
- [X] I've used `M-x checkdoc` to check the package's documentation strings
- [X] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for clatter

parenworks — Sat, 13 Jun 2026 08:26:12 +0000

### Brief summary of what the package does

clatter.el is a dedicated, IRCv3-compliant IRC client for Emacs, written in pure Emacs Lisp (requires only Emacs 30.1+ and curl for async URL fetching).
It supports the full IRC protocol plus IRCv3 features: CAP LS 302, SASL (PLAIN/EXTERNAL/SCRAM-SHA-256), message tags, batch, labeled-response, and chathistory. It also provides TLS with client certificates, a buffer per channel with nick colorization, a nick sidebar, desktop notifications, logging, full-text log search, and optional org-mode integration.

### Direct link to the package repository

https://github.com/parenworks/clatter.el

### Your association with the package

I am the author and maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a GPL-Compatible Free Software License (MIT)
- [x] I've read CONTRIBUTING.org
- [ ] LLMs were used to generate some of the code, and I've added an `Assisted-by:` line as described in CONTRIBUTING.org
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of package-lint to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in CONTRIBUTING.org

[pr-open]: Add recipe for octocat

razzmatazz — Fri, 12 Jun 2026 14:08:37 +0000

### Brief summary of what the package does

GitHub client for Emacs

### Direct link to the package repository

https://github.com/razzmatazz/octocat

### Your association with the package

I am the maintainer.

### Checklist

- [] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [] The package has been maintained in a public repository for 1 month or more
- [] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [] My elisp byte-compiles cleanly
- [] I've used `M-x checkdoc` to check the package's documentation strings
- [] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for git-overleaf

Jamie-Cui — Wed, 10 Jun 2026 15:17:37 +0000

### Brief summary of what the package does

overleaf-project integrates Emacs with Overleaf at the project level. It clones an Overleaf project into a local Git repository, records the Overleaf project metadata in that repository, and synchronizes complete project snapshots between local Git history and Overleaf.

### Direct link to the package repository

https://github.com/Jamie-Cui/git-overleaf

### Your association with the package

I am the package maintainer.

### Relevant communications with the upstream package maintainer

**None needed**

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for java-agent-loader

saulotoledo — Tue, 09 Jun 2026 18:48:58 +0000

### Brief summary of what the package does

`java-agent-loader` is an Emacs package designed to simplify the injection of Java agents (like Lombok, JaCoCo, etc.) into the JDT Language Server (JDTLS) process used by `lsp-java` and `eglot-java`.

It automatically detects configured agents in your project's dependencies (Maven or Gradle), resolves their JAR paths, and appends the appropriate `-javaagent` arguments to your LSP server's startup command.

### Direct link to the package repository

https://github.com/saulotoledo/java-agent-loader

### Your association with the package

I am the package maintainer.

### Relevant communications with the upstream package maintainer

The package is named `java-agent-loader`, but it uses `jal-` as the internal prefix for functions and variables to keep configuration concise. This currently causes Melpazoid to fail its verifications, as it expects the prefix to match the full package name.

I prefer this setup because the full name facilitates finding it, while the short prefix facilitates configuring it. It gives users the best of both worlds: discoverability in the package manager and concise code in their init files.

Could you please advise on how best to proceed under MELPA's guidelines? I am open to either renaming the package to `jal` or renaming the internal prefixes to `java-agent-loader-`.

### Checklist

- [X] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [X] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [ ] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [X] The package has been maintained in a public repository for 1 month or more
- [X] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [X] My elisp byte-compiles cleanly
- [X] I've used `M-x checkdoc` to check the package's documentation strings
- [X] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for nu-ts-mode

ItsOleks — Tue, 09 Jun 2026 11:18:58 +0000

### Brief summary of what the package does

Because nushell-ts-mode was broken and hadn't had a commit in the past 3 years, I wrote my own. It works based on the current version of the grammar and has tree-sitter-based highlighting and indentation.

I am not sure if this is fine with the "MELPA maintainers will reject packages that duplicate functionality provided by existing packages" line in the contributing guide, but as stated above, the other package is currently broken and the author doesn't seem to be reacting to issues/PRs.

Additionally, I am not an experienced emacs/treesitter plugin dev, so I am very open to any feedback or improvement suggestions.

### Direct link to the package repository

https://github.com/ItsOleks/nu-ts-mode

### Your association with the package

I am the author and maintainer

### Relevant communications with the upstream package maintainer

None needed

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [X] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] The package has been maintained in a public repository for 1 month or more
- [] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)
- LLMs were not used to generate any of the code, so that checklist item is deleted

[pr-open]: Add recipe for notmuch-multi

pivaldi — Mon, 08 Jun 2026 19:37:57 +0000

### Brief summary of what the package does

notmuch-multi extends the stock Notmuch Emacs UI to manage multiple mail accounts as separate, collapsible sections, something the default UI doesn't do.
Each account gets its own saved searches and `notmuch-jump` key prefix, a prettified hello screen showing an unread/total count per search, and truncated, emoji-stripped subject formatting for the search and tree views.
It also adds a soft-delete/expire tagging workflow (with separate, explicit file deletion of delete/expire-tagged mail), per-account recipient address completion scoped to the active `From:` account, and optional scheduled per-account mail fetching.

### Direct link to the package repository

https://github.com/pivaldi/notmuch-multi

### Your association with the package

I am the author and maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for countdown-modeline

jholland82 — Mon, 08 Jun 2026 12:15:06 +0000

### Brief summary of what the package does

[Please write a quick summary of the package.]

### Direct link to the package repository

https://github.com/jholland82/countdown-modeline
### Your association with the package

I am the maintainer

### Relevant communications with the upstream package maintainer

None needed

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for fzfa

jojojames — Sun, 07 Jun 2026 16:42:50 +0000

### Brief summary of what the package does

fzfa provides fuzzy async shell-command completion (completing-read interface) backed by fzf-native for scoring, analogous to counsel, helm, consult. It also provides various integrations using fzfa with notmuch, chrome, pass, mail, music.app, etc.

### Direct link to the package repository

https://github.com/jojojames/fzfa

### Your association with the package

Maintainer

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback

1 warning:
1881:5: warning: `with-eval-after-load' is for use in configurations, and should rarely be used in packages.
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for desert-theme

bkc39 — Sat, 06 Jun 2026 18:47:29 +0000

### Brief summary of what the package does

`desert-theme` is a warm, earthy Emacs color theme — a port of the classic *desert* colorscheme from Vim. It ships a fairly complete face set: font-lock, mode-line, line numbers, isearch/lazy-highlight, show-paren, whitespace, org-mode, diff, magit, and generic completion UI.

### Direct link to the package repository

https://github.com/bkc39/desert-theme

### Your association with the package

I am the author and maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses) (CC0 1.0 / public domain)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code) (`;; Assisted-by: Claude:claude-opus-4-8`)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe) — built with `package-build` and installed via `package-install-file`; the theme loads correctly

[pr-open]: Add recipe for shpaste

Bounga — Sat, 06 Jun 2026 08:46:25 +0000

### Brief summary of what the package does

`shpaste` is an Emacs client for [paste.sr.ht](https://paste.sr.ht) (sourcehut's
paste service), built on its GraphQL API. It creates pastes from a region or the
current buffer and manages existing pastes from a `tabulated-list` buffer
(open, copy URL, delete, refresh).

### Direct link to the package repository

https://git.sr.ht/~bounga/shpaste

### Your association with the package

Author and maintainer.

### Relevant communications with the upstream package maintainer

**None needed**

### Checklist

- [X] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [X] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [ ] The package has been maintained in a public repository for 1 month or more
- [X] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [X] My elisp byte-compiles cleanly
- [X] I've used `M-x checkdoc` to check the package's documentation strings
- [X] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Rename recipe from OAI to CUI

Anoncheg1 — Fri, 05 Jun 2026 20:32:10 +0000

### Brief summary of what the package does

Chat user interface with LLMs and agents in Org-mode blocks.

Screenshot

![screenshot](https://raw.githubusercontent.com/Anoncheg1/public-share/main/oai.png)

### Direct link to the package repository

https://github.com/Anoncheg1/emacs-cui

### Your association with the package

author, maintainer

### Relevant communications with the upstream package maintainer

**None needed**

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for denote-solo

pavlo — Fri, 05 Jun 2026 11:54:16 +0000

### Brief summary of what the package does

Provides workspace-like switching between Denote silos (note directories). Keeps exactly one directory active at a time - the "solo" - remembered across sessions and shown in the mode line. Unlike denote-silo, which prompts for a directory on every command, denote-solo lets you switch once and stay there until you switch again. The previous solo is pre-selected in the prompt for quick toggling between two directories.

### Direct link to the package repository

https://github.com/pavlo/denote-solo

### Your association with the package

I am the author and maintainer of the package.

### Relevant communications with the upstream package maintainer

None needed. I am the upstream maintainer.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

Note: the repository was created recently. The package itself has been in active personal use for a month prior to publishing.

[pr-open]: Add recipe for leadkey

jixiuf — Thu, 04 Jun 2026 11:19:30 +0000

leadkey

### Brief summary of what the package does

Translate leader keys to key sequences

### Direct link to the package repository

https://github.com/jixiuf/emacs-leadkey

### Your association with the package

maintainer

### Relevant communications with the upstream package maintainer

None needed

### Checklist

- [X] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [X] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [X] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [X] The package has been maintained in a public repository for 1 month or more
- [X] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [X] My elisp byte-compiles cleanly
- [X] I've used `M-x checkdoc` to check the package's documentation strings
- [X] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for denote-solo

pavlo — Tue, 02 Jun 2026 07:42:00 +0000

[pr-open]: Add recipe for sleek-modeline

abidanBrito — Sun, 31 May 2026 19:29:04 +0000

### Brief summary of what the package does

**`sleek-modeline`** is a minimal and elegant replacement for the default Emacs mode-line. It uses a left/right-aligned layout with configurable height and a registry-based segment system.

Built-in segments include buffer name (with an optional icon and modified-state highlighting), major mode, modal editing state (`evil`/`meow`), line endings, version control (branch name with state-aware coloring), diagnostics (`flycheck`/`flymake`), project name (`projectile`/`project.el`), and an LSP indicator (`eglot`/`lsp-mode`).

**_NOTE:_** optional `nerd-icons` support is used throughout with Unicode fallbacks.

### Direct link to the package repository

https://github.com/abidanBrito/sleek-modeline

### Your association with the package

I am the author and the maintainer.

### Relevant communications with the upstream package maintainer

None needed, I am the maintainer.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: include prompt directory into ai-code installation

tninja — Sun, 31 May 2026 18:20:22 +0000

### Brief summary of what the package does

include prompt directory into ai-code installation

### Direct link to the package repository

https://github.com/tninja/ai-code-interface.el, it is already included in melpa through this PR: https://github.com/melpa/melpa/pull/9754
### Your association with the package

maintainer

### Relevant communications with the upstream package maintainer

None needed

### Checklist

- [X] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [X] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [X] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [X] The package has been maintained in a public repository for 1 month or more
- [X] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [X] My elisp byte-compiles cleanly
- [X] I've used `M-x checkdoc` to check the package's documentation strings
- [X] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for mac-ime

ma0001 — Sun, 31 May 2026 11:03:01 +0000

### Brief summary of what the package does

Integrates the macOS native IME with Emacs using a dynamic module. It enables automatic IME state synchronization and smart deactivation (e.g., on prefix keys or in the minibuffer) without applying any Emacs patches.

### Direct link to the package repository

https://github.com/ma0001/mac-ime

### Your association with the package

Maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Repoint consult-notes, tabspaces, bibtex-capf to Codeberg

mclearc — Sun, 31 May 2026 03:54:22 +0000

These three packages' upstream repositories have moved from GitHub to Codeberg. I am the maintainer (Colin McLear, @mclearc). This updates each recipe to fetch from the new Codeberg git URL:

- consult-notes -> https://codeberg.org/mclear-tools/consult-notes
- tabspaces -> https://codeberg.org/mclear-tools/tabspaces
- bibtex-capf -> https://codeberg.org/mclear-tools/bibtex-capf

Same packages, same history and maintainer; only the hosting moved. The GitHub repositories are now archived read-only mirrors.