Skip to content

Honcho Dashboard 1.5.0

Latest

Choose a tag to compare

@github-actions github-actions released this 13 Nov 05:22

v1.5.0

What changed

  • Dreams (Honcho 3.6). A new DREAMS page reads Honcho 3.6's Representation History as a diff of what each dream did to a peer's representation. A summary line above the list says what needs a look on the loaded page: failed runs, runs that may be stuck, forgotten conclusions, changed peer cards and runs new since your last visit. Each count filters the list. Runs that started together are grouped, and each row shows +added ~rewritten −forgotten. An open run lists what was forgotten first, then rewrites with the old text under the new, then new conclusions. Peer card lines that changed value read as one change. A conclusion a later dream removed opens that dream with the conclusion marked. A run left running far longer than the others is flagged as possibly stuck. A peer row's DREAMS button opens its history, and SCHEDULE_DREAM picks peers from a list.
  • Per-session learning controls. An open session has a LEARNING tab with its conclusions, summaries, dreams and peer card settings, each shown next to the value in effect and where it comes from. With write actions on you can change them for that session, and every save is confirmed and read back. The session list marks sessions with learning off and can filter by it. Conclusions can be filtered by session and deleted together into TRASH.
  • Optional login. Set DASHBOARD_PASSWORD and DASHBOARD_SESSION_SECRET to put one shared password in front of every page, data route and the Honcho proxy. Sessions use a signed cookie, failed logins are rate limited, and changing the password ends every session. It is off by default. Contributed by @svallory (#17).
  • Server-held token. HONCHO_PROXY_TOKEN lets the server hold the bearer token for the default Honcho instance, so browsers never see it. A token saved in a browser still takes precedence. Set DASHBOARD_PASSWORD with it, or keep the dashboard on a private network. Contributed by @svallory (#20).
  • Operator database writes are off unless the server allows them. Retrying reasoning tasks now needs HONCHO_OPERATOR_WRITES=true on the server, not just the browser's write toggle. While it is off, Postgres itself enforces read-only on the dashboard's connection. Contributed by @svallory (#16).
  • Coolify deployment. A Coolify Service compose file and Traefik deployment docs. Contributed by @svallory (#18).
  • Large workspaces. Honcho 3.6 stops counting list totals at 100,000 by default. Totals past that read 100,000+, and page counts read as a lower bound until the last page.
  • Diagnostics for Honcho 3.6. Checks the new deriver claim table, the tenant-scoped message search indexes and the tenant setup. A server built from Honcho's main branch past a release is recognized and checked the same way.
  • Conclusion levels use the same icons and colours on Peers and Dreams.
  • Fixed the session list's settings count, which miscounted because the SDK returns configuration keys in a different case.
  • Updated the Honcho SDK to 2.9.0.

Compatibility

Works with Honcho 3.1 through 3.6.1. Dreams and the capped totals only appear on 3.6, and on 3.5 and older the dashboard sends none of the new requests. Unverified servers keep the new features hidden. Existing .env and Compose files work unchanged, with one exception: retrying reasoning tasks now needs HONCHO_OPERATOR_WRITES=true (see Upgrade). Login, the server-held token and operator writes are all off unless you set them. See the 3.6.1 validation guide for what was tested.

Upgrade

Update the dashboard image to ghcr.io/outpoints/honcho-dashboard:1.5.0, restart the dashboard, and reload open browser tabs. This update needs no database migration.

  • If you retry reasoning tasks from REASONING, set HONCHO_OPERATOR_WRITES=true on the dashboard, and give its database role UPDATE on Honcho's queue table. Without it the retry buttons stay disabled and say why.
  • If your operator database sits behind PgBouncer older than 1.26, nothing changes. It refuses the read-only startup option, so the dashboard reconnects without it once and logs one warning. The server-side write check still applies.
  • To add a login, set DASHBOARD_PASSWORD and a DASHBOARD_SESSION_SECRET of at least 32 characters.

You can upgrade the dashboard before or after Honcho 3.6. If you upgrade Honcho, go straight to 3.6.1. 3.6.0's tenant migration blocks reads and writes while it runs, and 3.6.1's does not. Read Honcho's release notes before upgrading the server.

Known limitation

  • Dreams only shows runs recorded after the server reached Honcho 3.6. Honcho keeps them for its retention window, 30 days by default.
  • The summary line counts the runs on the loaded page. Honcho's dream list cannot filter by status, so a failure on a later page is not counted until that page is open.
  • Honcho does not publish its count limit. If a server sets it below the default, a capped total shows as that limit plus one rather than with a +.
  • Restoring a conclusion from TRASH creates a new one, and dream history keeps showing the deleted one as unavailable.

Screenshots

Dreams, with the summary of what needs a look

A dream run as a diff: a forgotten conclusion, new conclusions and a changed peer card line

Per-session learning controls

Diagnostics checking the Honcho 3.6 schema

The optional login

All displayed data is synthetic.