Improve ghostwriter output language guidance (#248)

This commit is contained in:
Shaheer Sarfaraz
2026-03-10 14:52:19 +00:00
committed by GitHub
parent 8c952a4011
commit ee6f889094
4 changed files with 37 additions and 0 deletions
+6
View File
@@ -27,6 +27,7 @@ Typical use cases:
- cover letter and outreach drafts
- interview prep tied to the job description
- rephrasing with tone constraints
- multilingual drafting when you want replies in a specific language
## How to use it
@@ -44,6 +45,10 @@ Global settings affecting generations:
- `Constraints`
- `Do-not-use terms`
Ghostwriter follows the output language you request in your prompt. For example, `Ecris en français` should produce a French reply.
If you want a persistent default language, put it in `Constraints`, for example: `Always respond in French.`
`Do-not-use terms` are passed as guidance in the prompt. They are not enforced by a hard post-generation filter, so the model should avoid them but may still use them occasionally.
Defaults:
@@ -80,6 +85,7 @@ Compatibility thread endpoints remain, but UI behavior is one thread per job.
- Check model/provider configuration in Settings.
- Tighten prompts with explicit output intent (for example, "3 bullet points for recruiter outreach").
- If you need a non-English response every time, add that language requirement to `Constraints`.
### Missing context in answers
+1
View File
@@ -73,6 +73,7 @@ Settings gives you runtime overrides for the key parts of discovery, scoring, ta
- Constraints
- Do-not-use terms
- These settings apply to Ghostwriter and resume tailoring
- `Constraints` can also set a default output language, for example `Always respond in French.`
- Do-not-use terms are model guidance, not a guaranteed output filter
### Reactive Resume