hexis

kami/hexis

T

kami 945e4ba1ac Surface workspace-mcp tool-handler errors as execution failures

Decision: workspace-mcp's /api/tool, /api/tools direct-HTTP endpoints are
a first-class, server-sanctioned transport (see transport.py's "Direct
HTTP API for non-MCP clients"), not a workaround — Hexis's REST provider
is the right integration, no migration to the SSE/JSON-RPC MCP transport
needed.

The actual gap: workspace-mcp catches tool-handler exceptions and reports
them as an ERROR-coded warning inside a 200 response envelope rather than
an HTTP error status, so Execute()'s status-code check alone let every
such failure through as a successful execution. Detect the ERROR-coded
warning and return it as an error so it maps to Hexis's failed status.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018ghELqYhZNLub2TXGMazqA

2026-07-20 11:30:42 +04:00

cmd

Wire hexis.resolve_target to real Nexus, fix changes cursor, pass full execute fields over MCP

2026-07-20 11:28:13 +04:00

etc

Initial commit: Hexis capability registry + execution service baseline

2026-07-20 00:50:37 +04:00

internal

Surface workspace-mcp tool-handler errors as execution failures

2026-07-20 11:30:42 +04:00

pkg/client

Propagate correlation_id/causation_id through execution events, add API version header