Skip to content

Make bot replies short and conversational - #27

Closed
sousavf wants to merge 1 commit into
nikuscs:mainfrom
sousavf:feature/concise-replies
Closed

sousavf wants to merge 1 commit into
nikuscs:mainfrom
sousavf:feature/concise-replies

Conversation

@sousavf

@sousavf sousavf commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

Bots replied like reports: the answer, then sources, fees, caveats and what they could not do. This rewrites the built-in reply rule every bot gets so replies read like chat.

  • Answer in the first sentence, usually one or two sentences in total.
  • Bold the values the owner copies or acts on (amounts, dates, references, names), with a short example.
  • Leave out headings, recaps, sources, alternatives, what was checked, what the bot cannot do, and caveats that do not change what to do.
  • A list only for several separate items, a table only to compare them. Bot instructions can still ask for more detail.

Existing bots pick the rule up when they are next configured.

Testing

  • bun run check and bun run lint pass.
  • The repo has no automated tests for prompt text. Checked against one live reply from a fresh bot on Claude Haiku 5.5, shown below.

Screenshots

Taken from a local build with PRs 27 to 30 applied together, using a throwaway demo bot; other sidebar names and previews are replaced with demo text.

Short reply with bold key values

Answer in the first sentence, bold the values the owner acts on, and drop
recaps, sources and caveats that do not change what to do.
@sousavf
sousavf requested a review from nikuscs as a code owner November 8, 2026 09:38
@migsilva89

Copy link
Copy Markdown
Collaborator

Hey, thanks for this! I get the problem, some models (GPT especially) get lazy and turn every reply into a report. I really like the "reply like a person in a chat, not a report" part.

The rest feels too opinionated to be the default for every bot, though. How a bot talks is personal: some people want it chatty, others want it short and robotic, and if this is baked in, their own instructions end up fighting it.

What if we leave the built-in rule as it is and add a global instructions box instead? You write general instructions once and each bot can opt in or out. That way you can use this style on the bots you want, and nobody else gets it unless they ask for it. What do you think?

@sousavf

sousavf commented Nov 8, 2026

Copy link
Copy Markdown
Contributor Author

Fair point, let's drop this one.

What I was really after was a Grok-style default: short, direct, conversational answers out of the box, without having to tune each bot. Your global instructions box is a better home for that. I'll close this PR and open a new one for the global box, with this style available as a preset that each bot can opt in or out of. Sound good?

@sousavf sousavf closed this Nov 8, 2026
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.

2 participants