Ghostwriter
What it is
Ghostwriter is the per-job AI chat assistant in JobOps.
Ghostwriter uses:
- current job description and metadata
- reduced profile snapshot
- global writing style settings
The UI behavior is one persistent conversation per job, shown in the right-side drawer from job details.
Why it exists
Ghostwriter helps you produce job-specific writing quickly while preserving consistency with your profile and style settings.
Typical use cases:
- role-specific answer drafting
- cover letter and outreach drafts
- interview prep tied to the job description
- rephrasing with tone constraints
How to use it
- Open a job in
discoveredorready. - Open the Ghostwriter drawer.
- Enter your prompt and stream a response.
- Stop or regenerate responses when needed.
Writing style settings impact
Global settings affecting generations:
ToneFormalityConstraintsDo-not-use terms
Defaults:
- Tone:
professional - Formality:
medium - Constraints: empty
- Do-not-use terms: empty
Context and safety model
- Job snapshot is truncated to fit prompt budget.
- Profile snapshot includes relevant slices only.
- System prompt enforces read-only assistant behavior.
- Logging stores metadata, not full prompt/response dumps.
API surface
GET /api/jobs/:id/chat/messagesPOST /api/jobs/:id/chat/messages(streaming)POST /api/jobs/:id/chat/runs/:runId/cancelPOST /api/jobs/:id/chat/messages/:assistantMessageId/regenerate(streaming)
Compatibility thread endpoints remain, but UI behavior is one thread per job.
Common problems
Responses feel too generic
- Verify the job description is complete and current.
- Confirm style constraints in Settings are specific enough.
Generation quality is lower than expected
- Check model/provider configuration in Settings.
- Tighten prompts with explicit output intent (for example, "3 bullet points for recruiter outreach").
Missing context in answers
- Update profile data and relevant project details used by Ghostwriter context.
- Regenerate after updating job notes/description.