Files shared in chat
Press + in the message box to add files to a message in the mission dialogue. The files are kept with the mission, every member of the mission can download them, and Cora can read them when it works on the mission.
The examples on this page follow an invented café chain, Larkspur Coffee. Its marketing team is running a spring social campaign for a new iced drink.
The rules
Section titled “The rules”- Kept with the mission. A shared file stays with the mission’s messages for as long as they are kept. It shows as a chip on its message and is listed under Shared in messages in the Artifacts tab of mission details, after the mission’s documents, with who shared it, when and its size (D0548, D0566).
- Only sent files are kept. A file you add but never send with a message is not listed in mission details. About a day after you added it, it is deleted, together with the mission’s copy (D0581).
- Deleted with their message or mission. When a message or a whole mission is deleted, its shared files are deleted from storage first, and only then is the message or mission removed. If a file cannot be deleted, the message or mission stays until a retry succeeds. Only the background sweep may delete these files; the API cannot (D0145, D0579, D0603).
- Seen only by the mission’s members. Only members of the mission can see or download a shared file, and only Cora’s work on that mission can read it. A file shared in one mission is never shown in another mission or on the organisation-wide Artifacts page (D0566, D0853).
- Limits. Up to 5 files a message, each up to 25 MB, of seven types: PDF, Word (.docx), plain text, Markdown, CSV, PNG and JPEG. The type is checked from the file’s own first bytes, not just its name. See upload types and limits (D0548).
- Not scanned for malware. In this version, shared files are not scanned for malware. A file is available as soon as its upload finishes and passes the type and size checks (D0562).
- Served only as downloads. Every file is served only as downloads, through a short-lived link, and is never opened in the console. Images are not previewed. Your browser saves the file, and you open it with your own software (D0562).
- Cora can read it. When a message names a file, Cora can read it while working on the mission: the text of a document, or one image. Reading a file counts toward the organisation’s spend cap like any of Cora’s work (D0550).
Why there is no malware scan yet
Section titled “Why there is no malware scan yet”Scanning every file needs a service turned on in the cloud account Cora AI runs in, and that was not chosen for this version. The risk is that an infected file could be shared. It is kept small: files are seen only by the members of one mission, the type is checked on the server, and a file is only ever downloaded, never opened inside the console. Scanning will be looked at again before Cora AI takes paying customers (D0562).
So treat a shared file as you would an email attachment from a colleague: open it only if you expect it.
What it looks like
Section titled “What it looks like”Megan adds last month’s social media report as a PDF and posts “@Cora here is March’s report; what worked best?” The file shows as a chip on her message. Priya, who is in the mission, downloads it from the chip. Cora reads the report and replies in the dialogue with the three posts that did best.
What shared files are not
Section titled “What shared files are not”Shared files are reference material for the mission. They are not Cora’s documents: Cora writes its own documents, such as the full objectives or a status report, and those are kept separately and listed under Documents in Artifacts. Cora does not change a file someone shared (D0002, D0566).
Coming later
Section titled “Coming later”- Cora turning what is inside a file into the mission’s own notes, and translation, in Phase 2.
- A malware scan, before paying customers.
Decisions
Section titled “Decisions”- D0548: the + button, up to 5 files a message, 25 MB each, of D0089’s seven types, kept with the mission. This replaces D0014, under which uploads were read and then deleted.
- D0562: shared files are not scanned for malware in this version; they are served only as downloads.
- D0581: files never sent are not listed and are deleted after a day.
- D0145, D0579: shared files are deleted when their message or mission is deleted.
- D0566: shared files stay on their message and in mission details (Shared in messages), not on the organisation’s Artifacts page (Files until D0853).
- D0550: how Cora reads a shared file.
- D0002: only the API writes the mission’s documents.
- D0017: this page is published before file sharing is turned on.