Hook a guard into the router: judge requests before dispatch and filter answers as they are relayed
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
e701f92806
commit
979aa44804
12 files changed
+448
-12
No files matched your search
@@ -203,6 +203,12 @@ default output cap when the client omits `max_tokens`; `catalog.Capabilities`
|
||||
is advertised but never enforced; tool results are trusted input.
|
||||
|
||||
### B1. Hooks in the proxy and router (S)
|
||||
**Done (branch `guardrails-b`):** `internal/guard` holds the interface;
|
||||
proxy `Filter`/`StreamFilter`; the input hook runs after `loadThread` (the
|
||||
simpler choice); error codes, headers, Responses `incomplete`, usage columns
|
||||
`guard_*`. Moved to B2: holding `delta.tool_calls` until they are whole and
|
||||
reading their arguments — that is the tool policy's filter, not the proxy's.
|
||||
|
||||
- `internal/router/proxy/proxy.go`: add optional `InputRewrite func(body
|
||||
[]byte) ([]byte, Verdict)` on the request and two output hooks: `Filter`
|
||||
for `relayBuffered` (between `ReadAll` and `WriteHeader`) and
|
||||
|
||||
Reference in new issue
Block a user