# Can you look up cotypist and find out about it. In cotypist there is a small system prompt esque... ## Retrieval Notes - Session id: `019df907-58fc-74b3-9449-d79e1427d6f6` - Source: `Codex raw session` - Last activity: `2026-05-05T16:49:06.312Z` - Model: `gpt-5.5` - CWD: `/Users/nickyoung` ## My Notes <!-- Add your notes here. This section is preserved across syncs. --> ## Conversation ### User Can you look up cotypist and find out about it. In cotypist there is a small system prompt esque ting i can give it to help it complete sentences like me. once you weeork out whati mean i'd like you to look up best practices in terms of how to write this thing. if there are no best practices to be found, use your common sense as to what sort of thing should be in there. the above is part 1 of the task. part 2, is to use our conversations, and the ones i ahve with claude, to find out what information for me specifically you should put in this document. part 3 is writing the dcoument and telling me where to put it in cotypist ### Assistant I’ll treat this as both a current-product lookup and a Nick-specific writing-profile task. I’m going to first verify what Cotypist’s prompt field actually expects, then I’ll read the local memory/writing context before drafting something usable rather than generic. ### Assistant The Cotypist docs confirm the field is “Custom AI Instructions”: a short free-text note used on every suggestion, with optional per-app/per-domain additions. The product’s own guidance is surprisingly restrained: a few sentences about occupation, writing contexts, and style, because longer prompts can dilute the completion model’s focus. ### Assistant I’ve loaded the local writing profile and the operational routing note. The useful shape is becoming clear: Cotypist wants a compact orientation, so the Nick-specific work is mostly deciding what to leave out as much as what to include. ### Assistant There’s already a very relevant prior Claude conversation from April 14 specifically about Cotypist instructions. I’m going to read that rather than reinvent the answer from profile files alone. ### Assistant I’m going to create one small Markdown file with the paste-ready global instruction plus optional app/domain add-ons. Scope is only that file; I’m not touching Cotypist’s local database, your app settings, or any vault structure. ### Assistant Done. I wrote the paste-ready document here: [Cotypist Custom Instructions.md](/Users/nickyoung/Cotypist%20Custom%20Instructions.md) What I found: Cotypist’s own docs say the global Custom AI Instructions should be short, only a few sentences, focused on occupation, writing contexts, domain vocabulary, and style preferences. They explicitly warn that too much text can dilute the model’s focus. They also support per-app and per-domain instructions, which Cotypist appends after the global instructions. Sources: [Cotypist Personalization](https://cotypist.app/help/personalization) [Cotypist Tips](https://cotypist.app/help/tips) Where to put it: open Cotypist from the menu bar, go to Personalization Settings, and paste the “Global Custom AI Instructions” block into Custom AI Instructions. The optional blocks go under App Settings for Obsidian, Mail/Gmail, or AI-agent apps/domains if you want finer control. *Un buon completamento dovrebbe sapere abbastanza da seguirti, ma non così tanto da mettersi a scrivere al posto tuo.*