You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perplexity, NotebookLM, and ChatGPT all render 3 clickable follow-up question chips under each response. AnythingLLM, Khoj, and Open-Notebook don't. SurfSense's system_prompt.py already acknowledges follow-ups as a supported message type (line 168) but doesn't surface suggestions.
I'd add a suggest_followups tool that runs as the last step of each response and emits [string, string, string]. Frontend renders them as <Button variant="secondary" size="sm"> chips below the existing AssistantActionBar. Click → submits as a new user message via useThreadRuntime().append(). Feature-flagged via ENABLE_FOLLOWUP_SUGGESTIONS env (default on).
Scope: ~140 LOC total. Small, additive, no existing behavior change when flag is off.
Two quick questions:
Tool vs. appending to main response: I'd use a separate tool to keep the main response format clean — agree, or do you prefer structured suggestions within the response envelope?
Character budget: I'm targeting ≤12 words per chip. Acceptable or want stricter/looser?
I've shipped 3 PRs on SurfSense (#1215, #1220, #1233). Targeting dev, full unit test on the tool output schema, screenshot + GIF in the PR body.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Perplexity, NotebookLM, and ChatGPT all render 3 clickable follow-up question chips under each response. AnythingLLM, Khoj, and Open-Notebook don't. SurfSense's
system_prompt.pyalready acknowledges follow-ups as a supported message type (line 168) but doesn't surface suggestions.I'd add a
suggest_followupstool that runs as the last step of each response and emits[string, string, string]. Frontend renders them as<Button variant="secondary" size="sm">chips below the existingAssistantActionBar. Click → submits as a new user message viauseThreadRuntime().append(). Feature-flagged viaENABLE_FOLLOWUP_SUGGESTIONSenv (default on).Scope: ~140 LOC total. Small, additive, no existing behavior change when flag is off.
Two quick questions:
I've shipped 3 PRs on SurfSense (#1215, #1220, #1233). Targeting
dev, full unit test on the tool output schema, screenshot + GIF in the PR body.Beta Was this translation helpful? Give feedback.
All reactions