Files
Use files as Agent inputs, evidence and outputs, and understand where session files fit relative to durable Project knowledge.
Files can be part of the work going into a session or the concrete output coming back from it.
The Agent can read supported files, extract and compare information, transform data and create new files as the result of a task.
Add files where the work happens
Attach relevant material in the session and describe the outcome you need.
Point to the relevant page, sheet, columns or section when that helps narrow the task.
Files can play different roles
A file may be:
Input — material the Agent needs to process;
Evidence — material used to establish or verify what happened;
Output — a file created as the result of the work.
The role matters when sources disagree. An uploaded spreadsheet may be useful evidence without outranking the current ERP record.
Inspect generated files
When the Agent creates files, the session's Files area gives you a dedicated place to open them.
For important work, inspect the actual output rather than relying only on the Agent's summary. Check the rows, values, formulas, document sections or other result that matters.
Inline results and HTML artefacts
Not every result needs to become a separate file.
Compact HTML summaries can appear directly in the conversation as in-stream widgets. Richer outputs with more space or interaction—such as multi-section reports, tabs or dashboard-like views—can be created as HTML artefacts and opened in Lleverage's sandboxed preview.
Session files are not automatically maintained knowledge
A file appearing in a session does not automatically become maintained Project knowledge or a governed source of truth.
If information should be reusable across future work, move it into the appropriate maintained Project surface, such as Knowledge, a Table, Project Files, a Skill or the underlying business system.
If a required file is missing, the Agent should ask for it rather than inventing the absent evidence.
Last updated
Was this helpful?