GitLaw How-To guides
Attach a file to chat
To attach a file to a GitLaw chat, click the attachment button in the chat input and select a DOCX, PDF, MD or HTML file from your device. The file is added to your GitLaw files once you send the message. State what you want in the same message: the Agent reads your prompt to decide whether to use the file as reference, edit it directly, or create a copy from it.
Before you start: a GitLaw account, and the file as a DOCX, PDF, MD or HTML file.
How do I attach a file to a GitLaw chat?
- Open a chat session: start a new chat or open an existing one.
- Attach your file: click the attachment button in the chat input and select a DOCX, PDF, MD or HTML file from your device. The file is added to your GitLaw files once you send the message.
- State your intent clearly: type your instruction in the same message, or immediately after. The Agent uses your wording to decide what to do with the file.
What the Agent does with your attached file
Before making any changes, the Agent reads your prompt to understand your intent and acts accordingly, so the outcome depends on how you phrase your request.
| Intent | Example prompt | What the Agent does |
|---|---|---|
| Reference (context) | "Here's our company policy - draft an NDA based on it" | Reads the file as background context; creates a new, independent document. The original is untouched and no copy is made. |
| Edit | "Fix the typo in clause 3" or "Update the payment terms" | Edits the file directly. DOCX and PDF files convert to GitLaw's editor format on the first edit; the original is preserved as version 1 in the file's version history. |
| Template | "Fill this MSA for Client X" or "Create a new SOW based on this" | Creates a copy of your file with a link back to the source. The Agent edits the copy; the original stays untouched and remains reusable for future deals. |
Tips for getting the outcome you want
- Context: mention what you want drafted, not what you want done to the file. Phrasing like "based on this" or "using this as reference" signals context intent.
- Edit: refer directly to content inside the file, such as clauses, sections or specific wording. The Agent will treat it as a document to modify in place.
- Template: use phrases like "fill this for [client]", "create a new [document type] from this", or "use as a template". This triggers a copy so your master template is never overwritten.
Best practices
- Check the file opened in the editor: after the Agent acts, confirm it has opened the right file, the original or the new copy, before reviewing changes.
- Use version history: for edited files, open Version history from the … menu in the top right to compare against the original if needed.
- Keep templates clean: if you regularly reuse a contract template, always attach it with template-style phrasing so the original is never consumed.
Frequently asked questions
What file types can I attach to GitLaw chat?
DOCX, PDF, MD and HTML files. The attached file is added to your GitLaw files once you send the message.
Will attaching a file overwrite my original?
Not by itself. Reference-style prompts leave the original untouched. Edit-style prompts modify the file but preserve the original as version 1 in version history. Template-style prompts create a copy and leave the original reusable.
Related articles
Reviewed by the GitLaw team. Last updated 29 July 2026.