Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[FR] Per-user chat preferences (response depth, code visibility, custom instructions)

Offen
  • Stimmt etwas nicht?
#1,242 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

  • #1243 von @wilson101xx — ohne Merge geschlossen

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
45/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Ruhig
Tech-Stack
typescript
Bereich
ai, full-stack

Rechercherichtung

Start by tracing the Settings page, User model, and the agent's request-time system-prompt assembly described in the proposal. Done means per-user storage and editing for six response dimensions plus the 1000-character custom-instructions field, with preferences applied softly and higher-priority safety, citation, and diagram requirements preserved.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Feature

The need
Sourcebot's chat answers are great for engineers but can be too dense
for PMs and VPs on our team. The same question ("how does service X
work?") needs a different shape depending on who's asking — concept-level
without code for a VP, full implementation detail for an engineer.
Today the agent has one voice for everyone.

Proposal
Add a Chat Preferences page in Settings where each user configures how
Sourcebot talks to them. Two parts:

  1. Six response-style dimensions, each a radio with 3 levels:

    • Depth: Full detail / Concept-level / One-paragraph summary
    • Code visibility: Show snippets / Describe in prose / No code at all
    • Vocabulary: Jargon OK / Define terms / Business framing
    • Citation density: Every claim / Key claims / Just sources at end
    • Output structure: Headers+code / Prose+bullets / TL;DR + 3 key points
    • Diagrams: When useful / Often / Almost always

  2. Custom instructions — a free-text field (1000 char limit) for
    anything the dimensions don't capture. E.g. "use product analogies",
    "cite service owners alongside file refs", "I'm new to the codebase
    so define unfamiliar acronyms".

Preferences are stored per-user on the User model. The agent reads them
at request time and renders a <user_preferences> block in the system
prompt that biases responses accordingly.

Bias is soft, not a hard rule. If a user with "no code" set asks "show
me the function", the agent should still show the code. Safety, citation,
and diagram-generation requirements stay above user preferences.

Open questions for the team

  • Anonymous users — sign-in-only in V1 sounds right, but flag if you'd
    prefer a localStorage path for anon
  • Naming: "Chat Preferences" or "Custom Instructions" — the latter
    matches ChatGPT/Cursor convention but is narrower

Future considerations

  • Preset buttons that fill the radios (PM preset, Engineer preset, VP preset)
  • Per-thread override (this chat needs VP-style, override my defaults)
  • Per-message override (just this once, be verbose)
  • Org-admin default preferences for everyone in the org
Vorherrschende Sprache
TypeScript
Sterne
3.9k
Forks
374
Ø Merge
2 T. 21 Std.
Gemergte PRs (30 T.)
43

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus sourcebot-dev/sourcebot

Alle Issues in sourcebot-dev/sourcebot

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.