Skip to content

fix: keep AskUserQuestion answers whole in captured transcripts - #147

Open
nancy6547 wants to merge 1 commit into
supermemoryai:mainfrom
nancy6547:fix/keep-askuserquestion-answers
Open

nancy6547 wants to merge 1 commit into
supermemoryai:mainfrom
nancy6547:fix/keep-askuserquestion-answers

Conversation

@nancy6547

Copy link
Copy Markdown

Fixes #146.

Tool results in captured transcripts are cut to 500 characters (MAX_TOOL_RESULT_LENGTH in plugin/hooks/lib/transcript.js). With includeTools: ["AskUserQuestion"], that cuts the user’s typed answer, the one tool result that is the user’s own words and often the decision of the session.

This keeps AskUserQuestion results whole. Every other tool result is still capped at 500 characters. Redaction from #143 still applies, since it runs on the captured content.

Test: a capture-hook test in test/unit.mjs with a 700+ character answer and a 600+ character Read result. The answer is saved whole and the Read result is still cut. It fails without the change. npm test: 33 passed.

Tool results are cut to 500 characters, so a typed answer to Claude
Code's AskUserQuestion tool was saved cut off. Those answers are the
user's own words and often the decision of the session. Keep
AskUserQuestion results whole; other tool results stay capped.

Fixes supermemoryai#146
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Keep AskUserQuestion answers whole instead of cutting them at 500 characters (includeTools)

1 participant