Skip to content

v2.5.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 20:10
· 87 commits to main since this release

HexDB 2.5.0 adds the Oracle, a hex just for AI; an AI that watches the audit trail and alerts you; plugins in a sandbox; SQL DELETE; and retiring hexes, so a lattice can move to other regions or machines without losing data.

New

  • The Oracle. Give one hex identity.role = "oracle" and it answers every AI question the lattice gets (MCP, the chat, A2A) while keeping no data: it reads what each question needs from the other hexes, as the asking user, so AI traffic and its waiting stay off the hexes that hold your data. If it's down, the other hexes answer as before.
  • AI security reviews. With security.review.enabled, the lattice's AI reads a summary of the audit trail every 1 to 24 hours (failed sign-ins, refused requests, users on new addresses, activity by hour, administrative changes; never documents) and reports what looks like an attack or misuse, with the evidence. Reviews are kept for 90 days on the Security Reviews page. Those at security.review.notify_severity or worse (medium by default) are emailed over your own SMTP server (email.smtp_url, email.from) and sent to any alert channel you set up: PagerDuty, SMS through Twilio, Slack, Microsoft Teams or Discord, or a webhook signed with HMAC-SHA256.
  • AI. MCP clients that sign in with OAuth find the provider on their own (oauth.resource); chat answers stream as they're written; ai.max_concurrent_calls caps AI calls per hex.
  • Vector search. Filters an index can answer now narrow the nearest-neighbour search itself, so filtered similarity searches stay exact. A files tessellation can embed pictures with a multimodal model (source $image, e.g. voyage-multimodal-3), so a search by text finds pictures by what they show.
  • SQL DELETE ... WHERE. POST /sql runs DELETE FROM t WHERE ... as one restorable delete batch, cascades included, with dry_run, expect and all as for _delete. The JDBC driver's executeUpdate and the ODBC driver's SQLRowCount report the rows deleted; hexdb sql has --dry-run, --expect and --all. The AI's tools and MCP stay read-only.
  • Retiring hexes. POST /retire/{hex} takes a hex out of the lattice safely: its slices move to the other hexes first, and a retiring Overseer hands its role to a successor that has copied every slice. GET /retire and /status say when it can be removed.
  • Plugins in a sandbox. Process plugins now run in the process sandbox by default: Landlock, seccomp and resource limits on Linux, an AppContainer on Windows (as the file parser now does too). A plugin reads its own folder and writes its data folder (HEXDB_PLUGIN_DATA), and anything more only as its manifest's [sandbox] section declares (network, read, write, memory_mb).
  • Multicast discovery. With network.multicast = true, hexes on the same local network find each other with no peers at all.
  • HexDB Enterprise lattices can change their size, hex count and home region from the account page, and serve at a domain of their own.

Fixed

  • A POST /{t}/_delete retried with the same Idempotency-Key answered 500 instead of the first answer.

Upgrading

Restart the hexes one at a time, as usual: replicas first, the Overseer last.

  • Plugins: a process plugin that uses the network or files outside its folder must now declare them in its plugin.toml ([sandbox] network = true, read, write), or be run outside the sandbox with "sandbox": false on its registry entry. The bundled plugins already declare what they need.
  • Retiring hexes needs every hex on 2.5: an older hex doesn't know to leave a retiring hex's slices alone.
  • Route names: retire is now an API route, so a new tessellation can't take that name (an existing one keeps working).
  • SQL clients: the JDBC driver's isReadOnly and ODBC's SQL_DATA_SOURCE_READ_ONLY now say the source isn't read-only, since SQL can delete.

Full Changelog: v2.4.5...v2.5.0