| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-09-23 | 1.3 kB | |
| v1.29.0 -- agent-tunnel turn log source code.tar.gz | 2026-09-23 | 56.5 MB | |
| v1.29.0 -- agent-tunnel turn log source code.zip | 2026-09-23 | 57.0 MB | |
| Totals: 3 Items | 113.6 MB | 0 | |
v1.29.0 — agent-tunnel turn log
Feature: keep every answered HTTP turn, and read it back
agent-tunnel's HTTP front-end can now keep a durable record of what was
asked. Set [http] turn_log = "http-turns.jsonl" and every answered turn is
appended as one JSON line: time, handle, thread, question, answer, and the
caller's metadata. The sender is never written, and the file is
owner-only.
POST /askaccepts an optionalmetadataobject of flat strings (up to 20 keys, 4,000 characters each). A docs site sends the page and heading a question came from.GET /turns?handle=...&meta.<key>=<value>&limit=Nreturns the matching turns, newest first.- The
/askresponse gainslogged, which is false, with a notice, when the answer was delivered but could not be written.
The fork is still told who is asking and may repeat it in an answer, so a
caller that shows the log to other people should send a pseudonym as
sender.
The first caller is the Jev wiki: every section heading with earlier
questions shows an "N chats" link that lists them, read live through
GET /turns.
What's Changed
- agent-tunnel http: a turn log and GET /turns by @pchalasani in https://github.com/pchalasani/claude-code-tools/pull/210
Full Changelog: https://github.com/pchalasani/claude-code-tools/compare/v1.28.0...v1.29.0