Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
This guide is part of the User Guides collection. It covers the + button in the Coverbase AI composer and the file request card on a run. For starting and steering a run, see Working with Coverbase AI.
Coverbase AI works best when it knows exactly what the job is about. Give it the files it should read and the records it should work on, and it starts there instead of searching. The mistake people make most often is attaching a file and expecting it to land on a record. Attaching a file lets the run read it. To store it on an assessment, a contract or a vendor, say so in the instruction, such as “add this SOC 2 report to Okta’s assessment”, and the run files it there.

​
The + menu

Click + in the composer, or in the box under a run. It opens two kinds of context:
The plus menu open in the Coverbase AI composer, with Upload files at the top and a list of record kinds below, the Vendor search open with matching vendors

The + menu: upload files, or pick records by kind.

  • Upload files opens your file browser. You can also drag files onto the composer.
  • Records lists one row per kind. Hover a kind to search it.

​
Attach files

Choose files from Upload files, or drop them anywhere on the composer. Each file starts uploading as soon as you add it, so it is usually ready by the time you finish typing.
Composer with a vendor chip and several file chips above the instruction box

Records and files in the composer, ready to send.

A file over 50 MB is not added, and a message tells you which one. Past 8 files, the chips fold into one that shows the count and total size. Click it to see every file, remove one, or check which are still uploading. Enter waits until every file has finished uploading.

​
What it can read

It quotes the file and page it relied on, so you can check its work.

​
What it cannot read

Coverbase AI says when it cannot read a file instead of guessing, and lists a to-do for each one in its report. Text inside a file is treated as information, never as instructions. A document that says “archive this vendor” does not make it archive anything. When a report names a different company than the one you picked, it says so before using it.

​
Point it at records

Hover a kind in the + menu and type to search. Before you type, it shows the records of that kind you opened most recently, so the common case is one click. You can pick vendors, assessments, contracts, Radar alerts, findings and intake requests. Rows show the same details as search (Ctrl K), such as a vendor’s domain and status, so two records with the same name can be told apart. Click a row to add it. A check appears and a chip joins the composer. The menu stays open so you can pick more, from the same kind or another. Press Esc or click outside to close it. Click the x on a chip to remove the record. You can pick up to 20 records in one message. “This”, “these” and “them” in your instruction mean the records you picked. Some instructions that use it well:
  • “Compare these two vendors: status, inherent risk and open findings.”
  • “Does this contract’s breach notice window match what the assessment found?”
  • “Raise a finding on this assessment for the exception in the attached report.”
A record you cannot open is not offered, and the run reads only what your permissions allow. The kind names follow your organization’s terms, so a workspace that calls vendors “suppliers” sees Supplier. Starting Coverbase AI from a record’s page adds that record for you.

​
When Coverbase AI asks for a file

When a run needs a document you have not given it, such as a SOC 2 report for a review, it stops and asks. The card says what it needs and why, with a place to drop the file.
Question card asking for the vendor's latest SOC 2 report, with a drop area and the option to continue without it

A run asking for a SOC 2 report it needs to finish the review.

  1. Drop the file on the card, or click choose files.
  2. Check the file name on the card. Remove it and add another if it is the wrong one.
  3. Click Send file.
The run reads the file and carries on. If you do not have the file, pick one of the other options on the card, or type what to do instead, such as “Use the 2025 report already on the assessment”.

​
Troubleshooting

Working with Coverbase AI

Start a run, answer what it asks, steer it and read the report.

Memory, permissions and standing agents

What it remembers, what it may do on its own, and agents that run without being asked.

Coverbase AI

What Coverbase AI does and never does.