Skip to content

refactor(*): set whole repo up to date with latest hexgate version - #17

Merged
guillaume-hexamind merged 1 commit into
mainfrom
gp/refactor/hexgate_update_match
Jul 15, 2026
Merged

refactor(*): set whole repo up to date with latest hexgate version#17
guillaume-hexamind merged 1 commit into
mainfrom
gp/refactor/hexgate_update_match

Conversation

@guillaume-hexamind

@guillaume-hexamind guillaume-hexamind commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Brings the repo in line with the latest hexgate release.

Renamed HEXGATE_KEYHEXGATE_API_KEY

Updated every reference across code, config, scripts, and docs to match the env var name expected by current hexgate.

Fixed the hexgate version never upgrading

make install-hexgate guarded the install on a bare import hexgate, so a bumped pin in pyproject.toml was never applied (venv stayed on a stale version). It now always uv pip installs the extra so the pin (hexgate>=0.2.9) is enforced.

Surface agent/user bans to the frontend

A kill-switch ban now shows a clear message instead of a generic failure (or, for devops, nothing at all):

  • agent-server — healthcare & devops wrappers catch AgentBannedError and emit a structured error carrying code / ban_type / target / reason; protocol.error() gained an optional details field.
  • proxy — translators forward details; added the missing error branch to the Google ADK translator (also fixes any devops error previously being silently dropped).
  • front-app — renders a ban as a neutral system notice (with the operator reason when present) rather than a red error.

@guillaume-hexamind guillaume-hexamind self-assigned this Jul 15, 2026
@guillaume-hexamind
guillaume-hexamind merged commit 3ddc383 into main Jul 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants