Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
zlareb1
force-pushed
the
feat/prompt-observability-20261119
branch
3 times, most recently
from
November 21, 2026 16:54
6129bf9 to
b9ef5b2
Compare
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Share operation name resolution with routing so refused aliases retain their target, and classify unsupported per-call protocol versions as refusals. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Use the routing help aliases for invocation attribution and retain a bounded generic label for unknown or malformed loom_op requests. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Stamp resolved identity before cache replay so tenant trace discovery and erasure find each attempt. Early authenticated refusals carry verified token identity without trusting the requested namespace. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The HTTP observer calls the core dispatcher directly. Keep batch admission and pre-send proof assertions on the executed path. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Admitted replay spans carry the authorized tenant identity. Describe that order in the dispatcher documentation. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The transport adds bounded, redacted invocation headers without changing request bodies or admission. Renew only the two reviewed client module digests. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
One host tool can trigger several Loom requests. Logical request counting needs a caller guarantee of unique IDs that persist across retries. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
zlareb1
force-pushed
the
feat/prompt-observability-20261119
branch
from
November 21, 2026 19:13
b9ef5b2 to
6e04d61
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog category (leave one):
Changelog entry (one or two sentences a user of Loom can read without the diff; the release pull request collects these into the release notes):
Loom traces distinguish tool, automatic-hook and background-worker origins, with request outcomes, duration and optional benchmark correlation. Hook invocation headers need the next server release.
Why
Transport and session identity do not explain why Loom was called. Optional caller metadata lets evaluators connect actual invocations to a benchmark run, case and variant while leaving absent origin and usage unknown.
Scope and risk
HTTP operations and MCP tool calls receive one attempt observation, including catalog and dispatch-screen refusals. Nested retrieval and provider observations retain their own timing and measured usage. Origin metadata never grants access or replaces authenticated tenant identity. Host tool-call IDs can correlate several separate Loom requests. Combining retries requires a caller guarantee that an ID uniquely identifies one logical Loom request within its scope and stays stable across those retries. Concurrent calls keep separate context; private diagnostics retain their export boundary. Cached replays retain admitted tenant tags for trace discovery and erasure; early authenticated refusals use verified token identity with namespace unresolved.
The canonical hook transport identifies hook requests without requiring a prompt ID. Its generated mirror follows the same implementation. Both plugin manifests use 1.2.48.
Compatibility, rollout and rollback
_meta.loomfields; no operation arguments, stored identity or authorization defaults change.Tests
.venv/bin/python -m pytest -q tests/unit/test_prompt_context.py tests/unit/test_mcp_malformed_requests.py tests/unit/test_mirror_publication_batch.py tests/unit/test_public_copy.py tests/unit/test_session_content_senders.py.PROJECTION_BEHINDand installer failures also remain recorded; later success does not establish their causes or prove a flake. Full CI must clear before merge.AI assistance in the code (leave one; writing this description with AI is fine):
AI-generated (an agent wrote most of the diff): Codex. Focused regressions, privacy/auth behavior, generated mirrors and actual trace readback were checked.
I can explain every line of this diff and how it interacts with the rest of Loom.
Checklist
make test-unitand applicable integration results are reported by CI; a full local run is not required before pushing. Full CI remains required.