Repository navigation
SP1 — Do Claude Code and an MCP client send a sealed handle unmodified? #2257
Description
Spike
| time box | resolves | who | deliverable |
|---|---|---|---|
| 3d | OQ2 "Does every intended client accept the sealed handle as its bearer unmodified?" | a person | docs/spikes/2026-10-20-sealed-handle-bearer-clients.md |
Does each intended client send the sealed handle as its bearer, unmodified, in the header the store rule names?
- Hypothesis: Claude Code with an OAuth token and one MCP client send
Authorization: Bearer <value>with no token-shape check - Assumption: if false, the injection task adds a prefix-shaped handle or waits on the harness adapter, and its proof changes
- Method: run Claude Code and one MCP client against a local TLS-terminating stand-in that logs the request head, with an opaque handle in place of the token
Plan block
### SP1 — Do Claude Code and an MCP client send a sealed handle unmodified?
question: Does each intended client send the sealed handle as its bearer, unmodified, in the header the store rule names?
hypothesis: Claude Code with an OAuth token and one MCP client send `Authorization: Bearer <value>` with no token-shape check
assumption: if false, the injection task adds a prefix-shaped handle or waits on the harness adapter, and its proof changes
method: run Claude Code and one MCP client against a local TLS-terminating stand-in that logs the request head, with an opaque handle in place of the token
time box: 3d
resolves: OQ2
executor: human
deliverable: docs/spikes/2026-10-20-sealed-handle-bearer-clients.md
The finding this spike delivers carries these sections:
- Question
- Hypothesis
- Method
- Findings
- Conclusion: proved | disproved | partial | parked
- Action items
- Artifacts
Activity
norrietaylor commentedon Oct 19, 2026
Done in #2327: the spike measured that Claude Code and the MCP clients send the sealed handle unmodified. Write-up: docs/spikes/2026-10-20-sealed-handle-bearer-clients.md. The spec changes it called for landed in #2328.