Troubleshoot file links
What happens when a chat links to a file that has not reached the Vault.
A document created in the Desktop workspace must be saved to the Vault before you can download it from a chat. At the end of a chat response, Corint checks file links in that chat's Vault folder.
If the linked file is missing, Corint first checks the matching workspace path. It can also recover a file with a matching or similar name when the workspace search identifies one candidate. Automatic recovery applies to files up to 100 MiB and preserves files already stored at the destination. It excludes build dependencies, temporary files, and paths outside the current chat.
When a link is missing, malformed, or has several possible matches, Corint gets one correction attempt for the running chat job, including any follow-up messages you send while it is working. The corrected answer replaces the earlier answer. It may point to a verified file or explain that the requested file was not produced. Unsupported file or folder names may also require a corrected link.
Recovery does not guarantee that every file link works. A failed sandbox check, an incomplete search, or an upload problem can prevent recovery. If a link still fails, ask Corint to verify the file, save it in the chat's Vault folder, and send a fresh link. You can also inspect the Desktop workspace to see whether the document was created.