All plugins

git-tasks

Multi-repo GitHub issues & PRs in an Orca-style Tasks view for Hermes Desktop. Disclosure — uses your logged-in `gh` CLI and `git` through Hermes Desktop's shell bridge, or a GitHub token you paste in the panel (stored unencrypted in Desktop plugin storage, sent only to api.github.com); scans your configured clone folders for GitHub repos and reads skill names under ~/.hermes; polls the active-session list of every Hermes profile every 10 seconds for status chips; approve, close, reopen, comment and merge act on GitHub from the panel; creates git worktrees and opens Hermes sessions seeded with the issue/PR title and body as fenced untrusted text, and without a shell bridge asks the agent to run the worktree git commands.

meviusisbackDesktopv0.2.0Updated 12 days ago

About

Multi-repo GitHub issues & PRs in an Orca-style Tasks view for Hermes Desktop. Disclosure — uses your logged-in `gh` CLI and `git` through Hermes Desktop's shell bridge, or a GitHub token you paste in the panel (stored unencrypted in Desktop plugin storage, sent only to api.github.com); scans your configured clone folders for GitHub repos and reads skill names under ~/.hermes; polls the active-session list of every Hermes profile every 10 seconds for status chips; approve, close, reopen, comment and merge act on GitHub from the panel; creates git worktrees and opens Hermes sessions seeded with the issue/PR title and body as fenced untrusted text, and without a shell bridge asks the agent to run the worktree git commands.

git-tasks

A Hermes Desktop plugin that shows GitHub issues and pull requests from all your repositories in one Orca-style Tasks view — and lets you jump into the work with a single click.

Tasks view

What it does

  • One list for every repo. Pick which repositories to follow; filter by Open / All / Closed and by PRs / Issues. Lists refresh automatically.
  • Orca-style detail. Click a card to see sections (meta, body, comments, labels, checks, merge) with readable, wrapping text.
  • Start a worktree. One button creates a git worktree under your local clone and opens a new Hermes session already working in it, with the issue/PR in context. If the worktree already exists, the button becomes “Go to worktree”.
  • Choose your bot. Before creating, you pick which profile/bot opens the session and which branch to start from (default branch, origin/main, or the PR’s branch).
  • Missing clone? If the repo isn’t on disk, the plugin offers to gh repo clone it into one of your folders and keeps going.
  • Review actions. Approve PRs, close/reopen issues and PRs, merge (merge / squash / rebase with confirm), comment — all without leaving Hermes.
  • CI at a glance. A dot on each PR card: green (checks passing), red (failing), yellow (running).
  • Live session presence. Cards linked to a session show a status chip (working / waiting for input / idle / ended), refreshed every 10 seconds. A Go to session button jumps straight to it; you can also link any open session manually.
  • Skill on start. Optionally name a skill when creating the worktree — it is pasted into the new session input right after the issue/PR ref, ready to run.
  • Centered setup dialog, manual refresh, parallel loading. Worktree setup opens in a centered dialog; a refresh button reloads the list on demand; repos load in parallel.

Requirements

  • Hermes Desktop (recent version)
  • gh CLI, authenticated (gh auth login) — or a GitHub token (see Data source below)

Data source

Top-right of the panel, the Data source button opens the source settings:

  • Auto (default): uses gh when the shell answers, otherwise the GitHub API.
  • gh CLI only / GitHub API only: force one path.
  • The token (classic or fine-grained, repo scope) lives only in your browser's plugin storage, travels only as an Authorization header to api.github.com, and is never written to the repo or the logs.
  • API mode differences: no review-decision dot on cards (reviews still show in the detail view); worktree creation is delegated to the agent (it runs the git commands itself after your approval).
  • When the desktop shell bridge is unavailable, worktree setup always goes through the agent: the session opens with exact instructions (reuse-or-create worktree, suggested clone folders) and asks you if nothing fits.

Install

./scripts/install.sh

Then in Hermes Desktop: Ctrl+K → Reload desktop plugins → open /tasks.

Settings

Settings → Plugins → Git Tasks:

  • Repositories — which owner/repo to follow (up to 50). You can also pick them from your GitHub account inside the plugin.
  • Clone folders — where your local clones live (~/repo, ~/repos, …). Used to find clones and as the default clone destination.

How the worktree flow works

  1. Click Start a worktree on any card.
  2. Pick the bot profile and the starting branch, confirm.
  3. The plugin creates <clone>/.worktrees/<type>-<number>-<slug> on a new branch and opens a session there with the task in context.
  4. Work normally: commit, push, open the PR, merge. Afterwards clean up with git worktree remove from the clone.

Security

  • Every shell interpolation is quoted; repository names are allowlist-validated.
  • Merge methods are allowlisted and always confirmed; external links only open on https://github.com/.
  • Third-party issue/PR text is labelled untrusted in seeded agent sessions.
  • npm run test — pure-function tests, all passing.

Development

Single-file ESM plugin, no build step:

node --check desktop/plugin.js   # syntax
npm run test                     # tests
./scripts/install.sh             # deploy to ~/.hermes/desktop-plugins/git-tasks/

License

MIT

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

More by meviusisback

2 plugins by meviusisback in the catalog.

meviusisbackusage-statsMulti-provider usage/balance for the Hermes Desktop status bar — shows live usage for OpenCode, OpenRouter, DeepSeek, Kimi, NovitaAI, ZAI, Alibaba, Arcee, plus gateway-native Claude/Codex/Cursor/Nous.CommunityDesktop app2