Package Details: hermes-agent 0.13.0-1

Git Clone URL: https://aur.archlinux.org/hermes-agent.git (read-only, click to copy)
Package Base: hermes-agent
Description: Locally-run AI agent with tool use, web browsing, and automation
Upstream URL: https://github.com/NousResearch/hermes-agent
Licenses: MIT
Submitter: y0uCeF
Maintainer: y0uCeF (evorster)
Last Packager: y0uCeF
Votes: 3
Popularity: 2.19
First Submitted: 2026-04-02 18:38 (UTC)
Last Updated: 2026-05-09 20:44 (UTC)

Latest Comments

1 2 Next › Last »

y0uCeF commented on 2026-05-01 10:45 (UTC)

I updated the PKGBUILD, feel free to test hermes features on the new installation, especially things like integrations, browser use ...

With the new uv-based version, I removed all python-* references from deps/optdeps since they are 3.14 versions.

Also, users are instructed to copy skills on installation. What should happen when new skills are added with each update? users may not copy them everytime.

evorster commented on 2026-05-01 03:33 (UTC)

A new version just dropped. Just FYI, and for the previous version, this should be added into the PKGBUILD to build the tui:

❯ diff PKGBUILD PKGBUILD.tui 
75a76,81
> 
>   # Build the modern TUI. Upstream's wheel does not include ui-tui, but
>   # hermes --tui expects it next to the installed Python packages.
>   if [ -d "ui-tui" ]; then
>     (cd ui-tui && npm install --no-fund --no-audit --progress=false && npm run build)
>   fi
90a97,109
> 
>   # Install the modern TUI assets outside the wheel. The runtime launcher looks
>   # for PROJECT_ROOT/ui-tui, where PROJECT_ROOT is the site-packages directory.
>   _py_purelib="$(python - <<'PY'
> import sysconfig
> print(sysconfig.get_paths()["purelib"])
> PY
> )"
>   if [ -d "ui-tui" ]; then
>       install -d "$pkgdir/$_py_purelib/ui-tui"
>       cp -r ui-tui/dist ui-tui/node_modules ui-tui/package.json ui-tui/package-lock.json ui-tui/packages \
>           "$pkgdir/$_py_purelib/ui-tui/"
>   fi

evorster commented on 2026-05-01 02:47 (UTC)

Yes, please share that PKGBUILD and I'll have a go at it.

y0uCeF commented on 2026-04-30 09:56 (UTC) (edited on 2026-04-30 09:57 (UTC) by y0uCeF)

@evorster @marsxyz @Xelinor I am working on a refactoring of the package:

Install using a virtual environment using "uv" to /opt/hermes-agent/ similar to the official install.sh

Support "any" arch

Preinstall all node requirements: web dashboard, tui, whatsapp-bridge

I am still testing these changes and will push them once I fix all bugs (example: somehow the package still references absolute paths from my dev environment instead of /opt paths) If anyone is free to test I can share my current PKGBUILD. Co-maintainers are welcome as well

evorster commented on 2026-04-30 08:14 (UTC)

Running hermes --tui fails, and it complains that it is not installed.

Hermes on my machine was able to quickly fix the PKGBUILD to make this package install the TUI.

marsxyz commented on 2026-04-26 20:56 (UTC)

It's a shame it does not build in aarch64 (for Raspberry pi for example). Especially since the git version does build for aarch64.

y0uCeF commented on 2026-04-23 23:28 (UTC)

@Xelinor thanks for your comment, I do share your concerns and I will be trying to change that as soon as possible. python311 from AUR seems like a good solution.

Xelinor commented on 2026-04-22 01:20 (UTC)

@y0uCeF — thanks for maintaining this package. One concern: the PKGBUILD builds against system Python (currently for me 3.14.4 on Arch/CachyOS), but upstream's scripts/install.sh and setup-hermes.sh both pin Python 3.11 via uv, and the upstream troubleshooting docs explicitly flag "not yet fully compatible with Python 3.13+" (pathlib, tiktoken pyo3 issues). Wheels build fine, but runtime failures on specific code paths will surface as hermes bugs when the real cause is the version mismatch. Simplest fix is probably to depend on python311 instead of python and have the existing /usr/bin/hermes wrapper invoke 3.11 explicitly so that it matches upstream's supported runtime. Happy to test. Thanks again!

1 2 Next › Last »