Make summary prompt and Ollama timeout configurable - #8
Open
r0m1-b wants to merge 2 commits into
Open
Conversation
- Add option `SUMMARY_PROMPT_FILE` in .hushnoterc - Fallback to the default prompt if no prompt file is configured
- add a parameter SUMMARY_TIMEOUT in .hushnoterc - default value stays 300s (5 min)
r0m1-b
force-pushed
the
feature/minor_improvements
branch
from
August 11, 2026 19:40
fa544b3 to
36db849
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds two small configuration options for HushNote summarization:
SUMMARY_PROMPT_FILE: allows loading a custom summarization prompt from a file.SUMMARY_TIMEOUT: allows overriding the Ollama request timeout.Motivation
The summarization prompt and Ollama request timeout are currently hardcoded.
Making them configurable allows HushNote to support different workflows
without requiring users to modify the source code.
For example, a custom prompt can be used for meeting notes, study notes,
transcript cleanup, or other use cases.
Compatibility
The existing behavior is preserved when these options are not configured.