All plugins

project-command-center

A board for every Hermes Project: lane, live sessions, token spend, git branch and GitHub issues and pull requests in one place, with a detail page per project. Click an issue and a session opens inside that project's folder with the issue number, title and URL already in the composer, unsent. Branch rows open a session in a worktree or after a checkout, and each session carries its own lane, so a PR climbing to review is visible where the work happens. Includes a GitHub reader with full issue and PR modals, comments, status filters and a Zed-style commit graph. Disclosure — reads your git repositories and their history, switches branches and creates worktrees under `<repo>/.worktrees/` when you ask it to from the board (refusing on a dirty tree, an in-progress merge, a branch checked out elsewhere or an existing target; git's own repo hooks run as they would in your shell), and comments on or closes issues and PRs as your authenticated gh account. Board state lives in a local SQLite file under the Hermes home. Two hooks read a terminal call's `gh pr create` output to link the PR and move the session to review, and inject one short line naming the session's own card into each turn; each has its own kill file (`auto_link.off`, `card_context.off`). Network calls go to api.github.com, avatars.githubusercontent.com, and a favicon of a homepage a project declares.

NyllREDesktopv0.4.2Updated 54 minutes ago

About

A board for every Hermes Project: lane, live sessions, token spend, git branch and GitHub issues and pull requests in one place, with a detail page per project. Click an issue and a session opens inside that project's folder with the issue number, title and URL already in the composer, unsent. Branch rows open a session in a worktree or after a checkout, and each session carries its own lane, so a PR climbing to review is visible where the work happens. Includes a GitHub reader with full issue and PR modals, comments, status filters and a Zed-style commit graph. Disclosure — reads your git repositories and their history, switches branches and creates worktrees under `<repo>/.worktrees/` when you ask it to from the board (refusing on a dirty tree, an in-progress merge, a branch checked out elsewhere or an existing target; git's own repo hooks run as they would in your shell), and comments on or closes issues and PRs as your authenticated gh account. Board state lives in a local SQLite file under the Hermes home. Two hooks read a terminal call's `gh pr create` output to link the PR and move the session to review, and inject one short line naming the session's own card into each turn; each has its own kill file (`auto_link.off`, `card_context.off`). Network calls go to api.github.com, avatars.githubusercontent.com, and a favicon of a homepage a project declares.

Project Command Center

Your projects, your agent sessions, and your GitHub issues. One board.

Click an issue and a session opens in that repo with the issue already sitting in the composer. The agent works. When it opens the pull request, the card moves itself to Review.

Project Command Center

Watch the demo on X

hermes plugins install NyllRE/project-command-center --enable

A Hermes Desktop plugin. If you already push to GitHub and use Hermes Projects, you are set. No new account, no new tracker, nothing to configure beyond the gh login you already have.

The loop worth feeling

You stop translating between three tools.

The board

  1. The board shows every project at once: its lane, its live sessions, its branch, what is dirty, how many issues and pull requests are open.
  2. You click an issue. A session opens inside that project's folder, with the number, title, URL and repo already in the composer. Nothing sends. You add your own first line if you want.
  3. The agent reads the issue itself, works, and opens a pull request.
  4. The card moves to Review on its own, and the next turn already knows which project, lane, issue and PR it is on. It never asks "which project am I in" again.

This is what you land in. The issue is already written for the agent, and nothing sends until you press send.

A session opened from an issue

The project page

Everything about one project without leaving it: token spend, session count, what is live right now, and the GitHub work in progress.

The project page

Sessions are grouped by the lane they belong to, each with its own status badge, so you can see what is blocked, what is waiting on review, and what is still moving.

GitHub, without opening GitHub

Issues and pull requests render the way you expect: real markdown bodies, the full comment thread, reviews, checks, labels, assignees, and avatars that are actually people. You can comment and close from here.

Pull requests

Status filters are cumulative. Start on open, tick Merged, and see merged and open together. Icons carry the GitHub colour language: green open, purple merged or closed, red not planned, grey draft.

An issue, rendered in full

The whole issue, not a summary of it: markdown body, labels, assignees, and the comment thread with a composer at the bottom. Close or reopen without leaving.

#123 references turn into chips with a preview, so a PR that mentions three issues is three clicks, not three tabs.

A reference chip with its preview

History that looks like history

A commit graph with real lanes. Fork, merge, track across branches, and open any commit to read its diff, files and line changes.

The commit graph

Sessions that know what they are

Each branch row gives you a session, not a chore. Start one in a worktree, or check the branch out here first. When the project is already on that branch, the menu says so instead of pretending to switch.

Every issue row is a session door

Sessions carry a lane: backlog, active, review, blocked, done. The board summarises them per project, so "who is on review" is a glance instead of a hunt.

What it never does

It does not send your prompts. It does not stash, discard or force anything in your repos. It does not phone home. Avatar images, GitHub and the favicon of a project you point it at are the only things it fetches, and every one of those paths has a kill file.

The details are honest and boring, which is how you want them:

Requirements

  • Hermes Desktop, installed and running
  • gh CLI, authenticated (gh auth login)
  • At least one Hermes Project pointing at a folder that has a git remote on GitHub

Built by Ali Sokkar.

README from the reviewed commit eaa3e2d; it updates when the author re-pins.

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section