Files
boxmaker/crates/memoryd/tests/fixtures/honcho/README.md
T
kyleandClaude Opus 5.5 718e66d3f6 memoryd: Honcho responses for M5c-2's read path, recorded from rift (M5c-2 task 00)
Workspace search with a limit and with no match, conclusion queries for the owner's and another
agent's peer, and what a workspace that does not exist answers to search, query, chat and delete.
Recorded through roncho 1.0.0's blocking client in the throwaway workspace boxmaker-plan-probe,
deleted afterwards.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-28 16:20:42 -07:00

19 lines
1.1 KiB
Markdown

# Honcho responses, recorded
Real requests and responses from the owner's Honcho (3.2.0, rift), recorded on 2026-09-27 by the
design model for M5c-1, in a throwaway workspace, `boxmaker-plan-probe`, created for it and deleted
afterwards. Each request is exactly what `roncho` 1.0.0's blocking client sends. Each file is
`{"request": {"method", "path", "body"}, "response": {"status", "headers", "body"}}`. The fake
Honcho server in `memoryd`'s tests answers from them. Do not edit.
Files 30 to 37 were recorded the same way on 2026-09-28 for M5c-2, in the same throwaway workspace
(again deleted afterwards), through a proxy that allowed no other workspace. What they show:
- Search has no relevance cutoff: a query with no match (31) still returns the nearest messages.
- A search or a conclusion query in a workspace that does not exist answers 200 with no hits (34,
35); only chat (36) and delete (37) answer 404.
- The duplicate tea messages in 30 and 31 are real: the recording ran twice into one workspace.
A chat at `reasoning: low` was recorded too and left out: on rift it returned the dialectic
model's raw tool-call markup as its answer, not an answer.