• v0.1.0 09f6919f13

    zthor released this 2026-11-03 03:37:40 +00:00 | 11 commits to main since this release

    First tagged release, and deliberately a 0.x: the skills and bootstrap have run
    on real boxes for weeks, but the install/upgrade entry point is new, was
    exercised on one machine (Ubuntu 24.04.5, linux/amd64), and the Hermes update
    step was verified only up to its fetch. The interface can still move.

    One entry point. install.sh decides between two paths from what is on the
    box: a fresh machine gets the pack, an existing circuit gets the upgrade path.
    There is no second command to remember.

    Upgrade path (upgrade.sh):

    • backups ~/.config/tangled, ~/.local/share/tangled/circuits and ~/.hermes
      (config, state.db, plugins, skills) to ~/backups/agent-upgrade-<timestamp>/
      before touching anything;
    • upgrades the circuit binaries only when the installed version differs from the
      latest release, then restarts the daemon and waits for /healthz;
    • repairs a [email protected]: Hermes remote to HTTPS, which is what made
      hermes update fail with Permission denied, then updates Hermes;
    • refreshes skills and the session-rotate plugin without overwriting local
      settings or an existing mcp_servers.tc entry;
    • restarts the gateway last.

    Fresh install. Links 16 curated skills, writes env/agent.conf when
    absent, renders the session-rotate settings for the host, registers the MCP
    server, and offers to install Hermes Agent when it is missing.

    Versioned fetches. The installer resolves the latest release tag and fetches
    scripts and pack content at that tag; AGENT_BOOT_VERSION pins one explicitly.
    main is used only while no release exists.

    Honest limits. Linux/amd64 only. The circuit database is forward-only after
    DuckDB 2.0 — rollback is restore-from-backup plus the previous binaries.

    Downloads